Subnostr

Thanks #[1] for your great speech at #nostrica! It was very interesting, eye-opening and covered so many important topics, in which Nostr needs to advance. Thank you!

One quote that I find particularly important is about offensive and abusive speech:

"There are parts of Nostr that are incredible offensive and abusive. And when you make death threats that's not neutral, you are doing it to silence someone else's speech. […example post…] That's not okay, that is silencing. We need to build tools that let people use these platforms in a way that does not silence them. And We need to build tool on the relays, in the apps for the user to solve these problems. If we don't solve these problems we won't get widespread adoption."

https://nostrworks.com/images/nostrica-2023-rabble.webp

Reply to this note

Please Login to reply.

Discussion

Peter Gerstbach 2y ago

Inspired by #[1]'s #Nostrica speech (see #[2]) I queried my relay, if anybody reported something. Turns out I have only few reports, mostly from 2 users on my relay (thanks btw). But to be honest it is super hard to read them without proper tooling:

1. Login to the server (running nostream in my case)

2. Connect to the database

3. Query the reports, I used:

SELECT first_seen,event_pubkey,event_tags,event_content FROM events WHERE event_kind=1984;

This gets me the date, the reporter, and the event tags which contains the reported profile and/or note and some additional text, which was always empty.

4. Manually look up the profiles and notes in a Nostr client

I did step 4 for some reports and it showed that not a single event was actually stored on my (paid) relay.

So we really need additional tooling to make moderation even possible. It is not, right now.

Some ideas:

a) Only post reports to relays that actually have the event in question (maybe this recommendation should be added to NIP-56?)

b) For a start relays need some simple ways to query reports and show the linked content. My current approach is not feasible long-term, obviosly.