Soon, @bagder will be on vacation and @vsz, @jimfuller and myself can do what we want in the #curl project!

Wait…we already do what we want more or less…hmm…tricky…🙈

*looking at my secret feature list*

Now, which of these?🧐

Current weather for Marienburg SR / SA utilizing forza magnífico of wttr.in curl {ba{c{k{z{sh}}}}} and the sublime lolcat

Photograph in background composed with DSLR Nikon using FL Circular Polarizer 81A warming and of course Universal Love

#weather #curl #wttr #bash #csh #ksh #zsh #lolcat #technology #OpenSource #SR #SA #Marienburg #Commewijne #Universal #Love #UniversalLove

AWS SIGv4 is probably the most in-flux #curl code over the last years:

1. whatever AWS itself does is the correct behaviour
2. some parts of the behaviour are documented
3. when it does not work, rule 1 applies

This was the „industry norm“ situation before the IETF invented itself out of pure being-fed-uppery with the situation.

ok, for once I did replace #curl with the #aws cli tools in a PoC.

The curl command got several lines long, while it's a single aws call.

Sorry curl ...

#Unbound silently died on one of my #OpenBSD DNS resolver. And I only noticed it when I tried to DoH browse a website using #Librewolf.

Not what I expected to do today, but I now have #collectd monitoring the unbound process and sending a notification when there is no process alive. While I was there, I rewrote the old notification shell script into a 16 lines #Awk Intelligent one that pushes info to #Pushover using #curl; in reality, the script is 6 commands long but "Code is poetry".

(yes, this message contains non-paid products placement)

Youtuber "Low Level" speaks about #curl dropping the bug-bounty:

https://youtu.be/PG5sv20Jiic?si=Mg6Q0O_z69w69juk