Nostr Web Client

Thanks, it's of course a work in progress, but nice to see people saying good things about my work.

Coracle does follow the gossip model, but the result is that many times it uses relays based on context rather than your selections. So when creating a new note, it should be publishing to your write relays (let me know if not), but most of the time it will be looking at relays your follows use (for loading feeds), or relays a given note hinted or was found on (for publishing replies). The goal is deliverability, but it's not an exact science. One thing I could definitely do better is keep closer track of relay health and ignore bad connections.

I'm sure there are still bugs, so let me know if that explanation doesn't account for what you're seeing.

nobody 2y ago

I will look at it again later today. Thank you for your reply. The challenges around gossip model are something I am very interested in.

One thing that might be worth considering: on replies (which probably make up the majority of users posts) I wonder if it would be a good idea to send the post to both the poster, and the OPs relays, or a subset at least.

This would solve possibly two issues:

- when you jump to another client (say, on mobile) that doesn’t use gossip method, your posts won’t disappear from your view.

- for people who run a personal relay (on umbrel for instance) as a backup - my understanding is their replies may not find their way to their relay.

Reply to this note

Please Login to reply.

Discussion

hodlbod 2y ago

Currently Coracle writes to a sample of 10 relays, prioritizing hints, but including user write relay selections. So notes should be going to your relay selections (unless you have more than 7-8). The archival use case is worth considering, I do think NIP 65 should be updated to include categories for different use cases beyond read/write.