jb55 on nostr

I’ve never seen so many angry people just for suggesting not having amber support.

Damus Android’s chrome is being designed as the signer, and our hosted micro apps will communicate with the chrome for signing. This is no different than a browser with a signing extension, except the signer is embedded in damus in an isolated fashion.

We’re designing damus so that it can securely host multiple micro-apps for multiple platforms, and it will not depend on any external apps for its core function.

1469❤️23🤙18🚀5👀2💜2♥1

Danny · 34w

Sorry Will I respect your opinion and love the work you're doing with notedeck but you're wrong here. Remote signers like Amber give you more security and flexibility. I get why you're not building it, it does add complexity with the way you've been building the app, but it'd absolutely worth it b...

Tim · 34w

Why is the being called Amber support? It’s Nip-46, hopefully there is more than just Amber someday.

semisol · 34w

you could create a signer process, give it some socket FDs, and then the signer process assigns privileges to each FD + locks itsslf down then the main process passes the FDs to the different processes

Max · 34w

So add the signing logic of NIP55 to damus, so that it can be used as signer for other apps. Now all apps that do use amber currently, work out of the box with damus as signature provider.