balaji bought farcaster and banned all the builders so the best he got was bribing someone $2k to build a "client" (see screenshot) meanwhile, we have over 20 clients on Hypersnap being built now with many already fully functioning replacements for farcaster and we're doing out of sheer passion. your friends are on the fork.

The most difficult part of this entire struggle is trying to convey information about a deeply technical debate to non-technical people. Statuette is undoubtedly one of the best at succeeding in conveying this. Yesterday, the network state team published an update to snapchain, which took effect two hours after release. This broke replication to any peer who did not upgrade. When I worked for merkle, we had a process for releases, so that non-emergency (which this was) updates gave node runners an entire month to upgrade. When neynar took over, with no announcement to change in process, they shortened it to a week window. And apparently, as of yesterday, it has been shortened further to two hours. This is fine when you're rolling out code to your own fleet. You control it! But when you roll it out, with no announcement, to a p2p network, you're telling people that their nodes don't matter. And that message is true anyway, because any node that isn't theirs is actually read only. When you hear someone posting messages to a snapchain node they own, it doesn't actually participate in any meaningful way – read only nodes simply forward on the message to the NS-controlled validators. Hypersnap will change this in the next release for our side of the fork – we will resume a more reasonable upgrade cadence, and we will cut ties with their validator set so that any node can actually participate in building data on the network. We aren't surprised to see what happened with the new (sort of) snapchain team, and our bar is so low for disappointment with their team that this is essentially a non-event. They embody neither the ideals of decentralization, nor the technical skills to achieve it.

they genuinely think you're stupid. the API didn't have a bug. it was intentionally made read only for banned and non-yes-voting users. The API literally returned a response that stated the reason of your read-only status. When software literally prevents you from doing things, and tells you the reason explicitly was something they put into effect, there is no world in which you can call that a "bug". Those APIs are _still_ read only for users that voted no or were banned. No idea if non-voting users can use it now. You would know these things already, if they hadn't banned users that have called this out. I saw @jchaskin22 asked about this on farcaster, but of course, responding would be of minimal benefit, as they filter out my replies on their client. So tagging you here so you have direct confirmation from someone who has concrete knowledge of what happened from the other side.

A nightly update to hypersnap has been published. It should aid in preventing suppression from the snapchain side. If we continue to find anomalous behaviors ahead of the PoW fork, we will proceed with an immediate validator swap run by community nodes ahead of the PoW fork to prevent further obstruction of banned users. The internet perceives censorship as damage and routes around it. It would be wise to remember that.

The new owner of farcaster, @balajis, has banned me from their side of the fork. Absolutely incredible work. So anyway, we're doing the hard fork of farcaster and would love to hear name ideas for our non-cancerous side. Spinning up an emergency group chat: t.me/+4eYOApUSw500Yzgx