Hacker News .hnnew | past | comments | ask | show | jobs | submit | gsnedders's commentslogin

Apple’s own style guide says to use the name of the appropriate release: https://support.apple.com/en-gb/guide/applestyleguide/apsg72...

RSS 2.0 is kinda an unspecified mess, and at least 15 year ago, if you wanted to be compatible with the majority of content you needed some weird heuristics to detect which interpretation of the spec a given feed was using (lol).

And Dave Winer was strongly against ever clarifying the spec, and that’s part of what led to Atom.


Other common approaches:

1. Per capita

2. Per registered vehicle

3. Per trip

All of these have upsides and downsides (as does “per vehicle km”), and all will paint different pictures with different distortions.


https://www.spiegel.de/auto/aktuell/tempolimit-koennte-jaehr... claims a 75% higher fatality rate on unrestricted autobahn v. autobahn with speed limits.

But in general: freeways/motorways (whatever you want to call them) almost never account for the majority of fatalities anywhere — there’s a lot that makes them safer than the average rural road even given comparable speeds, and there’s fewer vulnerable road users around.


At least in SF, there’s both a phone number and a QR code on a sticker on the driver-side window, and per what’s linked from https://waymo.com/firstresponders/ it seems like that’s a dedicated phone line.

I wonder quite what the priority matrix looks like for support requests; I’d expect something like:

1. First responders 2. Human-initiated in-vehicle 3. Autonomous-initiated vehicle

But I of course don’t know.

Buttons are something that seem inherently obviously (both internal and external), but I’m also never sure quite how useful they’d be: a lot of the things that have gathered press have involved vehicles driving when it was unsafe to do so, and then any external button is of minimal use.

I also expect they have some level of concern about anything external having an abuse potential? (e.g., deliberately walk in front of an AV just to stop it in the road)

Something like “give first responders some mobile app which provides some level of direct control” feels like it should be doable (authentication there seems unlikely to be harder than the various “educational” authentication gates that Alphabet has in many products) — though of course that doesn’t scale with more AV operators, and thus maybe this just falls into the category of “this should be standardised” (by whatever SDO).

And some can clearly just leverage existing datasets — many jurisdictions have ways to publish things like “this road is closed from X to Y”, and you can imagine a slightly broader case of “close a radius of Z from point A” being something you might want, especially in the AV case (imagine a “police incident” closing an intersection, such as the one a Waymo drove through a few months ago — you probably want to close a bit beyond the interaction itself in all directions!).

And sure, to some extent things can be handled by AVs getting better at understanding their surroundings, but we’ll always have the question of whether they’re good enough, especially when they fail in non-human like ways.


Interesting, I can't say I've seen that sticker, but I've never looked for one there, either, as you're not supposed to use the driver's seat and it's always buckled up.

AS2 was mostly following the direction of ES4 — so it wouldn’t have diverged if it hadn’t been abandoned.

You cannot stop in a cycle lane to drop people off without first driving into the cycle lane.


That is technically correct but not how the language works.

"Advisory and mandatory cycle lanes, marked by a painted line, can be entered into by taxis and PHVs for pick-up and drop-off at the kerb edge"

You are allowed to drop off people in a lot of places you aren't allowed to drive or park.


A few devices do support USB 5Gbps over Lightning!


Also just unit tests in the source files, which again aren’t included in the binary via compile-time flags!


See e.g. https://developer.apple.com/documentation/network/creating-a... where the logging output makes it clear BoringSSL is what is used.

Or comments such as: https://github.com/apple-oss-distributions/Security/blob/rel...

Unsurprisingly, given BoringSSL doesn't have a stable API (yet alone ABI), it isn't exposed as a system library.


Seems like they use BoringSSL on their open source distributions, but their own library on their own platforms: https://forums.swift.org/t/native-implementations-and-boring...


CryptoKit isn't relevant to `goto fail`, which was the origin of this thread, given CryptoKit merely implements primitives and not TLS.

If you really are doubting what gets used for TLS, open up Console.app, start streaming, run `nscurl https://example.com/` (or load it in Safari, etc.), and you'll see logging like:

    default com.apple.network boringssl 18:11:46.229209-0700 libboringssl.dylib nscurl boringssl_session_apply_protocol_options_for_transport_block_invoke(2360) [C1.1.1.1:2][0x1008cef10] TLS configured [server(0) min_version(0x0303) max_version(0x0304) name(redacted) tickets(false) false_start(false) enforce_ev(false) enforce_ats(false) ats_non_pfs_ciphersuite_allowed(false) cc_mode_enforced(false) ech(false) pqtls(true), pake(false)]
It really is boringssl which is nowadays used for TLS by the Network framework.


iOS Safari definitely used BoringSSL last time I checked it with Frida


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: