# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 10
# self = https://watcher.sour.is/conv/5unwita
What do I do about the growing number of spam accounts on my pod lately? 🤔 Seems like I'm getting one per day, and I keep shadow banning them because they only post total spam crap that risks littering up the Pod's Timeline (Discover) with useless junk 🤦♂️
Disable Registrations for a few days? 🤔
What do I do about the growing number of spam accounts on my pod lately? 🤔 Seems like I'm getting one per day, and I keep shadow banning them because they only post total spam crap that risks littering up the Pod's Timeline (Discover) with useless junk 🤦♂️
Disable Registrations for a few days? 🤔
@prologic Do you see any regularity in the origins of the registrations? You might be able to ban a few IP ranges at the server level for awhile until it calms down. I've done that on the VPS I manage.
@abucci Unfortunately I don't do anything with such data. But if you have experience in this, maybe you can help me out?
@abucci Unfortunately I don't do anything with such data. But if you have experience in this, maybe you can help me out?
@prologic Yeah, they hit my pod too; not really sure what to do about it, tbh. :/
@jlj Well for the time being I'm just doing the following:
1. I follow them immediately
2. Then shadow ban their account so their SPAM doesn't shove up on "Discover"
And now'I'm asking the community for help on how we _might_ deal with this "abuse" of the software and ecosystem as I see it...
@jlj Well for the time being I'm just doing the following:
1. I follow them immediately
2. Then shadow ban their account so their SPAM doesn't shove up on "Discover"
And now'I'm asking the community for help on how we _might_ deal with this "abuse" of the software and ecosystem as I see it...
@prologic You may already do all this stuff, but here's my 2 cents.
One thing you can do is a use a site like https://myip.ms/browse/blacklist/Blacklist_IP_Blacklist_IP_Addresses_Live_Database_Real-time to download a list of blacllisted IP address in a format suitable for whichever firewall you're using. Then you can hard ban those IPs.
Another thing you can use is install fail2ban and set up rules appropriate to yarnd. I'm not familiar enough to say what those should be, but blocking http POST floods is a good idea. You can also manually add IP addresses to fail2ban jails, or semi-automate that where you read the IPs you want to ban from a list that you update regularly.
Finally, you could use something like akismet to automatically detect spam posts and block ones that fail their test. I'm not sure if you're able to self host if you're dependent on a call to their servers. Maybe there's something similar that you could host locally if nto.
Not sure if this helps in any way, but I had problems with this when I ran gnusocial, i then disabled http 1.0 or 1.1 in apache, that stopped 99.9% of them.