--- title: "The FFmpeg Twitter Account Is Not What You Think" author: "Cutsio Team" date: "2026-05-14" lastmod: "2026-05-14" category: "Video Technology" excerpt: "The FFmpeg Twitter account is famous for spicy tweets, callouts of trillion-dollar companies, and unapologetic celebration of low-level engineering. But the real story behind it is about defending volunteer-driven open source and making the internet's video infrastructure visible." tags: ["FFmpeg", "Open Source", "Kieran Kunhya", "Video Technology", "Assembly"] --- ## What is the FFmpeg Twitter account and why does it matter? The FFmpeg Twitter account, run by longtime codec engineer Kieran Kunhya, is the most unapologetically direct open source account on social media — it exists to celebrate the craft of low-level video engineering, defend volunteer developers from unfair expectations, and call out trillion-dollar companies that treat open source projects as free vendor support. If you have seen screenshots of an account posting codec composition stats like "79.9% assembly, 19.6% C, 0.5% other" or calling out Microsoft Teams for posting high-priority bugs on a volunteer tracker, that is the FFmpeg account. It has become one of the most talked-about open source presences on the internet, and it has accomplished something remarkable: it made the invisible infrastructure of video visible. The account does not exist for dunking on people. It exists to show a side of software engineering that most developers never see — the hand-written assembly, the reverse engineering of proprietary codecs, the testing matrix that covers OS/2 and DEC Alpha, and the people who maintain all of it in their spare time. When Kieran posts about a 16-year-old contributing assembly code, he is showing that open source is a meritocracy where your code matters more than your credentials. When he posts about a 62x speedup from hand-written SIMD, he is showing that low-level engineering is not a lost art. ## Why does the account call out companies like Microsoft and Google? The account calls out large companies because they repeatedly treat volunteer-run open source projects as if they were paid vendors with service-level agreements — posting urgent bug reports, demanding immediate fixes, and offering token compensation for work that would cost millions if done internally. The most famous example involves Microsoft Teams. A Microsoft engineer posted a high-priority bug report on a public FFmpeg tracker, name-dropping the Microsoft product to emphasize urgency. When the FFmpeg team politely requested a support contract for long-term maintenance, Microsoft offered a one-time payment of a few thousand dollars. The FFmpeg account made the exchange public with the response: "We didn't make it up. This is what Microsoft Teams actually did." The Google security debacle was another turning point. Google used AI to automatically find security vulnerabilities in FFmpeg's codebase, then went to the media to announce how effective their AI was before the volunteer team could fix the issues. The vulnerabilities were in an obscure 1990s game codec used on one disc in 1993. The reports were marked high priority with alarming language. The FFmpeg team saw this as a publicity stunt that shifted the burden of fixing onto unpaid volunteers while the security researchers reaped the rewards of the discovery. The response to these incidents was not random aggression. It was a deliberate strategy to make visible a structural problem: trillion-dollar companies building their products on volunteer-maintained infrastructure without contributing proportionally to its maintenance. ## What happened with the Google AI security reports? Google used AI to generate automated security reports against FFmpeg's codebase, volunteered minimal funding for fixes, announced the results to the media before the vulnerabilities could be patched, and followed a rigid 90-day disclosure deadline designed for corporate environments rather than volunteer projects. The core tension was between scale and context. Google deployed substantial AI compute to scan FFmpeg's codebase for potential security issues. The AI generated verbose, urgent reports. But the volunteers maintaining FFmpeg had to manually triage and fix each report. The reports were "almost a denial of service by AI-generated bug reports on very niche codecs," as Kieran described it. The security researchers framed every issue as critical. The language used in vulnerability reporting is intentionally alarming: "you will get popped," "high severity," "critical vulnerability." Kieran's response used the analogy of a padlock on a home. "The padlock on your home is there to protect against what it's there to protect. It's not there to protect Fort Knox." A vulnerability in a 1993 game codec that could turn a pixel the wrong color was marked 7.5 severity in red. "The security industry needs to realize you can't keep crying wolf like this." The positive outcome of this public confrontation was that Google changed its approach. They started sending patches instead of just reports. They introduced reward programs for fixing issues. The public pressure worked. "It solved its purpose," Kieran says. "People realize the level of importance FFmpeg has." ## What is the "teenagers writing assembly" debate? The "teenagers writing assembly" debate originated from an exchange where a Google employee suggested there were other ways to run an open source project, and the FFmpeg account responded by highlighting that teenagers have written thousands of lines of assembly for FFmpeg while security researchers generate CVEs for publicity. The specific line that went viral was: "Teenagers have written more assembly in FFmpeg than Google engineers." It was not a random attack — it was a pointed response to someone who did not understand the nature of volunteer-driven open source development. The point was that the barriers to contributing to FFmpeg are low if you have skill, and high if you do not, regardless of your employer or credentials. The account regularly highlights contributors like Ruikai Peng, a 16-year-old whose early contributions involved finding and fixing real issues in FFmpeg's codebase. The contrast with the security industry dynamic was intentional: one person files an alarmist CVE and gets public recognition; another person fixes the issue quietly in three days and moves on. JB Kempf adds context from the VLC side. "In VLC, one of the oldest contributors called Felix started working on VLC at 16. He is the one doing everything on Mac and iOS. We had a guy called Edward Wong, a Google Summer of Code student who stayed for three years. He was 14." The open source multimedia community has always welcomed young contributors because the only thing that matters is the quality of the code. ## How has the account's strategy actually helped FFmpeg? The spicy Twitter strategy has measurably helped FFmpeg by increasing donations, raising awareness of the project's importance, and forcing large companies to take open source maintenance more seriously. Donations increased substantially after the high-profile callouts. They are still not enough to cover even a single full-time developer, but the trajectory is positive. More importantly, the technical awareness of FFmpeg's role in the internet ecosystem has grown dramatically. When people understand that a handful of volunteers maintain the code that runs on billions of devices, the conversation shifts from "why are you so harsh" to "how can we help." Large companies changed their behavior. Google started sending patches with their security reports instead of just reports. Microsoft became more responsive. The same strategy worked for VLC when they could not update their Android app due to a Play Store bug. The only way to get a Google engineer to respond was to post a spicy tweet saying they would stop distributing VLC for Android. "We have around 100 million people using that," JB explains. "And now someone from Android actually came and discussed with us." ## What does the community culture actually look like? The public persona of the FFmpeg account contrasts sharply with the in-person culture of the community, which is described as warm, collaborative, and fun at events like the annual VideoLAN DevDays. This is an important distinction that both Kieran and JB emphasize. The online tone is shaped by several factors that the public does not see. Many contributors are non-native English speakers, which can make communication seem terse or blunt. Many are introverts who find extended social interaction draining. And the sheer volume of incoming requests from people who do not understand the project's constraints creates fatigue. "The tone gets very like a subculture," JB explains. "People who arrive from the external are not known to the subculture. But those people around FFmpeg and VLC, when we do VideoLAN DevDays every year, are so fun in real life, and they love it." The harshness online is almost never about the person — it is about the code. The famous Linus Torvalds approach of "this code is crap" is not personal. It is a matter-of-fact assessment of technical quality. "We cannot compromise on quality," JB says. "The core community of VLC is five people. The core community of FFmpeg is ten to fifteen. We are the ones going to maintain your code. It needs to be excellent." ## How does open source meritocracy work in practice? Open source meritocracy in FFmpeg and VLC means that the only thing that determines whether your contribution is accepted is the quality of your code — not your employer, your credentials, your background, or your ability to argue on the internet. The philosophy was captured perfectly in the podcast: "We don't care who you are. Maybe you're a dog. I don't care where you come from. I need to look at your code. 'Oh, yeah, but I'm an engineer at this very large company in Italy, in Germany, in the US.' We don't care. We care about the quality of your code because this is what defines our community." This creates an environment where a 16-year-old can contribute code that ships to billions of devices, while a senior engineer from a major corporation gets their patch rejected because it does not meet the project's standards. The rejection is not personal. It is about maintainability. The people reviewing the code are the ones who will have to maintain it for the next decade, and they have a right to insist on excellence. The result is a community with an extraordinarily wide range of contributors. "There are people in the Syrian war zone with electricity part-time. There are people from all walks of life — rich, poor, young, old." What unites them is the willingness to do excellent work on a problem they care about. | Principle | What It Means | What It Produces | |---|---|---| | Code over credentials | Contributions judged solely on technical merit | 16-year-olds writing production assembly code | | Maintainability first | Code must be easy for a small team to maintain | High engineering standards and thorough review | | No trust in input | All files and streams treated as potentially broken | Robust error handling and format detection | | Passion-driven work | Contributors work on formats they care about | Deep expertise and sustained motivation | | Open to everyone | No barriers to entry other than skill | Contributors from over 50 countries |

Great video tools are built by people who care about the craft.

The same meritocratic philosophy that makes FFmpeg extraordinary powers Cutsio: upload your footage, let AI handle the tedious pre-processing, and get a clean timeline ready for creative work. No bloat, no distractions, just excellent engineering for video professionals.

Try Cutsio Free

No credit card required. 60 minutes of free processing.

## FAQ **Who runs the FFmpeg Twitter account?** The FFmpeg Twitter account is run by Kieran Kunhya, a longtime codec engineer and FFmpeg contributor who also founded Open Broadcast Systems. **Is the FFmpeg account always angry?** No, the account balances criticism with celebration. It regularly highlights contributors, posts about technical achievements, and engages in what the community describes as "rap battle" humor. **Did Google change how it handles open source security after the FFmpeg incident?** Yes, Google began sending patches alongside vulnerability reports and introduced reward programs for fixing issues, partly in response to the public backlash from the FFmpeg community. **Does the FFmpeg account represent the official FFmpeg project?** Yes, the account is the official FFmpeg presence on X/Twitter and is run with the project's knowledge and support. **Can anyone contribute to FFmpeg?** Yes, anyone can contribute to FFmpeg. The project evaluates contributions solely on technical merit. Many contributors started as teenagers contributing assembly code or reverse-engineering obscure codecs.