[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [GNU-linux-libre] Status of google chrome and chromium
From: |
jaromil |
Subject: |
Re: [GNU-linux-libre] Status of google chrome and chromium |
Date: |
Thu, 7 Jan 2010 15:56:17 +0100 |
User-agent: |
Mutt/1.5.20 (2009-06-14) |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
sorry for quoting myself and so fast, but this is just flash news that
should close at least one concrete open issue with Chrome:
15:19 <_ale> jaromil: google-chrome --incognito
that's it, works from our own OS menu then.
so far, left open issues are:
- code audition (grepping for network operations and such) - hard!
(( should we simply trust some inquiries with trusted contacts? ))
- a summary of licensing concerns, if any are left. so far, to
confirm A.J.'s, collaborative approach, the EULA debacle had happy
ending
http://googleblog.blogspot.com/2008/09/update-to-google-chromes-terms-of.html
so i'm confident we can straighten up anything together, let's just
clear it up then.
and at the end let's just hope the chrome logo won't be a problem :^)
ciao
> > That being said, I agree that private mode should not be a
> > "select" option, it should be a default which those users who so
> > desire can opt out of. Presumably some people trust google (or
> > any other corporation for that matter) more than we do, I don't
> > think we should deny google the right to let people send them
> > information - that would amount to censorship on our part, but I
> > do believe harvesting it should require EXPLICITE consent.
>
> as of now browsing on Chrome: I notice that every time there is such
> a possibility the browser asks if you like to share information with
> Google. It's a little check button, even hard to hit. i'm fine with
> that, still (old issue) i'm not so fine with all the cookie mess
> going on already since long (which Firefox didn't made much
> better)... that's a practical reason why Incognito should be
> default.
>
> > So a patch to make incognito the default and have the option to
> > disable it in the settings may well be accepted (possibly with a
> > dialog to ask permission to disable it during the initial setup
> > wizard, gray area but one I can live with - thoughts ?) For
> > kongoni, because do source based ports, we could probably apply a
> > patch like that at install time for the users without chromiums
> > explicite agreement - but it would be better to have it in
> > upstream in the first place.
>
> I'm still on the task of understanding more about Chrome extensions,
> however now it comes to me in mind that this can just be a simple
> extension: shared as such and included by default in our
> distributions.
>
> surely we are more familiar with autoconf switches, still having
> this change made at runtime and by including a file in a directory
> sounds much easier and doesn't even needs to deal with upstream
> (eheh, sorry for being such an atheist...)
>
>
> > It's worth noting a major movement within google that aims
> > specifically to address the problems RMS has pointed out with cloud
> > computing and ensure their web apps are not problematic for users in
> > these ways (for example requiring all google web-apps to have the
> > capacity to easily export your data to a format you can easily use
> > offline or take to another provider), that keeps track of the
> > progress of various google projects on these matters.
>
> that's great to know!!
>
> We have also petted this argument within the Free Culture Forum, a
> recent initiative held in Barcelona a few months ago (RMS virtually
> present), calling it "Migration Rights" - be it that we are very
> affected by such issues IRL as migrants.
>
> Digital migration rights is just one among many issues now included in
> a FCF Charter that is also endorsed by the Brasilian ministry of
> culture, among the others. circulate it, join it and use it if you
> like http://fcforum.net
>
> in case there are suggestions / comments / criticism / additions i can
> play liaison to the current FCF editors
>
>
> > It's important to criticize the non-free status of popular
> > applications like picasa (or for that matter, their web apps) but
> > it's also important to recognize where the work they do benefits and
> > supports us - that is, after all, how we create motivation for them
> > to benefit and support us more.
>
> right on!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iQQcBAEBCAAGBQJLRfYMAAoJEAslGzkIl3JR+bUf+wW2Oin8EtJn3Re5fG7kkHx5
xksevEwtYcksR4+b2MigpSwNpX+74IQGLtwXePVEeoHoekDUsu0YXIvdCzK8ApGf
O7fZXAULpUY0qpWzLjoJ4Iv7otzhMSGi8M1oH7zkW/GvJqPUXakcEVk2F+ezvFG/
vJihajpcpoD9CUm3bl3bBmn1+oXbEnlnYQqqQsv1FCrANutpCi5RL6dELUki4rtH
lfYE0QMksclZ/EnEl3ro6QEY5UnV3pIWv+qJhatNRutXHc6XIcFYb3/BnidGXKOy
jTfV+2VKswAp/52cSZXy6GEajC14OTYMviqY3Jey8phOK+Rszm5butAQp9Jt6Ahc
WPJNZ4tSPLjspKzEAkua2UWztScHD8PeOuM+ziCYBcCj6OXulV0fFW6IKxxpq4df
KOayyeVmR9wpOZwK2qL/WMh7Pl0l3eZIz/WXU2ET6a9A0USDFGeLfb5mFoUh+KTY
K+XcnAqCFPvz6iVIB/mldY6Nn11dqHcrKhclvhU81X526GSi8j7tGMyXhgdwv86O
Lq6hiNrSUGBdAX1o8Mkz0RfXYrmesQ3HGFwaPYbhwAWtZlcFrke05exTHwDKSzMs
ND43e6FJRJ/R76hcUySFlrRwC6jXbtrsDgrJhFtPLgpxnsfN3ZfdPlNtBcneAPYl
+CIs7BzPO/dE5qtGOGtN2LbHeNbi3Ngib+boY4lhPDO4mtUbr/cqsmtKF3xcdT2c
eRglofKoGyWLUm2PpBJTokxrMr+3DhLC9ffGuQZlnWVcUo8NvZjLIp/U+61axLC/
DEo1+eqgh89ThD0lxuSOJxbcmLAhFMRkexiWWvewbvuZ/Bh9+fzqcljwXpdUuz7Y
lyuIHjmaV+YPIijhYTV/dRIQJdQVVjGrBbnUEs3Fh+zFHSRp5MwtEyIeQEGEcC/E
B+nm2oXQshRIVw5rZzCWU8Zd+zHrtG6Q4PpBJfrlbQysxJuUuPkyi8OFAv+nnHOd
nJ/aQWAoix0ra3sX0KCx0esQXAXE37NAtcF154ljmT61DRO2MyHub17XpF2o1aTo
9SgiusCcoI2uK9Ol/Y2fErphAb6P+WYc0IE88+55tNTmSvA4IMK419FbkrIFZxHR
rGEX2GyIh3Ze/gfzWvF+L5OJV1o0X2ZsqFOJLFXXO3tKMj8Q0HKUoCdHXr3+kC5A
G1H8c+yXtYA3f+7fWr6wvQlJzIe2dUoHdGQ8xOsaG+9nIHDMamCYJMvD7Ng52z7V
F8nJi/XLp4ujtKfew1a2l15hZAa0bADnNRWrOCj7RxRNbx94NhSHY1sCpRBdxGmC
7WKfG+QO2RxMPea/AOGjP+b1A2fL2ZIq6DeabwKjyljIEIrPKMY/TeqJUK0+UAo=
=XMek
-----END PGP SIGNATURE-----