Could/should there be a system to “back up/mirror/migrate” your account to another instance?
Perhaps we could agree on a main instance to back up every account?
If this were to be made, it should maybe have an opt-out? Idk, but it should definitely not be an opt-in thing that misses a lot off clueless new users.
I’m pondering a (strong) suggestion to make a global namespace happen (as it should have been done from the beginning). It would not actually be too difficult. It would mean that communities/posts/users could be handled independently from the domain, thereby effectively virtualising domains, and putting communities/users into a distributed directory. All of it can be backward-compatible and transparent to the user. This would help solve several structural problems at once. First one would be the internal links, then possibility of server migration (without breaking links), resilience against loss of domains/servers (easy use federation as backup) and rogue-going server admins …
I have seen this in so many places now that people come like “this is just not the way you do such a thing”, so I’m thinking about making it a lenghty explanatory post first, for comments to be made, because i might have missed some points and the github discussion board is unsuitable for casual human interaction. Will have to read up on ActivityPub before i proceed … and this is making me a bit sleepless atm ;-)
Could/should there be a system to “back up/mirror/migrate” your account to another instance?
Perhaps we could agree on a main instance to back up every account?
If this were to be made, it should maybe have an opt-out? Idk, but it should definitely not be an opt-in thing that misses a lot off clueless new users.
I’m pondering a (strong) suggestion to make a global namespace happen (as it should have been done from the beginning). It would not actually be too difficult. It would mean that communities/posts/users could be handled independently from the domain, thereby effectively virtualising domains, and putting communities/users into a distributed directory. All of it can be backward-compatible and transparent to the user. This would help solve several structural problems at once. First one would be the internal links, then possibility of server migration (without breaking links), resilience against loss of domains/servers (easy use federation as backup) and rogue-going server admins …
I have seen this in so many places now that people come like “this is just not the way you do such a thing”, so I’m thinking about making it a lenghty explanatory post first, for comments to be made, because i might have missed some points and the github discussion board is unsuitable for casual human interaction. Will have to read up on ActivityPub before i proceed … and this is making me a bit sleepless atm ;-)