I don’t think that’s even desirable and also legally questionable. But anyways, these posts are not gone with an instance shutting down and thus I don’t really see a problem. You can always add a link to a mirrow of those old posts in your profile.
Can you do that with a letter once it is send? And the instance admin of the mirroring server can delete posts if that is legally required for some reason.
And how would that even work technically? Bulk import posts and spam other instances with mass updates? That would immediately detected as a spam-wave and blocked. And back dating technically new messages is also not exactly a great thing to allow.
Other implementations of nomadic identity like Hubzilla get around this by letting you run two accounts in parallel and syncing them from your main account, but they will also not back-port old messages before you linked up the secondary account.
Basically anyone with some experience with federated systems agrees that importing old messages in bulk on account migration will never happen, and I don’t really see an issue with that, since messages are not lost.
Content is mirrored on all federated instances and it is very rare for an instance to shut down without notice.
I meant that it’s not directly associated with you as the owner through your migrated account.
Edited comment (many to some).
I don’t think that’s even desirable and also legally questionable. But anyways, these posts are not gone with an instance shutting down and thus I don’t really see a problem. You can always add a link to a mirrow of those old posts in your profile.
Except you no longer can edit, delete, etc. the posts.
You’ve lost complete control over your data, and there’s no way to get it back if your instance vanishes.
Can you do that with a letter once it is send? And the instance admin of the mirroring server can delete posts if that is legally required for some reason.
And how would that even work technically? Bulk import posts and spam other instances with mass updates? That would immediately detected as a spam-wave and blocked. And back dating technically new messages is also not exactly a great thing to allow.
Other implementations of nomadic identity like Hubzilla get around this by letting you run two accounts in parallel and syncing them from your main account, but they will also not back-port old messages before you linked up the secondary account.
Basically anyone with some experience with federated systems agrees that importing old messages in bulk on account migration will never happen, and I don’t really see an issue with that, since messages are not lost.