Per the Voltstats Facebook page, Mike is reporting that OnStar is shutting off the API feed he has been using to populate Voltstats. Apparently will be a temporary?? shutdown.
I may have been a little unclear in my earlier comment. I knew that Voltstats had nothing to do with my phone itself. What I had meant was that since the site used the phone interface, did losing the interface for the site mean losing the interface for the phone?saghost: It doesn't emulate your iPhone, it just looked like an iPhone to OnStar. It doesn't have anything to do with your phone.
Man, you got that right. For me, it's dropped data, fails to update tire pressure for long periods, and takes a LONG time to execute remote commands and charge level refreshes, even if ultimately it's going to fail (which it often does). I have a hard time believing just an API refresh is going to fix any of that, as I suspect some of it is due to infrastructure limitations, but I do hold out some hope!Voltstats is way more valuable than the OnStar myvolt site (which has been so buggy its not useful.
It happens more often than it should. Good example: If you've ever had to develop a website with FaceBook integration, you'll know what I'm talking about. Carelessly breaking other companies' production websites is standard operating procedure for them.I'm happy if they are trying to fix it and if that means a new API, that is understandable. But you just don't change things without notice.
OnStar is kind of like a poorly run startup when it comes to the API. For example, they have a great big event at a car show about how they're going to have an API, and Please, Please, Developers, Join Us! They didn't even have to build it, and the developers came. And OnStar ignored them. AFAIK, only 2 organizations have access to their API.I have to admit that I have been frustrated with GM for some time, but this seems like a gratuitous bit** slap. Why would the GM brass make this many Volt fans less happy with their favorite car?
No offense, but I'm not sure someone who can't recognize SAML and understand why its used should be commenting on secure application architecture.It goes and does your validation through yet another server - a complete no-no in security, but also a no-no for speed - there's no need to send your browser here and there - that comm could be more secure and tons faster done internally to their network.