I'unno, man. It's probably significantly lower than 99.99% of chrome users that stick with Google as their default search despite the first-run search engine selection dialog, but also likely not too much lower, either.…
I don't think there's a need to discuss it as some kind of frightening black box that nobody's too sure about, either. As far as is known, I believe Chrome - Chromium == Branding, MP3 codecs, Pepperflash, Foxit PDF…
This is a great point, and it illustrates the absurdity of many other laws as well.
What's your concept for bringing down the GFW? I'm very interested. Perhaps I could even help you.
Seems like this could be done with more respect for user/data sovereignty if done with Node.js. Essentially, you'd cat the file into the script, it would spin up an HTTP server, do some port knocking or whatever…
I wonder what building a Chromium version would entail. Do you think it would be a lot of work? I feel like it would have been done already if it were possible with the present extension APIs.
Do you any reference links for this being Google's stance? If so, I'd really like to see them. Thanks
There are in fact a number of free solutions... IIRC redshift was the most developed of them when I looked into it a while back. http://alternativeto.net/software/f46lux/?license=opensource
I'unno, man. It's probably significantly lower than 99.99% of chrome users that stick with Google as their default search despite the first-run search engine selection dialog, but also likely not too much lower, either.…
I don't think there's a need to discuss it as some kind of frightening black box that nobody's too sure about, either. As far as is known, I believe Chrome - Chromium == Branding, MP3 codecs, Pepperflash, Foxit PDF…
This is a great point, and it illustrates the absurdity of many other laws as well.
What's your concept for bringing down the GFW? I'm very interested. Perhaps I could even help you.
Seems like this could be done with more respect for user/data sovereignty if done with Node.js. Essentially, you'd cat the file into the script, it would spin up an HTTP server, do some port knocking or whatever…
I wonder what building a Chromium version would entail. Do you think it would be a lot of work? I feel like it would have been done already if it were possible with the present extension APIs.
Do you any reference links for this being Google's stance? If so, I'd really like to see them. Thanks
There are in fact a number of free solutions... IIRC redshift was the most developed of them when I looked into it a while back. http://alternativeto.net/software/f46lux/?license=opensource