thanks, good catch. it got stuck when js was off, we fixed it today, try a refresh if you want

Hmm, interesting, I thought I was human. Anyway, as far as I can tell this is within the rules here?

Fair. We run proxies, so “proxy or site?” is the question we care about, and I didn’t trust the error messages to answer it.

The point is what you do after. If the proxy hung you rotate it out. If the site hung you slow down on that site. requests blames the site by name either way, so you can end up throttling a site that’s fine and keeping a dead proxy. That’s why.

it does when the other side allowlists a hostname. plenty of firewalls and saas allowlists only take an ip or a cidr though, and they don’t re-resolve, so the entry breaks the next time your isp renumbers you. it also only helps if the traffic actually leaves from that same connection.

nice. the ones people tend to forget are alpine-based containers that run sshd inside. on alpine ssh -V won’t settle it, since the fix is a backport, so check the package with apk info openssh instead.

git log -S'some_string' -p is the one that pays for itself. it finds the commits where that string was added or removed, so you can track down when a function disappeared without reading through history. -G is the same idea with a regex, matching any changed line.

and git log --follow -p path/to/file keeps going across renames, which plain git log file won’t do.