persona_reuse

MAX has dedicated right-of-way outside the city centers, but in the cities it shares city streets. Tourists drive / stop-at-lights in the dedicated lanes a lot.

Streetcar is more susceptible to being stopped because someone parked over the white line, but with 20 minute headways it takes longer to cause a problem.

It's the Uber model. Operate at a subsidized low price, create stickiness, push out the previous generation, enshittify and raise the price, $$$.

I really thought the AirTag2 was heralding a watershed moment of UW2 in every model of phone.

One can figure out 'how' and 'what' from the code, given enough time. The most valuable thing in code is the brain of the Past Person who wrote it, looming over your shoulder, telling you 'why' in very explicit terms.

That 'why' also helps to show that Past You knew wtf you were doing, and lets Present You feel confident in making changes, because you know what the intent was.

"I'll remember this!" is one of the greatest lies in CS.

I can't remember where I read this and I can't find a cite right away, but I bet someone can confirm-or-correct me: the 6-letter reservation code for your flight? That used to be an explicit pointer of memory in oldold Sabre.

> because you never know what rules they are gonna enforce this time and for whom.

Narrator: "It was Gasly."

https://www.cbsnews.com/sanfrancisco/news/reid-hillview-airp... - closed for lead.

https://en.wikipedia.org/wiki/Meigs_Field - closed for 'safety'.

The concern among General Aviation is that there's nobody making new airports. Each loss is something that's almost certainly never coming back.

Previous company, I was a principal IC and I used to interview people. I was warned by HR never to discuss how the interview went or why the candidate bombed.

Their notion was: 1) We're there to find candidates, not improve people. 2) Time spent on someone you've eliminated is a loss. Cut your losses. 3) Think like you're talking to the police. Are you 100% sure you're not going to say anything that could be even remotely construed as illegally discriminatory? 4) Most states are 1-party-consent for recording, and even if it's an inadmissible recording, them having an interaction recorded can come back to bite you if they use it to jog their memory to perfection.

I think it's gross, but it's a litigious race to the bottom so I kind-of see their point. Really happy not to be an interviewer anymore.

Do the math. Their expenses for 2017-2018 were 81,442,265 (81 million). To live off interest (let's say they pull a safe and solid 5%. If you can reliably do better than 5% with annuity-level thinking, good for you), they'd need 1/0.05 = 20 times their run rate, or 1,628,845,300 (1.6 billion).

They hold just under 135 million in assets, so they'd need 12 times what they currently hold. That's why living off interest wouldn't work. They'll need the telethon til they can make that equation work, or at least come closer.

5 years of VPN admining here.

The openvpn community is pretty nonexistent. Core is about 10 guys (half on loan from the for-profit company) and they're multiple years behind on where the development should be.

2.4 release: currently 3 years old, decently robust, but limited. 2.5 release: 38 of 51 blockers still open, no release date in sight. 3.0 release: roadmap was written in 2010, no release date in sight.

OpenVPN 2.5 is where we'll have per-user tls-crypt. tls-auth/tls-crypt in 2.4 means when the PSK (that all clients share) leaks, you have to rotate a PSK for ALL users all at once. Or you could not use that PSK at all and just get DoS'ed over UDP all the time. OpenVPN 3 is where they're looking at being multithreaded. Let that sink in for a minute, because the devs haven't. You share one core with EVERYONE who's connected. openvpn is, performance-wise, a glorified openssl-pipe-to-nc at that point.

These are features that any server admin should be dying to have, because they're what let you scale from "my cute little tunnel from my home to my cloud instance" to "endpoints that can scale."

Tuning to get solid performance means getting the client config right with a lot of low-level tweaks, a lot of iperf and network-ops knowledge, shipping it out to the userbase, and hoping it works in their situation. Tuning later because you screwed anything up is hit and miss: some features you can 'push' out and fix, some you can't. The devs can't imagine tunnels where someone who isn't as immersed in the code as them doesn't control all endpoints and all configs, or where there's no burden to walking around and changing every user's config. I'm years into this and I'm still finding things to adjust or submit patches for, to make my users happier.

OpenVPN has one thing that other VPNs severely lack: a ABSOLUTELY SUPERB hook system. You want to have actions trigger scripts, they got u fam. You can do a lot of serverside and clientside magic because of that, integrating with your SSO and ACL management. Wireguard is much more in the beautiful-in-its-simplicity-but-that-still-means-simple 'static definition' camp (for now).

> I doubt we could have done anything more to not make it sudden for you.

It should have been a new-window snippet. Depending on users to read blogs is living by hope. They should have put the news in their faces, unavoidably.

To me, the sad part is (based on what little you can find in public bugs) the Shield team seemed to be engaged in this, and didn't raise a flag that their platform of experiments was being co-opted to push out a game.

There's all the talk that Mozilla violated peoples privacy, and they're not wrong, but the larger loss, I think, is all the technical people who will turn off Shield and never come back to using it.