Rotation would just be for privacy measures as that way any analytics tied to the account get dumped.
I wonder how the bot farms automate it, there's clearly a way they do it unless they actually have teams of people manually creating accounts. Even then based on user load there's only so many that would actually need to be made.
for a public instance I don't think that measure is needed, since dozens or hundreds of random people's traffic is aggregated together, and ideally each user would also have a bunch of public instances and use a different one each time (thats what Libredirect does) further diluting the pool
Rotation would just be for privacy measures as that way any analytics tied to the account get dumped.
I wonder how the bot farms automate it, there's clearly a way they do it unless they actually have teams of people manually creating accounts. Even then based on user load there's only so many that would actually need to be made.
for a public instance I don't think that measure is needed, since dozens or hundreds of random people's traffic is aggregated together, and ideally each user would also have a bunch of public instances and use a different one each time (thats what Libredirect does) further diluting the pool
That's the approach the Ad Nauseam extension takes, I guess at scale on a public instance it could work well enough