today you have to create a new signer for each device that you use with opencast on, which isn't great ux. would like to experiment with ways to address this without exposing user accounts to the risk of plaintext keys being stored in a centralized db

some initial ideas
1. populate the signer from a passkey somehow (i think largeBlob enables this?)
2. metamask snap for farcaster signers (would also enable you to sign into many apps with the same signer)

lmk if you have thoughts on this :)

cypherpunk wannabe, engineer working on @frames /open-frames /opencast
https://stephancill.co.za create stories at https://stories.steer.fun

Been looking into the decentralised storage world for my own app. Why not IPFS with the Lit Protocol?

26yo Fullstack Developer. Looking for a new job. Building @farlonger.

Haven't used Lit much myself, but the way I get you use the Lit protocol to wrap you data before you store it on IPFS (also believe, it works on-chain). Your data will still be publicly accessible, but thanks to the Lit wrapper it's encrypted.

For a better explanation, there docs seem to be pretty great:

Haven't used Lit much myself, but the way I get you use the Lit protocol to wrap you data before you store it on IPFS (also believe, it works on-chain). Your data will still be publicly accessible, but thanks to the Lit wrapper it's encrypted.

For a better explanation, there docs seem to be pretty great: https://developer.litprotocol.com/

i think passkeys provide a better ux for my use case but this could definitely be useful for something like user configurations 🤔