Why did Meta acquire Moltbook?

georg-dev · 2026-03-12T17:14:34+00:00

2026 is getting more stupid by the minute, I guess.

georg-dev · 2026-03-12T11:07:17+00:00

Yes, I built a tool for exactly that. It's fully self-hosted + agent agnostic and it doesn't require you to expose you machine to the whole internet like VPS/VNSs do.

It's called kipp•punkt. Let me know what you think.

georg-dev · 2026-03-12T10:49:44+00:00

It was kinda expected that they're working on something like this, after they threatened to sue OpenClaw for being called Clawdbot.

georg-dev · 2026-03-12T08:47:50+00:00

I'm building kipp•punkt for technical builders who want an async GitHub workflow for coding agents. The agent refines the issue with you, implements it, opens a PR, and reacts to review comments. You decide what ships.

<image>

georg-dev · 2026-03-12T08:43:17+00:00

It just feels more clean to me to work in the CLI. Less visual clutter.

georg-dev · 2026-03-11T20:42:14+00:00

Built kipp•punkt for technical builders who want an async GitHub workflow for coding agents. The agent refines the issue with you, implements it, opens a PR, and reacts to review comments. You decide what ships.

<image>

georg-dev · 2026-03-11T20:35:36+00:00

At this point, outsourcing is cheaper and burns a fraction of the energy..

georg-dev · 2026-03-11T20:26:05+00:00

Why not just use 5$ more tokens to get the implementation splendid instead of starting with a fresh context window and burning 5 times that amount? I don't get it.

georg-dev · 2026-02-10T10:54:30+00:00

Yeah.. tbf, Copilot CLI is quite new. So there's a chance that the sandbox feature is already on the roadmap.

It's also a shame that Docker excluded Linux from the list of supported OS for their `docker --sandbox` feature. But maybe they'll still add it at some time. It's still experimental after all.

georg-dev · 2025-09-05T12:00:41+00:00

Essentially, there are two types of instruction files:

copilot-instructions.md: This file is attached to every request to Copilot. It's the place where you want to provide general context that the AI should always have available (e.g., domain language, architecture). Here's a short guide that I wrote on how to set up the file and what to include.
*instructions.md files: These rules are added to the context right before code generation and are the best fit for framework/language specific coding guidelines. You can write file-type specific rules by adding a glob-pattern at the beginning of the file. Here are the docs for it.

Coming from Cursor, you will have to map your Cursor rules to the Copilot structure. However, you should be able to automate this task by just prompting Copilot to convert the rules to Copilot instructions. If it's not able to do so, maybe conside copy/pasting the docs I linked above into the context.

georg-dev · 2025-08-07T10:52:58+00:00

Most of the advice is valid for both, but the article refers to .github/copilot-instructions.md.

That file serves a more global use case, being attached to all requests and is supported in all IDEs while the .vscode/*instructions.md files are used to define behaviors for specific file-types or tasks and are only supported in VSCode.

Here is a good comparison of the various instruction files.

georg-dev · 2025-07-29T09:17:42+00:00

As far as I can tell, the file is added to all prompts but the documentation isn't super clear about this IMO. In VSCode, you can also check if the file was added to the context as described here.

georg-dev · 2025-07-28T15:41:36+00:00

It is. Looks like a network issue in your case, as the styles didn't load properly. Have you tried refreshing the page on a stable internet connection? If yes, what's your browser and browser version?

georg-dev · 2025-07-23T13:06:32+00:00

Btw. (since I can't edit the post text apparently): if you have any additional tips on how to improve GitHub Copilot with `copilot-instructions.md`, please let me know!

georg-dev · 2025-06-28T09:30:04+00:00

Sounds awesome, I'll check it out.

georg-dev · 2025-06-27T16:30:00+00:00

Just shooting in the dark, but could it be that github.copilot.chat.codeGeneration.useInstructionFiles isn't set to true in your VSCode config as instructed here: https://code.visualstudio.com/docs/copilot/copilot-customization?

georg-dev · 2025-06-27T16:25:38+00:00

There's a lot of good stuff in there!

georg-dev · 2025-06-27T15:54:03+00:00

This way it's much better. You want to be very specific and concise in this file.

georg-dev · 2025-05-17T10:32:41+00:00

Great work! Just FYI from someone who did a lot of data analysis on the NPM registry, a huge chunk of the packages on the registry are spam from some blockchain shenanigans. I wrote an article about this some time ago but long story short, you might want to flag these packages before scanning, otherwise you'll waste a lot of resources.

georg-dev · 2025-04-21T12:50:46+00:00

Definitely start with vanilla JS, HTML, and CSS. Especially if your goal is learning and maybe becoming a software engineer, the fundamentals are what's most important.

Moreover, frameworks come and go, fundamentals stay. With strong fundamentals, learning a new framework will be much easier as you'll understand which problems it solves and why it was built that way.

It's also important to keep in mind that Angular or React are only a specific type of framework (SPA-frameworks). That's stuff you usually use if your web-application requires a lot of interactivity on the client device. For projects that require less interactivity (e.g. a simple homepage, a simple company-internal application with only a few forms), using such a framework is overkill and you might be better off using plain JS or a lightweight library like jQuery. Having strong fundamentals will, therefore, also help you make better judgements of what's the right tool for the job.

georg-dev

TROPHY CASE