So the closure of home.social (see https://home.social/@admin/110419949340787839), from my memory of the recent musings of the admin, is another example of a sizeable instance closing because of admin burnout (partly, IIRC, from admin/instance infighting interestingly).
So given that account mobility is still imperfect, and frankly probably annoying and confusing for many people ... is there anything better that can be done?
bgrier@universeodon.com 1 year ago
@maegul @fediversenews
Hmm, not sure of all the detail and nuance needed, but it seems like an opportunity for a personal backup process to be developed.
I'm thinking that since the data is all personally migrate-able, shouldn't it be possible to do half a migration every X days to a 'backup' instance or some such?
The half I refer to is the copying of the data to the backup. The other half is the removal of the account from the source instance - which we don't want in this case.
Done cleverly, the destination could be something like GitHub or a cloud drive provider (for online storage) or to a personal local drive.
Seems weird that this isn't already possible.
maegul@calckey.social 1 year ago
@bgrier@universeodon.com @maegul@hachyderm.io @fediversenews@venera.social Yea, generally, the lack of single-user empowerment is just a little weird and I'm all for criticising the fediverse on this front. Hopefully these burn outs and closures don't harm the fediverse too much, but if they do, or cause more centralisation due to users just heading to mastodon.social out of fatigue, then it's a deserving hit IMO.