"SIWF is actually Sign in with Warpcast"

1. The AuthKit library is open source -- anyone is free to fork it and make it work with their client. https://docs.farcaster.xyz/auth-kit/

2. The long term goal is to make it work with any "Farcaster wallet", i.e. apps that can handle all the Farcaster-specific signatures and transactions for using the onchain / Hub identity system.

3. SIWF is currently an extension of SIWE (Sign in with Ethereum). This means you need to sign in with your Farcaster custody address / private key -- which for the vast majority of users is stored on their phone with Warpcast (many in a Passkey).

4. We opted for the pragmatic v1 where it works reasonably well (still some improvements on QR code) for most people in a more human readable way around permissions than a normal SIWE signature.

5. We will eventually add make it support multiple Farcaster wallets, but there hasn't been much demand from users and devs have preferred us to focus on growth.

FARCASTER LOGIN

What is Farcaster good for?

It’s good for devs.
It’s good for data analysts.
And it’s good for social login.

The last is the thing I’m most interested in. 

When you start a new site you can use Google or Apple login. And that’s fine. But it just gives you an email. And maybe Google Drive access in Google’s case.

You can also use X/Twitter, Facebook, or LinkedIn. But those APIs change so quickly and adversarially that you can’t really build features on your site that rely on them. So you end up using them similarly to Google login, where you get a username only.

Now arrives Farcaster. The first fairly large scale decentralized crypto social protocol. Where people aren’t in it solely for the money.

Now, for all users who log in with Farcaster, suddenly you can provide encrypted messaging between accounts and pull their full social context. And if they’ve connected a wallet and ENS, they have a balance and can spend and receive money in your app.

This changes everything.

I don't think anyone doubts that y'all are building this in good faith or that the initial centralization is just pragmatism (product led protocols, etc)

But calling it SIWF when it's currently SIWW leads to lost nuance and inflated expectations (eg. cast quoted)

I don't think anyone doubts that y'all are building this in good faith or that the initial centralization is just pragmatism (product led protocols, etc)

But calling it SIWF when it's currently SIWW leads to lost nuance and inflated expectations (eg. cast quoted)

https://warpcast.com/balajis.eth/0xdfcfcafd

See point 1. Any client is free to implement the core part of the standard and convince other apps to use it. It works for any Farcaster app that wants to do the work.

I don't want to shift my liveness risk to another counterparty, I want to avoid liveness risk entirely

I know y'all are going to get there, but #1 isn't sufficient to address the current risks