Joined April 2009
556 Photos and videos
Pinned Tweet
Won't be spending much time on Twitter. #Mastodon mastodon.online/@FourthWorld #Bluesky bsky.app/profile/fourthworld… #LinkedIn linkedin.com/in/fourthworld I'll keep this account until I know where to find the people important to me. I may post here now and then in the meantime.
1
3
144
Dropped back in here from #Bluesky to see how things are going. I guess I'll try again in another few months.
1
17
RT @EFF: When you go online, your rights should go with you. X is no longer where the fight is happening. EFF takes on big fights, and we w…
237
Today is Victor Papanek's birthday (22 November 1923 – 10 January 1998). Often called The Father of the Green Design Revolution, his industrial design career and bestselling book Design for the Real World have left a lasting influence in the design industry, and with yours truly.
1
37
I've been invited to moderate a discussion at @artshare_la Thursday night at 7pm on Art & AI & IP. Join us for a gallery reception at Art Share LA, along with a panel discussion and Q&A. Deets: luma.com/cpawmxds
1
1
180
Thought I'd drop in to Xitter to see how things are going. Guess I'll try back in another few weeks.
21
Dropped in here to see how it's going. It's only gotten worse. May try again later. Every minute here fuels the worst this platform offers. See you on Bluesky...
1
31
Richard Gaskin retweeted
“Remember when everyone lost their minds over Cambridge Analytica harvesting Facebook data from 87 million people?” That was adorable. Because that? That was the tutorial level. Today, you are the product. Your thoughts? Monetized. Your privacy? A punchline in Silicon Valley. The “broligarchy” doesn’t want you informed — they want you addicted. Welcome to the sequel nobody asked for: Surveillance State 2.0: Now with Bonus Authoritarianism. And if you think the Stasi had files? Google’s got receipts on your soul.
9
204
425
27,452
Richard Gaskin retweeted
Please tell me they weren’t stupid enough to do it on their personal phones.
1,173
964
16,645
480,046
Richard Gaskin retweeted
A federal judge has ruled that The New York Times and other newspapers can proceed with a copyright lawsuit against OpenAI and Microsoft seeking to end the practice of using their stories to train artificial intelligence chatbots. khq.com/regional/judge-allow…

1
571
Richard Gaskin retweeted
26 Mar 2025
Teen Warned Not To Accept Group Chat Invites From National Security Advisors She Doesn’t Know theonion.com/teen-warned-not…
52
2,070
11,098
400,709
Richard Gaskin retweeted
25 Mar 2025
🚨 I told you all this yesterday. 🚨 SIGNAL cannot be downloaded on government phones with SIPRnet and JWICS secure networks. These idiots were using THEIR OWN UNSECURED PHONES, which are hackable with keystrokes monitored by foreign intel services. politi.co/4kZsZlg
244
5,977
15,849
367,814
Richard Gaskin retweeted
X has purged community notes from this Pentagon account that posts about transparency and accountability. 1: At 12:06am 2: At 9:44am
261
3,621
16,469
677,889
Richard Gaskin retweeted
The founder of Signal, ladies and gentlemen
433
11,738
109,110
2,303,931
Richard Gaskin retweeted
26 Mar 2025
"we are currently clean on OPSEC", you write to the group chat with the journalist
27
162
2,437
67,879
Richard Gaskin retweeted
15 Mar 2025
get library cards and use them often (online e-book and audiobook rentals count!). sign up to volunteer at your local library. donate money to your library’s general fund. run for a spot on the library board.
3
21
150
7,906
Just checked in. This place has gotten even dumber than last time I was here. I'll try back another time. See you on Bluesky...
9
John Denver died because of a usability error. Sounds like $1.4 billion in ETH may have suffered a similar fate. Crypto will never cross the chasm until it recognizes it's time to cross the chasm. Techbros making apps for techbros won't cut it anymore. #UsabilityMatters
22 Feb 2025
ELI5 why we cannot "rollback" Ethereum? After yesterday's Bybit hack, crypto commentators are again asking why Ethereum cannot "rollback" the chain to reverse the hack. While experienced ecosystem actors near-unanimously agree that this is infeasible, it's worth breaking down why this reasonably sounding proposal is technically intractable for less knowledgeable observers. If that's you, consider this an "ELI5" version of why this is impossible. First, some context on rollbacks: The idea of a blockchain "rolling back" stems from an early incident in the Bitcoin blockchain. In 2010, less than two years since Bitcoin's launch, a bug in the client software caused 184 billion (yes, *billion*) Bitcoins to be minted in block 74638. To fix this, Satoshi released a software patch to the Bitcoin client which invalidated the transactions. This had the effect of "rolling back" the chain which had kept growing in the meantime to block 74637. In less than a day, the new chain had accumulated enough proof-of-work to become canonical and all user transactions that had been rolled back were included in the new chain. Note that at the time, Bitcoin's mining difficulty was 10 billion times lower than today, and the BTCUSD price was about 0.07$. In short, this situation was unique in that a clear protocol bug led to the problematic transactions, which could easily be identified due to their large amount. Additionally, Bitcoin's limited adoption made it easy to distribute a new client version and quickly mine a new chain segment. Ethereum and TheDAO: Ethereum's early history had a superficially similar crisis which often leads to confusion about the practicality of rollbacks. In 2016, a popular Ethereum application, TheDAO, had ~15% of all ETH in existence under its control. Unfortunately, a hacker found a bug in the application's code that allowed them to steal all of these funds. This was notably different than the Bitcoin situation because the Ethereum protocol worked as intended, it was the application built **on** Ethereum that had an issue. Luckily, the developers of TheDAO had implemented a failsafe where withdrawals from the applications were frozen for a month before they were completed. This presented a unique opportunity to address the bug: the code of the application could be changed to prevent the funds from ultimately going to the hackers. Because there was no way in the application itself to do this, Ethereum protocol developers had to make the change directly in the blockchain's history. This is called an "irregular state change", because the "state" of the application was changed by manually updating the database, rather than, say, by a valid Ethereum transaction. A rough comparison to the Bitcoin bug above would be to have set the balance of the addresses that received the 184 billion BTC to 0, rather than re-mining a chain excluding those transactions. This upgrade was contentious and the Ethereum community effectively fractured over it. A subset of miners refused to run the software patch and kept mining on the chain where the hack happened, which still exists as Ethereum Classic. The chain that is known as Ethereum today is the one where this software upgrade was activated. Again, this situation was unique. Hacked funds from TheDAO were effectively frozen for a month, giving time for the community to coordinate on a software upgrade. The funds being frozen had another major advantage: there was no "contagion" from the hack. Had the hacker been able to move funds at will, "freezing" the funds would be an impossible cat and mouse game, as the protocol is open source and any potential change which froze the funds would have to be broadcast to the hacker, giving them plenty of time to move their funds elsewhere. Which brings us to the Bybit incident. Why we can't rollback Ethereum Earlier this week, the Bybit exchange had 401,346 ETH (~1.4B USD) stolen. The theft was caused by the custodian of the funds signing a misleading transaction in a compromised multisig interface. The root cause for this hack was higher up the stack than both TheDAO and the Bitcoin overflow bug. There were no issues with the Ethereum protocol, or even with the underlying multisig application used by Bybit. Instead, a compromised interface made it appear as though a transaction was doing one thing while it was actually doing another. From the perspective of the Ethereum protocol, there is nothing to distinguish that transaction from other legitimate transactions on the network. There is no protocol rule that was broken where patching the issue would isolate the hacked funds, like in the case of the Bitcoin exploit. Furthermore, the funds were immediately available for the hacker to spend. Unlike in the case of TheDAO, where the community had a month to deploy a surgical intervention, here the hackers immediately started moving the funds onchain. Even if we could solve the cat and mouse game described above, the Ethereum ecosystem is far different today than in 2016. DeFi and bridges to other chains mean that any stolen funds can easily be mixed within a web of applications. For example, stolen funds can be swapped on a decentralized exchange, with the resulting tokens being used as collateral in a DeFi protocol, where the borrowed assets are bridged to a completely separate chain. This level of interconnectedness means that any irregular state change, even if socially palatable, would have near-intractable ripple effects. A "full rollback", where a portion of the recent chain history was invalidated, would be even worse. Any settled transaction, many of which have implications outside Ethereum (e.g. exchange sales, RWA redemptions, etc.) would be undone, with no way to revert the offchain half of it. So, to conclude, while Bitcoin was able to "rollback" its blockchain 15 years ago, today, the interconnected nature of Ethereum and settlement of onchain <> offchain economic transactions, make this intractable today. Technically, irregular state changes are still possible on Ethereum in cases where funds are frozen and isolated. The last time such a change was proposed, in 2018, to address a bug in Parity's multisig wallet where ~500,000 ETH were frozen (see EIP-999), it was strongly opposed by the community of the contention resulting from TheDAO.
48
I don't normally share video for subjects better covered in print. But this one is an exceptional summary of current #disinformation strategies and tactics arguably essential for a healthy #MediaLiteracy diet. youtu.be/GZ5XN_mJE8Y

1
26
Richard Gaskin retweeted
is there anyone who purchased the $TRUMP token who would be willing to speak? particularly interested in talking to those who lost money. DM or email me at molly@mollywhite.net
40
38
294
20,013
Everyone's talking about today being some sort of big Game Day. Alright, I'm in. #CoreSpace
19