> Tesla used to sell Model S vehicles with software-locked battery packs. This was a way to offer different range options without having to make production more complicated with different battery pack sizes.
> Later, Tesla started to offer owners of those software-locked vehicles the option to unlock the capacity for an additional cost. Tesla phased out the practice over the years, but the company still used software-locked battery packs when doing warranty replacements of battery packs of certain capacities that it doesn’t produce anymore.
Upgrading the head unit for a 2013 Model S triggered an error and reverted this old generation battery to software lock.
This clearly was a software bug and Tesla reverted it for all customers using these older batteries.
This has literally nothing to do with subscriptions (the word subscribe isn’t even in the article once). I don’t even think you read the article.
> Car is sold twice since, and now has a new owner (my customer). It says 90, badged 90, has 90-type range.
> He has the car for a few months, goes in and does a paid MCU2 upgrade at Tesla after the 3G shutdown.
> ...
> Tesla told him that he had to pay $4,500 to unlock the capability:
It's all in the article.
You can get all stuck-up about the word "subscription" but guy goes into Tesla for a non-battery related service and loses 2/3 thirds of the range the car claimed it had unless he forks over 5k.
Respectfully, I don’t think enough has been removed.
As someone with Indian heritage it’s super disheartening to see plenty of comments negatively generalizing a diaspora of over 1B people.
Treating anyone who presents as Indian as apart of cultural monolith is absurd. I was born and raised in the US, and have no connection to the alleged cronyism or caste-based discrimination.
Many of these comments make blanket statements about Indians. I don’t think the same moderation guidelines are being applied in this case. Replace Indians with Europeans, Black people or any other ethnicity and it should become clear that this violates the site’s guidelines.
Other browsers could add support for the native macOS password autofill apis (introduced back in 2020 in macOS Big Sur). So far both Chrome[1] and Firefox[2] have refused to add support.
That exchange with Vas (on the Chrome side) was more than a little frustrating.
"Chrome isn't just an App, it's a password provider. We're not throwing that away for Apple."
I don't think that was anyone's intention. Just to support filling passwords from other sources. But he locked into a single use case that was a straw man. "I can understand how some users might want that. That's not a priority for us."
Yattee is a good example for what Apple puts those developers through. Here is a direct quote from their website:
> Apple keeps rejecting macOS version of Yattee for several unrelated and random reasons. As I believe the App Store approval process is random and getting approval depends mostly on whether the reviewer has had a nice day, I keep resubmitting macOS versions with every update so maybe we will get lucky one day.
The app also has obscure and incomplete features & UI purely to comply with Apple guidelines (or trick human reviewers paid beans into not actually realizing what the app is).
I love the idea. Is there any way you could add in the functionality for the user to upload a dictionary for a specific language? I would gladly pay $20+ for a pro version.
I’ve been trying to learn Kannada, a South Indian language that my parents speak. Most apps like Duolingo and Babbel don’t support Kannada, so it’s been hard to be consistent.
Thank you! In the short term, I feel like that might require too much work comparing to adding new languages but in the long term, I might add a functionality for that.
https://heatherburns.tech/about/
If you scroll down you’ll see an image of the author.