I was looking at the NIP for the kind3 following list and it says the content field should be left empty. This seems like a perfect sport for an encrypted contact list payload, no?
Is there another NIP that defines an encrypted contact list standard?
#asknostr
Login to reply
Replies (5)
I built this functionality into Taskify for syncing the contact list between devices. Maybe it can become cross-compatible if more apps adopt it.
https://taskify.solife.me
nostr:nprofile1qqs9ajjs5p904ml92evlkayppdpx2n3zdrq6ejnw2wqphxrzmd62swspzemhxue69uhkummnw3ezumt0w46x7m3wv3jhvqgdwaehxw309ahx7uewd3hkce8zcw6 curious what you think about this, from what I can tell your private contacts are stored locally? Are there tradeoffs you see with this implementation?
0xchat uses the NIP-51 list to store the encrypted contact list.
Follow lists are kept as dead simple as possible, so that it can be reasonably expected for all clients to implement them.
We already have a lot of issues with follow lists getting nuked because a client can't find the user's most recent follow list, so it just generates a new one. Imagine the insanity we would have with some clients respecting encrypted payloads in the content field while other clients don't, and just dump the information whenever you follow someone new from their client...
That’s a great point, about the content field getting dumped with updates. That alone makes my solution impractical. Thanks for your insight! After hearing this I see why it would be preferable to just use NIP-51 lists.