Self-Host Weekly (2026-03-13)

#Booklore turns sour, software updates and launches, a spotlight on #OpenDroneLog -- a #drone flight log app, and more in this week's #selfhosted recap!

https://selfh.st/weekly/2026-03-13

#selfhost #selfhosting #foss #opensource #homelab #devops #sysadmin #newsletter #privacy #security #fediverse #app #apps #smarthome #truenas #ntfy

Self-Host Weekly (13 March 2026)

Searching for the next "claw", Booklore goes nuclear, and sourdough starters

selfh.st

@shollyethan it’s really a sad time with all the witch hunt around who use AI to develop their own app in an open source application they are not forced to use

As a dev I build project for my personal use with AI in days instead of month to solve problems I have, they are publicly available if someone stumble upon them, and they are definitely not perfect but they exist. Without AI ? They probably would have never existed

Alright enough rambling for today and thanks for the newsletter

@azsiaz @shollyethan I think that's a really weird take on the nature of popular open source projects. Booklore has nearly 100 different contributors. This is an active and engaged community of people making something where one person has suddenly started making decisions that others disagree with.

No one is coming after you for your projects.
@alex @azsiaz @shollyethan I think the undertone of what he is saying is still true. If you use AI “we” will disregard your project as slop and not project that maybe useful to you. In this case it feels like you said one person thing.

@train @alex @azsiaz @shollyethan

Maybe you haven't heard, but there are some big issues with vibe coded open source projects.

https://www.reddit.com/r/selfhosted/comments/1rckopd/huntarr_your_passwords_and_your_entire_arr_stacks/

This is as bad as it gets. I have zero trust in people vibe coding their projects, because I doubt that 90% of them will check the source code it has written in such a detail to catch (and fix!) critical issues like this.

[1/?]

@train @alex @azsiaz @shollyethan

selfhosted was already getting crowded with new projects, now with "AI" there are many more people programming their stuff once over a few days or a week, opening it up to the public, gaining a lot of followers and community and then moving on from their project after a month (or even less).

The only solution for me is to avoid such projects:
If the person isn't willing to write their own code, they will not check for critical issues and maintain it for long.

@Anachron @train @alex @shollyethan Of course there is issue, there is always a ton of issue with technology, never was it the fault of said technology itself but the decision of the person behind. Doesn’t mean he should be treated like this either, for the Huntarr, Booklore or anyone else for that matter

And people tend to forget but those kind of issue totally happen on project fully human made too, even if less frequently

@azsiaz @Anachron @alex @shollyethan . It still feels like scapegoating "I don't trust people / projects who vibe code".. Why would you trust people who don't "vibe code". You are making broad assumptions on both fronts. Slop is slop no matter who writes the code. If you don't think about what you are trying to build you will not build correctly. We as a industry/hobby are just not thinking about it and just doing, and then things blow up. Most of these " Look at what he did" developer stories you find could probably ( maybe even easily) handled by a conversation rather than trying to tear down the whole thing publicly because a AI built it some if not all of it. Of course people are people and we can be unreasonable but that's not a tech discussion.

@train @azsiaz @alex @shollyethan exactly! Its hard enough for me to trust people without vibe coding already.

With this technology it becomes increasingly harder.

If you dont have the time to write it correctly yourself, you will not have the time to review the LLM doing it for you.

All I hear is "please dont blame vibe coders, its so unfair!" but nobody actually has given me any solid reason on why not to.

Saying "non-vibe-coded" projects can be bad too just aint cut it.

@alex @shollyethan Sorry I should have been more explicit, the witch hunt itself is the issue.

And 100 contributors or not it’s his project and he is the one in control of his project for better or for worse for those who contributed real time to a project. And it’s the beauty of it, nothing is preventing them to fork, I am sure a lot of people would be happy to switch to it