Nostr Web Client

Issa a yellow aim icon there.

but here I’m thinking more from the pov of wanting to see a lack of actions by operators who claims that.

I’m no cryptographer, maybe it needs more complications, maybe those complications could be tied to some proof that the operator is in a v4v share with the writer of the implementation, and the receipt key is some derivative, because I’m mostly looking for the absence of action to verify that sales pitch is true.

but maybe it’s as simple as being familiar with how the implementation handles white and black lists and then format those so clients or relay explorers like .watch could surface them in a standard way. Maybe there is a way I can ping an implementation to return the list that I’m not familiar with. But I’m not speaking about making it easy to interope this data else where.

s3x_jay 2y ago

Thinking about it (casually)…

There needs to be a a block list for a relay that could be published under the pubkey of the account designated by the relay. I’d need to investigate the best way. I’d like to see things like a `reason` code that uses the “NIP-69" coding #[2] & I have proposed plus an `evidence` option that’s a comma-delimited list of nostr IDs and URLs that support the decision.

I also want `severity` and `confidence` options. Severity would be scales that define the level of “offense” within a defined category. And confidence would mostly be used by bots (e.g. they think they see nudity but they’re not sure).

Thoughts?

Reply to this note

Please Login to reply.

Discussion

yunginter.net 2y ago

the idea I’m presenting here is entirely aside from labels

s3x_jay 2y ago

I’d like to get it right the first time. Even if the details are worked out later.