Nostr Web Client

>if the nostr profile event contains all the outbound references to other protocols, teh other protocols can just refer to it and cover all bases.

You cannot just refer to a Nostr profile event. It can exist at the same time in x different forms and x different places. It's like referring to the health status of Schrödinger's cat.

The whole reason PKDNS exists is to solve the "refer to it" problem.

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 5mo ago 💬 1

that assumes that you don't create push or pull schemes to sync them

i've been saying it maybe 6 months that "directory" events need a strong consistency consensus. this means broadcasting them and fetching them and keeping the latest versions, at least.

that's user metadata, follow and mute lists, relay lists, there is probably others that need to be added to that list but until the nip guardians and their fans recognise this, it's just gonna be me saying it.

it has to be recognised eventually. we don't need to broadcast everything, just the map.

Reply to this note

Please Login to reply.

Discussion

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 5mo ago 💬 1

also, PKDNS is a consensus, which means that everyone has to follow it, or it doesn't work.

that's not how nostr works. nostr is only a protocol, not a consensus protocol. there is good reasons why you might not want to use the same protocol. like closed and private relays, companies will not want this information broadcast either, if it links to the company. the users directory events, though, are perfectly fine to be pushed and pulled from company relays if they decide to, it just leaks membership.

Garbage nsec 5mo ago

> companies will not want this information broadcast either, if it links to the company. the users directory events, though, are perfectly fine to be pushed and pulled from company relays if they decide to

All of that is perfectly achievable on PKDNS/PKARR/PUBKY though.