Replying to Avatar allen

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 …
Avatar
Peter Todd 2y ago

No comment on DID. But nostr needs a better key scheme with delegation and the ability to rotate keys. No doubt about that.

Reply to this note

Please Login to reply.

Discussion

Avatar
PABLOF7z 2y ago

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

Avatar
PABLOF7z 2y ago

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`

Avatar
Peter Todd 2y ago

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.

Avatar
allen 2y ago

do you think that is best solved at the protocol level or in some more removed manner that clients can opt into offering for the user and resolving for others? (or some third option that is beyond me at the time of writing?)

Avatar
Peter Todd 2y ago

Definitely needs to be solved at the protocol level.