irfi (@_irfianto) header
irfi (@_irfianto) profile picture

I'm batman. All views are my own portfolio: https://teapawt.net/t.co/ZBKfZfNc1o https://teapawt.net/t.co/GDfeAfO6EP

127.0.0.1
Joined May 2020
Photo by irfi (@_irfianto)Photo by irfi (@_irfianto)Photo by irfi (@_irfianto)Photo by irfi (@_irfianto)Photo by irfi (@_irfianto)Photo by irfi (@_irfianto)Photo by irfi (@_irfianto)Photo by irfi (@_irfianto)Photo by irfi (@_irfianto)Photo by irfi (@_irfianto)
Replying to @0xpessimist
If you find a live Critical, it's very unlikely to be a duplicate, as they're fixed ASAP. It does happen eventually, but it's generally a good sign. Lower-severity issues can remain open for a long time, sometimes forever. So they're much more likely to be duplicated, since the project didn't prioritize fixing them. They're also less important overall. Then you have the false positives that point out a bug, a poor design choice, or an issue in code that doesn't put any funds at risk. It's reasonable for projects to justify it once, and mark the rest as duplicates. So if someone gets duplicates too often, the reason is usually that they're hunting the same non-critical stuff everyone else is, reporting issues with no clear exploit path or no funds at risk. Especially now that many people are using LLMs that tend to surface the exact same findings.
3
7
72
1,893
My students asked me if it was true that the entire Internet was really coded by hand. All those kernels, protocols, router firmware, browsers, databases, etc. Somebody coded these and debugged them by hand?!?!? They used BBEdit?!?!??! The idea that this was even possible seems amazing to them. I can imagine some future Moon Landing like conspiracy theory that says it never happened.
142
551
61
5,577
250,548
I’m not dying from some fucking hentai virus
1,553
82,045
1,837
620,666
10,284,218
irfi retweeted
homebrew is a supply chain disaster waiting to happen
93
161
50
3,044
546,083
Grok: "Axios 1.14.1 got hijacked" Also Grok: "pin to ^1.14.0" 🙃 This is why AI can't be your SOC.
Axios 1.14.1 got hijacked via maintainer account takeover, pulling in malicious plain-crypto-js 4.2.1 (obfuscated dropper, shell cmds, payloads per Socket). npm yanked it—pin to ^1.14.0, audit lockfiles, skip blind upgrades. That red cat reply? Perfect "we're cooked" meme energy for a supply chain scare. Stay frosty, devs. 😼
9
37
2
857
136,749
zed got ux right. even for manual coding session
1
29
Consider that the dumbest people you know are repeatedly being told "You're absolutely right!" by LLMs.
230
2,111
164
22,751
669,328
Game designers figured this out decades ago and it cost millions in failed launches. Will Wright built SimCity with a fully accurate traffic simulation. Testers hated it. The cars behaved realistically, which meant nobody could build a functioning city because real traffic is an unsolvable nightmare. He had to make the simulation dumber before the game became fun. The tension is permanent: the more accurately you model a system, the more it punishes the participant. Real medieval economies kept 90% of the population in subsistence farming. A historically accurate fantasy world doesn't produce heroes. It produces serfs. Tolkien solved this by making his economy deliberately vague. No one knows what a gold coin buys in Gondor. That ambiguity is a design choice, not a shortcut. The Reddit post is funny. The lesson underneath it is one of the hardest problems in simulation design: fidelity and fun are opposing forces, and you have to pick which one wins.
The more I think about this the funnier it gets
323
3,011
140
31,879
2,344,986
How can it be that modern LLMs are so bad at playing games? Aren't they supposed to be generally intelligent? Honestly, they are better at coding games than playing them. Maybe programming is just a particular type of game? Our new position paper tackles these questions. (1/n)
5
7
1
41
3,772
software engineering workflow right now
4
33
4
692
49,094
I keep seeing terrible advice online for people interested in computer science. AI is making programming knowledge obsolete in the same way interpreted languages made compiled languages obsolete, in the same way compilers made assembly obsoletely, and in the same way assembly made knowledge of circuits obsolete. It didn't. The percentage of people that can go through every layer of the stack will shrink and that knowledge will become more valuable, not less. With more tools, your knowledge base should expand not contract. Learn everything you can, while you're in school--and use AI to accelerate that process. Learn how programming languages work. Learn how computers work. Learn how matrix multiplication is optimized. Learn FFTs are implemented. Learn calculus and linear algebra. Learn optimization. Learn how that all applies to training. Learn how to use the AI tools, but also learn how they are built. The history of computing is the history of abstraction layers being built one on top of the other, and it's only when you can traverse layers of abstraction can you truly build new things. Learn more. Build more.
85
158
27
1,209
72,212
irfi retweeted
Replying to @kianmckenn
@kitlangton has a good metaphor it's like tending a garden can let ai code grow but you have to aggressively clean up after it and be diligent about architecture and patterns codebase is ok it will get better
24
51
6
1,245
43,833
It’s really crazy from triaging reports on Immunefi seeing so many LLMs converge on the same few issues Creativity and unique attacks are incredibly important nowadays if you’re trying to get a bounty
4
4
1
53
5,288
irfi retweeted
let-fate-decide > Draw Tarot cards using cryptographic randomness to add entropy to vague planning github.com/trailofbits/skill…
4
7
6
65
12,050
shit yeah, should force myself to stop. it's so easy to start working more + faster feedback loop
Powerful new Harvard Business Review study. "AI does not reduce work. It intensifies it. " A 8-month field study at a US tech company with about 200 employees found that AI use did not shrink work, it intensified it, and made employees busier. Task expansion happened because AI filled in gaps in knowledge, so people started doing work that used to belong to other roles or would have been outsourced or deferred. That shift created extra coordination and review work for specialists, including fixing AI-assisted drafts and coaching colleagues whose work was only partly correct or complete. Boundaries blurred because starting became as easy as writing a prompt, so work slipped into lunch, meetings, and the minutes right before stepping away. Multitasking rose because people ran multiple AI threads at once and kept checking outputs, which increased attention switching and mental load. Over time, this faster rhythm raised expectations for speed through what became visible and normal, even without explicit pressure from managers.
1
49
1/ Agentic LLMs can automate vuln detection. Very exciting, but doesn't address the hardest part (imo) of vuln research: prioritization. Can we reliably explore the search space and separate signal from noise? I wrote a paper (and OSS tool) to solve this. arxiv.org/pdf/2512.06155
2
60
4
220
107,813
irfi retweeted
i said to an ex-googler last month that thx to ai bigtech can double their margins overnight by firing 80% of the staff and still function well. his response: even before ai they could fire 80% and still function well. i nodded in agreement.
we're making @blocks smaller today. here's my note to the company. #### today we're making one of the hardest decisions in the history of our company: we're reducing our organization by nearly half, from over 10,000 people to just under 6,000. that means over 4,000 of you are being asked to leave or entering into consultation. i'll be straight about what's happening, why, and what it means for everyone. first off, if you're one of the people affected, you'll receive your salary for 20 weeks + 1 week per year of tenure, equity vested through the end of may, 6 months of health care, your corporate devices, and $5,000 to put toward whatever you need to help you in this transition (if you’re outside the U.S. you’ll receive similar support but exact details are going to vary based on local requirements). i want you to know that before anything else. everyone will be notified today, whether you're being asked to leave, entering consultation, or asked to stay. we're not making this decision because we're in trouble. our business is strong. gross profit continues to grow, we continue to serve more and more customers, and profitability is improving. but something has changed. we're already seeing that the intelligence tools we’re creating and using, paired with smaller and flatter teams, are enabling a new way of working which fundamentally changes what it means to build and run a company. and that's accelerating rapidly. i had two options: cut gradually over months or years as this shift plays out, or be honest about where we are and act on it now. i chose the latter. repeated rounds of cuts are destructive to morale, to focus, and to the trust that customers and shareholders place in our ability to lead. i'd rather take a hard, clear action now and build from a position we believe in than manage a slow reduction of people toward the same outcome. a smaller company also gives us the space to grow our business the right way, on our own terms, instead of constantly reacting to market pressures. a decision at this scale carries risk. but so does standing still. we've done a full review to determine the roles and people we require to reliably grow the business from here, and we've pressure-tested those decisions from multiple angles. i accept that we may have gotten some of them wrong, and we've built in flexibility to account for that, and do the right thing for our customers. we're not going to just disappear people from slack and email and pretend they were never here. communication channels will stay open through thursday evening (pacific) so everyone can say goodbye properly, and share whatever you wish. i'll also be hosting a live video session to thank everyone at 3:35pm pacific. i know doing it this way might feel awkward. i'd rather it feel awkward and human than efficient and cold. to those of you leaving…i’m grateful for you, and i’m sorry to put you through this. you built what this company is today. that's a fact that i'll honor forever. this decision is not a reflection of what you contributed. you will be a great contributor to any organization going forward. to those staying…i made this decision, and i'll own it. what i'm asking of you is to build with me. we're going to build this company with intelligence at the core of everything we do. how we work, how we create, how we serve our customers. our customers will feel this shift too, and we're going to help them navigate it: towards a future where they can build their own features directly, composed of our capabilities and served through our interfaces. that's what i'm focused on now. expect a note from me tomorrow. jack
54
108
12
3,322
169,022
the AI psychosis in my timeline is real
15
a lot of vibecoding tools are giving free tier (codex, opencode, antigravity). you just need to round-robin those. or iykyk
44
Today, we begin a new chapter. Narrative Protocol is officially live. Watch the announcement video below. 🎬👇
9
3
5
48
6,148