251–260 of 600 posts
Earlier quoted context omitted.
Pasting the same thing over and over in different threads regardless of context isn't exactly arguing in good faith or inviting nuanced discussion, so I wouldn't go that route myself...
It's not regardless of context. It's because of context.
Google maintaining multiple APIs that essentially do the same thing. Google bad.
People are going to complain either way. I welcome this change personally and think it makes perfect business sense. I can't think of any Works with Nest that I have integrated in my home that's not already connected to my Google Home, so I don't really see this impacting many negatively.
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…
Because my app does not use the works-with-Nest API
Earlier quoted context omitted.
We expect web services to go away eventually. We expect physical products to keep working until they physically break. The problem is when companies sell physical products with a web service as a fundamental part of the product. Companies want to treat the web service like any other web service, while their customers reasonably expect their physical product to act like any other physical product. Edit: I want to add…
Are the physical devices not working after this change, or rather some of the applications developed for these devices need to switch to another API?
If you as a user or third party provider integrated with this API and rely on it for functionality, you have no alternative nor recourse.
Earlier quoted context omitted.
Uh, you realize that imap support has been in GMail for its entire history?
So? Doesn’t mean they can’t get rid of it.
Furthermore if you have an up to date sync on the day imap support ends then you have all your email and need face only changing over to a new address or if you already use a custom domain logging on and changing the email provider.
Earlier quoted context omitted.
Ideally your Gmail ought to be through a domain and services that add value via imap. Then its impossible for the functionality to evaporate.
You are assuming they will retain imap functionality. Ask the xmpp/jabber folks about hangouts.
Anyone know a good replacement for a nest cam?
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 .
This is why we need to be pushing for devices that use open protocols at the very least. (Ideally they'd be fully open devices.) It saddens me to see people buy into IoT and not think about the vendor lock-in or data exfiltration. The thing is, there really aren't any alternatives.
At the very least, the fact that the upcoming Nest Hub Max supports Thread is a (small) step in the right direction.
headline should be "that $300 doorbell is now a paperweight". in the future it will be "that $8000 trunk car driving computer is now a paperweight".
Pretty much straight up FUD. This is not bricking Nest devices.
I've been very happy in general that I switched to ecobee when I moved, and this made me even happier.