What's wrong with the name?

Differences from Plex:

- Watching your own films away from home isn't paywalled, and never will be.

- Hardware encoding is free, and always will be.

- No cloud account required unless you want my convenient discovery service.

- If you don't want to use a cloud account at all, you can set up your own discovery server on your own VPS for watching away from home even through routers and shit (also free).

- No ads, no storefront, no telemetry.

- Watch Together with voice. Multiple people can watch a synced video, and talk to each other (I've tested this with me in Germany and the other person in Australia, and it worked beautifully).

- Hardened against corrupt video files and issues like NFS failures (getting stuck forever in a syscall). Everything vulnerable is separated and isolated.

- Open source. The server is AGPL and the web clients are MPL.

- Your files are left alone. Media is read-only by default. The server reads the .nfo metadata files you already have, from Kodi for example.

What's not there yet:

- Native apps. I'm only doing a web client for the time being until all the features are in place. It's pretty fast, though.

- Music. This comes later.

How is this different from Jellyfin?

Jellyfin can only be used from remote if you can expose its ports somehow. Lots of routers block that, or your ISP is set up such that you need NAT tricks, and have to use STUN and TURN and such to work around it. Jellyfin doesn't handle any of that. Tailscale helps here, but then if you want family members to use it, you have to set them up on tailscale as well. Or you set up a service on a VPS.

I wrote this because I'm unhappy with the offerings out there, including Emby, Plex, and Jellyfin. Also too many bugs that have been sitting for years with no solution. For Jellyfin in particular:

- SyncPlay is buggy, doesn't support voice, and seems to be unmaintained now.

- Way too many CVEs, mostly FFmpeg injections (CVE-2026-35033, CVE-2026-35032, CVE-2026-48793, CVE-2025-31499).

- The session key leaking in URLs.

- Upgrades breaking the database.

- Needless transcodes and wrong "can play this" guesses.

- Subtitles that load late or drift after resuming.

Yeah for real, enlightened one. Russia is great by every metric /s.

Not sure I understand this hypothesis. GPUs age like leftover dinner unlike crude oil...

Replace oil with wheat, then - it can be stored for a few years, but it’s still perishable. Yet it still trades on commodities markets.

Not only that - technological obsolescence

You notice anything different about him? Look at his face.

There's no land in China?

That wasn't what they're referring to. What are you talking about? They're literally talking about land for migrants. Literally the comment says that.

The condescending way the comment was written...

Well I think that's being a little sensitive, frankly..

What's up with that absolute word salad of a README? Is that slop as well?

It reads more like a prompt than a useful README.

useful to whom? ai loves it.

I asked it to keep track of features as it implemented them. It isn't meant to be read by humans.

You go to the website, you connect your trainer, you ride your bike and you get healthy.

wtf do you care about a readme for? =)

README.md is for humans, AGENTS.md is for agents

That theoretically could be within reason!

Because you've hosted the code on github and the Readme is for humans but you've even slopped that. I mean who TF does that? Rarely see something so moronic while browsing someone's github project. Wtf. =)

I know, right!

The title. Are you an AI?

Looks like the account has been banned. I think it is very likely it was an AI.

Some people really get sour when others politely point out grammatical mistakes they've made on a written forum. It's understandable as some people don't really do it tactfully and it can come across abrasive. Then there's a special kind of person who gets sour and snarky over someone politely pointing out grammatical mistakes other people have made.