Sounds pretty hostile to consumers. A repair made that compromises the ability to safely charge does represent a huge risk. But what's their process for this? Do they publish this criteria? They say there's recourse for this, but it costs a lot and it sounds like the engineer goes off of "vibes" and not a rubric.
No, it was a clean title. Tesla decided it was "salvage" according to their own measures. I can imagine a scenario where a poorly done repair absolutely can make rapid charging a dangerous thing. But I would feel extremely swindled if this wasn't disclosed ahead of time.
And how does Tesla know repairs have been made after a minor accident? Or do they just yank your access to the network whenever they want and demand money to have it "recertified"?
> how does Tesla know repairs
> have been made after a minor
> accident?
Speculation: It was brought to Tesla after an accident, which inspected it, and quoted a repair price the owner didn't like, so his cousin Bob fixed it, but it's still marked as "HV needs inspection/repair" in Tesla's system?
Municipal utilities exist everywhere. I'm not sure why you're being all hypothetical about it. They work well and for many reasons discussed here, sound like a good fit for Walnut Creek.
That could definitely be it. They might also be trying to play it cool, and not appear to gloat before the corpse is even cold. Instagram is running a lot of ads on TikTok now though.
Yep, those exist across the western US too. I think many people are underestimating the scale and intensity of the winds California experienced. A single house on fire with relatively regular weather conditions isn't likely to spread to others - despite the "ha American houses dumb and wood" sentiment on this topic, there are building codes and fire safety is absolutely considered. But the Santa Ana winds are extremely dry and extremely powerful.
It's a hard engineering problem to solve, but an increasingly urgent one now that these major events are becoming more intense and frequent.
Comments like the last here irritate me. No, we all learn that wood is the only appropriate building material and the Salesforce tower in San Francisco required a whole forest of trees to construct.
The root comment is based on a very dated concept. Of course we can built earthquake resistant megastructures from steel and concrete. A lot of that building technology was created in California. It's either naive or willfully ignorant to think we can't solve this problem.
The issue with those materials is cost. Spread out, suburban design without density is expensive and wood frame construction is a great way to affordably build housing. Wood frame single family houses are not the problem - it's how we design our cities that's the problem.
Wood is incredibly cheap in North America. We're not cutting down forests for it, either. Much of the wood used for residential construction is milled from trees grown specifically for that purpose.
Lumber is quite a bit lower quality than it used to be, because we're no longer using old-growth timber. Less dense wood burns faster, as does the laminated strand board that long ago replaced plywood (unless you're really fancy) (and toxic fire retardant treatments be damned).
The low cost of lumber is one of many things in America that don't make sense economically, but that persist because of momentum, with each generation receiving an inferior facsimile of what the previous ones knew. See also: car-centric policy (from infrastructure to gas prices) and retirement planning (pensions to IRAs to nothing).
What is not to say that most of the wood in the US is illegal. It's probably a small share. But some of your houses do pretty much chop forests down. (And your government does help fight that, but it's hard to completely stop it.)
Yes, people from the US always say concrete is expensive and wood is cheap. And unless you are designing a tent (by the way, zinc is way cheaper than wood for a tent), only people from the US say that.
There's something distorting your economy. Concrete is incredibly cheap as a material, extremely prone to use in a large supply chain, and requires way less labor than wood.
You make houses siting over finely built wood lattices... how much do you pay to the people building those? Because I can't imagine it being justifiable with Brazilian salaries.
I'm clearly in the minority, but the new app is leaps and bounds more usable and stable for me. The functionality gaps don't affect me - those features weren't things I used. And it's way, way more responsive and consistent than the old one.
Perhaps it's just my specific network situation. The old app was a constant headache of inconsistent state - music playing while it showed nothing playing, pressing commands (like skipping a track or pausing) but those commands never happening on the device. It also took a very long time to show my entire device list. Never quite worked with the Roam like it should have.
So your experience is the exact mirror of mine. Old app was flawless and pretty low latency.
As soon as the new one came along I had the issues you describe with control latency - volume or track changes would either take a random amount of time, or do nothing, or sometimes queue up and all apply at once. Also had inconsistent state, the app showing music as playing while nothing happened, or the reverse. The app's home screen only partially loading, all sorts of crap, with the same issues present on android or iOS.
And apparently I'm one of the lucky ones - some people can't add new products or find existing ones.
Maybe one day they'll release a version that works for both of us :)
The first time I used a flare with their support agents, it truly felt like magic. It's such a clever way to perform data collection for a specific, imperative need without doing a dragnet of constant use telemetry (as far as I'm aware)
I half agree with you. We just went through an ECS to EKS migration, and we're still incredibly dependent on AWS. The hard part isn't the container orchestration system or even containerizing your workload - it's all the other crap you need to develop and maintain around it. Your databases, networking stack, MQ brokers, secrets managers, and everything else are still stuck to whatever cloud provider you're using.
EKS really isn't much harder to build out than ECS - but it doesn't set you up to be much more cloud agnostic.
