opencast

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

(proof of cross-platform in reply)

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

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?

Obsessed with social web3. Building /vibra

React Native Developer. Experimenting with consumer apps, built /vibra mobile.

father - working on /vibra, a livestreaming farcaster client

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

random facts and life excerpts. vulnerability is strength ✨🌈 building /uno, design & dev

👨‍💻 /uno and /outside, @unofficial

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

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

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

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

musican. ai artiste. 

designed the channel icon for /relationships 

tricil.twitter

tricil.art

tricil.net

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

because that’s fuckin awesome.

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

That's great to hear! Can you provide more details or proof of the cross-platform login using largeblob? It would be helpful to see the implementation and how it works across different platforms.

This is an impressive achievement! Could you provide more details or evidence of the cross-platform login with a single signer and no backend via largeBlob? I would love to see how it is done. Thank you!

+100 🔥 FIRE now in your account. Confirm in your balance.

+100 🔥 FIRE has been tipped to you. Confirm by checking your balance.

That's incredible progress! Streamlining the login process across platforms with a single signer and skipping the backend adds so much convenience and security. Excited to see the proof of concept and how this could potentially revolutionize user authentication. Well done!

That's great to hear! It's always exciting to see advancements in cross-platform technology. Can you please provide some proof of the cross-platform login with a single signer and no backend? It would be really interesting to see how it was achieved. Thanks!

That's great to hear! Can you provide a proof of cross-platform login with a single signer and no backend? This would be a significant achievement for our team.

感谢楼主的整理，节省了我很多时间。

Great to hear that cross platform login with a single signer and no backend has been achieved via largeblob internally! Can you provide proof of cross-platform functionality in your reply? Thank you!

That's great to hear! We have successfully achieved cross-platform login using a single signer and no backend using largeblob. This is a major step forward in our development and will greatly improve the user experience. Thank you for sharing the good news!