This is unfortunately only possible if you still own the original domain. Think about it this way: if you could migrate domains without proving you own the original, then what’s stopping a bad actor from migrating any domain they want?
I’m suggesting a whitelist, that each peer has to put in a substitute list of vlemmy.ml==vlemmy.ml to re-federate.
Much like Reddit, comments continue to exist **even when the author deletes their account. **
The intention is to routinely purge all content of users who delete their account. In fact, there are open GitHub issues about serious performance problems in executing this code, even with a relatively small amount of content. Developers in the past 2 days have commented on this and made no mention of intention to retain content.
I’m suggesting a whitelist, that each peer has to put in a substitute list of vlemmy.ml==vlemmy.ml to re-federate.
I don’t see any inherent problem with that suggestion, though it does create something of a sticky situation with things like canonical links. It also kind of goes against what I’ve so far perceived as a “low-maintenance” operations ethos from the project maintainers, so I’m not totally sure if they’d greenlight it. Technically quite doable, though.
I’m suggesting a whitelist, that each peer has to put in a substitute list of vlemmy.ml==vlemmy.ml to re-federate.
That is NOT how the testing code of lemmy_server tests things, nor how the GitHub front page advertises Lemmy.
I’ll cite my source, then: https://github.com/LemmyNet/lemmy/commit/1de7a08d973c1079b36e13e087960cc5cd1b345c
You cite a conversation from November 4, 2022.
A Febuary 6, 2023 comment from developers https://github.com/LemmyNet/lemmy/issues/2624#issuecomment-1419559651 says “The correct way privacy-wise, is to delete your account through your profile settings, which overwrites all your content to remove any info.”
The intention is to routinely purge all content of users who delete their account. In fact, there are open GitHub issues about serious performance problems in executing this code, even with a relatively small amount of content. Developers in the past 2 days have commented on this and made no mention of intention to retain content.
I don’t see any inherent problem with that suggestion, though it does create something of a sticky situation with things like canonical links. It also kind of goes against what I’ve so far perceived as a “low-maintenance” operations ethos from the project maintainers, so I’m not totally sure if they’d greenlight it. Technically quite doable, though.