Folks, we’ve received your reports. On the surface, it seems like a good faith attempt to start a discussion. This user isn’t breaking any rules. Please use your votes to determine the fate of their posts.
this post was submitted on 14 Nov 2025
-57 points (13.0% liked)
Selfhosted
53034 readers
857 users here now
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: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
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!
founded 2 years ago
MODERATORS
ew, botposting
Is it? How do you know?
It's hard to say exactly, it's like noticing when something is CGI in a movie. It's just kind of off.
The first few sentences gives it away for me. There's also the filler words.
Also the way it rephrases the sentences. You have:
there's always that one piece of software, that one perfectly tuned instance, where if it so much as hiccuped, you'd be ready to throw the entire homelab
Then again:
what's your absolute, non-negotiable, 'i will personally visit the datacenter if this fails' self-hosted application
It's also possible they just write like a bot.
I'll add that it's a multiple of parts (see this video), not just one factor that gives it away. But for me the most telling one is that the text looks like the author spent a lot of time thinking about what figures of speech to use but at the same time did not use capital letters. The prompt clearly included something like "don't use capital letters to make it look more casual". But the LLM forgot to make the semantics look casual.
It’s also possible they just write like a bot.
Unlikely but if it were true, it would not change a thing. For me it does not matter who wrote the slop. It's crap writing regardless and I don't want to see that on the internet.
Btw from the video we can see the "rule of 3 pattern" which was used in this post:
what’s your absolute, non-negotiable, ‘i will personally visit the datacenter if this fails’ self-hosted application
Also I think the greeting "alright folks, let’s get real" is a gipitism.
what’s your absolute, non-negotiable, ‘i will personally visit the datacenter if this fails’ self-hosted application
Here you missed that this sentence makes no sense in a selfhosted context. What datacenter??? I honestly don't know how can anyone doubt the elelemcy here.
Thanks for the warning. To the blocklist it goes.
Seconding the request for details - how do you know?
Well the only way my media server goes down is if the power is out for more than a few hours or my internet connection is down.
So I'd have to say that.
I don't believe you, but I'd like to be proven wrong.
I expect you have a UPS that feeds your hosts and networking equipment and something like ZFS for disk redundancy. This protects against the most common failures and is usually enough, but there are still single points of failure in such a setup, that are not as common, not as hard to deal with through manual intervention, and quite difficult to protect with redundancy.
I would be surprised if you are protected against the following single points of failure without manual intervention:
- NAS machine (not just disk) failure. You would need to have a multi-node distributed storage, like Ceph, to protect against this.
- Networking equipment failure. I think you can do some magic with BGP to do this, but I'm not a network engineer and I've never set up a redundant network.
Ceph for the proxmox cluster, 2x48 port switch + 16 port 10gbit as the core, 2xNAS (technically one is the backup, and there would be a few moments of downtime as the containers restart - a different container with the same config pointed to the backup NAS instead).
UPS and internet are the SPoF.
Impressive!
If you have a self hosted system and you throw the whole thing away because one service breaks you probably shouldn't be hosting because you learnt nothing during the process
Even Email can be down for two days or so without major consequences, and I could pull that up from backups on a spare server in another location within an hour max.