Ducky 🦆 @ducky.ws · 13/09/2026I can see why it's this way; PDSes are small enough to likely be running on shared machines with a single IP, or running behind a dynamic residential IP. Banning an entire IP is never a great idea in that instance. 120
fry69 @fry69.dev · 13/09/2026Do you think this is the right trade-off? How many PDS are out there that share IP addresses? Maybe @pds.dad or @mackuba.eu know? I'd rather err on the side of preventing an annoying scammer/spammer flooding the network. Also think of the constant moderation load: 430
fry69 @fry69.dev · 13/09/2026Currently scam accounts get banned after a while, but then the damage is likely already done. The notifications got sent out to mobile devices, people may have looked and followed the scam link. Bluesky/atproto is a very fast network and it only takes a few "conversions" to make this profitable. 120
Ducky 🦆 @ducky.ws · 13/09/2026Its a shame I can't use a labeller with @graze.social. A few labelers I subscribe to have picked it up now as engagement hacking and/or spam: it'd be nice to feed that data to the feed. 040
Spoopy Foxhack / Dave Silva @foxhack.bsky.social · 13/09/2026The other alternative I can think of is immediately banning an account if they spam a known scam url. But that would require effort on the part of this site's owners and they're too busy banning people for criticizing rich users. 000
Bailey Townsend 🦀 @pds.dad · 13/09/2026I take IP ban approach for selfhosted >.>. Always a bit of a fear that there will be collateral since some places blank share IPv4s...but I'm on a small enough scale that it's usually beneficial for the server to be possible and I have contact information out there if someone needs it and an error 040
