What happens to blocks when a fediverse account gets ported to a new instance?
Example: bad actor accrued several user blocks across multiple instsnces. Bad actor moves instance.
What's the flow of operations in this case?
What happens to blocks when a fediverse account gets ported to a new instance?
Example: bad actor accrued several user blocks across multiple instsnces. Bad actor moves instance.
What's the flow of operations in this case?
@uc
Yikes. I really need to get into the code and understand the whole process a bit better, but this seems like a glaring oversight.
Would it not be possible for a bad actor on, say, mastodon.social to:
- move their account to another instance
- move that account to .social, now without blocks?
If someone signs up with a new name and different mail address they will get a new account, much the same as any other social media system. They don't need a different instance to do that.
@uc
Right, that's true.
Likewise they can move from one instance to the next with the same name and mail, because it is the full instance handle on their previous which has been blocked, and not their personal details. There is no workable way around this aside from sharing private information across the fediverse - a decided no-no.
@uc @sb If an account is being outright abusive, not just sometimes breaking some rules, I'd consider (with some discussion) publishing a hashed IP address and hashed email address. That wouldn't give away the IP or the email address, but would let other instance admins check IP addresses and emails of user applications and compare. No one is going to do that though unless it were automated. If Mastodon showed me a list of instances the IP/email were banned on as part of approval for example.
@sb
There is no connection between old and new accounts as it is a different instance. That means the bad actor has a clean slate again.