it doesn’t matter

Hehe.

Anyway, I am also completely on Zigbee. While I like the concept of Matter over Thread, I wouldn’t want to switch, because it will start with a too small network to cover a good distance and if I start replacing Zigbee devices, I effectively sabotage that network as well. So my only move would be to replace all Zigbee with Matter/Thread devices. And that seems insane. So I hope I keep getting new Zigbee devices for a while.

I think EA was still worse. At least in my perception.

I think EA actually bought studios just to get the IP and immediately get rid of the employees. I also think they tried to milk a few of the IPs before letting it go downhill.

MS, from what I can tell, gave studios quite a lot of freedom to do what they do best. I don’t think they intentionally wanted to fuck over studios, but they rather sacrificed them.

Don’t get me wrong: that’s still bad. But there’s a difference between fucking studios over with intent and reacting badly to changed circumstances.

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.

On mobile I indeed also had that issue once. However I made sure they can’t lock me out completely. The db is stored using the opensource sqlcipher, so one can open it and extract everything manually, if absolutely necessary. As long as they don’t change this, I am fine. In the worst case that would still be a lot of effort for me, but not impossible.

The export has also improved a lot. You can now also export to JSON which includes all the data one could need.

If you don’t have a hard requirement of it being fully (!) OpenSource, then I would recommend Enpass. Relatively pleasing UI that runs native on Win, Mac, Linux, Android and iOS. It has browser plugins for Chrome and Firefox that talk directly to the running fat client (so no multiple authentication with different browsers necessary).

The password db is completely local, but it offeres several sync mechanisms like WebDAV or Dropbox or also iCloud; basically whatever can store files. If it’s a NAS in your home, it simply will sync once you are back home.

It also offers “WiFi Sync”, in which case you designate one machine running Enpass as the server and link other clients to it, then you don’t even need to run a separate hosting for it (but that machine needs to be on and running Enpass when you want to sync, obviously).

It’s basically a less open but much more convenient and beautiful KeePass(XC).

I think CryptPad has delete-after-view.

Edit: yes, it has

So, buzzer WRONG.

Quite arrogant after you just constructed a faulty comparison.

If I say my name is Doo doo head, in a public park, and someone happens to overhear it - they can do with that information whatever they want. Same thing.

That’s absolutely not the same thing. Overhearing something that is in the background is fundamentally different from actively recording everything going on in a public space. You film yourself or some performance in a park and someone happens to be in the background? No problem. You build a system to identify everyone in the park and collect recordings of their conversations? Absolutely a problem, depending on the jurisdiction. The intent of the recording(s) and the reasonable expectations of the people recorded are factored in in many jurisdictions, and being in public doesn’t automatically entail consent to being recorded.

See for example https://www.freedomforum.org/recording-in-public/

(And just to clarify: I am not arguing against your explanation of Twitch’s TOS, only against the bad comparison you brought.)

My impression of Starfield (after release, at least) was, that it was a bunch of pretty well intended and implemented subsystems (as is, to my knowledge quite common in game development; each team works on a different one), but they just don’t fit really well together. All the subsystems are good parts of a theoretically good overall big picture, but the complexity seemed too high for them to actually flesh out the big picture.

Technically it all works, but IMO you feel the conceptual gaps whenever you transition (UX wise) from one gameplay mechanic to the next. It just doesn’t (or didn’t) feel like a cohesive game.

No, I keep that private to minimize the information I leak about what I host, sorry. (I also don’t do git-ops for my server; I back the mentioned directories up via kopia so in case of recovery I just restore the last working state of data+config. I don’t have much need to version the configs.)

What I did to get rid of my mess, was to containerize service after service using podman. I mount all volumes in a unified location and define all containers as quadlets (systemd services). My backup therefore consists of the base directory where all my container volumes live in subdirectories and the directory with the systemd units for the quadlets.

That way I was able to slowly unify my setup without risking to break all at once. Plus, I can easily replicate it on any server that has podman.