it's been 84 years

can we finally decide on noteid, nevent or naddr for post sharing

let's at least have proper foundations set and a common ground to build various clients on

Reply to this note

Please Login to reply.

Discussion

The answer is all of them are applicable

...

note ID is just that, a specific note

a nevent is an extended note ID that *might* tell you where you could find it (it could also be lying)

a naddr is a pointer to a specific (P)REs identified by kind and depending on the kind a d tag, which could be any one of many different notes, but usually the latest one

and also it could tell you where to find it, or not

Consensus is an illusion 🙌

nevent and naddr ftw, specially if they have relay metadata

whatever y'all can find consensus on

IMHO naddr should be used for everything and everything should have a unique id d-tag

just decide on smth, our lovely devs

the users thank you

naddr if you know the person reads it in that client, so if you know the client will make it readable if not preview

Don't make things to easy ok?

I understand why we have all these different encoded entities but all nostr events should be representable with a unified entity. Its weird for users and weird for devs to deal with all these cases when all nostr events are nostr events.

Technically, today every event can be represented with a naddr if it has a d-tag. Not had to put a UUIDv4 on everything. Food for thought.

nostr:nevent1qqsdkxnpthtrtrqeakyzf0czhl2vfvjav7sz8k47g0zmxxh3mse7jsspz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygzu2zxrfavgvmk8xsd27yxvrt6jay3jhw0ct8ypq099ane24yal0qpsgqqqqqqs09m83z

Lol

That idea is sinking faster than the titanic. 🙃