sudo rm -rf --no-preserve-root / pfp

sudo rm -rf --no-preserve-root /

@pcaversaccio

164 Following
2819 Followers
sudo rm -rf --no-preserve-root / pfp
3 replies
0 recast
22 reactions
sudo rm -rf --no-preserve-root / pfp
2 replies
0 recast
18 reactions
sudo rm -rf --no-preserve-root / pfp
0 reply
3 recasts
16 reactions
sudo rm -rf --no-preserve-root / pfp
1 reply
2 recasts
16 reactions
sudo rm -rf --no-preserve-root / pfp
1/ Let's be real, a ton of people (yes, even probably you reading this) store pws, 2FA backup codes, and other sensitive info in `.txt` files. Even the 2FA providers themselves often give you those backup codes as `.txt` downloads. It's shit, but it's common. Obviously don't use `.txt` files to store any sensitive data, but let's address the major issue now: on Windows, Notepad is getting Copilot integration (sounds cool for many, but it's fucked!). That means if you open one of those `.txt` credential files, you're potentially leaking sensitive data to Microsoft's servers (I know you already leaked your dick/feet pics via the cloud sync feature of images but you don't care about those that much). They claim it only happens if you actively use Copilot features; but dude, who actually trusts that lol?
2 replies
0 recast
21 reactions
sudo rm -rf --no-preserve-root / pfp
1 reply
0 recast
23 reactions
sudo rm -rf --no-preserve-root / pfp
9 replies
7 recasts
69 reactions
sudo rm -rf --no-preserve-root / pfp
4 replies
1 recast
23 reactions
sudo rm -rf --no-preserve-root / pfp
3 replies
2 recasts
23 reactions
sudo rm -rf --no-preserve-root / pfp
1/ time for a quick vibes check on where our industry's at security-wise; well, folks, guess what, 95% of last months' SEAL 911 tickets were the same shitshows on repeat: folks running sketchy code some rando DMed them (stop cloning & running GH repos you got from some random dude who asks for your "help"), hopping on Zoom calls where scammers walk them through (effectively) self-pwning (dude, believe me you don't need to patch your zoom or google meet) their own machines, teams getting nuked because they thought hiring bargain-bin devs from North Korea was a great idea, or some skiddies calling up victims pretending to be Coinbase support (always Coinbase, like 90% of the time and the rest is Ledger) and walking off with their funds. On top of that, there's the usual: someone falling in love with a random Tinder match and getting rinsed by a textbook Sha Zhu Pan play, and of course, the ever-reliable dev who commits their .env file with private keys straight to GitHub, NPM, etc.
2 replies
0 recast
22 reactions
sudo rm -rf --no-preserve-root / pfp
0 reply
3 recasts
21 reactions
sudo rm -rf --no-preserve-root / pfp
5 replies
1 recast
23 reactions
sudo rm -rf --no-preserve-root / pfp
2 replies
1 recast
24 reactions
sudo rm -rf --no-preserve-root / pfp
7 replies
7 recasts
56 reactions
sudo rm -rf --no-preserve-root / pfp
2 replies
0 recast
26 reactions
sudo rm -rf --no-preserve-root / pfp
"Make Ethereum Cypherpunk Again" isn't simply a slogan for me β€” it's a statement of intent. This isn't branding. It's resistance. This isn't about playing nice. It's about reclaiming Ethereum's soul! Look it's very simple: Ethereum must provide privacy _unconditionally_. Today, it operates in a partial, opt-in model, forcing users to jump through hoops just to conceal their financial lives. That's not sovereignty β€” it's submission. Enough compromises. We need privacy by default. Over the past weeks, I've written a potential path forward β€” a vision for Ethereum as a maximally private, self-sovereign financial system. Read it. Challenge it. Improve it. Let's co-create it. Make Ethereum Cypherpunk Again. https://hackmd.io/@pcaversaccio/ethereum-privacy-the-road-to-self-sovereignty
2 replies
4 recasts
42 reactions
sudo rm -rf --no-preserve-root / pfp
2 replies
2 recasts
10 reactions
sudo rm -rf --no-preserve-root / pfp
Dropping some thoughts as this concerns me a lot lately: - What happens when a DPRK-backed persona slips into Ledger, Trezor, MetaMask, etc.? - What happens when client teams get compromised from within, turning trusted core devs into silent attack vectors? - What happens if the Kim boys start tampering with the cryptographic libraries we all rely on? (we don't know if this already happened btw...) So far, the attacks have targeted individual projects. The next phase? My guess is a full-scale takeover of the infra that holds our ecosystem together. Look, it's pretty simple: the threat model isn't just shiftingβ€”it's escalating. Every move you make without paranoia is an opening for state-sponsored actors to dig in deeper. If you're not fucking questioning everything, you're already playing their game. This industry's long-term survival depends on its foundational pillars operating in a constant state of paranoia. Like it or not.
1 reply
2 recasts
14 reactions
sudo rm -rf --no-preserve-root / pfp
EOF: When Complexity Outweighs Necessity https://hackmd.io/@pcaversaccio/eof-when-complexity-outweighs-necessity A lot of time and energy went into this new deep dive on EOF. We break down its supposed benefits and argue they're more "nice-to-haves" than essential upgrades. Instead of adding complexity, we highlight cleaner, less disruptive solutions that achieve the same goals. EOF's objectives are solidβ€”but there's a smarter way to get there. I would like to highlight that the authors and contributors of this post represent the full EVM stackβ€”from VM and formal specification maintainers to compiler engineers, application developers, and library creators. Please reflect on this guys. If you got feedback, let us know here: https://ethereum-magicians.org/t/ethereum-is-turning-into-a-labyrinth-of-unnecessary-complexity-with-eof-lets-reconsider-eof/23136 https://x.com/pcaversaccio/status/1900200732000759892
3 replies
14 recasts
53 reactions
sudo rm -rf --no-preserve-root / pfp
0 reply
0 recast
11 reactions