The read is in their DB so I’m assuming incompetence of not being able to render nevent links properly

The post actually exists but clients do client things. Ugh

especially would want your opinions:

Ah, no, I’m mostly thinking about a general framework for moderation (3rd party services + user + client + relay), and separate from that a set of baseline rules for *my* part of implementing it, especially as a large relay operator. For doxing, I’d say the expectation of privacy is the important part. Someone that is anonymous + took precautions shouldn’t get photographed at a conf close up without redaction, for example.

To #devstr and vibers: What are your main pain points with Nostr relays and infrastructure like search in general? Looking for some views on this topic (if it’s a vibecoded app, ask your LLM) Please also share this if you think people might be interested.

“Unconfigurable” being the service having a fixed policy. If you don’t want it, go somewhere else. Also, hosting PII is disallowed by many data protection regulations.

gm nostriches 🍍 we don’t have enough long form content, I think

I didn’t, where is it?

With Nostr that barrier doesn’t exist as much.

No we need a STARK and ZK proofs so we can sound cool and quantum. (I wonder if these ZK schemes have been audited against QC risks. I feel like a good chunk will fail)

One of my main goals is to keep the “unconfigurable” moderation as low as possible, like spam, doxxing, CSAM, etc. and allow users to decide whether they want more subjective stuff like AI slop.