Code Puppet on Nostr: nostr is not for deleting. I’m starting to think it’s also not for ...
nostr is not for deleting. I’m starting to think it’s also not for “unfollowing”. Following, and the opposite of following would be muting. To “unfollow” is to “mute”. Relays would always MERGE the contacts when different lists are found for the same pubkey, rather than using the “newest” one. To preserve censorship resistance, it should be easy to switch between clients and relays. It currently seems easy to lose your list of contacts if you switch either one of these due to the way clients are supposed to manage the contact list of a pubkey. Just my 2 cents.
Published at
2023-01-18 00:03:38Event JSON
{
"id": "79da5ea7762952aed744a22ff08e47e56c268ce522ceceaaf52c8d25f98857d8",
"pubkey": "0db80fa91e2ea00bd9b64364d289b4dfaebe19587043f12206ada163ccfad7bd",
"created_at": 1674000218,
"kind": 1,
"tags": [],
"content": "nostr is not for deleting. I’m starting to think it’s also not for “unfollowing”. Following, and the opposite of following would be muting. To “unfollow” is to “mute”. Relays would always MERGE the contacts when different lists are found for the same pubkey, rather than using the “newest” one. To preserve censorship resistance, it should be easy to switch between clients and relays. It currently seems easy to lose your list of contacts if you switch either one of these due to the way clients are supposed to manage the contact list of a pubkey. Just my 2 cents. ",
"sig": "d9a12ecc41ce2cbfbc3eed67fe2a5344be4b45a8e327885332bd9b2b68e0289e1e00a4d1e54881cc952bf015791f5c6f7c129cd24670ee0b304e9873f925f218"
}
