this post was submitted on 01 Apr 2026
696 points (99.2% liked)

Selfhosted

56957 readers
760 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
you are viewing a single comment's thread
view the rest of the comments
[–] atzanteol@sh.itjust.works 18 points 4 days ago* (last edited 4 days ago) (2 children)

Y'all are assuming the security issue is something exploitable without authentication or has something to do with auth.

But it it could be a supply chain issue which a VPN won't protect you from.

[–] WhyJiffie@sh.itjust.works 4 points 3 days ago (1 children)

to be fair, Jellyfin had multiple unauthenticated vulnerabilities in the past so it makes sense to talk about it

[–] possiblylinux127@lemmy.zip 1 points 3 days ago

The design of Jellyfin is really insecure

[–] possiblylinux127@lemmy.zip 0 points 3 days ago

It isn't a supply chain attack. If it was they would've disclosed it mmediately instead of waiting.