GM, challenge accepted. Today I will destroy the 16 year old Russian hacker script kiddies on Nostr.

nostr:note149a9s5svlwcmrxd43htz8yl99q6yrjjmqa4xkc6k0tqwrzj02mpqtaagqy


GM, challenge accepted. Today I will destroy the 16 year old Russian hacker script kiddies on Nostr.

nostr:note149a9s5svlwcmrxd43htz8yl99q6yrjjmqa4xkc6k0tqwrzj02mpqtaagqy nostr.fmt.wiz.biz


Godspeed and GM


Godspeed Spider-Man.


GM PV
Happy days

https://image.nostr.build/145389ab82d5f8615d5e53ff47c1b9a4d6e0f3f2972f103c5100bb7b2b039557.jpg


When building a moderation toolset, you want flexible pieces that you can use to quickly adapt to changing conditions.

The problem with this guy is he circumvented all the measures I already have, and I am unable to adapt to it quickly, because I am missing tools that introspect related events.

If I wanted to block this specific person, I would just block by IP. But that doesn't really solve the problem. My goal is not to block this specific person, but to build tools that make it easier to block specific behaviors. That way when he changes his script slightly, I can change my configuration slightly. It should be as effortless for us to adapt as it is effortless for him to circumvent.

All I need to do is expand my moderation tools to be able to fetch the author, fetch the replied-to event, etc. Then I can apply policies to any of those related events easily.

Then we are still playing a cat and mouse game, but at least it's a more fair one. Then eventually he will get bored and move on. But the next person will have an even steeper challenge that discourages them sooner. It's worse when you let them have a taste of it, because then they don't want to give up.


🧡 tesing...

🧡 tesing...