opencast

cross platform login with a single signer and no backend has been achieved internally via largeblob 

(proof of cross-platform in reply)

Nah I’ll add links to the docs I used in the code but it was a lot of trial and error. Might look for a library that makes it a bit cleaner and does better feature checking but the window.navigator.credentials call is quite simple 

Trigger warning: spaghetti code

I like baking /goodbread and building apps on web3 protocols. DevRel @ ENS Labs. gregskril.com

Nah I’ll add links to the docs I used in the code but it was a lot of trial and error. Might look for a library that makes it a bit cleaner and does better feature checking but the window.navigator.credentials call is quite simple 

Trigger warning: spaghetti code

 https://github.com/stephancill/opencast/blob/main/src/lib/passkeys.ts

v cool, is there a library or something you used for interacting with passkeys?

Building a swarm of beautiful agents in A0x

https://a0x.co/

React Native Developer. Experimenting with consumer apps.

lol it's just a joke reference to sam altman's "AGI has been achieved internally" i.e. i'm still busy working on it

the problem is when you log into opencast on one device and create a new signer, it stores it in your browser's local storage because opencast has no backend. so next time you want to log into opencast on a different device you need to create a new signer for that device, which isn't free ofc

what this does is it allows you to save your signer to a passkey so that when you access opencast on another device you can simply load the signer key that was stored in your passkey and log in for free

the lego blocks are coming together

what does achieved internally mean? can you explain more what is happening here and what does it mean to have done this?

you are doing work that is fundamentally valuable. thank you. this is extremely motivating.

cc @natedev.eth @cristianvaldivia

personality hire 🌈🤙 fullstack & ux, building /uno

Basically. Key generation happens locally, and then it sends the pubkey around for sigs 

Currently it’s just a button in a menu somewhere after you sign in. Will add to the create signer flow, but warning that support for largeBlob is kinda dodgy if you don’t use a password manager so it’s not fullproof 

Here’s the passkey business logic (can do with some refactoring and cleaning up still) https://github.com/stephancill/opencast/blob/main/src/lib/passkeys.ts

Also just a heads up, passkeys don’t like non-https environments so I ended up using ngrok to test

And another heads up, safari requires all passkey calls to be initiated by a user event so I ended up requiring the user to create the passkey and save the signer to largeBlob separately (https://github.com/stephancill/opencast/blob/main/src/components/modal/save-passkey-modal.tsx) there’s probs a better way

Trigger warning: lots of spaghetti code in this repo lol

I implemented wallet and warpcast signer flows. Wouldn’t copy and paste my implementations though lol

are you using the sponsored/unsponsored signer flow from Warpcast to generate the key pair? 

cc @erica we will add this in to the auth flow

16872 $DEGEN bruv mad shipping this week (UK slang to get over the UK referee yesterday)

musican. ai artiste. 

designed the channel icon for /relationships

lmao did you take twitters css and plugin farcaster instead?!

because that’s fuckin awesome.