this post was submitted on 13 Mar 2026
124 points (92.5% liked)

Selfhosted

60281 readers
808 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.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
ayyy@sh.itjust.works
curbstickle@anarchist.nexus
curbstickle_lw@lemmy.world
124
Probably want to stop using Booklore... (sh.itjust.works)
submitted 3 months ago by jasonweiser@sh.itjust.works to c/selfhosted@lemmy.world
78 comments fedilink hide all child comments
 

Just a PSA.

See this thread

Sorry to link to Reddit, but not only is the dev sloppily using using Claude to do something like 20k line PRs, but they are completely crashing out, banning people from the Discord (actually I think they wiped everything from Discord now), and accusing people forking their code of theft.

It’s a bummer because the app was pretty good… thankfully Calibre-web and Kavita still exist.

you are viewing a single comment's thread
view the rest of the comments
[–] fccview@lemmy.world 2 points 3 months ago (1 children)

degoog Dev here, definitely not vibecoded. Would you be able to tell me all these whack of privacy issues? I thought I had everything covered, but if you found something concerning it'd be nice to know before I get it out of beta :)

[–] PoliteDudeInTheMood@lemmy.ca 2 points 3 months ago (1 children)
  1. Fixed credential-exfiltration risk in /api/proxy/image: Previously the endpoint could:
  • accept arbitrary auth_id
  • load stored API keys
  • forward them to attacker-controlled URLs
  1. Enforced outbound host allowlist globally Previously:
  • allowlist existed
  • but outgoingFetch() didn’t enforce it
  • plugins/engines could bypass it
  1. Fixed extension store path traversal Previously a malicious store manifest could:
  • inject .. paths
  • escape install directories
  • reference arbitrary files
  1. Hardened proxy IP trust Previously:
  • rate limiting trusted any X-Forwarded-For header
  • clients could spoof their IP
  1. Fixed inconsistent settings authentication Previously:
  • settings UI stored an auth token
  • but the settings modal didn’t send it when saving
  1. Implemented Improved proxy deployment support
  • Added proxy-aware behavior:
  • DEGOOG_PUBLIC_BASE_URL for canonical URLs
  • secure cookie handling when X-Forwarded-Proto=https

Additional Improvements:

  • suggestion fetching hardened
  • DuckDuckGo suggestion parsing fixed
  • unified outbound request handling
  • install state guard properly cleaned up
[–] fccview@lemmy.world 2 points 3 months ago

Thanks, I'll individually look into all of these ♥️ I'll say some of them are more conscious compromises for the sake of an open scalable system where third party extensions can truly edit anything (intentionally) and everything around Auth/secure cookie is also fairly lax due to the fact the Auth is just a protection for the settings (which literally stop the settings from being served by the client), in the moment I decide to add some more structured Auth system/maybe users I'll look into proper secure cookie handling.

This is an awesome report, thank you so much for sharing it!!!