@clacke@loke@amberage I found an online converter that can convert back and forth between dew point and rel hunidity for a given air temperature. It also tells you the vapor preasure and absolute humidity.
@loke@clacke@amberage over here: 24°C with 15°C dew point: nice and warm 24°C witg 20°C dew point: damn why is this air so heavy I just want to lay down and conserve energy
@marcan@drewdevault@sxpert You know it, and take care of it, but if an average developer goes like "oh, marcan's project installs through curl|sh so I'll make mine install through curl|sh too" how will they know to include such protections?
btw. yes this happened, at previous job we got hit with an application-level DDoS of low bandwidth and around 1000 req/s which was 100x more than normal traffic and overwhelmed our shitty Django webapp.
Banning IPs / rate limiting didn't help because they kept coming with new ones. I'd somehow need to know the list of IPs ahead of time.
Caching would probably work until they figured out that the session cookie (ppl can log in) must be part of the cache key.
By the way, have you considered coming up with some convention on keeping the default mailing list address in the repo (as opposed to in .git/config) ? I know for large projects it's not that simple, since there are multiple mailing lists and you have to choose the right one, but I think for small projects it would be enough and would make contributing much easier if both git.sr.ht and git-send-email supported it.
@michiel@cjd I think IETF would not allow an internet standard with a single implementation, and I don't think they're capable of iterating at such breakneck speed as WHATWG
@BalooUriza@fribbledom counterpoint: at $dayjob, we (SRE team) rely on people asking multiple times if they still care about something. If we end up not doing it immediately, and a few weeks pass since the initial request without anyone asking again, we will assume it's no longer needed.