working on getting nsecbunker to create one-time-use tokens
you'll enter the generated token on a client and have a policy automatically apply to it the permissions the administrator has granted
here, a policy that just allows using DMs, but can't do anything else:
https://nostr.build/av/1acd661c0a267f3c859ce2cf1e9deadc1a4f5c2479f362d44a315df01d688dea.mov
What do you use for front end stuff, react?
no, I hate react
I reluctantly use svelte because I haven't found anything less bad π
forever grateful to nostr:npub1chakany8dcz93clv4xgcudcvhnfhdyqutprq2yh72daydevv8zasmuhf02 for the tip
You should really name this app nsequestr.
π€
I will probably change the name but not sure what to yet
Zapped you, hopefully it went to the right address π I love love love what Iβm seeing here btw π₯
Could this eventually allow for adding a nostr client to something like Hootsuite or Loomly for crossposting socials?
nsecbunker with granular permissions and policies π± this is what we wanted with NIP-26 Delegation.
Exactly, but this model permits a level of granularity (and full-guarantee revocation!) that NIP-26 could never ever dream of allowing.
I am now doing single use tokens; copy a single code (or scan a QR code) and an entire preset policy is set for that application! π
Do clients have to specifically add support for this though, just like NIP-26? That seemed to be a pain point for that NIP, getting support for it. If that's needed for nsecbunker, hopefully since it's much more powerful, we'll see wider support across the ecosystem.
No; thatβs the beauty of it. No one has to support it (other than the application users want to use) no relay needs to change, no client needs to change.
Iβve been using it for over a month and no one had to do anything.
No one can even tell that Iβm using it to write this very note! π
