this post was submitted on 13 Mar 2026
116 points (97.5% liked)

Selfhosted

61345 readers
410 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. 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. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. 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, and find example disclosures here.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] eodur@piefed.social 31 points 5 months 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 5 months ago (1 children)

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

[–] bobslaede@feddit.dk 7 points 5 months 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 5 months ago

BookLore

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

[–] EarMaster@lemmy.world 3 points 5 months ago* (last edited 5 months 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 5 months ago

They said they were disappointed, not mad.

[–] tofu@lemmy.nocturnal.garden 2 points 5 months 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 5 months 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 5 months 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 2 points 5 months 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 5 months 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.