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

𝚆𝙾𝚁𝙺𝙸𝙽𝙶 𝙾𝙽: @vision 👁️ ✦  ensdata.net ✦ pugson.net/rfe ✦ 𝙿𝚄𝙶.𝙴𝚃𝙷 ✦ 𝙿𝚁𝙴𝚅: @rainbow 🌈 

Umm, 😳 how is that possible?
They were ultimately written to the protocol, no?
Did you expect that behavior @pugson

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?

i did. from what i understand they are still there but hubs only index casts that are signed. removing the signature drops them from being available.

🐵 ← 🙈🙉🙊 → /phil → phil.cockfield.net, db.team →  ƒ(trust / time) →  ƒ(open-commons) → ƒ( /sys )  ← @cell primitive<T> 🧫

i did. from what i understand they are still there but hubs only index casts that are signed. removing the signature drops them from being available. https://warpcast.com/darrylyeo/0x297fa179

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

Oh shit, that seems like a design flaw worth addressing. 

It torpedos a bunch of what was good (in my mental model) of the protocol. Without that, any kind of “client opportunity” rhetoric has a defacto hole in the sack!

Thanks for helping me sync my mental model with current reality @pugson & @darrylyeo