Oddbean new post about | logout
▲ ▼
dtonon | 1 months ago (raw) | root | parent | reply | flag 
 I don't grasp your concerns, why would a relay ever decrypt anything? Can you elaborate?
▲ ▼
Braydon Fuller | 1 months ago (raw) | root | parent | reply | flag 
 For a relay that has your and your networks events with relay-to-relay network topology. I'm working on a tool for strfry that will use a configured pubkey to grab the `kind 3` (NIP-02) contact/follow list and then sync (with negentropy) and stream events for those contacts from their relays defined in `kind 10002` (NIP-65). I haven't added support for other lists other than `kind 3` yet, however it could easily. However, if the list is encrypted, then it wouldn't be able to do that.
▲ ▼
dtonon | 1 months ago (raw) | root | parent | reply | flag 
 Interesting.
What's the ultimate goal of this tool?
▲ ▼
Braydon Fuller | 1 months ago (raw) | root | parent | reply | flag 
 A few things, however, it solves a problem I have now in Amethyst, which is that many notes are only "seen" by one or two relays (and without connecting to many more relays listed via NIP-65 for contacts).

Once complete, Amethyst connects to that private relay (and a few others) and it will stream and sync from many hundreds to thousands of relays. Much more than just a few as it is currently.
▲ ▼
dtonon | 1 months ago (raw) | root | parent | reply | flag 
 > a problem I have now in Amethyst, which is that many notes are only "seen" by one or two relays

This should not be a problem, it is how the Outbox model works. Any other additional relay comes from a broadcast from users that interact with the event and this organically increase the decentralization and reachability of user's content.

It seems that you want to create an hybrid client/really, that actually could be useful in edge cases to support "thin clients", especially on mobile.