MSFT should be tried in the Hague for silently overloading #curl with Invoke-WebRequest in PowerShell. Just tell me cURL isn't installed!
Edit: Thanks! curl.exe *is*, but still, justice for `curl`
MSFT should be tried in the Hague for silently overloading #curl with Invoke-WebRequest in PowerShell. Just tell me cURL isn't installed!
Edit: Thanks! curl.exe *is*, but still, justice for `curl`
Welcome Johan Eliasson as #curl commit author 1360: https://github.com/curl/curl/pull/16990
Reminder: we do the #curl distro meeting 2025 this Thursday!
https://github.com/curl/curl/wiki/curl-distro-discussion-2025
The blog post from yday brought back this question: why aren't we using C99 in #curl? Here's my past response:
https://daniel.haxx.se/blog/2022/11/17/considering-c99-for-curl/
Remember, if you just take this day as a weekend, your #curl rewrite could be finished
(from the collection at https://daniel.haxx.se/blog/2021/05/20/i-could-rewrite-curl/)
It's been six years now since #curl dropped support for HTTP/1 pipelining.
https://daniel.haxx.se/blog/2019/04/06/curl-says-bye-bye-to-pipelining/
I have never regretted it.
I updated #mbedTLS and #curl in #DOjS. This one took a lot longer than I expected because curl dropped Makefile.mk builds and I had to switch to #CMake or #autconf.
I went with CMake, but had to work around some weird problems.
#MSDOS and #Linux build are already green again, I'll tackle #win32 later...
New and Improved!
Choose your flavour, cURL or wget!
#curl
```
curl -o- #https://gist.githubusercontent.com/ajaxStardust/674b5d86f1f4386e72937a607e263608/raw/install.sh | bash
```
(Octothorpe placed, in hopes that st nick soon would eliminate any unwanted html anchors as hyperlink. i.e. remove it)
**Note:** it will place the app in your file system, at the location (if able without sudo):
/var/www/html/mydocs/11011101/
#wget
```
wget -qO- #https://gist.githubusercontent.com/ajaxStardust/674b5d86f1f4386e72937a607e263608/raw/install.sh | bash
```
Seriously. Anyone. please do check it out. I'm curious if it's working on anyone's system other than mine. It's as easy as running that curl command, just like you were installing #nvm for example. Nothing is easier than that. Except getting pregnant.
The #curl repository now contains more than 100,000 lines of documentation.
100,002 lines to be exact.
brute-force testing random #curl build option combinations non-stop like a boss
#ayuda fediverso #api #http #peertube
#ayudaTec
https://framacolibri.org/t/http-api-video-upload-legacy-path/25386
estoy tratando de usar UploadLegacy para subir un video a peertube, pero quisiera no usar #curl pero sino http. por preferencia personal.
no logro usar un path para el "videofile". si adjunto un binario dandole a add file desde bruno / postman en el body multipart form; va que chuta (vease https://codeberg.org/audricd/yt_2_pt/issues/2#issuecomment-3486267 gracias de nuevo @cosstab !!) pero ahora trato de usar un path file en lugar de un archivo.
@kyva_dev @trankten @t3rr0rz0n3 @sam
se agradece #boost
What do you think about vsock support in #curl ? https://curl.se/mail/lib-2025-04/0005.html
@bagder You maintain a 5,000+ line configure.ac file? Holy fuck. You poor man.
Folks, please help this guy get the therapy he needs:
#curl's configure script has 75(!) different --disable options to disable specific things in the build.
That's 37778931862957161709568 build combinations only there. Tricky to test.
I'll speak at Joy of Coding in Rotterdam in June: https://joyofcoding.org/speakers.html
I'll bring #curl stickers. It could be fun!
amusing stat: in #curl 8.13.0 we have "surviving" code lines from 622 authors. (who has at least one production code line with their name in git blame)
That's 11 *fewer* than in the previous release.
In fact, we peaked at 636 unique authors in version 8.10.1 and it has gone down since.
No, I don't have any conclusion to make based on this. It's just variations over time.
@bagder Matching #curl binaries for Windows ready at: https://curl.se/windows/