jb55 on nostr

Open in Damus

@jb55 1756599319

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.

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

freemymind 🇨🇭 · 30w

I like the use of Amber. But. also like developers, which have the guts to try new stuff. When Amber will be hacked before Damus, you will might be true. When there is an exploit on Damus, it will be might been a stupid idea. When nothing of it will be exploited, then it will probably only be a ...

it's probably friction an android the majority of nostr users already use amber. To try out a new app with amber it's just one tab vs do I trust this app? where is my nsec, copy paste

the axiom · 30w

what about bunker support?

Amber is good because you can be very selective of the events you choose to sign. For example, I think Amethyst drafts suck, so I kill them with Amber. And for the first time, this security model is even possible. It's a shame not to even consider it, and stick to the idea that external dependencie...

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

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.