@alternative @dansup @trankten I'm an admin of tooot.im...

@alternative @dansup @trankten
I'm an admin of tooot.im from the list. we mitigated that by this point. also, ironically enough, once I posted about the incident from my admin account, I started getting these spam messages to that account from other instances.

Like 16 February at 7:32 | Wall-to-wall | Open on 433.world

4 comments

alternative

@Yuvalne @dansup @trankten

thanks!

16 February at 7:33 | Open on indieweb.social

Trankten :vf: :tkz: :lat:

@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.

16 February at 7:37 | Open on tkz.one

Talya (she/her) 🏳️‍⚧️

@trankten @alternative @dansup
I checked some of the IP ranges and found one where most of our bots lie but also one of our users. so I just restricted sign ups from that range for 1 month.

16 February at 8:08 | Open on 433.world

Trankten :vf: :tkz: :lat:

@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.

16 February at 8:14 | Open on tkz.one

Go Up