Computer Graphics (GLES/Vulkan/DX12/Metal) | AI Researcher | GPGPU (HPC) | Programming Python/C++/Cuda | AI Engineering (CV,3DGS,RL) | Gamedev | Aviation
Joined January 2022
- Tweets 1,430
- Following 196
- Followers 79
- Likes 1,699
wh1t3lord retweeted
2025 Canadian Federal Election by Polling Divisions:
I am the first person in Canada to make this, which took me 8 hours, and cleaning up the data alone took me 7 hours.
Please consider a like and repost!
Feel free to ask for any insets (zoom-ins)
wh1t3lord retweeted
Recently, there was a clash between the popular @FFmpeg project, a low-level multimedia library found everywhere… and Google. A Google AI agent found a bug in FFmpeg.
FFmpeg is a far-ranging library, supporting niche multimedia files, often through reverse-engineering. It is entirely the result of volunteers and a marvellous piece of technology.
For people who have never been on the receiving end of ‘security researchers’, it is difficult to understand why there is a pushback against them.
Think about the commons. In Quebec, these are pieces of land where farmers send their cows during the summer. It is collectively owned, like FFmpeg.
Everyone is responsible to care for the commons if they are using it. If you are not using it, you are supposed to stay away.
Now, imagine a rich corporation comes in and sends its well-paid agents into the commons to find issues with it. Maybe a broken barrier or a dangerous hole. So far so good… But instead of fixing the issues, the corporation says “you have a month to fix the issue or else I will report you to the government”.
How much love would the big corporation get in this context?
Why do the security researchers insist on disclosing the issue without having contributed to fixing it? So that they can get credit for it. That's their entire scheme: find issues, irrespective of whether they affect the use case of their employer... after all, all issues no matter how small can be potentially significant at some point... and then brag about it without doing the hard work of trying to fix it.
Let me be clear that no everyone working in security behaves this way. Many are good actors. But there are enough 'security researchers' behaving as parasites that it has become a recognizable pattern.
« But Daniel, who should be fixing the bugs then? »
If you are paying for commercial support, then get in touch with the folks you are paying. If you are not paying, then it is on you.
It says so in the licenses. It is part of the moral code open source. It is part of the legal framework.
Let me be clear. You do not get to bite back at Linus Torvalds if a bug in the linux kernel crashes your server. What you do is that you identify the issue, narrow it down and propose a fix. If you cannot do it, then you pay someone to do it. Or you just do not use Linux.
wh1t3lord retweeted
November 1, 1512: The ceiling of the Sistine Chapel, painted by Michelangelo, was exhibited to the public for the first time.
wh1t3lord retweeted
The US Air Force Reserve Hurricane Hunters flew straight through Category 5 Hurricane Melissa, capturing an incredible view from inside the storm’s eye.
wh1t3lord retweeted
Canadian Tire says it will begin selling the iconic Hudson's Bay point blankets and has pledged to continue a program started by HBC to donate the net proceeds to support Indigenous-led initiatives. toronto.citynews.ca/2025/10/…
Toronto renters should make about $44 hourly to comfortably afford a one-bedroom apartment: report cp24.com/local/toronto/2025/…
#Canada is so lucky to experience all four seasons to the fullest! In fall, it's one of only six countries where you can see vibrant red foliage—thanks to the same pigments found in cherries, anthocyanins. What's your fave place to go leaf peeping? 🍁
wh1t3lord retweeted
Physically Based Content irradiance.ca/posts/pbr/