This needs more work. Specifically, it needs a CAPTCHA on the server on the other end, and it needs to deal with cases where signups need to be approved manually.
What would perhaps work for that use case is to require you to sign up on the other server, generate a special token, and then use that in the migration screen.
I don’t think Lemmy migrations work, though. The Fediverse is not set up for full account migrations with data portability and locking users out of editing capabilities for their old posts (as well as having their old name plastered around everywhere) would lead to confusion. This needs a warning detailing what users can and cannot expect from account portability, and to write that you’ll need to work out the backend mechanism first.
This needs more work. Specifically, it needs a CAPTCHA on the server on the other end, and it needs to deal with cases where signups need to be approved manually.
What would perhaps work for that use case is to require you to sign up on the other server, generate a special token, and then use that in the migration screen.
I don’t think Lemmy migrations work, though. The Fediverse is not set up for full account migrations with data portability and locking users out of editing capabilities for their old posts (as well as having their old name plastered around everywhere) would lead to confusion. This needs a warning detailing what users can and cannot expect from account portability, and to write that you’ll need to work out the backend mechanism first.
This is how the transphobic people get into Beehaw.