Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google Is Turning Off the Works-with-Nest API

nest.com

Post reply on HN
Print view View original

271–280 of 600 posts

Re: Google Is Turning Off the Works-with-Nest API

#271

Post by panarky »

DivisionSol wrote: post #57
electrograv wrote: post #38

I see Google API/ecosystem fans often defending or dismissing Google’s pattern of behavior here, using arguments like this: “Well, sure, they shut down that API I don’t use — big deal; all things come to an end eventually! But, they’d NEVER do that to this API I rely on — that would be so horrible, Google just would not do it!” I hope we all can acknowledge that this argument is on perpetually eroding ground, at the…

I've been considering pasting this: https://killedbygoogle.com/ every time the argument comes up. Maybe Google proponents will make one for other companies notorious for killing services, but at least for now, the Google Graveyard grows.

Would love to see a comparison of products "killed by Google" to products "killed by Microsoft" or even "killed by General Electric".

I'd bet a week's paycheck that Google's list would be the shorter one.

Re: Google Is Turning Off the Works-with-Nest API

#272

Post by glangdale »

ImprovedSilence wrote: post #195
sanderjd wrote: post #172

Earlier quoted context omitted.

Why? There are tons of perfectly good rss feed readers. I've never understood this one. I was a heavy Reader user, seamlessly switched to Feedly like the day after it was spun down, and never thought about it again.

Do you mostly consume text, or images/rich media? Something about Reader just worked for me. It was partly some blogs I followed and wanted to keep up with reading, but the meat of it for me was just scrolling endless pictures from various design blogs, that i'd sometimes star or label. Or some webcomic that I'd share with my handful of friends that were on there. Or I'd catch up whatever BMX or ski edits that came o…

Reader worked really well for me, too. And killing Reader seemed to send a signal to a lot of people that rss was 'done', whether rightly or wrongly - all that matters is that people believe it. I saw a lot less rss around subsequently. I switched to a few other services but ultimately just faded out on rss in general, which is a shame, as it was nice to have a non-algorithmic-curation feed of stuff I liked.

Re: Google Is Turning Off the Works-with-Nest API

#273

Post by iknowordidthat »

asdfasgasdgasdg wrote: post #149
Despegar wrote: post #27

Earlier quoted context omitted.

Once again HomeKit's design proves to be prescient. https://www.theverge.com/2017/8/3/16083996/internet-of-shit-...

Hrm. How so? HomeKit does not allow third party devs to write apps to control HomeKit devices, AFAICT. So they never added the capability that Google is removing. People can still develop devices that are triggered by Nest and Google Home. They just can no longer write apps that themselves trigger or modify Nest devices. Or are you saying it's prescient because Apple saw that such capabilities were not economically v…

HomeBridge can control HomeKit accessories just fine.

Re: Google Is Turning Off the Works-with-Nest API

#274

Post by deadmutex »

diogenescynic wrote: post #262
gordon_freeman wrote: post #13

Earlier quoted context omitted.

I have Wemo smart plugs that I have plugged in all sorts of stuff like Heater, Lamps, and TV, etc connected to my Google Home and Home Mini. And I'd advise anyone to think twice before buying smart plugs or smart devices. There are so many bugs creating so many complications that I feel they are not worth using. You'd need to reconnect them with WEMO app time and again, restart these frequently if they just stop work…

I have Wemo smart plugs connected to AppleHome and have no issues.

Adding to this, I have them setup with Google Assistant, and Alexa. No issues with Assistant, and rare issues with Alexa.

Not saying the OP isn't having issues, but there might be a sample bias when reading the comments.

Re: Google Is Turning Off the Works-with-Nest API

#276

Post by codebook »

glitch003 wrote: post #258
tw04 wrote: post #173

Can't wait for them to tell me that Google Apps accounts aren't supported so I'll lose all access to my Nest devices... if that happens I'll be removing all of my Nest devices and selling my Google Home. I'm SO SICK of them acting like there needs to be a firewall between google apps accounts and everything else .

Well, Google Apps accounts are for businesses, so it makes sense that they wouldn't work like a personal account.

Well, it was firstly advertised as free account with custom domain. I was one of many who created the account. and keep frustrating and maintaining another @gmail.com account for this reason.

Re: Google Is Turning Off the Works-with-Nest API

#277

Post by bonzini »

lettergram wrote: post #235
DivisionSol wrote: post #57

Earlier quoted context omitted.

I've been considering pasting this: https://killedbygoogle.com/ every time the argument comes up. Maybe Google proponents will make one for other companies notorious for killing services, but at least for now, the Google Graveyard grows.

Huh didn’t realize YouTube annotations was killed off. Gotta say, most annoying thing to me was discontinuing support for the Nexus 6p after only 2 years. Made me switch to iPhone for ever.

YouTube annotations unfortunately were misused for spamming purposes. It is one of the few cases where you can say good riddance.

Re: Google Is Turning Off the Works-with-Nest API

#278

Post by Svip »

modzu wrote: post #265
Svip wrote: post #261

Earlier quoted context omitted.

Odd. I can't find "secure google search" on the website. Are you confusing it with "Encrypted Search", that allowed you to search anonymously?

see that's what i mean; "encrypted search" is on the list, which is referencing this: https://support.google.com/websearch/answer/7631341?hl=en and does not have anything more to do with "anonymous" searching

OK, but then that's different. Because you were complaining that they were not differentiating between actual killed services and things that naturally reached their end of life, but in this case, the site is actually wrong.

It clearly says that it provided provided users with anonymous search, which gives the impression of something like DuckDuckGo or Startpage. But that's not what's happening, and I think that's worse than your original complaint.

Re: Google Is Turning Off the Works-with-Nest API

#279

Post by eclipxe »

altec3 wrote: post #141
palebluedot wrote: post #33

This seems to include all of us using them in open-source "hobbyist" environments, like Home Assistant and Node-Red. I'm quite frustrated by this; I'll never buy another Nest product again, and I now regret my purchase of the Nest Thermostat. All the rest of my IoT stuff is either open-source hardware/software, or at the least local-only with known protocol interfaces. This was the one exception I made for IoT "cloud…

I'm using a Nest with Homebridge to expose it to Homekit. Didn't want to purchase one due to the reliance on the cloud and lack of Homekit support. After months of waffling I gave in and got one. I also regret that decision now too. Last Nest purchase I will ever make.

Same. Never buying a google product again.

Re: Google Is Turning Off the Works-with-Nest API

#280

Post by fragmede »

panarky wrote: post #271
DivisionSol wrote: post #57

Earlier quoted context omitted.

I've been considering pasting this: https://killedbygoogle.com/ every time the argument comes up. Maybe Google proponents will make one for other companies notorious for killing services, but at least for now, the Google Graveyard grows.

Would love to see a comparison of products "killed by Google" to products "killed by Microsoft" or even "killed by General Electric". I'd bet a week's paycheck that Google's list would be the shorter one.

Microsoft was founded in 1975, and GE was founded in 1892 (!), to Google's 1998, but there are likely angles that would make it interesting. Number killed/number alive? Number killed since y2k? etc
Post reply on HN