Search

Items tagged with: CURL


I found the chosen colors hard to distinguish in the key section and map to the graphs.

#curl does actually get way more PRs than issues?!

#curl


Look at that plot for monthly pull-requests in #curl taking off like its on steroids.
#curl


The funding of critical open-source projects of our everyday lives has becond increasingly important. The Sovereign Tech Fund has set out to improve the situation with various programs that assist these projects as @polexa explains.

We're thrilled being joined by @bagder who shares his experiences with maintaining the #curl project and the STF.

🎧 focusonlinux.podigee.io/113-so…

#FocusOnLinux #Podcast


#curl


#curl


#curl


#curl


Trying out what a #curl family tree could look like.
#curl


@markuswerle @jakob @pluralistic This is how I interpret the situation: #GitHub offers open source programs free access to GitHub actions today exactly as it did in the past. This access is limited in CPU performance and parallelism. It always was. All free CI services do this.

The #curl project was bumped to a fancier account to give us more actions powers: more CPU and more parallelism.

That is them doing us a favor and them supporting us, not the other way around.


with this knowledge we are pondering what we can to do make things less annoying for #curl on Windows.

What now takes a few milliseconds on my Linux machine, takes several seconds on Windows. Not ideal.

#curl


#curl


what people have been using for years already will start working in #curl 8.10.0: -vv, -vvv and -vvvv for more verbose logging.

Up until now, adding more vs did not do anything different.

github.com/curl/curl/pull/1397…

PR by the awesome @icing


Here's one way to view the 28 transfer protocols #curl supports.
#curl


#curl


#curl


#curl


#curl


Starting now, #curl shows extended help for a given command line option if you write it after --h. Like "curl -h --location" or "curl -h -O"

Shipping in the pending curl 8.10.0 in mid September.

github.com/curl/curl/pull/1399…

#curl



Unpopular opinion: Damn cool kids with their HTTPs 3 and QUICs and whatevers. HTTP/1.1 was good enough for everyone!

They're adding all that fancy stuff into the new #cURL version, and it causes #Transmission to crash. How am I going to seed all these Linux images now?!

github.com/transmission/transm…
github.com/curl/curl/issues/14…

#Gentoo


Bugfix rate in the #curl project is currently racing to an all-time high.

(yes, presumably this also means we insert more bugs as well as there need to be something to fix...)

#curl



#curl


The fifth QUIC backend being worked on for #curl could make the topology map look like this soon
#curl


#curl


#curl


#curl


I have this slide showing the 101(!) operating systems people have reported #curl to run on.

I now have a customer call scheduled about porting it to a 102nd...

#curl



According to @bagder the stubborn way the #OpenSSL project is handling #QUIC implementation is directly responsible for delaying HTTP/3 adoption (1), and I tend to agree. When the project rejected the community QUIC patches and decided to go with their own design, it wasn't difficult to predict problems. This was proven right by the massive feature gaps (2) and performance issues (3) discovered by @icing when trying to marry OpenSSL QUIC to #curl. Even with API fixes released in version 3.3 the implementation is still inferior, and there is no good solution in sight.

1) lwn.net/Articles/983380/
2) github.com/openssl/openssl/dis…
3) github.com/icing/blog/blob/mai…