We’ve had to temporarily limit mastodon.social’s federation here on social.lol due to an insane influx of spambot activity from the instance. Once we get the all-clear that it’s been handled on their end, we’ll remove the limitation. Sorry for the inconvenience.
Thank you! This was the first time I've had to block a spammer since I joined Mastodon in November of last year, so I'd say you all are doing a great job. 😀
@mayor Sorry about that! The DMs that came through before the limit was put in place will still show up, but at least there shouldn’t be any new ones going forward. Hopefully.
@rudi I believe it’s mastodon.social, though I think the spam activity in this case is unrelated — this appears to be the result of a pretty sophisticated automated attack on mastodon.social (though in theory it could be directed at any instance out there with open registration, sadly).
@adam personally I don't believe in coincidences like this, why target mastodon.social over multiple smaller instances with potentially less security/smaller teams other than it being the de facto for new users
@rudi Interesting point! And given that the end result has been a bunch of instance admins blocking mastodon.social, it definitely can be seen as an attack on that instance specifically.
@anniegreens It’s a little too streamlined in my opinion. No captcha involved! I hate captchas as much as anyone else, but they do serve their purpose in combatting automated attacks.
Add comment