waybarrios/vllm-mlx: OpenAI and Anthropic compatible server for Apple Silicon. I use this to run mlx-community/gemma-3-12b-it-4bit on my MacBook Air. It works very well, a small shell script to start the server and then I am autonomous. Not as comfortable as Ollama, but it perfectly supports Apple's MLX and thus makes good use of Silicon.
Archive 2026
mlx-community/gemma-3-12b-it-4bit · Hugging Face is currently the best model for local operation, allowing me to implement image captioning and even local chat. It's not the fastest, as it's quite large, but it's absolutely suitable for offline operation if I come up with a few mechanisms for batch processing of images, etc. This could be super exciting for vacation times. An image description might take a minute, but hey, no dependencies.
Models.dev — An open-source database of AI models is a very practical site that provides framework parameters for all kinds of providers and all kinds of LLMs, including even API prices. And technical parameters such as input/output tokens.
Ollama - a runtime environment for LLMs that allows models to be run locally. My favorite model at the moment: qwen2.5vl:7b-q4_K_M. With only 6.6 GB in size, this runs smoothly on a MacBook Air M4 and still has enough memory and capacity to run programs alongside it. The model is surprisingly usable in chat and above all has excellent vision capabilities. Ideal for providing titles, alt text, or summaries for images without having to pay big providers for it. And an important building block to bring bDS back to full-offline.
mistralai/mistral-vibe: Minimal CLI coding agent by Mistral - accompanying the AI Studio - Mistral AI there is also the Vibe coding interface to Devstral as open source. Very nice, because it makes a good pair. Will definitely try it out, even if I will probably rather reach for the powerhouses (Opus 4.6) for larger projects.
AI Studio - Mistral AI - as the situation in the USA becomes a bit more tense again, and simply because one should always check what is happening outside the USA, here is a link to a European alternative to the major US operators. Mistral offers a coding model with Mistral 2 that is not only open weights (i.e., freely available and operable if you have the necessary hardware), but also quite affordable when using Mistral itself. And the performance is slightly above Claude Haiku 4.5, and below Sonnet 4.5, but not by much. So quite usable and my first experiments were not bad. Unfortunately, no vision capability, so not very suitable for experiments with images (and therefore not ideal for my bDS), but still interesting enough to keep an eye on.
ZK I Zettel 1 (1) - Niklas Luhmann-Archiv - where the inspiration for my blog comes from, or what has always driven me beneath the technical surface.
If you, like me, want an overview of UI integration for LLMs and are wondering how A2UI and MCP Apps compare and what they offer: Agent UI Standards Multiply: MCP Apps and Google’s A2UI - Richard MacManus helps. I have implemented A2UI in bDS so that the LLM can also use visual aspects in the internal chat, and I really like that. But the idea of incorporating parts of my UI into external agents is also fascinating. Even if I find that "local HTML/JS in an IFrame" somehow sounds like a hack at first, but much in the LLM environment gives me the feeling right now, simply because everything is pushed through a normal text stream and you hope that the LLMs adhere to the formats (even A2UI works like this).
cloudflare/cobweb: COBOL to WebAssembly compiler - I'll just leave this here. Let someone else clean up the old stuff. what else can you say.
Pyodide is a bit of a lifesaver for me in bDS: I must admit, I'm not really super deep into TypeScript and I actually don't feel like writing it myself. If the AI does it, that's okay, there's enough knowledge for an LLM to draw on, but I don't really want to delve deep into it myself. And Python has been one of my favorite languages for a long time. And Pyodide offers exactly that: a port of CPython to WebAssembly. It provides a pleasant language for scripts and macros that can access everything the application does and - if I ever want to - can also load Python libraries.
Drizzle ORM - was suggested by AI during the construction of bDS and has proven to be very reliable. A clean ORM for TypeScript with a quite nice API that strongly reminds me of Django. Additionally, clean mapping of migrations, which then simply allow SQL, thus enabling more complex migrations. And so far completely unobtrusive in operation. What is particularly interesting: there is a direct translation to GraphQL, so that the objects can also be exposed to an API, which I think I should take a look at (or rather, I should complain to the AI that it should take a look at it). I am always a fan of flexible standard integrations to connect external tools.
A2UI is an interesting project for a streaming-oriented protocol for applications with LLM integration. The basic idea is streaming JSON snippets from which the UI is then incrementally built, and the LLM controls what goes into the UI. It allows the LLM to produce more than just simple textual descriptions or basic ASCII graphics and also gives LLM queries a different look. The whole thing comes from Google and is maintained on an open github project. In bDS, I have also integrated it, and it's quite something when you can get a heatmap of the distribution of your blog posts across the months.
Waggle Dance . oldie, but goldie. Always fun how this rather simple game can captivate people, even over 10 years after its release.
OpenCode | The Open-Source AI Coding Agent - an open-source coding agent that could soon outperform Claude Code. Very good in execution and above all provider-agnostic. You can attach any model, even one self-hosted with LM Studio or ollama. If you just want to play around, you can simply download it and get started, even without providing a credit card (then of course with limited tokens, but quite usable for initial experiments. And independent of the major providers (ok, except for their models if you want to use them - and for serious coding, those are unfortunately still necessary). OpenCode also offers its own AI models, which are then billed, but a few models are always freely available and thus offer quite serious experimentation without investment.
Steve Yegge on Vibe Coding
Steve Yegge talks in the interview about the future of programming and the challenges of vibe coding. The author shares his experiences and sees a upheaval comparable to the introduction of high-level languages.
bDS slowly usable
Now the new software is starting to be fun, everything you need for usage and creation is largely present. It still has a few minor flaws and there are one or two features I want, but I can already do everything I really need as a minimum. Publishing now works easily with a shell script:
#!/bin/sh
cd ~/Blogs/rfc1437.de/html
rsync -rav --delete \
--exclude='thumbnails/' \
--exclude='media/' \
* git.rfc1437.de:git-server/html/
cd ..
rsync -rav --delete thumbnails/ git.rfc1437.de:git-server/html/thumbnails/
rsync -rav --exclude='*.meta' --delete media/ git.rfc1437.de:git-server/html/media/
Yes, that was just to test my source formatting. And?
Big Damn Stupid - no, Blogging Desktop Server. Currently my favorite project where I play around with Vibe-Coding and build software with which I can run the blog. But this time with the clear perspective that I won't succumb to bit rot or the complexity spiral again. Simple software with a usable interface for maintaining blog posts, but storage as Markdown files with YAML front matter to be easily stable for the future. Then with sqlite for caching and full-text search and other comfort features and git for synchronizing the blog data, and git-lfs for the images. Feels quite usable right now.