@alezkar_
Account based inParaguay!
About this account
- Account based in
- Paraguay
- Connected via
- Paraguay Android App
X says this location may be affected by a proxy or VPN.
Account-level information from X, not a live location or the device used for a specific post.
ig: diegoaly_ nostr: npub1p3rfw7wscmzfn9z3fa74nzgyqe70p57j8mws0e88dh7awjepmzcq7jgxl9
Joined January 2026
- Tweets638
- Following48
- Followers22
- Likes1.4K
Diego Yegros retweeted
consistently amazed at peoples' inability to extrapolate into the future
no the mathematicians job won't be to "interpret AI results" for longer than a blip in history
AI results will become more advanced than any human intelligence can verify within far less than a generation
if a bug in the kernel can live for +10 years, supposedly with all the eyes over it
what can you expect from your company projects
Linus Torvalds used AI to help uncover Linux kernel bugs that had been hiding since 2013.
It started when developer Nils Ollrogge reported a bug and submitted a fix.
Linus found the code too obscure to follow, so he used LLM tools to understand it and split larger functions into smaller, more readable ones.
Testing then confirmed the reported bug and uncovered three more, all dating back to the library’s first commit in 2013.
The changes haven’t been merged into the mainline kernel yet.
Linus wasn’t asking AI to replace his judgment. He used it to make difficult code easier to understand, then tested the result.
Source: phoronix.com/news/Linus-Torv…
Diego Yegros retweeted
not gonna lie.. if you code daily with Opus 5.5, Karpathy says you're in roughly the top 0.2%.
"Restaurants still exist"
what a bad take to say.
You go to a restaurant because you want to eat well.
Software _needed_ to be handcrafted.
You don't need to go to a restaurant.
Your _job_ is not a _job_ anymore. Is a hobby.
Diego Yegros retweeted
Ledger hacker used zcash and was traced.
Ledger theft, day two. Since yesterday the thief has pushed ether through Tornado Cash three times, and each time on into Zcash's shielded pool. We followed every lot out the far side. Here is how, step by step.
1. THE SAME BUILD, THREE TIMES
An ether wallet pays a fresh splitter. The splitter pays four fresh wallets. The four drop it into Tornado Cash's 100, 10 and 1 ETH pools. Minutes, every time.
Run 1, yesterday 15:17: 1,254 ETH. Run 2, today 09:42: 1,291 ETH. Run 3, today 11:56: 450 ETH from 0xfa4EaBB840A33C156E600311433AE261CBfCb0e2, in the pools by 12:15.
2. OUT OF TORNADO CASH
The mixer breaks the link between a deposit and a withdrawal. We do not need the link. Our tooling fingerprints the withdrawal transactions themselves: how each one is constructed, who constructs it, and when.
Yesterday's 65 withdrawals (1,084 ETH) and today's 96 (1,726 ETH) all carry the same signature. The six other withdrawals from those pools in today's windows do not. Run 3 came out from 12:18 into 0x0d697aa182801566d87adc86e68e95fd3b2f5f82 (213 ETH) and 0x676b16cc18542f37d202a1a79ac05463395496a4 (122 ETH), and 195 ETH of it was inside a cross-chain swap service by 12:38. Forty-two minutes, end to end.
3. INTO ZCASH, AND OUT AGAIN
The swap service turns the ether into shielded ZEC, where sender, amount and recipient vanish. But the service's own shielding of each lot is public, and from it we derive a value signature for that lot's exit, then scan every transparent exit from the pool. 108 of 108 exits across both days match their lot to the zatoshi. Not one other exit from the pool does.
First lot today: in at 10:18:18, out at 11:06:16 in block 3512847 (8d26a9b095d4d28373527f7a6eb81a3be7f906d1e2190960c0512ff64f369418 and 738c6d1261e79766e4dd16bdbd38dced91b8e3a86ce41dcda83eda1f19208fbf), straight into a ZEC to USDC order.
Today so far: 20 lots ordered (2,379 ZEC, $2.9m), 14 out, 5 inside the pool, 1 still settling. Every exit feeds a ZEC to USDC order paying two wallets born at 11:11, 22 of the 28 paid by 12:43:
0x816D5Ee17DB1495d1409F135b98FF3edc5F3cDf8: 940,561 USDC
0xBA736A4b616e79867B6d586293966b552883f3F3: 852,258 USDC
1.79m USDC, unspent. @Circle can freeze it.
(1/2) 🧵⤵️
Diego Yegros retweeted
Technical moats are mostly over at this point. If you’re building something that is meant to be durable, the only moats now are:
• Proprietary data
• Network effects
• A physical component
Diego Yegros retweeted
This is why Omarchy Linux was needed: The anti-AI stance of many Linux projects, which is closely connected to their political views, is becoming a real problem and hinders progress.
Omarchy is completely free of such inhibitions and embraces AI.
Flathub (a Linux app “store” for Flatpak, heavily used by GNOME), is actively rejecting software made with AI assistance. Calls any AI influenced code “tainted”.
“We see [using AI at all] as a liability (no matter how much people swear they review)”.
“As long as your development and codebase rely on [AI], then it’s not super bueno.”
