floatingatoll

(I don’t like my advice here, now that I’ve had something to. File a safety complaint, not a feature rollback request. They’re more likely to listen that way.)

Previously on HN, there was a 288-comments discussion on “Mindfulness and meditation can boost depression and anxiety” (2020): https://news.ycombinator.com/item?id=24185710

When considering these two studies together, I find a very interesting question to ask: Have we evaluated treatment of depression and anxiety as if they were self-enhancement disorders?

That’s not our call to make when filing a safety complaint. The NHTSA is tasked with evaluating safety complaints from drivers, interpreting the rules and law, and reaching a judgment on whether a response should occur. Our part in the NHTSA process is to file the safety complaint, not to tell them how to do their job in response to it.

For those of you that file a complaint, please maintain your focus on the safety issues the update has created in your driving, rather than verging into specific demands of outcome. “I can’t find my front defroster while I’m driving since XYZ software update” is really great and specific, “so therefore Tesla and NHTSA should do ABC” is unhelpful and does not strengthen your case. No need to backseat-drive the NHTSA, just please do get the safety report filed.

Statute inherits from SAE J902A which costs $89 to read, so we don’t know from the statue alone.

I’m not up for buying an SAE standard today so I hope someone else is, or already has it, and can do so for the discussion’s sake :)

They already do have to adhere to regulations of those functions:

https://www.nhtsa.gov/interpretations/23055-2drn

And pass the FMVSS 103 Windshield Defrosting And Defogging safety test:

https://www.nhtsa.gov/sites/nhtsa.gov/files/documents/tp-103...

Which specifically requires: photos of the instrument cluster to be filed. Has Tesla violated their certification by altering the instrument cluster without going through the appropriate 103 certification process?

The document also inherits from SAE J902A, which I can’t view as it costs money, even though it’s US law. Does J902A require a button to always be present, such that use of submenus for said digital button would be illegal under federal law?

If you own a Tesla, file an NHTSA complaint and say as much to them. They could well do so tomorrow if they can find sufficient rulings already on the books about this and enough legitimate owner complaints are filed.

My car radio has this as well: I have dedicated volume knob with mute push, next and previous track buttons, and a Home button that takes the nav system to the Home Screen. It’s minimum, sufficient, and I would really regret not having them.

It’s not your fault. I find Teslas so confusing that I am visibly anxious to approach them and ride in them as a passenger. In an emergency, I would rather land a plane than try to operate a Tesla.

Is the front defroster so significant a safety concern that it must always be possible to activate with one touch/press/turn?

If so, then Tesla would need to dedicate one such button to the front defroster regardless of menu state.

I hope they filed an NHTSA complaint, as they’re describing a software update that will increase the risk of collisions, injuries, and/or deaths if left uncorrected.

US Tesla owners, if your Tesla is affected by this issue, and you believe that removing the one-tap defroster button is a safety risk to your driving, please report that ASAP: https://www.nhtsa.gov/report-a-safety-problem

You jest, but “stand up a government” is a primary barrier to entry to being considered a “fiat currency”, which makes sense given the drawbacks of trying to qualify as a currency without one.

A banking-grade currency would have reversed the WETH transactions and prohibited new ones. Ethereum has refused so far to do so, even though it’s in their power to hard fork. Whether or not you view them as a currency, that’s not the sort of behavior that engenders a perception of financial trust and safety in their work.

Noted!

That downside is acceptable to Chipotle, it seems.

They would gain trust for returning all of the WETH accumulated in all of the contracts where it’s been idled due to PEBCAK, in concert with a code fork that refuses to accept such transactions. That would be a sign of maturity and intelligence to bankers, and influence their consideration of whether Ethereum might be a viable platform for their financial business someday.

Telling the customer to leave immediately for the store is the only viable solution for a time window that could be 7 to 55 minutes wide, if your priority is maximizing pipeline efficiency and throughout at the expense of occasionally making customers wait for up to 45 minutes in-store. Providing a <10 estimate to all customers ensures that they do their part by showing up in a timely manner, and removes their ability to blame the store for a cold pie. When the kitchen breaks down it may mean waiting in the store for an hour, but at least you’ll know that’s the case because you’re at the store on time.

If the pizza’s ready in 7 minutes, you’ll be there in 10 and receive a hot pizza.

If the pizza’s ready in 55 minutes, you’ll be there in 10 and receive a hot pizza eventually.

You could theoretically try to offer more accurate arrival times, but then you’ll have to play queuing theory “fairness” games with the pizza queue versus in-person and phone orders to try and ensure that the pizza isn’t made too soon, as well as have to deal with people thay show up late and lie about the estimate shown in-app so they can get a new freshly-made hot pizza (which generates food waste). Doing this requires competent pizza personnel with a good understanding of how to manage expectations fairness, and if there one thing I would not expect from a Chipotle-sized business, it’s that — they’ll have maximized efficiency by removing human consideration from the equation altogether.

No.

This means that embedding any resource from a non-GDPR destination URL is a violation of GDPR law unless explicit opt-in approval from the user is first received.

If you are subject to GDPR law, then the above applies to all sites owned and operated by you and your subsidiaries. If you are not subject to GDPR law, then the above does not apply.

Resources could be hosted by http:, https:, ftp:, or any other protocol. Resources could be .js, .gif, .html, or any other format.

If you’re asking “can I dynamically detect the user’s country of origin and enable GDPR protections only if I determine they’re in that country?”, no: the user has a right to legal protection if they are a citizen of a GDPR-protected country and are residing in a GDPR-bound country, regardless of what their IP address is.

(I am not your lawyer, this is not legal advice.)

It does not necessarily set a precedent: use of APIs hosted fully within GDPR countries would be unaffected by this Google Fonts judgment, which only concerns a GDPR site using non-GDPR resources without user consent.

CDNs under the auspices of a non-GDPR government cannot offer any legally-binding assurances that they will comply with GDPR. Their government can legally compel them to lie about honoring the GDPR and secretly act otherwise. Since US courts and authorities are no longer bound by law to honor the GDPR, no service owned by, operated by, hosted within, or subsidiary to a United States entity can guarantee compliance with GDPR.

Any CDN that is owned/operated/subsidiary in full within countries that have legal GDPR protections in place, such as member states of the EU, would be fine to use — but that rules out Cloudflare, Akamai, etc.

(I am not your lawyer, this is not legal advice.)

Sadly, the United States used to have a treaty law in place that delivered the easy solution you describe. In mid-2020, the treaty was found not to provide the necessary protections, and invalidated by EU courts; no replacement treaty was negotiated or signed by the US, and so here we are.

Using a CDN service operated by a non-GDPR business such as Cloudflare, Google, Amazon, or Akamai could potentially be confirmed to be a violation of GDPR, yes, if the CDN-hosted resources are used without opt-in. I’m eagerly awaiting the first complaint on these grounds to be reviewed and judged, now that the GDPR treaty with the United States has lapsed. It doesn’t matter where the CDN’s servers are; without the US having signed a treaty into law, each of their businesses are subject to compulsion by various US authorities to dishonor their commitments to the GDPR.

GDPR specifies otherwise than your interpretation, logical as yours may be from a technical standpoint.

The site operator chose an optional way to embed fonts in a way that divulges PII to a non-GDPR destination. As there is no legal or technical requirement to embed Google Fonts, the site operator is therefore liable.

If use of Google Fonts was mandatory for the web to function, then the site operator would not have been found liable. It is not: they can be mirrored locally, or simply not used, and the web as viewed from the user’s perspective will continue to function just fine. (IANYL, etc.)

If you specify preload=yes or other take any steps whatsoever to promote preloading of the (non-GDPR) YouTube link, then you would definitely be responsible for the user’s IP leaking to a non-GDPR site, and risk owing fines under GDPR.

If you do not request preload behavior, then you’re just linking another site on the web, and users are considered to understand that links go to other sites, and that’s acceptable. A theoretical GDPR complaint would find that the user agent was responsible for the behavior, not you as site operator.

(I am not your lawyer, this is not legal advice.)

GDPR specifies a different interpretation of events, that takes precedence here: the user chose to visit GDPR-bound site A, and the law requires site A not to compel the user to visit any site B that is not bound by law or treaty to honor GDPR as well.

You’re not wrong that one could logically evolve your interpretation from circumstances, but GDPR’s authors chose not to accept your interpretation as sufficient, and went further than that.

Or in Instagram’s case for me, you read the article and see a strange mess with empty holes today, because your IP address hasn’t logged into any Meta properties in the past year and so Instagram won’t serve you embeds anymore.

It would horrify a lot of people to discover that clothing and personal care businesses that market specifically to women send 10-100x as many emails per month to their customers as other businesses.

I don’t exaggerate; in my testing with fresh email addresses, registering as a woman at fashion-linked retailers would generate up to 4 emails per day from certain well-known retailers, while registering as a man simply would not (or maybe one a week, or month).

It’s bad enough that brands are so thirsty for our wallets, but they had to find a way to be even more greedy and cruel about it.

Modern email clients don’t comprehend the concept “I want one thread in my email listing for all Nordstrom emails”, so retailers just bombard us all to death with emails to flood our inbox. There’s a simple fix, of course: threading by ‘sender’, where you just mark a given email as sent-by Nordstrom or whatever, and all future emails go into that thread, and it shows newest-first and defaults to “mark all older messages read”. This would utterly destroy the relevance of email bombardment and crater open rates, especially if the client doesn’t show the unread count for the thread, since older unread content from that sender doesn’t matter.

This doesn’t make it right for TeamViewer, but at least it would be one step closer towards neutering greedy marketing.

Exactly so.

Splintering off the toxic division as a subsidiary.

For example, Google, the "be evil" toxic advertising-tracking company, is now a splintered subsidiary of Alphabet.

But Amazon and Facebook don't seem much interested in doing the subsidiary thing, at least not to Alphabet scale, so I'm not sure what they'll do instead.

(For context, FAANG is an acronym: Facebook, Apple, Amazon, Netflix, Google.)

Hi, and welcome to this post and discussion for the first time.

If you’d like to register a complaint with the mods about my participation here, you can email them directly at the footer contact link.