ba
ba6afb68
ba6afb688488572c58071e9ad9980359aa66d6759107b10ce0ad7954f134f2ed

Ok, that sounds like you want to ignore the problem. That is fine. But good clients and good relays will figure out how to block this horrible stuff no matter “where” it is hosted. Many relays seem to do a fairly good job of blocking bad things from their global feed. This takes time and effort, so this indicates that people like Nostr.band who provide a clean feed have made a decision to fight this and have taken time and effort to stop it. I guess you have put in some effort to build Damus and would not want to have it brought down because you came ip with a clever “we don’t host it” argument. Anyway, I care about the NOSTR ecosystem. Trust me, this is your problem, and a problem for everyone spending time and effort on NOSTR. Anyway, it would be great to see NOSTR publish a list of “safe relays” and it would be great to see clients actively preventing their users from accessing this stuff. I don’t like raising these issues and I don’t want argue about this stuff . I want NOSTR to succeed! This is my last message about this.

Hey! NoBody! I have invested a ton of time developing for NOSTR. I am fixing a bug for Damus. Just go to Damus and search for #child . Do you think that is a good look for NOSTR? If you want NOSTR to succeed you will take an active stance against this. I guess the NYT would write an interesting article if they got on Damus and started looking around. How about Tim Cook? Want to latch the bug before Tim Finds it? FUD? How about thank me for the big fix? Pretty big bug if you ask me! @fiatjaf

Yes! Could you put together a list of “safe” relays? nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s can you block hashtags in Damus? You might think you don’t have a problem on Damus, but search #child and you will see that you indeed have a problem!!!! NOSTR cannot tolerate this. Or at least the leadership cannot condone this