Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Domain farm in action #154

Closed
piccolbo opened this issue Dec 3, 2022 · 6 comments
Closed

Domain farm in action #154

piccolbo opened this issue Dec 3, 2022 · 6 comments

Comments

@piccolbo
Copy link

piccolbo commented Dec 3, 2022

I took a look at the federated timeline and I see only spammy posts from domains like

3ggqbyltr.activitypub-troll.cf

With minimal content

1h
1nyghw775@3ggqbyltr.activitypub-troll.cf
1nyghw775 @1nyghw775@3ggqbyltr.activitypub-troll.cf
@1a61qk2ak @19scasybn

I can't block it or at least it would be a fool's errand because every post is coming from a different subdomain. I think the bad actors are finding mastodon weaknesses. I don't see any payload. At least they are honest, the domain declares itself as a troll. Not sure what we can do, maybe there is an admin-level tool to deal with this, but, as a user, they just saturated my federated timeline and there's nothing I can do.

@Ghryphen
Copy link

Ghryphen commented Dec 3, 2022

Just adding a screenshot for reference.

Screenshot_20221203_025134

@ineffyble
Copy link

I can't block it or at least it would be a fool's errand because every post is coming from a different subdomain.

If you block the domain itself (activitypub-troll.cf), that will apply to all subdomains.

@ineffyble
Copy link

Related: mastodon/mastodon#21977

@piccolbo
Copy link
Author

piccolbo commented Dec 3, 2022 via email

@ineffyble
Copy link

@piccolbo Oh, hmm, I'm wrong. Instance-level domain blocks apply to subdomains. But users can only block specific domains.

@piccolbo
Copy link
Author

piccolbo commented Dec 3, 2022

Thanks for the clarification. I guess we'll report to mods and they'll do the clock. It seems to have stopped.

@piccolbo piccolbo closed this as completed Dec 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants