Test - image uploaded to a blossom server using noStrudel!
Big thanks to nostr:npub1rw7hlhmgat6ur9zxcw40vweem49guv6530yk767j8xjpynv0y20q6qsl3w for spotting the bug in parameterized replaceable event updates! 🙌 I've fixed it, so make sure to download the latest nostr-relay-tray for better experiences. 🚀 https://github.com/CodyTseng/nostr-relay-tray/releases
This bug also existed in https://github.com/CodyTseng/nostr-relay-nestjs and has been fixed as well.
#bugfix #nostr #relay #devstr
🫡
Exactly yes, I was thinking about the phone case. But if you're running on wifi, I don't know, maybe it shouldn't be that much of a difference. I haven't tried NWC with alby, is it much faster?
do yall know why there’s a bigger delay when using mutiny nwc vs alby nwc? nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg
wild guess would be mobile networking vs cloud networking?
spring browser comes to mind
Legend, it was a pleasure to meet you man, safe travels back home and see you later!
"nostrockeeeeeet" 🚀
can confirm that 6cm should be enough
celebrating 50k calisthenics version
#SovEng
"Any time before 13:00 is early" -- nostr:npub1m6z9nxv9tej9wa327qgpkt540m00jswe7gvsc8lvzyyyyr6l8njq6t4ttu
classic H
🤔
I see the risk in this and I think it also applies to other NIP07 applications that can get signatures on notes from the extensions (they could publish fake notes signed by you).
There seems to be no other way than to show the user what they are signing. I wish nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm had a dedicated way of showing details of the ecash that is being signed. Maybe one day?
Definitely needs trust in the application that is requesting these signatures. What's true for signing messages is also true for signing transactions.
Yeah, having a clear UI for the user seems necessary. Anyways, this is great.
nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm extension allows you to produce a Schnorr signature with your on arbitrary data. That's freaking cool! nostr:npub1mhcr4j594hsrnen594d7700n2t03n8gdx83zhxzculk6sh9nhwlq7uc226 is making use of that to spend Pay-to-Public-Key (P2PK) locked ecash in the browser.
What does that mean? Someone can post ecash publicly that is locked to your npub (on nostr or *anywhere else*). Everybody can see it and verify that you're the recipient, but only you (with your nsec) can actually spend it (using Alby) to your wallet.
We're going to use nostr identities for payments and we're not going to ask for permission. 🤙
nostr:npub12rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sf485vg what do you think about the risks of signing arbitrary data? Maybe for this operation the user should always be prompted to confirm? We were talking about this a few weeks ago with nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr
https://github.com/CodyTseng/nostr-relay-tray is great as a local dev tool too
Start Mining in Ember & Earn Satoshis. After Redeem into BTC, Widthraw to Any wallet or Exchange.
✅ Install Ember App n Login
✅ Ragister & Create Username & Password
✅ build Your Team & Do Mining Everyday
✅ REFERRAL id - MNG1MQ12JBU
#BTC
https://emberfund.onelink.me/ljTI/bce33290/?mining_referrer_id=MNG1MQ12JBU
wtf