pull down to refresh

134 sats \ 6 replies \ @TonyGiorgio 20 Aug \ parent \ on: Private Messaging meta
How are you thinking of doing it? We're exploring combining e2ee / private key management stuff with secure enclaves to add verifiably private and secure use cases to existing applications via JWT / normal user login / oauth.
Could be a cool proof of concept here if you're open to that approach.
write
preview
76 sats \ 2 replies \ @k00b 20 Aug
We would probably use signal’s protocol with clientside key management. We aren’t actively working on it so nothing is locked or anything.
reply
126 sats \ 1 reply \ @TonyGiorgio 20 Aug
Might be able to help with at least the client side key management part. Expecting users to manage, sync, and secure private keys for normal applications (let alone wallets) may be a big limiting factor. Even if you still want to roll your own, would love to chat as you start thinking about it more.
reply
151 sats \ 0 replies \ @k00b 20 Aug
Cool we’ll reach out before we begin seriously working on it
reply
0 sats \ 2 replies \ @Satosora OP 20 Aug
You have to talk to @ek and @k00b for that one. I will ring them up for you.
reply
20 sats \ 1 reply \ @k00b 20 Aug
He replied to me so I was notified. Thanks though
reply
10 sats \ 0 replies \ @Satosora OP 20 Aug
oh right. Sometimes I forget those details.
reply