h3ron

They’ve been around for ~150k years. That’s plenty for trial and error.

recline is much more than a cli utility. If you run rclone as a daemon (I use the “serve S3” comand to encrypt my backups before sending them to the cloud), it’s nice to have some sort of dashboard where you can monitor what’s going on.

This will surely make everything cheaper.

it’s more like a superposition of closed and more closed

NATO is not just bureaucracy, it’s an alliance. You CAN ask allies for help, but you are supposed to treat them as such.

At least for me your argument is invalid.

1. I installed Wholphin on my TV and it’s both a jellyfin and an (experimental) jellyseer client
2. Here in Europe I have fast internet, so downloading the whole file is not really a problem. Also I configured my arr stack to prefer a certain size (on the smaller side) for each resolution.
3. I remapped my Netflix button to Wholphin

Frankly I’d prefer 4 slots at 4.0 speeds than 1 at 6.0.

Well actually it is very easy to spin up in docker and most of the configuration happens through env variables.

juicefs itself only exists on the client side, so you basically only have to install and configure the CSI driver with helm.

as it took me a few days to come up with this solution I’d be happy to share my config files.

Performance wise is quite fast on sequential reads (it saturates my 2.5G bandwidth) and slower than I expected on sequential writes (for me it caps at 60MB/s). Postgresql seems happy. I saw no visible performance degradation with Authentic, Immich and Opencloud. Nextcloud installation took ages. I’ve yet to try it with jellyfish and the *arr suite.

A simple NFS share would be faster, but it doesn’t support replication, failover and CSI snapshots.

I have two storage nodes and one is much faster than the other.

I’m currently evaluating a juicefs deployment based on two minio instances (one per node, replicated with async bucket replication) through a load balancer (sidekick) in failover. Because juicefs also needs a db for metadata, I went with valkey + sentinel.

Juicefs provides a CSI driver that supports ReadWriteMany volumes and CSI snapshots and manages both read and write cache. Performance is much much better than Ceph. In theory it should be riskier (because of the async replication) but in practice I haven’t yet lost a bit.

Because Ads are usually recognizable as such in your doom scrolling. Sometimes you can even filter them out with ad blockers.

Ads in AI response is more similar to influencers not disclosing their sponsored messages.

Probably the fact that they have many ISOs tailored for each supported hardware configuration, and they point the user to the right ISO with a clear wizard in their download page.

Also basically it is an unbreakable gaming focused OS very close to SteamOS, that you don’t have to maintain, and it comes preconfigured with Steam and the right drivers for your setup. I’m not the target audience, but I see the appeal.