this post was submitted on 13 Mar 2026
190 points (94.0% liked)

Selfhosted

57629 readers
2301 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
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
HybridSarcasm@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
190
Probably want to stop using Booklore... (sh.itjust.works)
submitted 4 days ago by jasonweiser@sh.itjust.works to c/selfhosted@lemmy.world
81 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
[–] PoliteDudeInTheMood@lemmy.ca 2 points 2 days ago (1 children)

It's not, the second I cloned it and gave codex access it found a whole whack of privacy issues. This was 100% human coded

[–] fccview@lemmy.world 2 points 1 day 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 4 points 1 day ago* (last edited 1 day 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

Made some other changes for my specific deployment. Very happy with your work so far. Thanks so much

[–] fccview@lemmy.world 2 points 1 day 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!!!