I've was watching the workflow page over the weekend. Wow 👀😂

Protects against crashes when the signer sends an unverifiable payload back to Amethyst Sir what is this? Like if signature is bad or event is malformed? Which signer does this?

Many signers do it. You need to verify the signature all the time.

👀

i worry that @greenart7c3 needs some help with manual amber.. from you guys. I see utxo has given up already, supporting it (maybe jokingly, but users told to accept all). And amethyst still is broken as well. Mostly when using DMs is what I see. I really think this is important and I love seeing what I'm signing and approve for time window etc.. Is this an unsolvable problem because of android architecture or is it just that more integration testing and fixing is required?

It's just so much work to build happy paths for every type of permission being approved/rejected, it's too cypherpunk

@utxo the webmaster 🧑‍💻 sending sats to @Vitor Pamplona for @Amethyst . This is how we grow.

I love Vitor and amethyst I still use it, doesn't mean we can't tease each other, like bmw and Mercedes

Its payment for copying our ideas.

Well, as long as the app is satisfied with blanket reject for all nip44 encrypt/decrypt, I can settle for that. Wisp seems to function ok in this mode (eg. DMs turned off). Unsure about amethyst. Curious what @Vitor Pamplona thinks. Are we too cypherpunk? :claudemax: :thisisfine: