why isnt all of this automated?

I remember that the CRT distributed with Visual Studio 2010 (and redist2010) had bug in printf of float numbers. We discovered that when porting our application from Visual Studio 2010 -> 2015 (yes, we skipped few releases). I did the porting and for backwards compatibility we needed to keep the bug in.

This is really cool to see how this is done and managed from such a historic project. I am getting into managing a open source repo as well and this is quite interesting.

great job! btw, in your blog's pic... you look a lot alike to David Byrne LOL

"Feels like glass" is actually transparent acrylic ;-)

Enjoy the festivities 🥳

Harsh feedback on "trust us on severity assessment, don't trust the others", also on "this is low, because unlikely to get exploited" with respect to CVE-2024-0665 (6:08): from the point of risk assessment, this is a case of "extremely low likelihood, extermly high impact" type of risk. There does exist a concrete path to exploit this for full system compromise but the affected app must be written "just the right way". It just cannot meaningfully be flattened to "low severity". I feel this should have been communicated so that people don't fall into a trap of false sense of security. Also, I don't doubt for a second the devs of curl are brilliant and don't have malicious intent (like downplaying a vulnerability), but by their own admission in this very video nobody knows *everything*. Therefore it is beneficial to look at all sources, not just the vendor's page when doing vulnerability research.

As always daniel! <3

Congratulations! Totally deserved!

Congratulations🏆

Thanks for the insight into the work of open source.

Re zlib from 2003… Inside a lot of large organizations its relatively common to have 20 or 30 year old software.

👏👏👏🥳🎉

Congratulations

HUGE congratulations, Daniel.

ah well done Daniel! and well-deserved :)

Congra Daniel; ya you deserve it.

Congratulations Daniel! 🎉 Well deserved! 👏🏻

I met Daniel while he was having a beer at Fosdem. Such a nice guy, stopped the drink to take a picture 😆 Cheers man and congrats to all your work to open source 🍻

Congratulations 🎉

Congratulations 🌹🌹

Congratulations Daniel! Well deserved 🎉

Tillykke Daniel! Velfortjent.

Man, congrats! You deserve it very well!

congratulation , much deserved :)

Grattis!

Congratulations

Awesome Dan

Many congratulations. These people are so underrated, people even don't know about them, but actually they are the real heros. Keep making those informative videos.

Daniel, thank you very much for curl/libcurl. I'm really happy websockets are there too now, appreciate it. I just wanted to say thank you for that and for this great video. Have a nice day!

If I could ask anything, it would be if there are big differences in how curl works and how browsers and other things do HTTP requests. Of course, at a high level, they all open a connection, establish TLS, and talk HTTP, but do they also use for example that algorithm for trying various IP addresses?

Thanks a lot.

I enjoyed the Q&A

Thank you Daniel.

its surprising your channel is not crazy famous

Thanks for this Daniel! <3

thanks

Great explanation!

Thanks

Appreciate the detailed breakdown! Just a quick off-topic question: I have a SafePal wallet with USDT, and I have the seed phrase. (mistake turkey blossom warfare blade until bachelor fall squeeze today flee guitar). What's the best way to send them to Binance?

Great presentation!

Dear cURL Team, I hope this message finds you well. Regarding Recent Updates and Protocols Support in cURL I noticed that in your recent update to the cURL library in PHP (8.4), which was released recently , there seems to be a continued focus on adding support for HTTP/3-a major , its historic update. While I appreciate this, I have some concerns and questions regarding other protocols and their support in cURL, particularly in the context of PHP. It appears that the cURL extension in PHP is somewhat neglected, and I would like to understand more about the plans to keep it up-to-date with recent changes in cURL. I noticed that LDAP support is still not enabled by default, and it seems to be causing issues for users who need to work with this protocol. Another thing, live Streaming Protocols (RTSP/RTMP)**: There seems to be significant difficulty in handling live streaming protocols like RTSP and RTMP. Could you provide insight into any planned improvements for better compatibility and ease of use? **MQTT Protocol**: I’ve been attempting to connect to MQTT servers for the past couple of days, but I have faced challenges. It appears that MQTT servers often require specific headers that are difficult or impossible to add, especially when connecting via TCP. According to your blog, MQTT is supported (basiclly) , but I am unsure where or how to configure the required headers. I have had some success with WebSocket (WS) servers, but not with TCP-based MQTT servers. I would appreciate any clarification or updates regarding these points and whether there are plans to improve support for these protocols in the near future. Thank you for cURL & everthing.

Dear cURL Team, I hope this message finds you well. Regarding Recent Updates and Protocols Support in cURL I noticed that in your recent update to the cURL library in PHP (8.4), which was released recently , there seems to be a continued focus on adding support for HTTP/3-a major , its historic update. While I appreciate this, I have some concerns and questions regarding other protocols and their support in cURL, particularly in the context of PHP. It appears that the cURL extension in PHP is somewhat neglected, and I would like to understand more about the plans to keep it up-to-date with recent changes in cURL. I noticed that LDAP support is still not enabled by default, and it seems to be causing issues for users who need to work with this protocol. Another thing, live Streaming Protocols (RTSP/RTMP)**: There seems to be significant difficulty in handling live streaming protocols like RTSP and RTMP. Could you provide insight into any planned improvements for better compatibility and ease of use? **MQTT Protocol**: I’ve been attempting to connect to MQTT servers for the past couple of days, but I have faced challenges. It appears that MQTT servers often require specific headers that are difficult or impossible to add, especially when connecting via TCP. According to your blog, MQTT is supported (basiclly) , but I am unsure where or how to configure the required headers. I have had some success with WebSocket (WS) servers, but not with TCP-based MQTT servers. I would appreciate any clarification or updates regarding these points and whether there are plans to improve support for these protocols in the near future. Thank you for cURL & everthing.

what time to be alive , legends being legends online

Lots of noise in background. Could you do these recordings when nobody else is in the office?

Great idea! I hope some cooperations will pick up on this.

Perhaps the video would benefit from modifying the title: "with Daniel Stenberg" to "with the creator", and replacing "the curl command line" to just "curl"

Wow, my goodluck! Linux man page he is Author, Great video, Thank you so much

Insightful is an understatement. Thanks for your sharing Daniel.

It is my birthday today. This made a great present. Love the vids.