Slashdot Mirror


Google Updates Chrome's Terms of Service

centuren writes "In response to the reaction to Chrome's terms of service, Google has truncated the offending Section 11, apologizing for the oversight. The new Section 11 contains only the first sentence included in their Universal Terms of Service, now stating: 'You retain copyright and any other rights you already hold in Content which you submit, post or display on or through, the Services.'"

4 of 318 comments (clear)

  1. So do they... by Leptok · · Score: 5, Interesting

    relinquish rights to the stuff that may have been created before the update?

  2. Re:But.. by Darkness404 · · Score: 4, Interesting

    Heck, I'm surprised there's no community project out there to provide an EULA-free Chrome fork.

    2 main reasons. Right now, Chrome is essentially Windows only, and as we know, most people who use Windows don't care about EULAs. And secondly, Chrome isn't used much, right now people are wondering if it is the future or nothing more then a nice experiment, if Chrome stays around then expect Debian to fork it like they did with Mozilla. If it dies, expect a very small fork to continue development of it.

    --
    Taxation is legalized theft, no more, no less.
  3. Chrome code not public! by nephridium · · Score: 5, Interesting

    The Chrome browser binary you can download is *based* on the Chromium source code, which is free (see http://dev.chromium.org/developers/how-tos/build-instructions-windows on instructions how to compile). The Chrome browser itself is NOT under the BSD license. I was quite disappointed when I realized that. - Just because they say "open source" somewhere doesn't make the Chrome browser itself open source.

    And what's this "installer" program to download the browser for you, why not just give us a download link to the browser itself? Furthermore, the browser will also *update* anytime it feels like it. Afaik there's no way to deactivate this *feature*.

    I'd love to see a site dedicated to compiling daily builds of the Chromium source code, maybe through in some forks by private fiddlers, because right now following the instructions from the link requires you to use a non open source tool "gclient" to download about 500MB of source and then compile it using M$ Visual Studio - and then hope it produces a working binary (oh, and have the time for this). So far I couldn't find anyone doing this and putting the binaries online yet - not even using google ;)

    --


    And when you gaze long enough into the code, the code will also gaze into you.
  4. Re:Well that sounds reasonable. by palegray.net · · Score: 4, Interesting

    Funny how their stuff routinely fails to fail...