-
Notifications
You must be signed in to change notification settings - Fork 53
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
Comments
If you block the domain itself (activitypub-troll.cf), that will apply to all subdomains. |
Related: mastodon/mastodon#21977 |
For my education, how do you do that? When I see a spammy message I click
on the three door menu, block domain. I get a dialog to confirm the block
on the subdomain without a chance to edit it.
…On Sat, Dec 3, 2022, 7:47 AM Effy Elden ***@***.***> wrote:
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.
—
Reply to this email directly, view it on GitHub
<#154 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAG5CW73TUQ4VHP4FDAZW5LWLNTP5ANCNFSM6AAAAAASST5TXI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
@piccolbo Oh, hmm, I'm wrong. Instance-level domain blocks apply to subdomains. But users can only block specific domains. |
Thanks for the clarification. I guess we'll report to mods and they'll do the clock. It seems to have stopped. |
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.
The text was updated successfully, but these errors were encountered: