Submitted 11 months ago by maegul@hachyderm.io to fediversenews@venera.social
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?
@maegul one piece of the answer's the same as it's been for the last 6 years: make account mobility easier and better (even if still imperfect). But then again, that would make it easier for people to migrate from .social, so it's not surprising it hasn't been prioritized.
We reached out and there was no response.
If admins are burning out, there is a huge admin community we need to better champion to people so they don't think they're on their own and isolated.
I offered to re-host or even offer our moderation capability and never received a response.
As for post migration, the difficulty is the design. Perhaps we can clone what Calckey does and import them as a hidden post so people have them and may be able to quote and boost them to get them re-federated. Right now the post ID is unique to the instance that generated it. I guess one migration may be to collect an archive, send mass deletes to every instance and then import so there isn't dereferenced data...
curious what people want... tired of the debate being about M.S when that doesn't really matter right now.
bgrier@universeodon.com 11 months 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 11 months 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.