@jwildeboer the only feasible option is to block those big #SPAM distributors like #GMail / #GoogleMail, #Outlook.com / #Hotmail / #Office365 & #YahooMail entirely, but they are "#TooBigToBlock" I guess!

@lauren @threatresearch @Rycaut yeah...

#Google knows that #Gmail / #GoogleMail is "#TooBigToBlock" re: #Spam so they don't give a shit (in my experience)!

@vxo @harmonycorrupted yeah.

mastodon.social is the #GMail / #YahooMail / #Outlook / #Hotmail of the #Fediverse:

• "#TooBigToBlock" in spite of being #1 source of #Spam, nonexistant #moderation or consequences for #abuse...

@CursedSilicon @patagona yeah.

• Worst are the "#TooBigToBlock" #Spammers like #Microsoft, #Google and #Yahoo which will instantly blackhole your mails to their customers (but not vice versa!) if you don't comply to their bs, but in return they don't even take #AbuseReports.

• Same with everything registered/hosted at #GoDaddy & #NameCheap: They just refuse to act upon #Spam-Reports at all!

@stacksmashing because #Google's #GMail are part of the problem.

• Along with #Outlook.com / #Hotmail & #YahooMail these are the 3 "#TooBigToBlock" #Spammers...

@XEJKnol @GossiTheDog I disagree...

#CloudFlare isn't "#TooBigToBlock" and when forced to choose between it's other customers and Shitter, they'll drop shitter, as they did with KiwiFarms...

https://infosec.space/@kkarhan/113161503728222558

@ParadeGrotesque @cstross This. Mega instances are parasitizing on the smaller instances’ capacity to moderate. They can do this because they are #tooBigToBlock.

@fuomag9 granted, @stratosphere only lists what pinged / portscanned / attacked their systems and nothing else.

Which is why I use multiple blocklists simultaneously to filter traffic.

Personally I consider #ClownFlare aka. #CloudFlare to be a #RogueISP that was allowed to become #TooBigToBlock just like #Outlook.com / #Hotmail,#GMail and #YahooMail as well as #Mailbox.org are today in terms of #eMail...

@fuchsiii @georgsassen @jaypatelani #Fact: #Microsoft are literal assholes and #outlook / #hotmail, like #Gmail and #YahooMail are known to not only refuse to process #AbuseReports but randomly block domains for ni reason until they bend to their whims.

As a matter if fact, These 3 are considered "#TooBigToBlock" and that's the real problem!

@thefreehunter whereas if we allow the #GAFAMs inside, we instantly get "#TooBigToJail" or rather #TooBigToBlock instances which - like with #Spam from #GMail, #Outlook.com & #YahooMail - can basically deny to ever give a damn aboit their users' misbehaving and toxifying the #Fediverse.



These people fled here because , #tumblr, , & Co. went ...

And it's not funny!

@mastodonmigration depends...

In the end it's up to every server & instance admin to make a decisin.

Personally I'd recommend people who can to do #SelfHosting.

Also based off #TooBigToBlock issues with #eMail - #Spamming, I think we need to avoid creating the #Fediverse - equivalents of #GMail , #YahooMail & #Outlook.com where said hosters get away with ignoring #abuse #reports...

Sometimes a precendent must be set and "Fix your spamming or GTFO" is reasonable.

@euroinfosec the sheer fact that they needed to be court-ordered says a lot about the #AbuseHandling of #Microsoft and it's Services.

#TooBigToBlock is a serious issue with #eMail, as #Gmail, #Outlook.com & #YahooMail are the primary sources of #Spam and #Malware via eMail...

@lexfri
mastodon.social is too big to provide consistent, instance-wide moderation and develop a consistent culture. Since it has so many accounts, there will always be accounts that make federating with it impossible for other instances.
Instances like these need to stop accepting new accounts and they need to split up.
Otherwise the fight about whether or not to block huge instances will do much damage and split the network.