I have started a new project to make a blog system. I'm not exactly a prolific blogger, but for many years have been using Bludit for that. Recently it came to my attention that Bludit was starting to accept slop pull requests. Reading slop code is inadvisable for your mental health, but of course I did it anyway and I noticed questionable stuff going on which could create security problems.

So what to do? I could have put in a bug report, but I thought if the project is willing to waive through slop then it's probably time to part ways. I could find another blogging system - of which there are many - but at this juncture in the software industry hellscape I just don't trust other developers not to suddenly ditch "best practices" and start vibe coding (or "slop prompting" seems to be becoming the more accepted terminology). It's a sorry state of affairs. Some of the narratives being produced by developers who in past times I held a higher opinion of indicates that "AI psychosis" is really becoming a genuine problem. The old aphorism still holds true: garbage in, garbage out.

The new blog system is going to use some of the functions already developed in Epicyon, but it will be a far simpler project than Epicyon is. It will be written in Python, have no javascript, support tor/i2p/yggdrasil, have no database (just markdown files), and support multiple languages and themes. No database means no database injections. It will also scrub any metadata from uploaded media, have low bandwidth capability, and support text mode browsers. I will try to keep the dependencies minimal. It also definitely won't be vibe coded and I won't be accepting any LLM pull requests.