The only slop worth using is slop you make for yourself.
Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
That is so accurate. I have a couple of LLM-coded applications running, either because a solution wasn't available, or existing solutions were beyond the scope of what I need, and would idle at up to 1 GB of RAM instead of 10 MB. In situations like these, being able to get a quick solution thrown together is such a boon.
Can confirm, am running a lot of services on a VPS that make my life more convenient. I prompt from my phone and get useful stuff out. I am a software engineer, so I can course correct ir when necessary. I only use opencode for this, not Hermes or Openclaw
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| Git | Popular version control system, primarily for code |
| IoT | Internet of Things for device controllers |
| VPS | Virtual Private Server (opposed to shared hosting) |
[Thread #47 for this comm, first seen 8th Jul 2026, 14:40] [FAQ] [Full list] [Contact] [Source code]
As Linus Torvalds said, give the compiler some credit.
This is the main reason why vibe coding, even if it produces good code, is still a major problem. It encourages people with the goal of making software, but without the actual will and motivation to keep supporting that software to pump out software and publish it.
It's like all the faceless AI-automated YouTube channels we have now. It's not that these people had no way of doing it before, it's just that it's easy and might make them some money, or make them feel like they accomplished something until they get bored and move on.
There's something to be said for convenient and easy to use things, but they're a double edged sword, because they also directly target people with the least emotional investment to use them, as a side effect of that convenience.
On the flip side, if you’re vibe coding an app you should seriously consider whether it’s something you want to open source or make available publicly. There’s a social contract that comes with that.
I have 2 self hosted slop apps I build and maintain myself. I think people would genuinely get great use out of them.
…but then I’m inviting critiques and feature requests and am roped into supporting them so it’s not just a big pile of shit that wastes everyone’s time. And I don’t want to spend my limited free time making common sense improvements to improve it for others. I want to write a lazy Claude prompt with insufficient context, get it barely doing what I need, and then spend the rest of my time eating crayons and similar pastimes.
If someone isn't motivated enough to actually think and create something, what makes you think they'll be motivated enough to maintain that thing they didn't create?
Vaporware is never not a thing.
I thought vaporware was announced or promised code that never materializes, or shows up much later than claimed. Often used by big companies to squash competition, who typically have very real solutions available.
That's one example, yes. My point is we like to invent new ways to call out the same shit. Vibe coded projects that get abandoned within half a year are just another example of vaporware, just a new take on the concept.
I made the mistake of installing Starling recently, not realizing how it was made. I contributed a PR to it, wrote a few issues describing some showstopping bugs, and since then there's been absolutely no activity from the creator.
That's fine, they are under no obligation to work for free. But I wouldn't have installed it if I knew it was abandonware.
We went from “everyone will know how to code in the future” to “no one know will know how to code” pretty quickly
Everybody did think becoming a developer is where it was at, so a lot of people did, now these people looking at an ever tightening job market (even before AI) with LLM's possibility annihilating the need for their expertise entirely at some point.
At least maybe people will stop telling other people what to do. It's obvious we don't know what is relevant next week, much less in 10 years.
All these people that are now told to school themselves for manual labour are being set up to run into the same thing. Especially when those chineese bots inevitably also escape the gadget level.
There are no "AI safe" jobs. Even if it can't do your job (yet) all the people that are made redundant and need new work will be flooding remaining markets.