I would really like to see a NIP where each follow is just another event. The contact lists seem kind of orthogonal to the rest of the protocol and are one of my least favorite aspects of its design.
At least for something that is updated very often.
reply
Likes are more trivial than contact lists and take way more space.
Maybe the spec should've encouraged relays to make at least one backup instead of a SHOULD delete past contact lists.
reply
Never paid attention to NIP-02:
Every new contact list that gets published overwrites the past ones, so it should contain all entries. Relays and clients SHOULD delete past contact lists as soon as they receive a new one.
That update probably made it to all relays which means my data is permanently lost.
It's very kind of you to say least favorite, I would say it's terrible design. Any client you authorize to sign gets full access to perform any writes and in this case can make you permanently lose data which is a form of censorship.
reply
Technically, any event on nostr could be removed by a client that you give unrestricted signing access to (assuming relays respect delete requests ... which the earnest ones probably do).
Browser plugins and clients should probably treat this kind as more special though because the design is extra brittle ... I suspect this was a bug/accident on the client and not intentional. It's a foot bazooka.
reply