Skip to main content


#libcurl has proudly served as the HTTP(S) engine in #git for nineteen years now.

Seirdy reshared this.

in reply to daniel:// stenberg://

it sometimes boggles even my mind to say something like that. Time flies!

You can write transfer library replacements, but it is hard to compete with the age, experience and polish several decades of Internet transfers bring.

in reply to daniel:// stenberg://

So I can blame you now for every single commit any developer has ever made? 😜
in reply to Ondřej Kolín

@ondrejkolin you mean like git push origin main to a remote? Like with Github or GitLab or Gitea or Bitbucket or Codeberg ;)
in reply to HAMMER SMASHED FILESYSTEM 🇺🇦

@lkundrak libcurl established a presence already decades ago, yes, but that does not mean that we relax or think we are done. Internet transfers keep evolving and so does libcurl.

We work hard to satisfy all the old legacy needs and support the new upcoming ones - at the same time.