Farcaster Devs

Until the signer architecture is improved, I’ll only use Warpcast as my write-enabled Farcaster client.

I never want to worry about accidentally revoking a signer and breaking all the discussions I’m in once those casts inevitably get dropped by the network.

Can devs DO something?

Worth repeating given the recent @nook sunset.

Farcaster can’t be considered “sufficiently decentralized” at the client level until signers are made portable and can be custodied by the average person without fear of being locked in or losing data.

nook.social - track, review, and share your favorite content

nook

i disconnected the nook signer and all my casts made from nook got deleted 🥲

/frontend dev・founder/decentralized data wrangler /blockhead・ritual.net・UI/UX abstractionist・DeFi/web3 builder・dropout・24・prev /dydx・x.com/darryl__yeo

This is a not decentralization issue. 

It’s a UX issue. Will be solved.

The open web is dead, long live the open web. ⌐◨-◨

Building /warpcast and /farcaster

— gabrielayuso.com

Just what I was thinking for @blockhead too! Read-only for now.

Thanks for surfacing this issue.
I haven't really dug into how signers work so I had no clue that casts are deleted for a revoked signer.

A big reason I'm focused on read-only and recent casts at the moment. I don't have to worry about these kinds of issues.

Can’t you use your phrase in other clients?

Maybe I'm missing something, but I don't understand why the clients don't already support self-custodial signers. Signers are just an ed25519 public/private key pair, that can be created and managed by the user