CISONAUT retweeted
FFmpeg's complaints are invalid.
They don't care about writing secure code. They don't care that somebody can send you a video file that takes control of your machine.
They are like every other "vendor" of software that doesn't care about the security of their code and who looks for reasons to pretend the vuln finders are the bad guys. The person finding a vulnerability in your code isn't the one who created it.
I say this as somebody who has analyzed many bugs in FFmpeg. The code is inherently broken and unfixable.
For example, one bug I looked at allocated a buffer in one library, using one algorithm to calculate its size, and then filled in the buffer in another library, using a completely different algorithm to calculate its size.
Obviously, there was a size mismatch.
The fix isn't to change the calculations to come up with the same size, but to carry bounds information with the buffer, so that the code filling in the buffer knows the buffer size, and can check it against an accidental overflow.
Since these were different libraries, this requires a change in the API -- something no outside vuln researcher can do, something only a core maintainer can do. FFmpeg cannot be fixed without a major redesign of its API to carry bounds information.
FFmpeg code is neither secure nor securable because they don't care ab out security. Google's vuln researchers didn't create this problem.
FFmpeg has 1 person generating insecure code faster than 1000 vuln researchers can keep up pointing out problems.
FFMPEG had one of the most valid crash outs in infosec history IMO. There's a huge elephant in the room when it comes to the fact that cybersecurity is extremely unbalanced. You have like 1,000 people pointing at problems for every 1 person fixing them.
Vulnerability research is extremely important, but it's become somewhat of a marketing stunt. First with fuzzers, and now with LLMs. It's a lot of "look what my new toy can do" rather than earnest attempts at actually fixing security problem.
What Google did to open source developers was especially egregious. They're a $3.6 trillion dollar company, who spent billions upon billions of dollars building a bot that points at problems really really fast, then they just dumped them all on a bunch of unpaid open source project maintainers to fix.
Then because of Google's 90 day disclosure policy, the maintainers have 90 days to fix the issues. After 90 days, Google goes public with the issues, making their project look bad if the vulnerability is yet to be fixed, and also potentially harming users if it gets exploited.
The 90 day policy was intended to give developers a reasonable amount of time to fix issues, while also applying some pressure with the threat of disclosure. Otherwise, you do get a bunch of goober ass vendors that will just ignore all security issues reported to them, then act completely surprised when their software gets hacked.
But when you're a small team, non-profit, or a solo developer, and you have a trillion dollar company's AI just blasting you with infinite problems to fix (each coming with a 90 countdown & a threat), that becomes extremely untenable. They're essentially inadvertently blackmailing developers into becoming unpaid interns.
Then on top of that, Google profits unimaginable amounts of money from the use of open source code. They use FFMPEG's code extensively across several highly-profitable products, meanwhile FFMPEG's developers work for free. There's no reason Google couldn't have donated money, engineers, AI tokens, or something towards fixing the problems. They can more than afford it.
I don't think Google has any malicious intent at all, it's just that the whole incentive structure behind vulnerability research is completely whack. All the glory goes to people who find issues, not those who fix them, so there's not a whole lot of interest in helping with fixes. Some vulnerability researchers will submit fixes with their reports, but most don't.
Honestly, in 2026 cybersecurity basically just feels like the equivalent of 50,000 people following the housecleaner around yelling "you missed a spot". Abysmally little effort has gone into anything outside of pointing out vulnerabilities.
Nothing to be said that wouldn’t take away from what was said .. original poster is captured, or his intellectual horsepower lacks the potential to power a more balanced and informed perspective
1
14
“…vulnerability researchers and AI companies burying software maintainers under an endless torrent of bug reports, while doing little to nothing to help with actually fixing the bugs”
the same tool that finds the bugs is available to ease the burden of exterminating them
I get what Google is trying to do, but I don't agree with it at all. Sure, there are some vendors who just sit on bugs forever and don't make any effort to patch them. But there's way more overworked & underpaid teams, non-profits, and solo projects who are patching bugs as fast as they physically can.
The number of CVEs found in 2026 is double that of 2025, so double the workload for anyone doing security fixes. Then on top of that, reducing the disclosure time from 90 to 60 days gives them 2/3 of the time to do double the work.
At some point the dam is going to break. You have vulnerability researchers and AI companies burying software maintainers under an endless torrent of bug reports, while doing little to nothing to help with actually fixing the bugs. Eventually, the software maintainers are just going to burn out and give up.
1
56
CISONAUT retweeted
just talked to my friend
non technical + retarded
but just went from 0->1m arr in 2 weeks
i’m pretty sure this is illegal but this is what he did
he got access to a deepseek 4.1v 1017 cyber
loaded up $250 in credits
and literally got database level access to over 19 companies with credits to spare
fucking insane btw
then he gave the companies an ultimatum
either pay him $5k or he emails all their users they were hacked
his offer has a 100% take rate
he did this all while not knowing how to code + spending less than $250
and on top of that he got a few offers from companies to consult them on cyber security
wtf is life
CISONAUT retweeted
i have no time to maintain all my vibe coded tools
we need a business model where someone else maintains the code and i just pay a monthly fee
one of the problems with the current approach is ultimately an identity (proofing) & access management problem…
if I’m affirmatively identified and authorized as a defender - I should be able to wield the full spectrum of the capability to defend
OpenCode is currently under a sustained cyberattack, and mid-incident they ran into the same problem Hugging Face did: the frontier models they were using for defense began refusing to help fight attacking agents because analyzing the attacks started triggering safety guardrails.
1
56
“IQ 150”
🙄
I don't know why this isn't obvious to people, but the car clearly should have fallen down from the ramp long before it "flew." It wasn't going fast enough at all to stay on the under side of the ramp through centrifugal force alone. So something else was rigged to keep it on the under side of the ramp before it "launched" into flight.
It turns out that cars don't drive upside down on the bottom side of giant structures without falling down. So the question is: What was used to keep the car's wheels attached to the under side of the ramp BEFORE the "flight" segment?
Or are people too mesmerized by the demo to think logically about physics?
Readers added context they thought people might want to know
The Tesla Roadster demo used an explained multi-mode fan suction system for up to 2G downforce to adhere to the ramp underside (not centrifugal force or hidden rigging), plus cold-gas thrusters for the flip/landing, as shown live and confirmed by Tesla and attendees.
snopes.com/fact-check/tes…
tesla.com/roadster
theverge.com/transportation…
pcmag.com/news/tesla-sho…
14
CISONAUT retweeted
I'm so excited to be releasing this engine.
This represents the first of hopefully a long line of work with Nvidia
We didn't put comparison charts in the main post
but rest assured
WE SMOKED EM
this is the best engine for your dgx station.
its not close.
Actual Computer turns your NVIDIA DGX Station into a department-scale AI factory.
Read the full case study:
actual.inc/company/blog/case…
👀
We've developed a new inference engine, called 'e'.
It's the closest thing to alien technology which we have, and pushes 10,500 tok/s aggregate on a single DGX Station with the new @NVIDIAAI Nemotron 3.5 Super VL model, released a few minutes ago.
25





















