#banlists

Kevin Karhan :verified:kkarhan@infosec.space
2025-10-13

@edwardk I sincerely disagree with the #cyberfascist demands for any #Gicware, and rather want to point out that #banlists for #StolenDevices already exist and it's trivial for the destination country to locate & ban said devices from their network, but the "P.R." #China AFAICT is neither #interpol member nor do they have any #MLAT with the #EU or #UK nor have they ever cooperated with #LEA|s unless they deemed it in their opportune interest…

Kevin Karhan :verified:kkarhan@infosec.space
2024-12-22

@DeltaWye @SynAck @Kuniti_shino @ErikUden OFC that's the nature of most services tht are open t new users.

  • #Abuse being a statistical inevitability:

#Shitter (rather #Teitter before #Mus ruined it!) had #API #RateLimiting to make #Spamming less effective (255 Statuses per 24hrs) even back when #TweetDeck was a seperate company...

  • Making dynamical limits that instantly lockout i.e. brand new accounts sending the same.message to 10+ others as a DM within 48 hours of registration should act as a speed-bump to #Spammers.

It won't prevent it entirely but make it more cumbersome.

This prevents remediation and correction of #banlists & #blocklists, leaving a lot if domains burned forever as the only.options are "replace" and "merge" and the average #ActivityPub admin or even #User isn't going to learn or setup a #git!

  • which is frustrating as I maintain multiple blocklists to help cleaning up the mess.

I.e. there isn't really a good way to combat #Typosquatting-based #Phishing beyond banning.offending domains...

Client Info

Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst