A lot of it seemed like entrail-reading to me while engineers who were experimenting with totally new approaches were discounted. That’s what I like about #nostr - we can experiment before the majority users show up, asking for more of the same.
McDonald’s is a real estate company.
All the stuff I’ve seen on key rotation using cryptography means protecting even harder the root key. If that key gets leaked, you’re really screwed over.
Posting NIP-60 for handy reference while implementing.
Author of NIP is nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft
Interesting. Now I better understand what motivated all those ‘user-centric’ design folks working on improving unpaid (public) services. They wanted all those people to be part of their product.
I think key rotation (recovery, history) is a higher level service that requires a social component, not just cryptography. My current thinking is baking key rotation into the did:method is a mistake. I think it can be addressed with a trusted nip05 service.
Network routers now have a voice on the network thanks to nostr:npub1vfl7v8fgwxnv88u6n5t3pwsmzqg7xajclmtlfqncpaf2crefqr9qu2kruy ! nostr:note1m67arp35xa8szhsvncxuctvvs25qhhzv5spxm52aknvs2yp6fn7srxn4cy
Any hot takes on TBD DWN?
https://x.com/csuwildcat/status/1814321949054763510?t=E3XJFQY8tEaDuThzfv44Ew&s=19
Turtles all the way down...
The key abstraction in #REST is a RESOURCE. Any information that can be named can be a resource: a document or image, a temporal service (e.g. "today's weather in Los Angeles"), a collection of other resources, a non-virtual object (e.g. a person), and so on.
By comparison, the key abstraction in #NOSTR is an EVENT. Any information can be an event: a post, metadata update, and so on. #NOSTR also provides the key assurance of authenticity by requiring that each event be signed by a private key, having a corresponding public key that makes it easy to very and attribute to the actor holding the private key.
With #nostr there is no critical infrastructure
Stateless pairs well with Eventful
Thanks. It’s these types of exchanges that really clarify my thinking. I am really trying to zero in on WTF should I care about #nostr in the face of all those ‘yeah, but the old way is fine.’
I guess for #nostr it’s an signed-event-first model. That’s the innovation IMHO
It’s not actually #REST, it’s the API that’s part of the problem. With an API model you have to depend on an endpoint with stuff happening behind the API that you can’t access. With the event model, it’s all out on relays.