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.'"

15 of 318 comments (clear)

  1. Re:But.. by Repton · · Score: 4, Informative

    Why is this modded "Funny"? The code is under a BSD license. You can do exactly that.

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

    --
    Repton.
    They say that only an experienced wizard can do the tengu shuffle.
  2. Re:TOS by conlaw · · Score: 4, Informative

    Corporations just don't copy and past legal stuff -- EVER.

    As a past member of three corporate legal departments, I'm ROFL at this quote. Most contracts start as boilerplate and only get changed through negotiation between the parties.

  3. Re:Well that sounds reasonable. by Konster · · Score: 5, Informative

    It's available for download on their main page. This seems to me that they really are releasing it to the public.

  4. Re:What Will Firefox Fanboys Do Now? by Mandelbrot-5 · · Score: 4, Informative

    I'm running xp-64 and run Chrome just fine.

    --
    Math is like sex. People who get it are popular in class, people who don't are not.
  5. Re:What Will Firefox Fanboys Do Now? by onlysolution · · Score: 5, Informative

    Chrome works just fine for me on Vista64 and integrates very slickly with Aero Glass. If you look at the build requirements it lists the Vista SDK, so frankly I'd be pretty amused if it didn't work on on Vista.

  6. Re:So do they... by Evanisincontrol · · Score: 4, Informative

    [so do they] relinquish rights to the stuff that may have been created before the update?

    No, they said that this change would be applied retroactively.

    ...right, and since "retroactively" means "Influencing or applying to a period prior to enactment", that would make the answer yes, not no. How did this get moderated informative?

  7. Re:Well that sounds reasonable. by Anonymous Coward · · Score: 5, Informative

    Some people are trying to make it a new punctuation mark to indicate sarcasm.

  8. Re:Sane legal system please?? by LauraW · · Score: 4, Informative

    Can't we have a legal system that would just dismiss something so ridiculous and unreasonable???

    This actually happened just the other day. A court in Washington state struck down the AT&T long distance Terms of Service. The court ruled that the TOS was "'unconscionable,' meaning that no reasonable individual would have agreed to them had he or she realized their full scope." (quoting from the Ars Technica story).

    A PDF of the decision is here. The interesting bits seem to start around page 23 or so, though my eyes glazed over fairly quickly.

    -- Laura

  9. Re:What Will Firefox Fanboys Do Now? by dennypayne · · Score: 5, Informative

    If you use Privoxy you can have Chrome with ad blocking as well. Works like a charm for me. Credit to this blog for pointing me in the right direction.

    Denny

    --
    Erecting the wall of separation between church and state is absolutely essential in a free society. - Thomas Jefferson
  10. Re:Well that sounds reasonable. by Repossessed · · Score: 4, Informative

    No, the *code* is under a BSD license, one of the things about BSD style licenses is that the binaries can have whatever license you want (see OSX).

    --
    Liberte, Egalite, Fraternite (TM)
  11. Re:Chrome code not public! by mr3038 · · Score: 4, Informative

    [...] right now following the instructions from the link [http://dev.chromium.org/developers/how-tos/build-instructions-windows] requires you to use a non open source tool "gclient" to download about 500MB of source and then compile it using M$ Visual Studio [...]

    Actually, it seems that gclient is open source (python source with Apache License 2.0) and you can get source for it with a simple
    svn co http://gclient.googlecode.com/svn/trunk gclient-dev
    For more information, see http://code.google.com/p/gclient/wiki/StartingDevelopment

    --
    _________________________
    Spelling and grammar mistakes left as an exercise for the reader.
  12. Re:Well that sounds reasonable. by PReDiToR · · Score: 4, Informative

    If you don't like the thought of Google watching your every move, you could always try Scroogle.

    More information here and here.

    Firefox search plugin available too, but some links to it don't work.

    --

    Do not meddle in the affairs of geeks for they are subtle and quick to anger
  13. Re:Chrome code not public! by Orphis · · Score: 5, Informative

    I'd love to see a site dedicated to compiling daily builds of the Chromium source code

    You can download snapshot of the latest version of Chromium for XP from the buildbot here : http://build.chromium.org/buildbot/snapshots/chromium-rel-xp/

  14. Re:Chrome code not public! by atomice · · Score: 3, Informative

    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 ;)

    As already mentioned the gclient tool is open source. Since its written in Python its distributed as source code anyway and the code is under the Apache 2.0 licence.
    As for 'hope it produced a working binary', I compile Chromium for the first time from SVN yesterday without any hitch whatsoever. And yes, my binaries are online.

  15. Re:Well that sounds reasonable. by TheRaven64 · · Score: 3, Informative

    One of the key differences between the BSDL and the GPL is that the GPL has a clause saying that you may not impose any conditions on the code not present in the original license. This is what made it incompatible with the Apache license (v3 allows a small list of extra conditions you may impose). The BSDL allows you to take the code and distribute it in source or binary form, with or without extra conditions, as long as you retain the copyright notice. This is one of the reasons why things that are dual-licensed under the BSDL and the GPL are stupid - the conditions imposed by the BSDL are a subset of those imposed by the GPL, so you can trivially include BSDL code in a GPL'd work - no one would ever choose to use the work under the GPL because it grants them no extra rights.

    If you take a BSDL work and distribute it under a more restrictive license, then people are unlikely to actually use your code unless you modify it first, of course, since they can get the less-restrictive-licensed version and use that instead. If you make changes, people have to decide whether your improvements are worth giving up some rights in order to use. One example of this is a FreeBSD-derived operating system whose name escapes me at the moment which is used for router platforms. It is provided in binary-only form, and costs a small amount (I think it's free for individual use). If it has features you need that aren't in FreeBSD, then you can either pay someone to add them to FreeBSD, or buy a license for this platform and then be locked in to a single supplier for support.

    --
    I am TheRaven on Soylent News