#[0] are damus bookmarks local only or sent as an event to relays?
Login to reply
Replies (11)
I’m changing them to encrypted bookmark lists. They are local only for now.
Ah nice thanks! Is the list gonna be one single encrypted json object or every bookmark as its own encrypted bookmark event?
Same question here. I am implementing similar features in Blowater and would like to be compatible when reasonable
Single encrypted bookmark events are probably the better solution, since it‘s less taxing on the relays (pagination etc.)
Single encrypted json object (list of event ids)
Whats the reasoning behind this? Isn‘t there a danger of these event list objects becoming too big? Most of the time users probably want to look up their most recent bookmarks, so there is no need of downloading the whole list (so single encrypted events & pagination would be beneficial here)
The main reason you do it this way is so you can replace the list with a new one when you add or remove stuff (via the replaceable list spec). If you have them as separate events they aren’t as easy to remove.
Hmm yea you‘re right the deletion aspect is kind of tricky with single events 🤔 one way of solving this would be to create addition and deletion events, and bookmarks which are followed by a deletion event would then be hidden in clients
@jb55 After I log off and log back in, New version of #[4] not displaying .gif for me. I have to delete cache every time
To make it work again.
But this will introduce more inconsistency if a user uses multiple devices with different relay settings.
True, there is a danger of inconsistency. With the information from NIP-65 the bookmark list could be recreated pretty accurately though