Any screenshots?

yes here are a few of different areas:

That looks great!

Great app and AI disclosure. AI is a tool and useful when used properly.

Gonna try it!

Is this compatabile with Emby per chance?

Unfortunately, it’s Jellyfin-only. Emby and Jellyfin came from the same codebase originally, but their APIs and auth have drifted apart enough that Fathom’s Jellyfin-specific calls won’t work against Emby. No Emby support planned, the focus is Jellyfin, alongside the Seerr and YouTube pieces.

I’m assuming the youtube client is precisely that, right? Meaning that it’s the client that fetches the stream, not the server. Asking because Google’s been very annoying about not veing able “verify my country” due to travelling for extended periods of time. So I’m trying to find a way to spoof my location.

Yes, the YouTube side is fully client-side, the app resolves and fetches the stream directly, the Jellyfin server isn’t involved at all. So YouTube sees the connection of whatever machine is running Fathom, using that machine’s IP and location. Fathom doesn’t spoof anything itself, but because it’s client-side, running it at home or behind a VPN is what should decide the location YouTube sees.

Yeah except that YouTube support told me that they can detect if you’re using a vpn or no. At least in my case, using ProtonVPN that seems to be the case because when I try to subscribe to premium, it says that they can’t verify my country.

Yeah, unfortunately that’s a Google account/billing thing, not a playback thing. Fathom only fetches the video stream on your machine; it doesn’t touch your account or Premium. That “verify your country” check is much stricter than playback and wants a residential IP in the country, so datacenter VPN ranges like Proton’s can get “flagged”. Nothing i think a media client alone can get around.

My thought was that (maybe) the server (aka fathom in this case) could be the one that has the active youtube session so that it fetches the stream and then uploads it to the client. Acting like a proxy of sorts. To youtube, the user is always where the server is, but you can move around freely without issues.

Any idea of integrating it into I2P? Being able to torrent files anonymously would be nice maybe?

Interesting idea, but that’s out of scope for this app, Fathom is just a Jellyfin/YouTube/Seerr client, with no torrent or P2P layer, so there’s nothing for I2P to integrate with.

Alright, just an idea. Will check it out when I get back to my computer.

i cant sign-in, any chance this is because i use LDAP auth plugin in jellyfin and its not implemented here?

Sign-in goes through Jellyfin’s normal username/password endpoint (AuthenticateByName) plus Quick Connect, which is the same path the LDAP plugin hooks into, so LDAP logins generally work with a standard client like this, it shouldn’t be the blocker by itself. A few things worth trying: if your server has Quick Connect enabled, try that (it sidesteps the password path entirely and is a good way to isolate the problem); double-check the server URL has the scheme and port (e.g. host:8096); and a self-signed HTTPS cert can also cause a failure. If you can paste the exact error you’re seeing, I’ll dig in, and a GitHub issue is welcome.

this is all i see


i am using the linux Appimage, quick connect simply times out, no messages in console except :

./Fathom-x86_64.AppImage 
Gtk-Message: 18:26:14.006: Failed to load module "xapp-gtk3-module"
Gtk-Message: 18:26:14.006: Failed to load module "canberra-gtk-module"
package:media_kit_libs_linux registered.
[W][18:26:18.213431] pw.conf      | [          conf.c: 1209 pw_conf_load_conf_for_context()] setting config.name to client-rt.conf is deprecated, using client.conf

I have jellyfin running on a domain with proper certs and jellyfin's official client works perfectly.

Sorry about that. That message is a network timeout, so the Quick Connect request isn’t getting a response back within the window. Since you had to enter the server address to reach that screen, plain reachability and your cert are should be fine, so it’s something specific to the Quick Connect path.

Two things would help me narrow it down:

Does normal username/password sign-in work against the same server, or does that time out too? If password works and only Quick Connect hangs, that isolates it to the Quick Connect endpoints.

Is Jellyfin behind a reverse proxy (nginx/Caddy/Traefik), and which Jellyfin version?

was running v10.11.9, updated to 10.11.11 and it started working. 
interface looks nice! but playback stutters, with hardware acceleration on or off (makes no difference).

Glad 10.11.11 fixed the login. Since it’s the same with hardware acceleration on or off, decoding isn’t the bottleneck, it’s likely delivery or frame timing. Two quick checks: in your Jellyfin dashboard, is that session Direct Play or Transcode? And does the same file play smoothly in plain mpv/VLC (Fathom uses libmpv underneath)? That’ll tell us if it’s server/network vs. something on the Fathom side.

def. on fathom side since it plays smooth in jellyfin official client. and its direct playing. there is tearing, stuttering in video, audio is good.

Thanks, that narrows it down a lot. Fathom renders through libmpv and currently leans on its default frame timing, where a well-tuned client instead syncs frames to the display refresh.

Two questions would let me pin it down:

Which official client are you comparing against: the web client in a browser, or the Jellyfin Media Player desktop app? It matters because a browser hands video to a hardware overlay that is tear-free by design, while Jellyfin Media Player runs the same engine Fathom does, just configured differently.

What OS are you on, and what is your monitor’s refresh rate (60, 120, 144Hz)? On Linux, which desktop or compositor?

On the fix side, the next dev build adds a “Smooth Motion (Display Sync)” option under Settings > Playback > Advanced that paces frames to your monitor’s refresh. That is the usual cure for this kind of judder, so please try it when you have a moment.

The same build also adds a Diagnostics screen under Settings > About. Open it, turn on Diagnostic Logging, start the video again, let the stutter happen for a few seconds, then use “Copy Diagnostics” and paste the result here. That shows me the exact decode path and frame timing instead of me guessing. It strips out anything sensitive before copying.

github.com/Fathom-Media/fathom/…/v0.9.1-dev.3

Oh man, of this just had a controller friendly interface for YouTube I could ditch my Nvidia shield and setup an HTPC with KDE big screen and this. Would’ve been awesome!

Nice project anyways!

Sounds rad. Can’t wait to try it out.

Does it have adblocking and sponsorblock for youtube?

yes both are included as an available option to enable/disable!

That’s great!