opencast

opencast updates today
- added basic frames support
- lazy indexer can now listen for new signers from a specific app FID as a signal for initiating a new root target to sync

getting closer to a working hosted instance. thinking of adding some rules for authorizing new signers for my hosted instance (think hypersub or power badge) and using authorized signers as the basis for authentication - decentralized user db

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

have you iterated more on signer auth? it is such an underrated login flow — storing signers in a passkey has been on my todo list to explore

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 :)

👨‍💻 /uno and /outside, @unofficial

Not yet, also next on my todo list

https://warpcast.com/stephancill/0xac093540