I love Nostr, think it's awesome in all sorts of ways. I probably won't be using DMs on it in the foreseeable future though, given all meta data is public. I'd rather have a company try and keep it secure with the chance of it leaking increasing by the day than to broadcast it in public. Most preferred solution would be e2e encrypted sockets between clients, somehow, some day.

ctrl+enter test

Got links about existing solutions to mitigate spam on Nostr? Thanks in advance! (already found related issues on Nostr and Damus Github)

Gm! 🤙 Looking for something to read/learn about existing solutions to mitigate spam on Nostr. I found issues on the Damus and Nostr Github with suggestions in them, but was hoping someone could tell me how it works in practice without having to sift through all the code. I would love to run a relay and go through the code myself, but I have too much other stuff to focus on right now, unfortunately. However, I am finding the time to write an article about Nostr and a possible way to add relatively simple and efficient spam and Sybil-resistance that I'll publish here (first!) when it's done. That's why I'm looking for more info to make sure I get things right and to hopefully not waste anyone's time. Hope it'll help, and thanks for yours in advance!