Similar to the three-dimensional Cartesian coordinate system (x,y,z), #Nostr can be thought of a non-Euclidean cyberspace coordinate system of (n,e) where n is a 32 byte #npub, and e is a 32 byte hash of an event.
With (n,e) you can reference and attribute anything in cyberspace. That’s all you need for a standardized coordinate system. With #Nostr, you get some additional nice things like Schnorr signatures and and event kinds, but these are conventions, not core to the standardized coordinate system.
Thus, in the physical realm, you have (x,y,z) and in the digital realm (n,e).
Time (t) can be added, but that’s a function of the observer.
Nah. You can do full Cartesian plane using nostr too. #cyberspace protocol by nostr:nprofile1qqsw3mfhnrr0l6ll5zzsrtpeufckv2lazc8k3ru5c3wkjtv8vlwngkspz9mhxue69uhkummnw3ezuamfdejj7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uqsuamnwvaz7tmwdaejumr0dshsq9cn9q outlines this well.
Oh, cool! Can you give me a link?
https://github.com/arkin0x/cyberspace
Great stuff!
I have a simpler conception, though.
i-space only with coordinates (k,e), where k is public key with private counterpart, and e is events (versus notes). d-space is not really needed as an an event in i-space can correspond. Also, all entities can be distinguished with a k.
In the end, similar model: I just have a simpler conception
Oddbean new post about login | logout