Carlos Henrique Lima Melara

@charles_melara
28 Followers
29 Following
194 Posts
Debian Developer, Free Software Advocate, Software Developer, Bug Hunter
nicknamecharles
pronounsHe/Him
Homepagecharlz.net

In two weeks we run the #curl distro meeting. You are invited!

https://daniel.haxx.se/blog/2026/01/28/curl-distro-meeting-2026/

curl distro meeting 2026

We are doing another curl + distro online meeting this spring in what now has become an established annual tradition. A two-hour discussion, meeting, workshop for curl developers and curl distro maintainers. 2026 curl distro meeting details The objective for these meetings is simply to make curl better in distros. To make distros do better … Continue reading curl distro meeting 2026 β†’

daniel.haxx.se

Looking back at all (now) published vulnerabilities in #curl that were present in code from 2020 until now, at no point in those years was the share of "C mistakes" higher than 15% of all vulns.

Through all years, the C mistake share of all vulnerabilities in #curl was never above 45% at any single point in history.

Remember: on March 26 we have the annual #curl distro meeting. If you work on packaging curl for a distro, or a distro-like situation, I'd encourage you to join!

https://daniel.haxx.se/blog/2026/01/28/curl-distro-meeting-2026/

curl distro meeting 2026

We are doing another curl + distro online meeting this spring in what now has become an established annual tradition. A two-hour discussion, meeting, workshop for curl developers and curl distro maintainers. 2026 curl distro meeting details The objective for these meetings is simply to make curl better in distros. To make distros do better … Continue reading curl distro meeting 2026 β†’

daniel.haxx.se
on this evening, 18 years ago, the #Linux-libre project was launched.
https://web.archive.org/web/20140203134408/http://lists.autistici.org/message/20080221.002845.467ba592.en.html

before that, every distro that wanted to respect its users' freedom had to remove itself all of the binary blobs that were distributed as part of the kernel Linux's so-called sources

it took a little while for Linux to react to being so called out, by first making those binary blobs loadable separately, and then moving most of them to a separate subproject.

that didn't really solve any freedom issues, given that the drivers still demanded users to install and run those blobs.

Linux-libre joined the #GNU Project a few years later.

the set of blobs demanded by Linux has grown out of control, much faster than Linux itself. nowadays there are even binary blobs that contain a binary copy of Linux!

you might think that, after the split, the kernel Linux became entirely Free, and that the only remaining problem are the demands for binary blobs and the documentation that directs users to install them.

unfortunately, not even that is true. Linux still carries a few binary blobs disguised as arrays of bytes in what was supposed to be source files. there have even been recent additions to this wall of shame.

so it doesn't look like we'll be able to retire GNU Linux-libre any time soon.

when you're ready to try software freedom for real, we'll be here for you
https://linux-libre.fsfla.org/
[blag-devel] linux-libre

No comment needed

Did we just hit the grand irony of this decade?? OpenAI was the one bringing the hype on "AI" and all that vibe coding. Then a vibe coder creates an application built by "AI" (clawdbot, renamed to moltbot, now openclaw) and sell it to openAI 3 years later! I'm really amazed!

Disclaimer: it doesn't look like he sold open claw or his company, just that he joined OpenAI. But please give me the poetical freedom to enjoy the previous paragraph

RE: https://ursal.zone/@DanielaAbade/116040507653717907

Many shocked U.S. citizens yesterday!

happy birthday mewtwo!

PSA: Did you know that it’s **unsafe** to put code diffs into your commit messages?

Like https://github.com/i3/i3/pull/6564 for example

Such diffs will be applied by patch(1) (also git-am(1)) as part of the code change!

This is how a sleep(1) made it into i3 4.25-2 in Debian unstable.