Nostr Web Client

Why would I trust that a relay would hold kind:0 indefinitely? I don't think that's a requirement. Moreover, relay X may have started long after any kind:0 for user xyz was sent, so it may never have that kind:0 for user xyz.

Is it more private to use a kind filter? I don't see why. If the data is available, it's available.

Is it more efficient to use a kind filter? I suppose, but the traffic of metadata messages on the network doesn't seem particularly burdensome compared to the event traffic.

The more-speech use-case is apparently quite a bit different from some other clients. Some clients treat nostr as a kind of twitter replacement. But more-speech uses nostr more as a news channel; a place for longer articles and prolonged threaded discussions.

As such, more-speech does not use the REQ filters to follow users. Rather more-speech gathers every message on the network, and then allows the user to pick and choose which users and topics they wish to follow by separating them into various tabs on the screen.

So, if I want to see all the 'bestofhn' stuff, I can go to that tab. If I want to see 'RobosatsOrderbo' I can go to that tab. Indeed, I have a tab set up for this particular discussion.

>From: Giszmo47 at 07/29/22 09:58:43 on wss://nostr-relay.wlvs.space

>---------------

>For that you use a kind filter. Get all replaceable events without a "since" and all other content "since" last connection loss - 1day or so. Other clients do it that way and it's certainly more efficient and private.

Leo Wandersleb 3y ago

Organizing stuff in tabs doesn't preclude you from querying kind 0 and 3 without limit for accounts of interest.

Reply to this note

Please Login to reply.

Discussion

40e162e0... 3y ago

I do this, using a since date for kind and the relay.

unclebobmartin 3y ago

>From: Giszmo47 at 07/29/22 10:59:39 on wss://nostr-relay.wlvs.space

>---------------

>Organizing stuff in tabs doesn't preclude you from querying kind 0 and 3 without limit for accounts of interest.

True enough, but separately querying kind 0 and 3 doesn't help me much either. In more-speech I keep my own list of profiles. Once I see a metadata event, I record that profile and never forget it. So I never need to explicitly ask for kind 0.

Having said that, I can see an advantage to allowing the user to asks for all the kind:0 from the beginning of time to gather up all the users that the relays know. I may have to implement that at some point.

As for kind:3, I really don't know what to do with that. I mean, why do I want to have some relay hold my contacts and pet names for me. I keep all that in flat files on my machine. Yes, I suppose it would be convenient to pull that down into a new client but I'm so far away from needing that kind of ability that it's not real high on my priority list.

Leo Wandersleb 3y ago

People change their metadata and querying all kind-0 of all users you know costs the client 1s and maybe 100ms CPU time.

40e162e0... 3y ago

For twitter like kind 3 is good to mimic follows but yep I don't see why a client would always want to store contacts publicly like that.