Yeah, it is a slap in the face, but understandable since the old hardware needed proprietary drivers to work.
However, there is good news, as mentioned in this post at webOS Nation
"There are two things to keep in mind moving forward. One: there's a large and growing number of Android devices out there that offer support for the Linux Standard Kernel 3.3, and given the number of devices supported by the open source CyanogenMod Android project there are plenty of drivers available for those components. Two: The webOS homebrew community cannot and will not be held back. They've already started working on the webOS Community Edition release of LunaSysMgr to see how well they can get it to work on the Pre3, and it'll only be a matter of time before they figure out how to get the goodness of Open webOS to work on our current webOS devices, HP be damned."
I love the elitist comments in this thread that are marked up as Insightful, especially from Anonymous Cowards who probably don't work for companies where STABILITY, especially with something as important as a 'fucking WEB BROWSER' are concerned. Our shop, a major east coast University, relies on a couple of MISSION CRITICAL systems whose vendors ONLY RECENTLY began to upgrade their software to support the newer browsers. I personally use the newer Chrome for most web use, but I still had to hang onto a copy of Firefox 3.5 (!!) in order to use said software for my job.
We got more applications than we could handle well, which is a good problem to have. Unfortunately, it means we dropped some things on the floor, and that's bad, but with the impending "stuff" that's coming, this is all going to get a lot easier for everyone and a lot more transparent.
If you didn't get a response in a timely manner, let me apologize to you. We should have done a better job on this, and I apologize for this. I'm working with the people I work with on this to try to make sure we do a better job of this moving forward. Good news is we've hired some people -- one's started, one starts next week, and the third starts the week after that, and that'll give us some great people and some new resources to make sure this gets fixed and works properly.
As the previous poster started, unlike the iPhone, there is a very active home brew community which Palm has not only blessed, but has assisted with:
http://www.webos-internals.org/wiki/Application:Preware
http://www.precentral.net/fyi-pre-reports-your-location-palm
When PreCentral's people asked Palm about this, their official statement to them in part was:
Our goal has been to follow industry best practices on data collection, use, and encryption. Like most EULAs and privacy policies, though, the terms tend to get pretty detailed about potential scenarios. And because the terms are meant to notify users about all possible variations, we wanted to err on the side of over notifying rather than under notifying users through the terms of use. So there's really nothing here "beyond the norm" for a EULA or privacy policy.
The provision you've quoted explains why Palm might collect user information. For example, we collect and transmit users' email addresses, email content, contact lists, etc. to provide WebOS services such as back-up and restore for the purpose of backing up that data and helping users restore the data if needed (in that case, it would not be limited to just the email address collected at registration). If users someday make purchases on their device through the Apps Catalog, then we would also collect payment information to process the transaction.
At all times, we'd be strictly bound by our privacy policy. Our privacy policy, like virtually all others in the industry, contemplate our using data to provide services users have requested, improve our products and services (hence the reference to Palm's own "sales and marketing" in the privacy policy), troubleshoot, etc. We also refer to affiliates because Palm is a global company, and we may need to transmit data from our European subsidiary to the parent company. We're obviously not a conglomerate with many different subs and affiliates, but the terms specifically mention subs and affiliates so that we can comply with European data protection laws that require us to spell out that data collected by a European sub can be transmitted to another part of the company.
If all else fails, lower your standards.
