1. User complains to #hackerone that I named his *previous* name when he renamed himself to a silly name after I banned them in a #curl report filed back in October. 2. Hackerone asks me to respond on their support forum, on which I have no account. Grrr. I refuse to. 3. Replying to the hackerone email about this instead, I get a bounce saying they don't accept emails on support@hackerone ... Kill me now.

I added a sentence to the #curl hackerone submission page: "Please present your case briefly and to the point. Do not use an AI to help you blab hundreds of lines that will exhaust us to death instead of making us understand your claim."

We end the year with 6 more #curl command line options than we had last new year's eve; now at 273 in total.

#libcurl grew with a mere 100 lines of code in 2025. At 149,000 lines.

"Subject: New financial contributor to curl: CarGurus ($3,000.00)" I don't know what CarGurus is, but I love it.

If your company needs #curl support for OpenSSL 1.1 in 2026, just say so and we can have you covered in no time. OpenSSL 1 support is dropped from the regular #curl releases but is available as a commercial offer.

When you need to shrink your SVG images to their bare minimum, this is an awesome resource:

SVGOMG - Optimize and minify SVG images

make a photo realistic embroidered wall piece with the words "never expect two independent URL parsers to treat every URL identically" okay, that failed "again without repeating any words" *ripping my eyes out*

This is not working. The number of #hackerone report submissions for #curl in 2025 is going through the roof, while the quality is going through the floor. And the year isn't over yet.

If you've been wanting to speak securely to your garage door or whatever MQTTS capable devices you want to control with your #curl command lines, look no further: (this is planned to merge in time for the March 2026 release)

GitHub

mqtt: initial support for MQTTS by bagder · Pull Request #19418 · curl/curl

test cases documentation