I once wrote a cloud status monitor UI for a corporation that wanted to migrate its customers away from on-premise.

The availability was not good and managment ordered the red to be changed to a more pleasing color. A red bar for several hours made it too easy to notice that their cloud sucked.

After some initial resistance, I „fixed“ the color, possibly mumbling obscenities.

Some people said I am „difficult“ to work with. That might not be totally wrong, from their perspective.‍️

Do not travel to the USofA, part XXXIV:

- doing everything right is not enough
- white skin does not protect you
- detention may mean a cell shared with 70 people, fighting over food, without medical supplies
- your signature will get forged if you refuse
- judge orders for release on bail are ignored

https://www.theguardian.com/us-news/2026/feb/09/irish-man-seamus-culleton-ice-detention

@david_chisnall Perhaps @CoolSWEng can shed some light on this?

@david_chisnall @wingo @whitequark Thanks for the insight.

@wingo @whitequark Ritchie probably spins in his grave.

These standardization foobars commonly happen when implementors with commercial interests seek to „compromize“ out of being buggy.

Update: @david_chisnall points to this probably just being a misbehaviour of earlier tool chains. See below.

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.

@david_chisnall Otoh, if someone starts paying people to be decent persons, please give them my name. ‍️

@david_chisnall I think that is a money sink without a bottom, willingly taking in all money from everyone.

@bagder Yes, that would explain some things. Meh…