what do people on nostr (and hence who presumably enjoy it and are getting value from it) make of the whole DID/web standards/key rolling critique?
it seems to have become oddly partisan wherever you look so I’m keen to crowdsource some thoughts that may well be passionate but are at least also sober and disinterested …
Unsure of what specifically u mean by did/web standards/key rolling
He’s referring to this
https://twitter.com/level39/status/1632240495396044800?t=18hzKUv7O9UTfwHkllljcA&s=35
I don’t mean any specific thing, but see this (very long) twitter thread for a flavour of what I’m getting at:
No comment on DID. But nostr needs a better key scheme with delegation and the ability to rotate keys. No doubt about that.
100%
I've discussed this with fiatjaf, and he argues that nip-26 delegation token revocation can't be guaranteed;
I still think it should happen:
* nIp-26 delegate key to a new pubkey
* if pubkey abuses, delegator creates an opentimestamped event revoking and blasts the revocation to all known relays
* if delegatee continues to abuse delegator has timestamped proof that abuse was not authorized by the delegator
furthermore, we need nip-26 to be extended to allow scoping the token further
right now we can only limit created_at and kind
we should have the capability of scoping `content` (https://github.com/nostr-protocol/nips/pull/222) and `tags`
Well, I didn't say NIP-26 is ideal. :) Delegation that is only valid for a limited period of time might be better; OTS+random beacons can likely help that.
I'm not technically knowledgeable enough to know how much of an issue it is, but I read the thread and it appeared a bit of a storm in a tea cup.
You have stolen my dreams. How dare you
Fiatjaf has talked about DID being OTT in the past. DID guys have argued it’s naive to not have all the protections that come with these open standard frameworks. So I would like to think that as the most popular use cases of these keys becomes apparent (pubkey vs DID)then the maturity of the key infrastructure is better and it’s more obvious to merge / migrate to the winner.
Implement DID can permit to some participants to chose a method provided by Ethereum like the case of NIP-05 trough "ethnostr.com" using "MetaMask", spitting on "sovrin" method defined by (Augmented Backus-Naur Form).. Simply because “w3c” has knowingly declared war on the Bitcoin protocol & hopes to compromise the future scope that “Internet” can have by imposing “specifications” that will benefit other crypto-ecosystems that will have to bend under their requirements. This would be an imposture & a betrayal on the part of the “Nostr” devs towards the proto-ecosystem.
w3c’s recommendations have been widely adopted by governments & regulatory bodies worldwide..
Don’t remplace the Web with "insanity".. Why no Bitcoin integrations into Browsers ??
I think it’s interesting 🧐 but I feel one thing that NEEDS to happen in this space is a more formal ironed out approach to discussion. I’m not a btc dev so forgive me if my ignorance shows, but how people interact sometimes seems really counterproductive when both sides intend good (mostly).
So if there was an official platform where issues can be clearly and without bias, be explained to everyone, the pros and cons, I think more would be achieved. At least it would allow people to feel heard, even if they are untimely ignored. I feel that if people feel ignored from the start, they take to Twitter to rally support and it becomes an argument. That’s essentially what the courts are supposed to do. Provide a place for things to be aired and at least an attempt to resolve. So maybe before we talk about DID’s, drive chains and soft forks we start developing a ‘public square’ where things can be presented with manners and evidence, devoid of degrading replies and swearing at each other lol 😂. I don’t think Twitter, or Nostr is a place for that. It’s too chaotic.
Outside of that, I do feel that things may need to become more refined as it relates to the keys, as it’s seems very geeky right now, something that bitcoiners would get but nocoiners may struggle, and it essentially comes down to UX, which is the most important thing imv.
That’s all I wanted to say.
I'm sure we can find a way to bury ourselves with all good intentions.
Alan Kay was able to break the glass ceiling!
https://www.quora.com/Should-web-browsers-have-stuck-to-being-document-viewers/answer/Alan-Kay-11
nostr works. key management is a problem. it can be extended over time with or without DID.
this
doesn't need to be solved on layer 1; we just need better key management solutions on the protocol; identity belongs in a higher layer
Key management in nostr has a long way to go but it's based on a very simple design. This has allowed it to gain adoption quickly. It's a bottom up approach, solving problems if/when they surface.
The first DID specification was published in 2018. It's a noble effort where every edge case is being carefully considered.
My take is the DID team looks at nostr and says: "You clearly do not understand, it's not that simple"
Meanwhile nostr continues growing because developers have something easy to get started with.
nostr now has the advantage of developer adoption combined with increasing user adoption. History shows that momentum has no regard for technical purity.
Both ecosystem (Nostr & DID w web5) will serve various use cases and even when both are heavily used, we would not have reached out to the 70% population on planet that struggles everyday today. Tech bros are like avengers all with diff super powers but gotta zoom out of their nerd cave every now and then, and see the bigger pic 😬
