Gregory's Server@mastodonmigration @Gargron There is another argument. Every time a spam wave comes from mastodon.social, they cause reports on smaller instances and the admins of these smaller instances have to deal with those reports, which costs time and energy. That's not something normal users see, but we admins have to deal with. This extra work is caused my mastodon.social. It happened 3 times in less than 10 days.
|
5 comments
 @mastodonmigration @Gargron The hackers don't care about the Blame Game. They try to use loopholes and social engineering to get their stuff sent, is all. Making the fediverse and specifically mastodon more resilient and less attractive as a target — that IS our task. @mastodonmigration @Gargron Changing the default in Mastodon to "DMs only from people I follow" would already stop many attacks and, IMHO, would also meet expectations of users. The last few spam waves used that loophole — that anyone can send DMs to anyone by default.  @jwildeboer @mastodonmigration @Gargron I completely agree and I do not like that it’s so open I have a bigger problem with puritanical idealists with a large ego thinking they can just slide into my DM’s and basically harass me to insist I stop using Twitch just because they have some political disagreements with Twitch. Or when I’ve had other idealists annoy me in DM’s because they didn’t like a hashtag I used. We should have comtrol over DM’s period  @mastodonmigration /cc @jwildeboer |
@jwildeboer @Gargron That is because they hackers are currently targeting mastodon.social. The next attack could be against another instance. Would the extra work then be caused by that instance. No. In both cases it is caused by the hackers. What they want to do is to get us blaming each other, when it is the invader that is at blame.