I don't see anyone painting Alibaba as the wronged party in that piece though -- seems like a fairly helpful piece at least for us not-in-the-know anyway. Are you talking about some other articles instead?
_Man_
_Man_
http://scobleizer.com/2012/09/12/context-is-the-new-battleground-between-android-and-ios/Glympse‘s CEO, Bryan Trussel, told me his team develops its contextual mapping app on Android first, then moves it to iPhone.
Why is this?
A few reasons:
1. Android lets developers have access to the dialer so that app developers can watch who calls you and who you call.
2. Android lets developers look at the wifi and bluetooth radios on the phone so app developers can build better systems to track where you are, who you are near, and whether you are near things like your car.
http://www.cultofmac.com/160248/what-the-hell-is-a-udid-and-why-is-apple-worried-about-them-feature/Apple has been allowing devs and ad networks to track UDIDs for years. Why the sudden backlash now?
For iOS app privacy concerns, the straw that broke the camel’s back was Path, a social networking app for the iPhone that was uploading a user’s iPhone address book and storing it on its private servers without permission. Nothing nefarious was being done with the data — and, in fact, uploading address book contents to third-party servers is a common occurrence — but the news hit at the perfect time to raise a stink about mobile app privacy in general.
The controversy surrounding Path had nothing at all to do with UDIDs, but it was so well publicized that people started wanting to know how much our apps know about us and what they do with that information. We all want our information, like an address book, to be protected. Although we constantly share everything we do online, there’s still a desire to have at least a semi-private life in a digital world.
Following severe criticism of Apple’s iOS privacy measures from the media, members of the U.S. Congress sent letters to Apple and App Store developers asking how apps collect and manage their users’ personal information. Apple eventually responded, saying that it was working on a new way for everyone to opt into sharing personal data with apps in the future.
http://arstechnica.com/apple/2012/09/publishing-firm-ios-udid-leak-came-from-us-not-the-fbi/As we wrote in our Ask Ars on the topic, the UDID itself is just a string of characters that uniquely identifies a particular iPhone, iPad, or iPod touch—practically every developer that offers apps on the App Store has a list of UDIDs somewhere, and the UDID alone cannot reveal much about you. But many app-makers did collect some personally identifiable information from users—such as names, phone numbers, addresses, and other data—and associated it with their UDIDs. As such, it is possible to de-anonymize a UDID and associate it with other information floating around on the Internet.
I honestly never heard of Blue Toad before this, CNN says:But Apple has affirmed that the data stolen from BlueToad is typical of what an app developer might have on record.
"As an app developer BlueToad would have access to a user’s device information, such as UDID device name and type," Apple spokesperson Trudy Muller told the Times. She added that developers would not automatically have access to other personal information "unless a user specifically elects to provide that information to a developer."
http://articles.cnn.com/2012-09-10/tech/tech_web_apple-hack-bluetoad_1_unique-device-identifiers-antisec-hack-attackBlueToad, a privately owned firm based in Orlando, Florida, has 30 employees and works with 5,000 to 6,000 publishers to repurpose their content on various devices.
Although DeHart declined to name BlueToad's publishing clients, the company's work is seen on 100 million page views monthly, he said.
"I would like to think this wouldn't happen again, but with thousands of attacks (daily), this is an evolving, continuing process," he said.
[COLOR= rgb(81, 81, 81)]Then open -- or [/COLOR]“openy”[COLOR= rgb(81, 81, 81)] -- nature of Android has its advantages -- a wide variety of hardware, hackability and custom ROM support, endless choice in screen sizes, software customizations, multimedia chops, chassis styles and industrial designs. But it comes with one major Achilles heel -- the labyrinthine, time-consuming and expensive process of getting phones updated with a new version drops. It’s not necessarily anyone’s fault, but it's a weakness that's built into Android's DNA, and one we doubt will ever be overcome.[/COLOR]