Joe

But not Fire tablets (kids profile) or Samsung TV or many others that Plex currently supports.

JellyFin android phone app’s UI is a little weird at times, but does work pretty well for me.

…

What I would adore from any app would be an easy way to upload specific content and metadata via SFTP or to blob storage and accessible with auth (basic, token, or cloud) to more easily share it with friends/family/myself without having to host the whole damn library on the Internet or share my home Internet at inconvenient times.

Client-side encryption would be a great addition to that (eg. password required, that adds a key to the key ring). And of course native support in the JellyFin/other apps for this. It could even be made to work with a JS & WASM player.

Don’t they know that the kids deserved it, because they like Hummus. Yes, I’m sure that was it.

I used to love Pocket … I remember they changed something, and then I refused to use it since. I don’t remember what it was now, though. I assume enshittification of some kind.

Yeah, at that point I wouldn’t worry. If someone has docker access on the server, it’s pretty much game over.

Encryption will typically be CPU bound, while many servers will be I/O bound (eg. File hosting, rather than computing stuff). So it will probably be fine.

Encryption can help with the case that someone gets physical access to the machine or hard disk. If they can login to the running system (or dump RAM, which is possible with VMs & containers), it won’t bring much value.

You will of course need to login and mount the encrypted volume after a restart.

At my work, we want to make sure that secrets are adequately protected at rest, and we follow good hygiene practices like regularly rotating credentials, time limited certificates, etc. We tend to trust AWS KMS to encrypt our data, except for a few special use cases.

Do you have a particular risk that you are worried about?

Normally you wouldn’t need a secrets store on the same server as you need the secrets, as they are often stored unencrypted by the service/app that needs it. An encrypted disk might be better in that case.

That said, Vault has some useful features like issuing temporary credentials (eg. for access to AWS, DBs, servers) or certificate management. If you have these use-cases, it could be useful, even on the same server.

At my work, we tend to store deployment-time secrets either in protected Gitlab variables or in Vault. Sometimes we use AWS KMS to encrypt values in config files, which we checkin to git repositories.

… and then out$ourced!

But you’ll still sell weapons to them, right?

It would be naive to think this isn’t already in widespread use.

Challenge accepted.

I’d argue that your average communist is moral and trustworthy right up until the moment they get any power, then they are just corrupt(able) politicians, ready and able to fuck over group A to benefit group B, who they happen to favor more this week (decisions must be made, after all!). No system is perfect, and definitely no individual.

Big picture view: The scales will tip every now and then, but it’s ultimately survival of the fittest system that wins, with none existing in isolation - there are always external forces at play.

With that in mind, I’d put my money on more limited socialist-style-carve-outs like single payer healthcare in the US, more rent controls and housing subsidies, slightly better employee protections. Just enough to placate the masses, while the ruling class mostly continues as before. Even this will require a massive effort. Post-republicans, of course.

Anki ?