@Moon@shitposter.club Switching domains should in theory be possible but no fediverse software is built for it so it will be a ton of manual database editing to even attempt something like that, but I think it can be done in theory?
@lanodan@SuperDicq people are going to expect to be able to do this when the domain is lost unexpectedly, and doing it in a for loop takes a ton of time.
@Moon@SuperDicq SJW had to do a domain change from neckbeard.xyz to bae.st, but it really messed up all the previous status posts prior the change. Possible but really shitty.
@lanodan@SuperDicq@Moon Incidentally users being owned by an instance is one of my gripes with the Matrix homeserver model, I don't like migration processes, I want federation/decentralization to go harder into nomadic ideals. ofc, much harder problem than just trading profiles and posts that are hosted by known servers
@lanodan@SuperDicq@Moon main reason for not taking that approach is i'm tired, and last year I committed myself to the idea that I will run the place until the taliban killed it.
@birdulon@SuperDicq@Moon And true nomadic without even an identity server so far means that users would have to keep private keys on their machines. And no one does that properly, not even cryptonerds. At least I'd much rather get funny bits like servers getting shut-down by the talibans than a constant stream of users loosing access to their accounts or even getting hacked en-masse because of a cloud storage leak.
@lanodan@SuperDicq@birdulon I feel like you been here long enough you don't think it's so bad if someone changes domains, even loses their post history.
@coin@SuperDicq@Moon Nekobit swapped domains on his instances almost a dozen times, he has a whole migration script for that. But it always involves dropping follows/followers.
@Moon@SuperDicq@birdulon Right, because it feels like caring about a chatroom history to me, if it's important it'll end up in something like a blog, which by design are way more stable.
@coin@Moon@SuperDicq If I ever have to switch domains (which is a possibility considering donuts/identity.digital are a bunch of cucks), I'll probably do the same but keep the original DB intact, then automatically run migrations and follower imports for each user.
@Moon@shitposter.club@lanodan@queer.hacktivis.me@birdulon@shpposter.club Sometimes I think about designing a dead man's switch but then I think that I could publish everything accidentally by forgetting about it or the mechanism failing or something like that and I don't want it anymore.
@Moon@SuperDicq@lanodan amusingly one of my online friends had the opposite problem, he retained his domain but lost his server db, he tried starting a new instance with the same domain but it never federated correctly with servers that the old one had federated with, so he had to instead use a new subdomain for it.
I had a friendica server on social.hacktivis.me around like 2016, server fell over, didn't care enough to restore, then years later I had the exact same hostname idea for my previous Pleroma instance (which had no backups because broke student).
@lanodan@SuperDicq@Moon Right yeah, people are going to have different views on how ephemeral the content should be. If they like the term "microblogging", they probably would like it to be a bit more permanent than say the text chat record of a TF2 lobby.
@lanodan@Moon@SuperDicq I know the go-to example for this is IRC chatrooms but I consider my decade+ of those logs to be a treasure trove of greppable technical discussions that keep being useful to this day.
2 year old chatlogs are like who the fuck cares but if you have 30 year old chatlogs it's gonna be like "woah look how people lived back then" and shit.
@birdulon@SuperDicq@Moon Yeah, it's why some of them are publicly logged or even archived (meetings over IRC specially do this, like all the gentoo council ones are). Yet we all know that IRC is quite ephemeral, and I think it's fine for like half of fedi instances to be, at least I don't think everything ever should be kept forever, but should at as closely as possible be kept as long as someone cares.
@SuperDicq@Moon@lanodan It helps that text logs are really small and very searchable relative to other data that gets backed up. The old imageboard folders? I might go through them every now and then for a laugh but I almost never find anything I'm specifically looking for in them (my fault for poorly cataloging I know I know)
@birdulon@Moon@SuperDicq In a way, I love BitTorrent for this, but it also quite sucks in terms of discoverability so stuff sadly often ends up separated/duplicated.
@lanodan@SuperDicq@Moon One of my favourite features of IRC logs is that they aren't inherently authoritative, so plausible deniability is a lot higher than e.g. discord log dumps.
I mean I can go into my files and start pulling out random memes I saved 2008 no problem but if I ever wanna find a specific one that's never gonna happen because nothing is catalogued and not even the filenames are meaningful.
This is actually one of the things where I think those fancy neural networks would be useful.
@SuperDicq@Moon@lanodan the queer.af database has gotten backed up every night, so despite never having had data loss issues we were protected against that. But i'm pretty sanguine about historical posts; maybe I'll rescue some of my more important ones from the export at some point.
(I didn't bother backing up media; I figured the probability of an entire AWS region catching fire was low enough)
@erincandescent@SuperDicq@Moon For stuff like AWS I'd more worry about getting your account cancelled or hacked or some kind of human error, rather than an hardware failure. That said OVH Strasbourg demonstrated the possibility of a entire DC catching fire.
@erincandescent@Moon@SuperDicq At least half of the reason I make backups is because I know I can be an idiot and accidentally delete/overwrite my data. (Most stuff being textual means it's often done via having git repos mirrored)