trangus_1985's comments

Car accidents resulting in fatality are relatively uncommon, thanks to modern safety standards, and Tesla FSD doesn't have nearly as many miles as it needs.

Your sample size is way too small to be implying that FSD is safe - given a year or so, with millions more miles, we'll see what the score is.

By the way, and this is anecdotal, I was personally given a FSD demonstration a few weeks ago. The car immediately did an unsafe lane change in the middle of an intersection. Albeit, that was one of the pilot program beta versions.

> scroll back a few days

I did and I'm not sure what I'm looking for. Could you do it and post here so that I can verify what you're talking about?

>Sure you document such stuff before releasing it?

These are all likely documented internally - the process of cleaning it up is probably something they only care to do once a year. Very little of this affects most developers, and the stuff that does is available in the dev docs.

I can't go too into details, but now that the AOP is doing cryptographical operations and key escrow, the internal bus is likely to show up in future documents. Maybe not the AOP but certainly the mechanisms it uses to interact with the find my network. It may also be a separate find my network whitepaper.

"who hates HN"

This site, and this community, is great in my opinion. But it's not without valid criticism, especially considering the impact it can and has made in the industry and tech society.

"naively uninformed tantrum"

I'm unable to find the posts you're talking about.

They do yearly updates, the 2022 doc will very likely have more information. Regardless, the 2021 doc has some key foundations of the technology that are worth knowing.

The contract tracing docs _should_ be almost the same technology, and knowing how that works _should_ be a good start. At least, from my eyeing the OP's article as a lay person.

If you're not familiar with it, their platform security team releases a whitepaper about the technical details of their security. Regardless of how you feel about Apple, these documents are incredibly well done and interesting to read. The Find My section may have more information, as will their contract tracing docs (which use a riff of the same technology)

https://covid19.apple.com/contacttracing

I highly recommend anyone interested in security or privacy to read this from start to finish:

https://manuals.info.apple.com/MANUALS/1000/MA1902/en_US/app...

They had an agreement pre-established. I think he was just being polite. Versus "yo we agreed not to do this".

I made a coworker really uncomfortable by offering to smoke him out after work when he was visiting our site. But there really wasn't any recourse - he was conservative visiting from a conservative area (where it was "understood" that pot is a hard drug). I'm from the Bay Area: I'd been smoking weed since I was 16.

I've always been cognizant of differing understandings around the drug, but I definitely think it still takes some discretion.

By the way, the key difference between a drink at lunch and some pot is that im pretty useful around 2p with a drink - stoned, I might as well go home for the day. (Of course, everyone's different).

So, I think this discussion is worth having in a respectful manner - it's new rules.

I don't think HN was ever about just "technical" stuff. There is Lobsters for that kind of thing.

Out of curiosity, I brought up HN from 10 years ago on archive.org. I counted - 10 of the top 20 links were things that I wouldn't consider to be "technical".

It is a requirement, although you can now use "e-labels". Such as, a page in the settings that has the FCC information. (IANAL)

I've had it disabled for years, without it reporting home. So far, Microsoft seems to respect group policy and disabled services on Pro edition.

You've always been able to turn it off with group policy and disabling the reporting service. It still bugs me, on principle, that you can't easily disable it even on the Pro edition.

> we count the lethal damage caused to others

So, that's a pretty hefty claim. I'd like to see some data. :)

A very large chunk of motorcycle accidents are single party (about 25%), the rest involve a car, usually at low speeds such as an unprotected left turn or bad merge.

I did some quick googling and found that motorcycles are less likely to be involved in pedestrian accidents than cars, but I think the the onus is on you to support your claim.

Motorcycling is deceptively safe. It's just that the cost of finding out when you fuck around is very high.

Safe riding is still more dangerous than being in a car, of course. But, the vast majority of motorcycle injuries are due to known dangerous factors such as alcohol, or going too fast through turns.

Well, my fix would be to remove the "dick face" art.

And, if I was feeling fancy, spend an hour or two applying consistent styles, and trying to apply a linear and progressive story structure to the posts to help people understand the charges better.

Correct. It's a good assessment and I stand by it.

>Can you blame the guy?

IDK if you're trying to get a message out, doing things like that is extremely self-sabotaging to the message.

While the veracity of this is hard to determine, these sort of actions don't surprise me. If you have some of this evidence in writing, a lawyer might be a good place to start.

However, what really stood out to me was the design, or lack of it. The childish paint.exe job on the hero image doesn't help either. It really reads like a scrawled out screed of grievances, being aired without much forethought.

IANAL, but my understanding in the jurisdiction in which I live is that having this sort of stuff up can actually make your case harder! Refine the message and make it much more clear and logical.

In my opinion, you should take this down and contact a lawyer.

Ah, sorry, I guess my op wasnt clear, but that was my intent