@Hughenknubbel @Gargron Depends. It's easy to block one server (when it is not "to big to block"). And problems never affect the whole network.
Top-level
@Hughenknubbel @Gargron Depends. It's easy to block one server (when it is not "to big to block"). And problems never affect the whole network. 10 comments
@SolSoCoG @Hughenknubbel Yes until they solved the issue. We (lediver.se) also limit mastodon.social for the time being. But a smaller instance would make less problems @moanos_foss @SolSoCoG @Hughenknubbel But it has different problems https://mastodon.social/@nhan/110222576212477948. @moanos_foss That's just gonna make your users having hard time to communicate with his friend at that blocked instance.
@moanos_foss @Hughenknubbel @Gargron how about when it is "to big to block"? And why can't they spam the whole network? Obtaining a list of accounts as they're doing now and just... spam like email? @moanos_foss there must be only one Docker Container Script, that setting up Mastodon instances automatically with random users while sleeping and federating some time and you will have the same problems. @gargron @Hughenknubbel Nope, you need domains to do that, they are at least somewhat expensive (you can block a root domain and all subdomains) @Hughenknubbel Bu you still have to pay it. And I guess domain registrars also have anti-spam measures (as they also have to deal with the outfall). So while not bullet-proof it's much better. My stolen credit card number this past weekend had 8 transactions (over an hour) on it before the fraud detect at the bank took action. Average transaction was $20 USD. Funding is not a problem for a determined mal-actor. |
@moanos_foss @Hughenknubbel so you would just block an instance that is targeted by spam abusers? :schmusekadser: