jellyfin-web

Add a custom "welcome message" in Server Settings (https://my.immich.app/admin/system-settings?isOpen=server) to make your login page look different compared to all other default Immich login pages. This is probably the easiest non-intrusive tweak to work around the repeated flagging by Safe Browsing, still no 100% guarantee. I agree that strict access blocking (with extra auth or IP ACL) can work better. Though I've seen in this thread https://news.ycombinator.com/item?id=45676712 and over the Internet that purely internal/private domains get flagged too. Can it be some Chrome + G Safe Browsing integration, e.g. reporting hashes of visited pages? Btw, folks in the Jellyfin thread tried blocking specifically Google bot / IP ranges (ASNs?) https://github.com/jellyfin/jellyfin-web/issues/4076#issueco... with varying success. And go throug

It doesn’t seem like email scanning is necessary to explain this. It appears that simply having a “bad” subdomain can trigger this. Obviously this heuristic isn’t working well, but you can see the naive logic of it: anything with the subdomain “apple” might be trying to impersonate Apple, so let’s flag it. This has happened to me on internal domains on my home network that I've exposed to no one. This also has been reported at the jellyfin project: https://github.com/jellyfin/jellyfin-web/issues/4076

https://github.com/jellyfin/jellyfin/releases/tag/v10.10.0 https://github.com/jellyfin/jellyfin-web/releases/tag/v10.10... https://github.com/jellyfin/jellyfin-ffmpeg/releases/tag/v7....

Honestly - just stop using Google search (and while I remain flabberghasted I'm saying this - Edge is a better chromium browser than Chrome.). Or better yet, any Google product. The company is diving off a cliff. For reference... A private Jellyfin server I use for hosting videos of my kid for his grandparents, and some music I legally own is consistently flagged as phishing (along with basically anyone else hosting them publicly based on this thread: https://github.com/jellyfin/jellyfin-web/issues/4076) Google has "automated" itself into the garbage.

Most of the webOS development happens in the web repo, you can see some items with webOS tag. https://github.com/jellyfin/jellyfin-web/labels/p%3A%20webos

I think parent says that +/-200ms is acceptable for snapcast, but unacceptable for lip-syncing. I am not sure snapcast can't sync down to a few ms. If so, the issue would be syncing video with the audio clients, which certainly sounds feasible if integrated in the video player. That's what jellyfin does: https://github.com/jellyfin/jellyfin-web/pull/1011 (I tried to help a bit with that one).

Clients are a gap for sure. I have a PS4 and Wii U already under my TV; I'm in the process of motivating myself to set up a proper media server, and Plex seemed like a safe option given that there are phone and game console apps, and a web client for desktop use. Would love to try Jellyfin, but I'm definitely not setting up another box + remote for it, and it sounds like the web client is a little patchy in the PS4's browser. (looks like the web client does have a bunch of PS4-specific detection in it, so it's getting at least some testing/use— perhaps I'll check it out: https://github.com/jellyfin/jellyfin-web/search?q=PS4&type=C...)