When an admin fails to police their own content, or even to respond to complaints at all, it’s not reasonable to allow their instance to pollute the timelines. That’s why I’m silencing pl.smuglo.li.
One of my users complained that they received spam from @firstname.lastname@example.org, whose timeline currently looks like:
It turns out this whole instance is screaming with spam red flags:
- It doesn’t verify email addresses1,
- The site that the spambot is advertising, MastodonUserMatching.tk, is a redirect to vinayaka.distsn.org (which is on the same domain as the Mastodon instance2), and
- The bot’s source has the same name (“vinayaka”) as the subdomain it’s spamming ads for.
I conclude that this instance is specifically deployed to allow and assist spamming, and as such, I’m suspending the 2.distsn.org domain effective immediately.
I silenced our first domain this morning (and updated the status page) because a user pointed out questionable content and I agreed with their assessment.
Much has been said about that particular instance and I’m not getting into all that. It did want to comment on the rationale behind the action, though: