The web client supports it too, as do other apps like Tusky and Ivory. The official app is just a weird outlier.
The web client supports it too, as do other apps like Tusky and Ivory. The official app is just a weird outlier.
Totally negligible. All you need to keep is a line in a database with the person’s email, hashed and salted password, and a unique identifier for each game they own - that’s an amount of space that won’t even register on any service nowadays. There might be other optional stuff that takes more space, like display pics, cloud saves etc but you can delete those without deleting the whole account.
I don’t think a guaranteed replacement is the reason why warranties can contribute to something being BIFL: rather, the lifetime warranty is the manufacturer putting money on the durability of the item, which increases my confidence that they genuinely believe their product is actually durable.
It’s still no guarantee and there are lots of other factors to consider, but I think taking a warranty into account is reasonable.
Not at all! We just need a combination of A) more new instances popping up, B) some people moving to other instances because they like them better or they run faster, and C) kbin.social admins scaling up this instance. It’s just an adjustment process.
The good thing about fediverse services is that as long as there are people willing to throw up a server, you can just keep scaling - unlike on a centralised service where if the owner doesn’t scale, that’s tough.
The backup service is good, inexpensive and easy to set up, so easy to recommend.
I now use their B2 service with duplicati (available as a docker container, but idk how well it works with Synology). It’s dirt cheap and equally reliable, but requires more setup by the user, and you must follow good practise and do a test restore of some files to make sure it works.
So it’s really a trade-off, depending on what you want to prioritise.