5 minutes ago, @karpathy just dropped karpathy/jobs!
he scraped every job in the US economy (342 occupations from BLS), scored each one's AI exposure 0-10 using an LLM, and visualized it as a treemap.
if your whole job happens on a screen you're cooked.
average score across all jobs is 5.3/10.
software devs: 8-9.
roofers: 0-1.
medical transcriptionists: 10/10 💀
https://t.co/7MWRgdtLDI
[1/2] I've designed and coded this funky hacktro for PHRACK magazine Call For Papers! Check out the video version here (remember keep the volume up): https://t.co/TSmSVv7LSq #phrack#hacktro#pouet
Spread the word! @phrack CFP with demoscene cracktro is live. Turn up the volume and enjoy the awesome stylings of @PiotrBania with some hopefully inspiring text from phrack staff :)
https://t.co/8YTaL7JzDQ
Remembering memories with my friend Felix ‘FX’ Lindner @41414141, hacker extraordinaire with a huge heart, who passed away last week. Whether in Berlin, San Francisco, or Sao Paulo, hanging out with FX was never dull. FX was prophiled in @phrack #68 https://t.co/CshcZBcJlL
Launched binb https://t.co/3Tokgk8sEM : ELF (Linux) & PE (Windows) binary emulator in the browser!
Still a beta but usable and everything is happening locally in your browser via wasm!
Today marks 25 years since the first commit to FFmpeg by Fabrice Bellard
FFmpeg was made to play DVDs, DivX and other video files for free, and continues to be developed by enthusiasts
FFmpeg changed the world, powering all online video
Happy 25th Birthday FFmpeg! 🎉🎁🎂
Stealth died 😢 A member of Team-Teso, Phrack staff, and many other groups. A true hacker—perhaps as true as a hacker can ever be. WE MISS YOU. 🩷
More: https://t.co/Jx0JYfrjnG
<stealth> we had joy we had fun we had a rootshell on a sun.
If you're excited to see the WhatsApp bug thrown @thezdi - free to watch my talk from @reconmtl 2025 on 4 remote bugs I discovered last year!
While they're not 0-click RCE - there are some remote corruption and funny logic bugs in there.
https://t.co/N78H5QeNNZ
What really bothers me is that neither F5’s statement nor the attestation letters from NCC Group or IOActive mention when the breach actually happened.
They only say that F5 “learned” about it in August 2025. That’s not when it started.
There must be forensic evidence pointing to the first signs of compromise - timestamps, login traces, file access logs, anything. Was it weeks before they noticed? Months? Maybe even years? They don’t say. Not even approximately.
When companies omit that detail, it’s usually one of two things:
- They genuinely have no clue when the attackers got in (which would be disastrous), or
- They <know> it started long before discovery and don’t want to admit how far back it goes.
Either way, that’s the part that stinks the most.
Just wrote a new blogpost, I've spent the last few weeks learning about GPU programming, this blogpost is about Gluon and what led me there:
https://t.co/0UU6IDH2Bx