how it's going vs. how it will be
TIDAL support widget:
chatbot vs nostr community support through embedded nostr client https://nostri.chat
cc #[0]
some benefits:
* no more fear of navigating away and losing your chat history with a support rep
* if you don't want to use the chat widget you can continue the convo on any kind-1 app like damus
* other people can help you, not just support reps, can help you (though whitelisted pubkeys can be highlighted as officially part of the support team)
* the knowledge base generated from support tickets is not lost and can be accessed anywhere in nostr
how it's going vs. how it will be
TIDAL support widget:
chatbot vs nostr community support through embedded nostr client https://nostri.chat
cc #[0]
yesterday I went with my family to #[0]'s unschooling meetup in Madeira
one of the parents there was a yoga teacher and did her first LN transaction as compensation for a class
https://twitter.com/RobBrinded/status/1632422392390623232
circular economies, one link βοΈ at a time
thank you, sir -- I'll post the bounty, and I'll put out a zapraiser to see if others want to chip in
want to spearhead the bounty proposal and send a PR to https://github.com/coinkite/bountsr.org.pub ? you have great understanding of the NIPs involved, I'll zap 1M sats to this note to add to the bounty if we go ahead.
you got it; I'll do it tomorrow
#[6] in 14 hours
thank you, sir! π
π―
NIP-46 was merged very, very recently; when I added support for it, it was far from being merged, but I rolled the dice since I wanted to show a real-world use of it
so no, mobile clients definitely don't support it yet
I agree a bounty would be a good idea
you scan the QR code once to do the handshake, then you'll need to approve per-event or grant access to approve always, pretty much like nos2x or alby do
afaik, the only app that enables NIP-46 is #[2] 's Nostr Connect
Not sure about apps that implement it other than mine, like https://nostri.chat
I'll be adding support for it on https://nostrit.com too, and probably to https://ananostr.com as well
nip-26 allows you to create temporary derived keys for signing events in behalf of a root key. nip-26 and nip-46 (derived temporary keys and remote signing) can be combined https://github.com/nostr-protocol/nips/blob/master/46.md#delegate
important caveat: nip-26 delegation tokens are NOT temporary and ripe for abuse if we don't improve the protocol
I wrote about it here:
#[6]
nip-26 allows you to create temporary derived keys for signing events in behalf of a root key. nip-26 and nip-46 (derived temporary keys and remote signing) can be combined https://github.com/nostr-protocol/nips/blob/master/46.md#delegate
for example, when I made this video, nostr connect didn't support nip-26 yet
https://www.youtube.com/shorts/gfItS5Qe6tI
there you can see specifically the functionality that NIP-46 enables
nip-26 allows you to create temporary derived keys for signing events in behalf of a root key. nip-26 and nip-46 (derived temporary keys and remote signing) can be combined https://github.com/nostr-protocol/nips/blob/master/46.md#delegate
exactly, nostr connect supports nip-26 now, but that's a separate functionality
they didn't have a valid LUD16 on their kind0 π€·ββοΈ
losers...
itβs really annoying and flying sansa is awesome and just a few minute walk away from the intl airport
I do not; I was planning on flying sansa to the nearer airport and getting a car from there;
Mainly because I hate driving out of San Jose π
I agree and at the same time canβt stop