Farcaster Devs

Neynar

We got a fair number of asks for two things:

1. Developer branded signers for SIWN - so it says "sent from [developer_brand]" instead of saying "sent from neynar"

2. Using SIWN inside mini apps

Both are solved now! 
- mini app developers can now use SIWN to get permissions without leaving the mini app to an external web page
- developers get their own branding

https://docs.neynar.com/docs/mini-app-authentication

In order to get the above benefits, the flow does require slightly more work than earlier (don't worry the earlier approach is still around if you need it). 

If you implemented SIWN previously, you don't have to many changes as a result of this. What you have will continue to work. If you're building new, there's more functionality available now. 

h/t @shreyas-chorge for the work and reach out with any feedback 🪐

We've made managing and using @farcaster signers quite simple, but requesting permissions for signers is still a complicated UX to build. 

We'd seen the hard work @ampsfun, @dashapp, and others had put in to get a system for sign-in + signer approval going within their mini app, and decided to simplify it to the point where it's as simple as a component.

It's secure - the signer identifier and API key never touch the client.

It'll work across 
1. Farcaster - iOS & Android apps + desktop web.
2. Web app - desktop & mobile. Yes, it works outside the mini app context as well.
3. @coinbasewallet - iOS and Android apps coming as soon as they build the signer approval flows. cc @aneri.base.eth @dylsteck.eth :)

🪐

A sufficiently decentralized social network. farcaster.xyz

product lead apps, social, and creators @base

A mini app for exploring videos on Farcaster! — Follow /dash for announcements, updates and discussions around the project.

We've made managing and using @farcaster signers quite simple, but requesting permissions for signers is still a complicated UX to build. 

We'd seen the hard work @ampsfun, @dashapp, and others had put in to get a system for sign-in + signer approval going within their mini app, and decided to simplify it to the point where it's as simple as a component.

It's secure - the signer identifier and API key never touch the client.

It'll work across 
1. Farcaster - iOS & Android apps + desktop web.
2. Web app - desktop & mobile. Yes, it works outside the mini app context as well.
3. @baseapp.base.eth - iOS and Android apps coming as soon as they build the signer approval flows. cc @aneri.base.eth @dylsteck.eth :)

🪐

Building /neynar 🪐

We’re hiring staff software engineers, check out neynar.com/careers

these apps need to call sdk.actions.close after the openURL the deeplink, because the farcaster connect signer requestor opens behind the app

Elevating onchain creators 

@nodefoundation @brightmoments 
@ampsfun

I just want us to have fun | Cofounder @ Resolve (YC) - spatial tech for construction. FC tinkering: @livecaster @harmonybot | Ask me about /f1 /vr /orange-dao

ah ok I see. is this right?

- click create signer (or whatever prompts the signer flow)
- redirected to browser via signer link
- browser redirects back to FC via deeplink
- when you land back on FC the signer approval isn't visible because it's covered by mini app

android. showed a QR code, but the deeplink opened behind the mini app, so had to close the mini app

i think this is on farcaster end though, the signed key deeplink doesnt behave like other deeplinks that would minimize the mini app

also weird behavior between Android and ios, have found farcaster:// to work best and /~/ routes to sometimes work on one but not the other

will send a vid when i can

On Farcaster this happens? Mobile or PC?

I haven't had any reports of this. I've observed openUrl redirecting to the  browser outside of FC which then redirects back to FC approval page. 

Do you have a video? That would be helpful!