Hacker News Reader

Comment by user- | Hacker News Reader

The readme was obviously written with a LLM and it makes it so hard to read. High word count isnt a good thing

I didn't catch this until you called it out. While I reading I was anticipating an argument that would convince me that I need Kyoo. I'm not convinced that its setup once and forget it -- especially since it also says that its not afraid of adding more services (complexity). Further, the hard stance on cinema only instead of books, games, etc made me think that the project was rigid. Making me potentially add more services to manage all of my entertainment media.

As a user, you don't really need to care about the number of containers since everything is managed by docker-compose or k8s (soon). The advantages of having more containers is that you can have specialized softwares. For example, the search system is based on meilisearch which makes it way better than what could have been done by just using postgres/sqlite. It also makes distribution or replication built-in (for example, to have a transcoder on a remote computer), jellyfin/plex does not support this natively and users have written their own remote transcoder for that.

Only half kidding, but you've heard of processes right? :)

Plex for example starts many transcoder instances within a single container for scalability. You don't _need_ to scale at the container level.

There's pros and cons to each approach, but for the self-hosting crowd keeping the deployment simple may broaden your audience.

A good example I have experience with is vaultwarden: people use it because it's a single container deployment as opposed to the complex and resource intensive setup bitwarden provides.

Are you planning to run these containers in the same Pod? And/or what is the deployable unit going to be?

Not sure yet, I'm a beginner at k8s and just started writing a helm chart on a branch/reading the documentation. I have devops friends to help me with my skill issues tho x)

I was also surprised by that bit about adding more services:

> We're not afraid to bring in additional containers when it makes sense

That is one of the last things I'm thinking about when I choose a media organization and streaming app, and if I do think about it, having more containers is a red flag more than something that sets my mind at ease, because of that added complexity. I experienced this with Photoprism when I wanted to customize it a bit, because I then had to figure out the roles of the containers and which containers did and did not need the customization bits I was adding, etc..

You're right, but in today's github if you want to stand out you need this kind of readme or an existing community. To be fair, the important features are in bold and the philosophy/why another browser is handwritten.

I'd still recommend reviewing the output more closely, particularly in top-level paragraphs.

> Designed from the ground up, Kyoo stands out as a powerful alternative to Plex and Jellyfin.

This sentence doesn't really mean anything - designed from the ground up to do what? Plex and Jellyfine were both designed as well, so part of the first hype paragraph has me sitting here wondering what information was supposed to be conveyed here.

Project looks nice, though, and I have been wanting to move away from Plex for a while. Lack of TV/iOS apps is unfortunately a blocker for me, but bookmarking to check out 6 months from now. Good luck!

Reply on news.ycombinator.com