Nostr Web Client

I haven's spent much brainpower on it, but isn't partial results the default? In my mind it's ok if relays withhold some events without telling the user, because no relay has a complete dataset. Communicating that that's happening, and how to get around that is harder, but maybe a job for LIMITS or nip 11 or something.

Mike Dilger ☑️ 10mo ago

I'm having this kind of failure with nostr-sdk (rust):

client: REQ sub1

relay: AUTH

relay: EOSE sub1 (no events, all redacted, but stays open due to nature of the filter)

client: CLOSE sub1

client disconnects and fails to return the event.

The client has a signer that is allowed to read the event, but it is not using it because it looks to the client like it wasn't there and the client was never informed that maybe it was redacted.

Reply to this note

Please Login to reply.

Discussion

hodlbod 10mo ago

Ah, I see, the client would have to block on auth in order to make sure it got the maximum results. Hmm

cloud fodder 10mo ago

yeah, its quite insane.. glad to see someone thinking about how to do auth in a client because i think the big pushers of partial/redacted just didnt want to implement auth at all. so it remains open for them while everything gets more complicated on the auth side.

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 10mo ago

IMO nip-98 on the connection right at the start or no beans