Gregory's Serveryou should all check those instances
/ -> .
|
7 comments
Some says The biggest reason is that there is no Captcha system when joining and i thinkt it's very reasonable  @alternative @dansup @trankten @Yuvalne @alternative @dansup Same happened to me! When I posted about the spam publicly, the bots started to register in my instance but suspended them asap. Some of them have the same IP address while others don't so it seems they are behind a VPN. IP blocking might block legitimate users who use a VPN to prevent ISP geoblock. Not an option for me. I am not 100% sure what to do beyond manual check. @trankten @alternative @dansup @Yuvalne @alternative @dansup Oh that's amazing and probably a good idea. Is it possible for you to share the IP ranges? Maybe we can check on that all together and find some pattern or users responsible somehow. |
@alternative @Yuvalne @dansup Problem is the randomness.
Usually the bots register a few accounts in every instance they find so a Fediblock tends to affect every user in the instance who have regular posts and legitimate use the Fediverse. A list of instances is not going to help but can mitigate if they are blocked manually.
It is up to #MastoAdmins to suspend the accounts in their instances as soon as possible, but the problem comes with unattended instances with open registrations, which are quite a few and if no active moderation is taking, more spam bots will register and will end Fediblocked.
Regards.
@alternative @Yuvalne @dansup Problem is the randomness.
Usually the bots register a few accounts in every instance they find so a Fediblock tends to affect every user in the instance who have regular posts and legitimate use the Fediverse. A list of instances is not going to help but can mitigate if they are blocked manually.