andrewjf
Joined 12 years ago
Joined 12 years ago
I also use BGP advertised pod networks so each pod gets it's own IP address that's directly routable (l3 ipvlan) with the rest of my network (hint, don't use 100.64.0.0/10 for that if you use tailscale), so I don't bother with NAT on the host itself or port mapping or port conflicts. It also makes caddy in front of it super easy, barely an inconvenience.
Sorry John Gruber rather have his tech fix than standing up for what's right, I guess.
Half joking.
I used to manage Tru64 (Alpha) and OpenVMS (VAX and Alpha). Mostly Oracle DB and whatever they called their App development suite (horrible, horrible software) for a University's ERP system (called Banner) and infrastructure (Multinet on OpenVMS/VAX for DNS, DHCP, mail, etc). After that I moved on to AIX on Power5 for Oracle on HACMP and Veritas Cluster. Such a different world from what we have now.
I have an old AlphaServer ES47 running OpenVMS and Power5 560Q running AIX in my garage
IMHO, only languages with exceptions or Sum types that encode that a return is either a value or an Err (but not both) actually do what Golang says it does (make you handle errors).
The error messages seem to be written by people on a happy path who don't know how utterly broken almost everything about networking and DHCP even is.
And this is all IPv4! The IPv6 stuff is even more cryptic with different DHCP options and dealing with RAs and managed-flag, other-flag, etc.
It's infuriating. And I work on a team that writes code to generate all these things for automating bare metal for a living.
Frequently the desktop app and the safari extension won't be in sync and missing a recently added password, or doesn't show up on my other devices hours later. I still have no idea how the extension vs desktop app actually work together, or if they do at all.
Sometimes 1password (safari extension) is "locked" - but the desktop app isn't locked? and No amount of clicking the little 1password icon, that's supposed to unlock it does anything. Just a completely no-op button. Quitting safari _and_ the desktop app seems to be what's required to fix it.
I've been thinking about just moving back to native macOS keychain, but I haven't bothered to check on linux+windows support.
Your obsequiousness is disgusting.