It really depends on if you need transcoding or not. If no, it doesn’t matter. If yes, check for integrated GPUs on both models and check that it will work as a transcoder for jellyfin.
It really depends on if you need transcoding or not. If no, it doesn’t matter. If yes, check for integrated GPUs on both models and check that it will work as a transcoder for jellyfin.
What? No no no no… You don’t understand. NixOS is hot shit, how can they be wrong in any way…
That’s and interesting way to misspell “Zwetschge”
Kavita works well for me.
Are you high?
The idea is that the router plugs in to your home internet and the server into the router. Between the two they get the server able to handle incoming requests so that you can host services on the box and address them from the broader Internet.
Why would I need a separate router for that? I’d need to configure the main router anyway.
No, why? That’s capitalism for you. It’s still a US company/subsidiary, just with a German owner.
And you think this behavior magically goes away just because it’s a different language?
“Toastbrotmann” ist jetzt auch nicht wirklich die beste Verkleidung.
a motivated group of talented Rust OS developers could build a Linux-compatible kernel, from scratch, very quickly, with no need to engage in LKML politics
Riiight… Because those developers would always be of the same opinion… Good luck with that.
Docker image is already updated.
If setting up TLS is too much work, better stay with a service. Signal is nice.