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: 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.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
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!
view the rest of the comments
From a quick glance at the repo?
The commits generally come hot and heavy. Going back to the earlier 2025 commits and the messages mostly look like what you would expect from folk raw dogging
main. Arrdalan in particular looks "real"-ish. Whereas jkaczman is already showing signs of the kinds of commit messages that claude et al generate, but those ARE based off certain style guides.Roll up to 2026 and I can see 11 commits on May 17 alone, they all look like claude messages, some are outright just arbitrarily changing magic hashes, and there are little to no comments.
Not gonna fully call this ai slop but, it is REAL flipping sus as it were. At best, this is enthusiast code without proper engineering and is immensely unmaintainable. Use at your own risk.
Those 11 commits were from a rebase-and-merge PR, which changes the date from the original commit. Notice how there's a week gap between those and the prior commits on the main branch.
The only thing AI is used on in this project is strictly for user interface work (our website, the front-end for the mobile app, the front-end for the deploy tool). We carefully vet anything like that.
Fair enough. I'll still say that is bad engineering but acknowledge that starts to get into the realm of taste.
Either way, in the past 24 days you have MR commits on 8 of those and April looks similar. The code is generally poorly documented and skimming the closed MRs, I am not seeing much discussion or review in any of them. So I stand by
Fair points. I appreciate the constructive criticism! Moving forward, we will improve on our documentation. In terms of review, we always review and test each other's code (sometimes via other mode of communication), even if there weren't any comments on the pull request.
What an amazing conclusion, and the best part is, no matter what you've been waffling about before - it's always right. Can we stop calling random things AI slop and telling to be careful bEcAuSe iTs Ai sLoP, and go back to being cautious until something has been reviewed properly? Being careful with random stuff from GitHub you install and run in your private network?
Your whole comment may have been AI slop as well. "From a quick glance at the repo", you should be careful! Thanks, Sherlock.