> Public transit networks and shared autonomous vehicles are part of a complementary mobility ecosystem. As transit agencies modernize their payment systems to accept tap-to-pay debit and credit cards, multimodal trips are becoming more convenient than ever.
What a tonal shift immediately after the intro paragraph. I have to wonder how many times this went back and forth with PR and Legal to end up with this particular wording and to be the very first thing they stress after the basic facts. Especially the word ‘shared’ in ‘shared autonomous vehicles’ to connect people's thinking to ‘public’ transit. They even make sure to repeat the word ‘shared’ back to back to back in each of the final three paragraphs to make sure you end with that idea in mind. Yet all the cars are owned by Waymo and aren't ‘shared’ like the train and bus fleets which are owned by transit districts that I can vote on.
Translation: Waymo would like to learn how to prioritize their fleet of privately-owned vehicles, like where to have empty cars circling, where to expect them to be sent, and via what routes to send them, in order to replace the transit portion of the trip for as many riders as possible. Who wouldn't choose a single door-to-door trip over a transfer if the wait time is low and if the dollar cost of the private Waymo ride can be set approximately equal to the invisible ‘price’ people assign to the value of their time.
And just in case a reader doesn't pick up on that stuff, they directly tell you how to feel by quoting their very unbiased business partner:
> “San José has always believed innovation should make everyday life work better,” said San José Mayor Matt Mahan. “This partnership does exactly that by using new technology to strengthen public transit, not replace it, making regional travel more seamless and giving people more ways to get where they need to go.”
Fun fact: Waymo pay $4 to the San José Department of Airports for every pick-up or drop-off at SJC.
Widespread Waymo usage probably wouldn't “replace” the public transit routes we have now, sure, but it would remove the public's shared will to vote for transit expansions that could replace the Waymo portion of people's “““multimodal trips in a complementary mobility ecosystem””” (lmfao) instead of the other way around.
> When riders in the SF Bay Area use their Visa card to take a Waymo trip and public transit within 2 hours of each other, we will automatically issue $2.85 in Waymo Cash, which is the cost of a bus fare in San Francisco.
Great ‘anchoring’ technique in this wording too, to make people feel like $2.85 is getting them something tangible instead of being a pittance to pay for this type of hyper-personal behavior data.
> Fun fact: Waymo pay $4 to the San José Department of Airports for every pick-up or drop-off at SJC.
This is pretty normal. LHR charges £5. SYD charges A$5. Airports are often highly congested and pushing more people to take public transit instead of private drop-off/pick-up is a big lever.
> Fun fact: Waymo pay $4 to the San José Department of Airports for every pick-up or drop-off at SJC.
That's pretty common, no? Many airports have fees that even traditional taxis have to pay (which is usually passed on to the rider as a part of the fare). It seems reasonable to me: car traffic can be be pretty bad at airports, and extra fees help encourage people to take buses, shuttles, trains, etc.
But overall, I do agree with your worry about this framing/anchoring harming future transit expansion projects. And I'd bet that Waymo would be right there lobbying against any transit expansion that threatened one of their well-established last-mile routes.
I do think transit just needs to be better, though. I could take transit to SFO (either Caltrain+BART or Muni+BART), but my car ride there is 13-16 minutes (via Lyft/Uber; Waymo still can't drop off at SFO proper, and it's a 19-minute walk with luggage from where they will drop off). Best case with Caltrain+BART is 33 minutes (but only with an express train during rush hour), and is more like 45 minutes for the rest of the day (and that's assuming the comparatively-infrequent Caltrain service lines up with my needs). I can take a Muni bus to BART (and actually have several choices there), but the total trip time is 50-70 minutes that way. Then there's the general uncertainty of making the transit connection without issues. (Yes, I'm fortunate that I can afford Lyft whenever I need to go to the airport. I ride transit within the city often, but it just doesn't work for me for airport trips.)
I think of other cities like Tokyo or Taipei, where taking transit from the airport to the city is a reasonable option, and is often faster than getting a taxi (and for Narita to many places in Tokyo, it can be north of USD$200 to take a taxi). Even in NYC it's often faster or at least reasonably convenient to take transit to one of the local airports, even Newark. Don't get me wrong, SF's transit system isn't bad! Even though it's not going to stand with the best in the world, it's still great and I use it often. But it has some very significant gaps.
Yep. I live in SOMA, near both the freeway and a BART station.
Without traffic, a car has me (and a friend) curbside in 12 minutes for $30. Even during rush hour, the southbound traffic between the 7th St onramp and the SFO exit is almost never very slow (while NB is always a standstill).
BART is 30 minutes on the train + however long it takes to walk to the station + the transfer from BART to SFO AirTrain to get to the terminal. Minimum 1 hour. Easily another 30 min if you're unlucky with train arrivals. And by getting off BART at the airport stop, you pay a premium fare of $11.80 per person.
I don't really think it's about the data. I think by Occam's Razor, Waymo (owned by Google) just sees a way for them to put transit directions in Google Maps where the last mile of your trip is a Waymo. By subsidizing part of the transit cost and it all being on one credit card, in the future you could pay for a whole transit + taxi trip only once and not multiple times at each leg
Nerds have vested interests (exposure/influence/status based on exclusivity of skill) to oppose letting ”the wrong people” create software, versus a company like Microsoft is the other way around because they get paid and get to further-entrench their platforms (but I repeat myself).
And/or too many people have internalized a feeling of “I am Very Smart because I know better than to ever try anything unique”, as exemplified by that awful xkcd ‘Standards’ learned-helplessness comic somebody will always rush to post in a discussion of any New Thing, and thus would never even dream of creating RAD tools whose entire premise is the creation of bespoke software.
> Ganatra: I-- this-- it's tough, because I don't specifically remember-- it's not like a presidential assassination or 9/11 where, "Where were you the day that Copland was cancelled?
What? The GBA knows exactly what it is and has all sorts of sprite scaling and rotation features that would look like total crap on a CRT: https://gbadev.net/gbadoc/sprites.html#attr3
Look at Kuru Kuru Kururin for example, a launch title where the GBA's fancy new sprite rotation effect is kinda the entire game:
Some server-focused programs pull in UI toolkits anyway. Take qBittorrent for example: I only use its web UI, but it's still a QT program, and on my OS of choice its package will try to pull in a bunch of display-related stuff by default unless one knows to use the “nox” package Flavor: https://cgit.freebsd.org/ports/tree/net-p2p/qbittorrent/Make...
> The rest of the upgrade came out of my junk drawers. Two DDR4 sticks from an old laptop take the memory to the platform maximum of 32 GB
Realtalk: make sure you are religious about testing your RAM if you're going to run ZFS with non-ECC RAM. I'm not going to say “don't do it”, but know what you're getting into and how to protect yourself from this failure mode.
It's unintuitive, but ZFS will actually modify your files on disk as a side effect of a read-only operation if blocks get read into bad RAM and checksum mismatch compared to the blocks on disk.
This happened to me in 2013–14 with some bad PC3 10600 in my 2600K desktop FreeBSD system, and it rotted a bunch of my most frequently accessed files. I was able to figure out what was going on once audible blips started appearing in all of my favorite most-listened-to music, then I learned about `flac -t` and was able to confirm the rot thanks to the fact that FLAC files embed an expected MD5 digest in their `STREAMINFO` block. `man flac` sez…
“In test mode, flac acts just like in decode mode, except no output file is written. Both decode and test modes detect errors in the stream, but they also detect when the MD5 signature of the decoded audio does not match the stored MD5 signature, even when the bitstream is valid.” (emphasis mine)
[Lammy@popola] flac --test "Floating Door - Hypersomnia in loop - 12 templeOS.flac"
Floating Door - Hypersomnia in loop - 12 templeOS.flac: ok
[Lammy@popola] metaflac --show-md5sum "Floating Door - Hypersomnia in loop - 12 templeOS.flac"
d9ccdc78cfa45dda01b38198575b4f56
[Lammy@popola] flac --decode --stdout --silent --force-raw-format --endian=little --sign=signed "Floating Door - Hypersomnia in loop - 12 templeOS.flac" | md5
d9ccdc78cfa45dda01b38198575b4f56
After that experience, I moved my ZFS storage to a dedicated system — first on an Atom C2750 board and later (and currently) an Atom C3758, both with ECC UDIMMs. (Stay away from the C2xxx series tho; they are all doomed to CLK-circuit-degradation death which repairing only prolongs but does not prevent)
Which ironically makes the Internet more surveillable, because now every single connection has to hit some TLS-terminating origin and can't be cached at the edge of our own networks. Don't confuse security with privacy.
Let's be realistic, very few networks had speed-improving caches that weren't surveilled. Transparent proxying was most often used to inject malware and fourth-party ads, instead.
The internet is only more concentrated because most people choose price and convenience over a foolproof level of security. The cost/effort required to surveil traffic in coordination with TLS-terminating CDNs is multiple orders of magnitude higher than the effort needed to throw some high-Tbps middlebox in an IX rack to siphon every packet passing through it.
Not what I'm saying. No coordination is necessary. I'm talking about metadata, not encrypted contents — just the fact that you made some number of connections, at a certain time, from a certain network, to a certain network, in a certain order, with requests and responses of a certain size. It really doesn't matter what's inside.
- https://youtu.be/kV2HDM86XgI?t=1072 “First of all, David's description of what you can do with metadata […] is absolutely correct. We kill people based on metadata.” ― Former NSA and CIA director General Michael Hayden (2014)
Sure, but hiding the contents provides a lot more value than hiding some parts of metadata.
It's ridiculous to argue otherwise.
It's true that general resources could be cached in some cases, but personalized information couldn't be (and yes was served over HTTP, not just HTTPS).
> It really doesn't matter what's inside
It certainly does matter what is inside, and it's trivial to think of cases where it does. Hiding that content is much much more valuable.
My point is that you aren't. For example under the old HTTP only internet they could see you were visiting HN, who you were and what you published.
Under HTTPS they see you are visting HN.
It's strictly better except in cases of visiting highly popular data which was cached in public caches. These public caches were much less wide spread than you appear to believe (for example in Australia the Internode ISP tried one for a little while but abandoned it because of the problems with it serving info one logged in person to another - cache invalidation was frequently buggy)
> One will note that it's called ‘HTTPS’ and not ‘HTTPP’
Not sure who that is aimed at but I didn't write HTTPP, and yours is the only mention of it on this page.
> lol
If you are going to lol you had better make sure you are correct about what you are laughing about....
> These public caches were much less wide spread than you appear to believe
You can keep your belief or disbelief. I ran my own, transparently with Squid on my FreeBSD PF gateway box back in The Day when we had a cable ISP with a restrictive data cap. I could send my roommate a link, or reload a link myself any number of times, and it never left the edge of my network after the first. It was really cool.
These days you don't even need to actively do anything for most operating systems' default configurations to loudly announce your presence and behavior to the ‘Room 641A’s of the world:
- Join any Wi-Fi network and your OS or browser (or both!) will automatically hit a well-known captive portal test URI.
- Most OSes will hit an NTP server that reveals the OS maker (depending on if it's Google's or Apple's or Microsoft's or the NTP-dot-org pool) as well as providing a heartbeat to tell the network you're still physically present when you make subsequent requests every ${default-periodicity} minutes following the first time sync following the captive portal check.
- Then once TLS' regressive dependency on synchronized time is satisfied, many default OS installs will hit a weather API whose transport layer is “secure” but whose response size is, if not unique among all possible geolocations that could be requested at the same timestamp, at least a piece of identifying information to combine with others. If I were NSA I would be making requests to APIs like Foreca for every possible geolocation at every ${change-frequency} seconds and storing every bit of sidechannel metadata about them forever for comparison with other recorded traffic.
- And most people's machines will announce their unique collection of software to the world through the act of making network connections to the known networks for the background update checks and “““telemetry””” (remember when the term was “spyware” for anything that remotely reported user behavior?) that have sadly become normalized in modern software.
if you visit wikipedia.org/whistleblowing, what exactly value is there from hiding content but force revealing you visited it, making sure it can't be retrieved from a cache within your organization/school network?
and doesn't pervasive tls termination mean that Cloudflare/etc sees plaintext anyway? do we really believe that palantir isn't tapping into that?
i can imagine just a few scenarios where hiding content on the web actually achieves something. mainly stuff like webmail, web chats, banking.
> if you edit it to leak a secret the protection is everything.
It’s really not, because knowing when you edited it is already enough, given that there’s a timestamped edit history. And the size and shape of your request payloads will show that you edited it, not merely performed GET requests.
Can't cache interactive content which is probably more invaluable than static. HTTPS is overall a massive win, which is why NSA wanted to surveil it in the first place.
reply