Date: Thu, 4 Sep 2008 20:12:47 -0700 From: "Ted Mittelstaedt" <tedm@toybox.placo.com> To: <freebsd-questions@freebsd.org> Subject: RE: Google Chrome Message-ID: <BMEDLGAENEKCJFGODFOCMEODCFAA.tedm@toybox.placo.com> In-Reply-To: <20080904131458.6b9e7781@scorpio>
next in thread | previous in thread | raw e-mail | index | archive | help
> -----Original Message----- > From: owner-freebsd-questions@freebsd.org > [mailto:owner-freebsd-questions@freebsd.org]On Behalf Of Gerard > Sent: Thursday, September 04, 2008 10:15 AM > To: freebsd-questions@freebsd.org > Subject: Re: Google Chrome > > > On Thu, 4 Sep 2008 08:26:46 -0700 > "Ted Mittelstaedt" <tedm@toybox.placo.com> wrote: > > [snip] > > > I must have missed something, how would running the Chrome > > browser collect our valuable data? > > > > Obviously, keying in data into a search engine to find > > things is giving the search engine data on what people > > are searching for. Is there any requirement to do this > > if your running Chrome? And, how else would you find > > something? > > > > I think I'm missing something here in this argument. > > Please don't top post. It makes reading a thread a lot harder than it > needs to be. > > I think I posted this yesterday. In any case, you might want to to take > a look at it and its implications. > > http://yro.slashdot.org/article.pl?sid=08/09/03/0247205&from=rss > Um, the OP used "Chrome" to refer to the Google browser under FreeBSD, strongly implying compiling the source to it under FreeBSD. (ie: porting to FreeBSD) At least that is how I took it. The Chrome open source code is under the BSD license, the EULA that is subject of the discussion is attached to the compiled binary that is (I would assume) the result of Google compiling that BSD licensed source under a Windows compiler. You should certainly be aware of the terms of the BSD license by now - if I want to take a product like FreeBSD and compile it's source, I can then commence to apply whatever restrictive EULA that I please to the result. Google is free to license Chrome under BSD then compile a Windows version of Chrome and then apply an EULA to it that is more restrictive - and that appears to be what they have done as documented by this thread you posted. Since the EULA is only under the Windows precompiled binary of Chrome, it isn't applicable to a FreeBSD version of Chrome or to this discussion. So once more, what is the issue here? Since you have the BSD source for Chrome you can certainly remove any secret data collection routines that might be buried in the browser code (if that is your concern, assuming such things even exist) then compile it how you want. Ted
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BMEDLGAENEKCJFGODFOCMEODCFAA.tedm>