Hacker Newsnew | past | comments | ask | show | jobs | submit | more RyanShook's commentslogin

I think Alibaba uses TSMC for their foundries, like everyone else. I would assume that they did use ASML machines for this.



Never heard of it. Looks like more dime-a-dozen AI hype-slop.


Looking forward to the class action on this one…


Tesla has binding arbitration that prohibits class actions.


Won't help them in most of Europe. Consumer protection laws here are stricter.


But class action suits are not a thing here. And FSD is not deployed in Europe.


They’ve been selling FSD in Europe since 2018.

I know because I bought it in March 2019 on a Model 3. (I got it because I thought it would help my elderly parents who mostly used the car.)

7500 euros completely down the drain. It still can’t even read highway speed signs. A five-year-old would be a safer driver than Tesla’s joke FSD.

They do have the audacity to send me NPS surveys on the car’s “Teslaversary.” Maybe they could guess by now that it’s a big fat zero.


But it's promised.


If that’s the case I’m guessing a smart-assed lawyer will use grok to open one arbitration case per tesla sold.

However, I’m not sure that’s necessary, They lost the Tesla Roof class action suit, so it’s clearly possible to sue them.


Can someone at Google explain why the company can’t end formal support for the thermostat but make the API open? It’s a thermostat. It has 3 real functions - cool, heat, fan. What could it possibly hurt to let owners access the endpoints without touching Google servers?


This assumes Google's servers are pushing to the thermostat. It seems more likely that the thermostats are pulling from Google's servers, so that they don't have to worry about firewalls.


But then the customer might not buy a new nest....


They might not buy a new one regardless because they are upset with the company :). Just saying


With a big company like Google I'm sure lawyers are the ones preventing an open API and not the developers. The API is a liability for Google. It could infringe on patents or it could have a bug.


API access is being ended as well, so third-party apps and services will not work.


I was hoping that at least my Home Assistant integration would keep working. That sucks terribly. Lesson of the day: Avoid any IoT device that you can't use without an external service.


FWIW, I replaced my Nests with Centralite Pearls a few years ago, and have been extremely happy with them WRT Home Assistant. The Pearl doesn't seem to be widely available anymore, but any Zwave or Zigbee thermostat + a local hub gets you a thermostat that should work with Home Assistant and will be immune to being sunsetted like this.


That's a good suggestion. Thanks!


If you're interested in the "dark age" of Disney history, I recommend the book After Disney by Neil O'Brien - https://amzn.to/4mvMxgX


It’s great that it avoids pay-per-token pricing and is very powerful. The downside is right now it decides what to do and executes with very little guidance or guardrails. You basically have to shout at it or force quit to make it stop executing commands.


Any Claude desktop MCP recommendations?


This thread is more about building your own custom mcp server. You can find a lot of official pre-made ones at https://mcpservers.org/


"The only choice we get is what to worship." Thanks for sharing.


Thanks for sharing. Looks like a great tool. Unfortunately it requires allowing full keystroke access which is too much of a security risk.


Its a standard practice for third party keyboards on iOS, I doubt you'll find any keyboards worth using that don't request full access. Otherwise Apple cripples the experience a lot.


Thank you for checking the app out! Ah that's too bad :( I don't collect any data and the app only connects to the internet at launch (to check subscription status) and when you use the dictionary feature. You can choose not to allow full access and still use quite a few features!


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

Search: