Yet another example of how blogs can be used to answer concerns raised in the community. Here the MSN Search Blog answers privacy concerns raised by O’Reilly and BoingBoing.
Privacy concerns raised (and answered) about Live Local
Published by
Robert Scoble
As Startup Liaison for Rackspace, the Open Cloud Computing Company, Scoble travels the world looking for what's happening on the bleeding edge of technology for Rackspace's startup program. He's interviewed thousands of executives and technology innovators and reports what he learns in books ("The Age of Context," a book coauthored with Forbes author Shel Israel, has been released at http://amzn.to/AgeOfContext ), YouTube, and many social media sites where he's followed by millions of people. Best place to watch me is on Facebook at http://www.facebook.com/RobertScoble View all posts by Robert Scoble
The TOS says that Microsoft stores location information and will provide it to third parties if required to do so by law. The blog post says that location information is not shared with third parties. There seems to be a contradiction.
Mike Liebhold points out that Placelab can provide location information without disclosing the users location to a service. Why didn’t Microsoft use this approach?
The blog post says that “Locate Me” sends standard HTTP header information to the service. Does this include cookies? Can these cookies be tied back to personal information in an MSN account?
The TOS says that Microsoft stores location information and will provide it to third parties if required to do so by law. The blog post says that location information is not shared with third parties. There seems to be a contradiction.
Mike Liebhold points out that Placelab can provide location information without disclosing the users location to a service. Why didn’t Microsoft use this approach?
The blog post says that “Locate Me” sends standard HTTP header information to the service. Does this include cookies? Can these cookies be tied back to personal information in an MSN account?