Trish 🫧 retweeted
Help us PROTECT THE PROTOCOL!
We’re raising funds to print materials for our Protect the Protocol activations at @EFDevcon Mumbai.
If you can spare a few gwei to help make it happen, we’d really appreciate your support! 🙏
Link in the next post.
We’re raising funds to print materials for our Protect the Protocol activations at @EFDevcon Mumbai.
If you can spare a few gwei to help make it happen, we’d really appreciate your support! 🙏
Link in the next post.
10
23
62
2,432
Trish 🫧 retweeted
It took four tribes to silence one.
The Phäros were sealed in a realm without sound. Millennia later, their bloodline survived. Now they fight back.
Introducing Project Phäros.
An original fantasy universe. A legacy of light.
Sounds on. 🔊
The Phäros were sealed in a realm without sound. Millennia later, their bloodline survived. Now they fight back.
Introducing Project Phäros.
An original fantasy universe. A legacy of light.
Sounds on. 🔊
820
304
841
75,562
Great ad. I spy @TayZonday
How is the internet less private than in 2006, when the whole family shared one computer?
Back then, the internet was weird, personal, and all of ours.
So, we got your favorite meme legends back together to say it louder: What happened to the internet? 1/3
2
0
6
515
Trish 🫧 retweeted
The signature carved wooden mice created by Robert "Mouseman" Thompson, a renowned British furniture maker from Kilburn, North Yorkshire.
50
2,036
21,968
364,032
Trish 🫧 retweeted
A researcher mapped 335,000+ surveillance cameras across America.
Flock's response? Try to take it down.
Our response? Build a tool so you can find those near your home.
Flock's response? Try to take it down.
Our response? Build a tool so you can find those near your home.
88
611
3,008
97,535
thanks @ProtonPrivacy
JUST IN: Proton defies legal threats from Flock Safety by hosting a public map revealing the locations of over 300,000 surveillance cameras across the U.S.
5
0
23
844
Trish 🫧 retweeted
Factory workers in Karl-Marx-Stadt relaxing in a sauna, GDR, 1970s.
114
662
12,018
1,598,229
Trish 🫧 retweeted
live-tweeting on samsung findings were fun.
i'll let my agents give it a bit more time, but this document is already the most comprehensive breakdown of some key concerns of tizen i've seen run on a live device.
it takes like a good while for me just to scroll through it ups as of right now on individual functionality).
release is probably happening in a few days.
i'll let my agents give it a bit more time, but this document is already the most comprehensive breakdown of some key concerns of tizen i've seen run on a live device.
it takes like a good while for me just to scroll through it ups as of right now on individual functionality).
release is probably happening in a few days.
50
154
1,953
236,558
Trish 🫧 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.
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 e 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…
11
32
148
4,066
Trish 🫧 retweeted
no amount of wine can fill this void but i’m going to try anyway, kjersti faret, 2015 | hand embroidery with beadwork accents.
5
20
209
4,340
Trish 🫧 retweeted
Still minting ! Get your ASABL cards to watch my new short film !!
A SONG ABOUT BLACK LOVE
asongaboutblacklove.com
7
9
31
866
