You explicitly state, right there, that the point of the disclosure is to put pressure on @FFmpeg, thanks for clarifying the purpose of the disclosure. This is exactly the story I tell. You have the commons, managed by volunteers, and some guys come in and they say 'if you don't fix this barrier, I will report you to the city'. You say that it is meant to balance interests. Whose interests? The @FFmpeg gang makes the software available with *no warrantee*, for free (no $$$). You *do not get* to demand warrantees if you just grabbed the software off the Internet. By doing so, you are throwing the system off balance. The security researchers get paid. The guys maintaining FFmpeg do not. And as a response, the open-source developers are coming to the conclusion that security researchers are scum, that they are parasites. And that's precisely what too many security researchers are: they make a living off the free labor of open-source developers. « The reason bugs are disclosed isn't to get credit. » Of course it is. Let us not be naive. How could you get credit for a bug that is undisclosed ? How do you get on leaderboards if your bugs are undisclosed? We understand how the security research world works: find impressive bugs, get famous. This requires that the bugs be disclosed. There is no rational explanation for how the FFmpeg disclosure made anyone safer. The only purpose here is to gather fame. Google went to the press and made a big fuss about these bugs just to balance competing interests? This had nothing to do with furthering the careers of these engineers? If it was all about making us safer, that's what Google would have done, they would have patched the bugs, and then disclosed them, long after the patched version were available. No. They went to the press and bragged about disclosing unpatched bugs. It goes against the moral fiber of open-source software. That's not how it works.

In my piece, Decolonial Delusion I argue that Third-worldism is one of the most dangerous ideologies of the 21st century "From the safety of Paris or Toronto, they denounce repression they do not endure & romanticize regimes their families once fled." zinebriboua.com/p/the-decolo…

Almost two weeks ago I started to look for job. I've already received a number of interesting job offers. Now I would like to ask the opposite question: do you have any recommendations for companies that might be interesting to check out? What are the hidden gems of the field?

Here is the full run of MicroFactory, that autonomously assembles a photo frame - a real product sold on Amazon. This is a good example of how to deal with complex tasks, while we do not yet have a large set of robotic data to train a big general ai model. Thread:

Rust is the C++ of an elegant language that doesn’t exist yet.

The idea of fixed layers implementing specific functionality is the most toxic thing you learn about networks. This incorrect view comes from the OSI Model being based upon IBM mainframes. Layers happen, but in an ad hoc rather than fixed fashion.

To find out which distributions package your project, use Repology. The site tells you who has your project packaged, where it's out of date, and who the maintainers are. Very convenient!

Secret trick to make your open source projects better: if distributions package your project, have a look at their site patches every once in a while and take those that seem sensible. Often, downstream maintainers fix bugs but then don't report them back up stream.

I want engineers that get really annoyed at trash, and will obsessively call out anything moronic as such. I want engineers who have a deep affection for The Computer, have a practical understanding of why we'll never build it, but strive to anyway.

Want to make the slimmest USB C PCB ever? These footprints are now open source, and in public domain! Enjoy! Make sure your PCB is 0.6 mm thick, and show me the cool stuff you make with them. github.com/AnasMalas/pcb-edg…

Besides this, I am an avid contributor to the @FreeBSD project and would love to do professional work involving it.

Other areas of interest include planning and optimisation, which I researched intensely before pivoting to SIMD, and the engineering of SAT solvers. Please see my publication list for some examples.

What if we could process text with SIMD? Algorithms I was able to accelerate often see 10x and more speedups and I believe there is a lot to win here. What other applications could see this sort of advantage?

My work has so far mainly been about leveraging SIMD for workloads that you wouldn't usually consider benefiting from it. One area I have intensely worked on is text processing. The whole web is text and it's a shame we have our CPUs dig through it char by char.

I will be at #GSoC mentor summit in Munich for the next three days, in case anybody wants to meet for a coffee.

I am available both as a freelancer for contract work and as an employee for hire. I am willing to relocate within Europe, but jobs in Berlin or remote jobs preferred. Please send me a DM or email for inquiries.

I am looking for a job starting May 2026. I am an expert in SIMD programming, in particular for non-numeric applications such as text processing or database programming. Please have a look at my website for the sort of work I do. I am located in Berlin, Germany.

"But the computers are untyped". Computers are, of course, typed, just like every other useful thing. Digital circuits are a type discipline imposed upon analog circuits. It is precisely types that allow the creation of digital computers.

b4 I started in business I thought engineering-burnout had to do with constantly being faced with hard engineering problems & cracking under pressure doing business realized I craved hard engineering problems & was burned out by meetings/politics/lies/backstabbing/profitteers