Farcaster protocol update announced in a private group chat

Submit
@CryptoStatuette
@CryptoStatuette

Great news for all the digital felons of the world! Our democratically decentralized democracy reps announced a new @farcaster_xyz protocol update! Hearing about it randomly from a fellow peasant in a TG group chat gave me much gratitude. Especially after last week’s sneaky, late night protocol update that froze all our clients. But my favorite part was how they shared this very essential info in a private group chat on a farcaster client where the builders are banned! They’ve clearly learned a powerful lesson: the community can’t complain about an announcement it can’t see! 🧠 I’d like to thank our overlords for relieving us of the burden of being represented. Following protocol updates was definitely interfering with my wrongthink addiction recovery. 🙏

Tweet image
x.com

Farcaster protocol update announced in a private group chat

submitted bymisha13,2035h
2
Read original article
AI summary of the linked article

The article is a sarcastic post saying Farcaster announced a new protocol update in a private group chat on a Farcaster client where the builders are banned, and it criticizes that choice. The author says they heard about the update by chance from another user in a Telegram group chat, after a previous late-night update had frozen all clients. The author mocks the announcement method as a way to keep the community from complaining about updates it cannot see.

2 comments
avatar
tim· 4 hours ago
Wow she’s really salty about it. But Farcaster is just the brand, no? It should be fine to lose the main client? Why is it not?
avatar
mishaSubmitter· 4 hours ago
As I understand it, Farcaster (NS-owned) controls all validator nodes and is trying to prevent non-NS aligned clients from connecting through sneaky secret protocol upgrades. But must admit mostly enjoying the drama from the sidelines, not really deep into it.

Featured on Kiwi News: this story reached #1

Featured on Kiwi News

Wrote it? Add the badge to your post or README:

Top stories that week →