this post was submitted on 13 Mar 2026
108 points (97.4% liked)

Selfhosted

58044 readers
1254 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
top 22 comments
sorted by: hot top controversial new old
[–] eodur@piefed.social 29 points 2 weeks ago (5 children)

The BookLore thing is really disappointing. I hope we see a quality fork in the near future.

[–] KairuByte@lemmy.dbzer0.com 13 points 2 weeks ago (1 children)

Just read through some of the BookLore stuff and that was a wild ride.

[–] bobslaede@feddit.dk 7 points 2 weeks ago

Yeah... I will not be updating my instance for a while. Will probably start looking for something else.
Wild ride...

After reading both the accusations and the dev response I don't know who to believe. I love BookLore and have not encountered any issues, so I guess I'll stick with it for now.

[–] irmadlad@lemmy.world 5 points 2 weeks ago

BookLore

I have seriously considered spinning up Booklore. Great looking UI. Oh well.

[–] EarMaster@lemmy.world 3 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

I'd rather have a happy and productive maintainer than a burnout and an orphaned project. Either way forks can be made at any point - so if you don't like the use of AI just fork it or don't update any more and stay happy. No need to get mad at each other.

[–] iamthetot@piefed.ca 4 points 2 weeks ago

They said they were disappointed, not mad.

[–] tofu@lemmy.nocturnal.garden 2 points 2 weeks ago (1 children)

I'm not sure a fork makes sense given the dev merged way too much nonsense already. Maybe from a point in time before it started?

I've been looking to check out Booklore over some annoyances I have with CWA but IDK anymore.

[–] panda_abyss@lemmy.ca 1 points 2 weeks ago (1 children)

Don’t let perfect stop you from achieving good.

It’s not radioactive waste, it’s code. You can read it, write it, change it. Just like any legacy codebase it’s full of shit, and maintaining means addressing the specific issues.

[–] Zos_Kia@jlai.lu 0 points 2 weeks ago (1 children)

This whole debacle is showing that people fundamentally misunderstand how code works. They are trying to declare code good or code bad because of some silly heuristics like ai/not-ai, as if it wasn't literal lines of text which you can read before you form an opinion and make a fool of yourself.

[–] panda_abyss@lemmy.ca 1 points 2 weeks ago (1 children)

Good code has always been about simplicity, taste, and understanding.

If a human provides understanding and taste, they can elevate AI code to be good.

Likewise if an AI isn't well guided it won't understand, has no taste, and will generate overly complex code. AKA Slop.

[–] Zos_Kia@jlai.lu 2 points 2 weeks ago

Exactly. And a commit is a commit. Unless it's 10Kloc in one go you can just read what's in it and decide for yourself.

At my previous job we used to jokingly (?) tell our engineering manager "no commits, no opinions" well I think it's kinda like that.

[–] IanTwenty@piefed.social 14 points 2 weeks ago

Hello

Somebody developed a Home Assistant integration for monitoring and managing sourdough starters

[–] panda_abyss@lemmy.ca 10 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

It feels like there's a meta-discussion to be had about AI disclosure and AI use in a lot of these projects and it's starting to boil over.

I would suggest that maintainers should:

  • Add an AI disclosure in their readme, which is what I do on my projects. If you don't like AI then it's on the tin and you can avoid it -- explicit is always better than implicit.
  • Provide guidelines on AI contributions to their project. Every project needs an AI contribution policy now because we live in a world where most devs do use AI code gen. If you accept a patch from a community user it's probably been touched by AI.
  • Detail their AI workflow, but specifically how they review this code. I can only really work and review at a file-at-a-time pace so that 100% of AI code is reviewed by me, in detail, and it's up to my standards.

When it comes to existing projects that start adding AI contributions it's always going to be difficult. It's not something projects started with even the option of, there's no way to get consent from your users (nor consensus on whether you should you get their consent), and there have been varying levels of AI code gen for years now from simple completions to now agentic vibe coding.

I'll be honest, most of my own projects use AI generated code, and I use it for work. It's never code I couldn't have written myself -- because if it were how could I review it? But the fact is, in the year 2026 AI code generation is both fast, usable, and it's near ubiquitous. There are tasks I could work on for weeks that I can build plus review in a couple of hours with AI. It's very hard to argue with that, and I'm a very picky coder+reviewer with a full time job.

And lastly, for the community we all need to be mindful of open source maintainers.

They work hard, for free, and get treated like shit by users, the law, and big corporations. There's a new generation of people who sign up for code hosting services just to request features or complain in your git issues, they're opening up slop PRs and emailing you. Plus, internet users love to pile on and harass people.

Please remember there's (usually) a human made of meat at the end of the intertubes, and when 100s of people write mean/abrasive things it adds up. Nobody is perfect, open source devs are just trying to share and help.


PS for mods: I saw there was another thread on another app using AI that was locked as off topic, I am trying to be constructive in this comment, but if it's off topic/too divisive I understand.

[–] Zos_Kia@jlai.lu -1 points 2 weeks ago (1 children)

I think disclosure is good and should be tackled as soon as possible because being transparent in your communication is just good practice in general.

However I feel like this will soon be rendered useless as all projects will move to agentic (or otherwise ai-assisted) coding.

Maybe there'll be a movement of hand coded FOSS but realistically they'll have a hard time. Resources are already tight for most projects, and rejecting productivity in favor of aesthetics is a rich guy's strategy.

[–] GreenKnight23@lemmy.world 7 points 2 weeks ago (1 children)

However I feel like this will soon be rendered useless as all projects will move to agentic (or otherwise ai-assisted) coding.

mine won't. ever.

Resources are already tight for most projects, and rejecting productivity in favor of aesthetics is a rich guy's strategy.

you're overlooking principles. I'll trade "productivity" for my morals every time.

I know I'm not the only dev to feel like this.

[–] Zos_Kia@jlai.lu 1 points 2 weeks ago (1 children)

And that's great for you but I still think you'll be in a minority. Which is not necessarily bad of course.

Open Source devs mostly come from the industry and the penetration of agentic coding in the industry has been massive over the last six months. I don't think I've ever seen anything of this scale.

[–] GreenKnight23@lemmy.world 3 points 2 weeks ago (1 children)

minority or not. I'm not going to make excuses to just "join in" when there's heavy implications of licensing violations and poor ethical practices surrounding the implementation of slopware.

I'll never use AI in the development of a project because it goes against every single principal that drives me. AI is my arch enemy, the antithesis of my whole being.

[–] Zos_Kia@jlai.lu 1 points 2 weeks ago

Oh man believe me I'm all for it. I totally understand having an approach of engineering that is not bankable or tailored for Californian degen culture.

I'm not saying there's anything wrong with your stance. Just saying it will become an aesthetic niche just like there's some people who still track music on magnetic tape when it would be exponentially faster to use cubase.

I don't have your specific axe to grind against AI but my personal angle is to only use old hardware and make software that runs on it.

Not everything has to be superlative, and self imposed constraints are great for quality of life.

[–] WestyFlyer@lemmy.world 5 points 2 weeks ago (2 children)

I’ve never tried Booklore (glad of that now!) but what were the greatest benefits over something like Audiobookshelf (what I currently use)?

[–] retro 1 points 2 weeks ago

For me Booklore has better metadata management

[–] tofu@lemmy.nocturnal.garden 0 points 2 weeks ago

I never tried ABS, but since I just read ebooks and don't listen to audiobooks, it just never seemed fitting for me.