aksdb

The British?! Pro-colonialism?! That can't be. /s

I imagine it's rather licensing. If they have to provide the software at some point, they can't use components they are not allowed to distribute. And I agree, that this will impact development costs. But with the law in place, this is not an unexpected cost but one that can be factored in. Might be, that some live services are then no longer viable... but I don't care. There are more games than anyone could play and games are cancelled or not even started to develop all the time for various reasons. One more or less is just noise.

Same for the "online only design" argument. The moment they decide it's not viable anymore and they want to shut it down: what does it matter to them, what players do with it? As long as they offer the service themselves, no one is bugging them. (Although I would absolutely be in favor of also getting self hosting options right from the start, I am realist enough to accept, that this would indeed lower economical feasibility of some projects.)

Do you want to know more?

Does it make a difference, if that setting uses a trailing slash? Might be it redirects you to the path without, which triggers caddy to redirect you again, and so on and so forth.

You could also, instead of redirecting, rewrite it. Then it is handled serverside without sending the client somewhere else.

Are all the *arr services aware that they are expected to have a certain basepath?

If you go for subscription, you accept that the stuff is temporal. Or at least you should. So it should make no practical difference if a game vanishes because it gets pulled from the catalog or if you decide to cancel the subscription because you consider it too expensive.

If it fits your gaming profile, it's a pretty good deal.

LOL, ok, fair 😁

You should in any case consider your backup strategy. If you have reliable backups, your fuckups can't be as bad anymore. If you don't have reliable backups, a "raw" storage doesn't help you either. Maybe even the contrary: you won't notice, if individual files get corrupted or even lost until it's too late. (Not talking about disk corruption, against which the right filesystem can guard you.... but I am not sure you trust filesystems either 😛)

Why does the storage layer of seafile scare you? Are you also scared of databases and prefer storing things in raw txt files? The difference is the same. You get certain features in return:

• Versioning is possible (so each file can have a history you can roll back)
• Sync is very fast
• It can sync incremental changes even of big files

You still have access via:

• Web
• Synced locally using Seafile Client
• WebDAV
• Mounted as network filesystem anywhere using SeaDrive.

I don't like the syntax, the runtime environment (which runs interpreted) and for PHP more than many other languages (aside from JS), a lot of code out there is hacked together horribly which makes me completely distrust the community.

Personally I stay away from anything that doesn't have a compiler.

I was in the same boat and therefore my nextcloud instance was mostly running for backwards compatibility with a few setups I have, while I mostly use seafile, immich and sogo. But a few days ago I updated to nextcloud hub 10 (I think that's with nextcloud 31 under the hood) and damn does that run smooth. I was so impressed I got motivated to finally setup the high performance backend for nc talk.

I still dislike PHP, but nextcloud just won back my heart a little.