It looks like shit sandwich migrated some of his accounts. Update your blocks folks. @truthsandwich @TruthSandwich
Apparently he thinks his particular brand of trolling will be more welcome on those servers.
@serge and @wild1145
You may want to take a close look at one of your newer members. He's a malignant troll who constantly switches accounts to avoid blocks and spouts hateful rhetoric as pictured in previous posts. #fediblock
All three servers have been thoroughly investigated. In all three cases, they continue to be vectors for spam attacks. No action on spam reports has been taken by moderators, admins have proven to be absentee, and registrations continue to be open.
This is because:
☠️ It was a source of Spam
☠️ It was running an insecure and outdated version of Mastodon
☠️ It has been abandoned by the administrator
FYI: On the onging #spam#discord issues...
I had started out by just suspending every domain from which the spam was emanating. Then I tried only Limiting a few of them.
Every domain I Limited has returned with more spam. So I am back to suspending all of them. At this point, if the compromised domains aren't aware of the problem then they're probably not going to wake up anytime soon, if ever.
Also, why can I not “select all” from the report menu so that I can limit/suspend a large number at a time for exactly this kind of situation? This seems like basic functionality.
Rather than:
Individually clicking each report—>
New Domain Block—>
Limit/Suspend—>
Confirm.
Repeat x number of times.
It should be:
Select All (up to 20, 50, 100)
Choose Action (Domain Block)
Confirm
List of Domains to Limit/Suspend
Choose Action (Suspend)
Confirm
Back to Reports
Select All
Choose Action (Assign to Mod)
Confirm
Select All
Choose Action (Mark as Resolved)
Confirm
Done.
All of these servers are vectors for an ongoing spam attack. Despite me giving them ample time to respond to reports, they refuse to respond. They show no inclination to moderate, and no action has been taken by them whatsoever.
In all cases, these are abandoned servers with open registrations. It is likely they will continue to be used for sending spam across the Fediverse.
They are on MastoHost but are raging because their instance will be auto managed under certain circumstances to limit spam.
If they don't care about limiting spam, then why should we all care to stay federated?
Again, they're on MastoHost so the spam problem won't be an issue, but the admin not caring about potentially spreading spam is quite worrying to say the least...
Please update your mastodon instance, or I'm going to #defederate it since you have SEVERE security issues. You claim to be running mastodon v3.2.1, which is quite old (we are at v4.2.7 now)
phpc.social has temporarily limited + rejected media from quakers.social due to spam. They're currently cleaning things up, so I expect we will remove that limit soon.
phpc.social has limited + rejected media from nasface.cz and contacted its admin, as while the instance is still active, it's consistently churning out spam as 99.99% of its posts right now.
L’instance h4.io se montre toléraite envers les racistes, attention !
Plusieurs posts de chez eux ont été signalés depuis lundi 12, un MP envoyé aux admins, des engueulades en public hier soir… (le pire des posts a enfin été supprimé entre hier soir et aujourd’hui)
D’ailleurs, être raciste n’est pas illégal d’après les admins. Wtf ?
Each of these servers served as vectors for the last spam attack. In every case, they have ignored my spam reports that I sent to their admins, and I’ve given them ample time to respond. Spam still exists on their servers, and no action has been taken whatsoever.
As well, I have investigated each of these servers individually, and have determined that they are still vulnerable to spam attacks. Likely, they will be used for spam again in the future.
In most (perhaps all) cases, these are abandoned servers with open registrations, and an admin who has done little or nothing to moderate new users.
Am I imagining things or has the spam wave actually stopped? It's been 20h since I last got a report and all formerly spamming instances I check that still have the spam posts didn't receive any new ones in the last 13h either.
How do you deal with this? Leave the limited federation active in case it starts again? Did I miss any news about this?
#fediblock bottomservices.club for hosting pro-contact/MAP services
it's literally just a MAP site. no questions needed (while there's no instance at the moment, i recommend blocking it just in case an instance were to ever pop up)
We've also limited terere.social with rejected media as they have a significant spam problem, but some of their legitimate users follow some of ours, so we're not tearing that bridge down just yet.
Hallo alle Fedi-Admins die Probleme mit Spam haben!
Die Mute-Liste 2.2.2
Ich habe die Spam-Liste aktualisiert und ~104 zusätzliche Instanzen gefunden, die weiterhin spammen! Ich habe, mit viel Hilfe von anderen Fedi Admins, die Instanzen in einer Liste zusammengestellt, die sie stumm schaltet und nicht von ihnen deföderiert!
Ich würde mich sehr über eine kleine Spende hier freuen, da Ich wirklich hart und lange an der Erstellung dieser Liste gearbeitet habe, was Ich angesichts meines aktuellen Zeitplans kaum rechtfertigen kann! Dankeschön!
Es gibt eine neue Art von Spam, die gleichen Instanzen sind betroffen wie vorher. Die Verantwortlichen in Japan sollen verhaftet worden sein.
Ist diese Liste importiert ist ein Großteil des Spams vorbei. Das ganze ist für euch leicht, geht mit einem klick! Zudem wird keinerlei Instanz für immer geblockt, keinerlei Follower etc. zerstört oder deföderiert, sondern nur stummgeschaltet. Das ist sehr leicht umkehrbar.
Ihr könnet diese Liste einfach importieren, indem ihr auf https://yourinstance.tld/admin/export_domain_blocks/new geht und yourinstance.tld durch die Domain derer Instanz ersetzt, von der ihr der Administrator seid!
Alternativ könnt ihr auch auf Einstellungen => Moderation => Föderation => Importieren drücken, um diese Liste zu importieren.
Beachtet, dass zwar alle Instanzen mit einem Klick importiert werden können, dass aber diese Instanzen einzeln entfernt werden müssen, wenn der Spam vorbei ist.
Beachtet auch, dass es nur Sinn ergibt, diese Liste zu importieren und die Spam-Instanzen stumm zu schalten, wenn ihr euren Spam lokal und nachhaltig blockiert habt, wie hier beschrieben.