Comment Re:Seriously? (Score 2) 380
But it is not like Bind crawled Google or anything like that, which Google would like everyone to believe.
But they did. Instead of using a program to do the clicking, they used humans.
But it is not like Bind crawled Google or anything like that, which Google would like everyone to believe.
But they did. Instead of using a program to do the clicking, they used humans.
Microsoft does disclose that Suggested Sites collects information about sites you visit. From the privacy policy: When Suggested Sites is turned on, the addresses of websites you visit are sent to Microsoft, together with standard computer information. To help protect your privacy, the information is encrypted when sent to Microsoft. Information associated with the web address, such as search terms or data you entered in forms might be included. For example, if you visited the Microsoft.com search website at http://search.microsoft.com/ and entered "Seattle" as the search term, the full address http://search.microsoft.com/results.aspx?q=Seattle&qsc0=0&FORM=QBMH1&mkt=en-US will be sent. I've bolded the key parts. What you're searching on gets sent to Microsoft. Even though the example provided involves a search on Microsoft.com, the policy doesn't prevent any search -- including those at Google -- from being sent back.
It's worth reading the IE privacy policy to see what all they reserve the right to do with what you do in IE. I don't see the limitations regarding which components specifically will spy on you; some mention it specifically and then there's a broad statement about recording what you do and sending it to Redmond.
IMHO, that's the real story here. That, and the fact that people apparently still need reminding that MSFT is an advertiser just like GOOG, just less successful at it to date.
It's not in the EULA.
You're right; it's perhaps in the privacy policy (arguably, this is part of the EULA, but it's also a separate document):
Microsoft does disclose that Suggested Sites collects information about sites you visit. From the privacy policy: When Suggested Sites is turned on, the addresses of websites you visit are sent to Microsoft, together with standard computer information. To help protect your privacy, the information is encrypted when sent to Microsoft. Information associated with the web address, such as search terms or data you entered in forms might be included. For example, if you visited the Microsoft.com search website at http://search.microsoft.com/ and entered âoeSeattleâ as the search term, the full address http://search.microsoft.com/results.aspx?q=Seattle&qsc0=0&FORM=QBMH1&mkt=en-US will be sent. Iâ(TM)ve bolded the key parts. What youâ(TM)re searching on gets sent to Microsoft. Even though the example provided involves a search on Microsoft.com, the policy doesnâ(TM)t prevent any search â" including those at Google â" from being sent back.
(source: TOFA: http://searchengineland.com/google-bing-is-cheating-copying-our-search-results-62914) It's worth reading the rest of the privacy policy; apparently other bits of IE can and will send your information to Microsoft. http://www.microsoft.com/windows/internet-explorer/privacy.aspx
They do spy on (sorry, gather 'click stream' data from) IE users (through IE itself, or one of its add-ons). Read those EULAs veeery carefully, folks!
Somehow this extremely relevant part of the story keeps getting skipped over whenever it's being told.
The 'click fraud' accusation is hilarious and quite arguably libelous as fraud (and click fraud) is a real criminal act.
http://en.wikipedia.org/wiki/Click_fraud
"Click fraud is a type of Internet crime that occurs in pay per click online advertising when a person, automated script or computer program imitates a legitimate user of a web browser clicking on an ad, for the purpose of generating a charge per click without having actual interest in the target of the ad's link. Click fraud is the subject of some controversy and increasing litigation due to the advertising networks being a key beneficiary of the fraud.
Use of a computer to commit this type of Internet fraud is a felony in many jurisdictions, for example, as covered by Penal code 502 in California, USA."
(also claimed to be a felony at http://www.legalmatch.com/law-library/article/click-fraud.html with claims of arrests.)
Summary:
One of the things Microsoft has done well for many years now (since they got called on the carpet about Windows 95) is providing compatibility with assistive technology used by the blind. Their current push is for a set of APIs called User Automation.
Article:
For the [non-minor visual, physical, and audio as well as any other] disabilities, access is via an assistive technology (AT) that mediates the user experience. This is where our the accessibility challenges lie. The challenges stem from the fact that Microsoft Windows doesn't provide a real accessibility infrastructure - as compared to UNIX systems with GNOME, the Java platform, or Macintosh OS X. In Windows, virtually all of the information needed by assistive technologies has to be obtained by patching the operating system, replacing/chaining video drivers, reverse engineering applications, and/or using proprietary COM interfaces to get at the data within an application. The first accessibility API Microsoft put forth for accessibility - Microsoft Active Accessibility (MSAA) - fails to provide most of the information needed for screen reading and other AT uses, and is being supplanted in future Windows releases. What this means is that for an application to be accessible in Microsoft Windows via a particular assistive technology, that AT vendor has to have made a significant investment in customizing their product to that application. The greater the customization investment, the "more accessible" an application is deemed to be, at least via that particular AT. For example, the Windows screen reader with the largest market share, JAWS, has made a huge investment in customization of their product to Microsoft Office (and in contrast made a much smaller investment in customization for WordPerfect). For this reason blind folks generally feel that Microsoft Office is "accessible" (and that WordPerfect "isn't as accessible") - not because of work done by Microsoft or Corel, but work done (or not done) by Freedom Scientific, the creator of JAWS.
Quoth http://en.wikipedia.org/wiki/Microsoft_UI_Automation
In 2005, Microsoft released UIA as a successor to the older Microsoft Active Accessibility (MSAA) framework.
Seems to be a decade missing there.
The best things in life go on sale sooner or later.