ππππππππππππππ.πππ retweeted
GM! Today on @farcaster_xyz Resistance HQ Diaries:
Staryear 2026 | Day 9 of the Resistance
Our new overlords assured us we are absolutely FREE to leave once they execute the cockroaches infesting their APIs. I fully support this. Those bad roaches kept telling us to bend the knee!
However, today we found out sleeping is not compatible with freedom... Who knew? π€·ββοΈ
This morning, my fellow peasants and I were trying to find out whether the cockroaches had been taken care of. To our surprise, we found several farcaster clients frozen in time!
One GitHub archaeological expedition later, we discovered a sneaky chain upgrade whose final activation schedule was merged barely two hours before it took effect!
Perhaps digital felons arenβt on the mailing list but we feel grateful for the warning hidden inside the PS about the nodes that would stop working.
So it turns out, decentralization means spending your Saturday morning figuring out what our new overlords changed while we were asleep.
Weβre still investigating the frozen clients and those βbend the kneeβ errors. But overall, the decentralized democracy experience is going beautifully. My casts eventually escaped through one client and appeared in another. We are now communicating with our homes via digital carrier pigeons. π
to be continuedβ¦
ππππππππππππππ.πππ retweeted
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.
GM! Today on @farcaster_xyz Resistance HQ Diaries:
Staryear 2026 | Day 9 of the Resistance
Our new overlords assured us we are absolutely FREE to leave once they execute the cockroaches infesting their APIs. I fully support this. Those bad roaches kept telling us to bend the knee!
However, today we found out sleeping is not compatible with freedom... Who knew? π€·ββοΈ
This morning, my fellow peasants and I were trying to find out whether the cockroaches had been taken care of. To our surprise, we found several farcaster clients frozen in time!
One GitHub archaeological expedition later, we discovered a sneaky chain upgrade whose final activation schedule was merged barely two hours before it took effect!
Perhaps digital felons arenβt on the mailing list but we feel grateful for the warning hidden inside the PS about the nodes that would stop working.
So it turns out, decentralization means spending your Saturday morning figuring out what our new overlords changed while we were asleep.
Weβre still investigating the frozen clients and those βbend the kneeβ errors. But overall, the decentralized democracy experience is going beautifully. My casts eventually escaped through one client and appeared in another. We are now communicating with our homes via digital carrier pigeons. π
to be continuedβ¦
We are the table and on the tv at dinner π½οΈ
1/2 #hasanabi
ππππππππππππππ.πππ retweeted
in case you are inclined to believe the revisionist history of temu duterte / @balajis :
dan romero himself said the original 'friend group' churned very quickly including balaji
i was actually there and your positive sum network state leader is just straight up lying
ππππππππππππππ.πππ retweeted
Gm, with a reminder:
I wasnβt banned. I voted no and got exiled.
I want nothing to do with this authoritarian group.
I just donβt want to lose my family and my home in the process of leaving.
Replying to @CryptoStatuette
It happens. Have forgivness in your heart to qualify for the appeal...
Or else!
They will know.
ππππππππππππππ.πππ retweeted
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.
ππππππππππππππ.πππ retweeted
for a dude who claims to like crypto and is apparently going to use bounties as the primary method of marketing for his new social network he seems to have done a poor job of researching crypto-powered bounties that run on his new social network
ππππππππππππππ.πππ retweeted
Quorum updated their threading and it's beautiful
deep conversations between interesting people being displayed two, three, four replies deep
you can scroll and have visibility into all of them without leaving your home feed
Farcaster the way it was meant to be seen
ππππππππππππππ.πππ retweeted
Hypersnap won't make you sign a loyalty pledge.
Say what you want, how you want.
ππππππππππππππ.πππ retweeted
Balaji is referring to kicking everyone who disagrees with him off his app as "the first decentralized democratic digital election."
You don't hate these people enough
ππππππππππππππ.πππ retweeted
what is more "network state"-aligned?
> bounties where one person says they'll pay an amount with a "trust me bro" promise (they don't escrow anything onchain)
> bounties where the funds are escrowed onchain, anyone can crowdfund the reward, and contributors vote on payouts
ππππππππππππππ.πππ retweeted
Guess farcaster is dead? What the heck is this pledge to some weirdass techno religion?
Give me back my $120 and fuck off to play with your cults in your own little bubbles.
ππππππππππππππ.πππ retweeted
Quorum Mobile update is out
TestFlight: testflight.apple.com/join/PPβ¦
Android: releases.quilibrium.com/qm-2β¦
ππππππππππππππ.πππ retweeted
Replying to @ChainLeftist
you're always welcome on the censorship free side of the fork
ππππππππππππππ.πππ retweeted
I'd left X mostly because its owner was an anti-freedom, censorship tyrant hiding behind the "freedom of speech, not freedom of reach" BS.
I've been in Farcaster this whole time. Balaji (another techno-fascist) bought Farcaster and one day later banned all left/centrist accounts
ππππππππππππππ.πππ retweeted
incredible scenes on @farcaster_xyz (which i literally canβt speak about on its own platform since they banned me preemptively)
techno-fascism (real)




























