At some point I think it will only be fair to require --insecure for #curl to do an unauthenticated protocol transfer (unless it is localhost). For clear text http:// etc.
If you can trick a user to run a command tool in a way that ends up causing the user problems, that is not a security problem in that tool.
Just saying. In case you're thinking of submitting such a report about a command line tool in your toolbox.
But surely no sane person would. Right? Right?
What do you think are the primary challenges for Open Source the coming years?
Security? CRA? Financing? Maintainer burnout? Recruiting young developers? Adapting to a country-former-ally going nuts? AI slop? AI bot overload? Something else?
(I'd like some more food for thoughts for an upcoming talk)
The AI bots that desperately need OSS for code training, are now slowly killing OSS by overloading every site.
The curl website is now at 77TB/month, or 8GB every five minutes.
The thing about me being a BDFL for #curl is that it has the D in there. I have the means and ability to push for just about anything I like. I say that I truly try to be a benevolent dictator, but then I presume quite a few dictators would say so.
Next week I will tell you all about how I view this dictatorship and how it is not quite like a dictatorship of a country since in our case, everyone could just leave if I misbehave.