From the linked article:

Two things that aren’t changing: every Strava athlete can still access and download their data for free, at any time – and wearable and device integrations are not affected.

For everyone else who’s deep into the Apple world: No iOS app and thus no sync to Apple Health.

There’s also XPenology - a hacked Synology software to run on non-Synology systems. Awesome when you’ve got it running, can be somewhat adventurous and/or nerve-wrecking when a major update is due.

If you are not a Gitea customer, you are not being informed of security updates in a timely manner

I don’t need a notification of issues, I need a notification of when there’s a new version to roll out. And that can be solved by using things like WatchTower or setting up release notifications on GitHub.

And, of course, a comparison hosted on ForgeJo’s webpage will make it out that they’re “the better choice”.

Also, ForgeJo was promising federation which is still a WIP several years later.

Oh no, it doesn’t do the big feature™. I guess it’s unusable now.

Well, that was the one big distinguishing thing between the two, back when ForgeJo was the new kid on the block. ForgeJo wanted to make it a priority to implement federation.

And I never said it’s unusable - it’s just that I, personally, don’t see any reason to switch from Gitea to ForgeJo.

I’m staying with Gitea. They’ve created the Ltd. so they can sell professional support as most businesses will want a proper invoice. I don’t see anything wrong with that. Also, ForgeJo was promising federation which is still a WIP several years later. And, the one time I’ve tried ForgeJo it shit itself when I’ve added an emoji to my username. For some reason Gitea didn’t have any problem with that.

For #1 a quick search spat out this.

For #2 have a look into XPenology.

64 containers in total, 60 running - the remaining 4 are Watchtowers that I run manually whenever I feel like it (and have time to fix things if something should break).

“The cloud is just someone else’s computer.”

A hacky solution would be to copy all images into a directory on the other server and sshfs-mount that to where WordPress expects it on the current server.

TerraMaster F4-423 and then replace the internal USB drive with a fresh one and install OpenMediaVault or TrueNas or whatever.

INWX seems to offer .at Domains as well as an API.

This probably won’t help you much, but Apple Mail has this feature regardless of the server.

Check out GL.iNet products. They’re all based on OpenWrt with a more beginner-friendly GUI on top. (LuCi can be installed via a few clicks.) And very affordable. Some can be flashed to vanilla OpenWrt as well.

I did it for a while but my system was constantly busy and there was this controversy about the image cache and possible CSAM which then prompted me to switch to using the flagship instance. Haven’t tried any of the alternatives, though.

This GitHub and the README in there say otherwise. Also the fact that I’ve got it running locally. 😉

How does it compare to DaWarIch which seems to be basically the same?

Same here. Once in a while I update the config with all the changed engines. But that’s about it.

I’ve got a so-called “Asteroid” with UberSpace. You just have to bring your own domain and configure DNS to use their servers. Unlimited mailboxes, unlimited aliases, Sieve scripts … and SSH access.

Apart from that, I’ve got a free account with disroot for emergencies.

Items are tracked using IDs. But if a movie was imported from Douban, NeoDB only knows the Douban ID. Same with IMDb. However, since TheMovieDB records often have IMDb IDs as well, it’ll import both identifiers if you import from there.

And there’s a feature to merge duplicate imports into one. This will make that resulting record available under all the different IDs.

Yes, whenever you mark a movie or an episode as “to watch”, “watching” or “watched”, this gets published like a Mastodon post. You also have the option to automatically retoot this from your main Mastodon account. Others can follow you from Mastodon and react to your events. (For some reason, they don’t properly show up here, though.) And, of course, it all shows up for other users on NeoDB.