Avatar
franzap
726a1e261cc6474674e8285e3951b3bb139be9a773d1acf49dc868db861a1c11
Building nostr:npub10r8xl2njyepcw2zwv3a6dyufj4e4ajx86hz6v4ehu4gnpupxxp7stjt2p8 and #purplestack | BA 🇦🇷

I meant as a signer but nevermind. We'll implement it and hit known NIP-46 signers

Actually 😆 just way more simple

nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z while brainstorming ways of prompting a developer (or anyone, really) to sign a pre-populated event, Neil mentioned this idea of sending a DM with the event. An app like Amethyst would pick up a certain format an prompt for signature - as it has access to the nsec. How does my note above sound as a super simple protocol?

Replying to Avatar Niel Liesmons

nostr:npub1wf4pufsucer5va8g9p0rj5dnhvfeh6d8w0g6eayaep5dhps6rsgs43dgh9 it's this kind of DM frame that I was talking about. For Zapstore it'd have a "Confrim & Sign Release" button or sth like that.

Also, if you do know of a way to do this without having to run web-stuff (html, ...) 👉 let me know.

A link (that Amethyst etc would know how to interpret) can be an option, avoiding the whole frame things since it's just one action anyway.

That DM action seems to be something different. Maybe as simple as:

- when receiving an unsigned (partial) nostr event via DM, prompt for signature

- probably integrate WoT checks as it could be dangerous

Replying to Avatar Niel Liesmons

nostr:npub1wf4pufsucer5va8g9p0rj5dnhvfeh6d8w0g6eayaep5dhps6rsgs43dgh9 it's this kind of DM frame that I was talking about. For Zapstore it'd have a "Confrim & Sign Release" button or sth like that.

Also, if you do know of a way to do this without having to run web-stuff (html, ...) 👉 let me know.

A link (that Amethyst etc would know how to interpret) can be an option, avoiding the whole frame things since it's just one action anyway.

Love the idea. I think widgets is a good term. I wonder if nostr:npub1p4kg8zxukpym3h20erfa3samj00rm2gt4q5wfuyu3tg0x3jg3gesvncxf8 's hypernotes that he demoed in Madeira would be interesting to consider.

Just spent a little time trying to find a more suitable/constrained language for this but can't find anything better than HTML (and probably JS). The majority of runtimes support web, maybe not ideal but best we've got I think

Wen airplane-mode-maxis community?!

Just tried to purchase my flight, 20 minutes filling out stuff to get to "not possible, return to home page" and start all over again.

No explanation on what went wrong. Nothing. Credit card on my name, usual setup. Didn't like my IP, issue with my bank, was I blacklisted, what is it?

So found Travala and purchased with Lightning... easy! Very cool. Using them moving forward. FIAT AIRLINES GFY

Thanks. I'm gonna look up who TF Gary Cardone is

Going over the README of AppVerifier

Similar to zap.store but using centralized trust, recommending to verify their APK on Bluesky, and asking for donations in Monero.

Nostr allows solving this problem in an insanely smoother way

https://github.com/soupslurpr/AppVerifier

Actually zap.store should handle this case well, but it doesn't. It's interesting because it prompted me to find a solution to the problem of what will happen when users start publishing apps with the same identifier (that will 100% happen when we open up)

Sounds good. It doesn't matter if the SMTP server is open source - we still need to trust the operator. The only thing that fixes that is your reputation (open source helps there but probably not enough)