Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove Google Search; Google Analytics #2460

Closed
wants to merge 3 commits into from
Closed

Remove Google Search; Google Analytics #2460

wants to merge 3 commits into from

Conversation

resynth1943
Copy link

Remove Google Search

This commit replaces the Google search box to a DuckDuckGo search box.

I have chosen not to use their search box, but instead I have incorporated
this functionality into the search box that was previously being used.

I have also added short codes to every locale file, as seen in the previous
commit. DuckDuckGo supports localisation, so this should make the search
experience nicer for visitors of the Ruby website.

I am unfamiliar with Google, so this may be a guess, but I have witnessed
that some CSE special codes were missing from the locale files. I can only
guess that these were previously being used for localisation, e.g. choosing
a specific language for the search box.

If so, this should be a massive win for users of this site that are: not fluent
in the English language; do not have a Google account tailored to their language.

Moreover, this change will be a brilliant win for the privacy of the users of
your site. As Google is an advertising company, we can only guess what they do
with the data they collect on millions of users every day.

In my personal opinion, tackling this abhorrent abuse of data should also be
peformed by FOSS projects. Just think: every time someone searches, you've just
saved their online privacy! :D

Theoretically, DuckDuckGo should in fact be more performant than a Google search,
too. I have friends who have just confirmed this, which speaks volumes of
DuckDuckGo as a service.


Remove Google Analytics

This commit removes the Google Analytics 'functionality' from this page. Following on
from the previous commit, this change also greatly improves the privacy of
unsuspecting users.

If you must have an analytics system, might I suggest either:

These solutions are all well-tested and open-source. This, of course, means they
can be independently audited for privacy and security. Instead of using a proprietary
nonfree system such as Google Analytics, perhaps we could work together to replace
it with something slightly more ethical?

Furthermore, the majority of privacy features in evergreen browsers block Google
Analytics from being run. I can not say the same for solutions such as Plausible,
which suggests they are trusted for their privacy by independent persons.

Thankfully, this change is relatively easy to make, as you have a brilliant
taste in build tools! Jekyll is, thankfully, rather easy to work with.

If you need any more information, please contact me!

This commit replaces the Google search box to a DuckDuckGo search box.

I have chosen not to use their search box, but instead I have incorporated
this functionality into the search box that was previously being used.

I have also added short codes to every locale file, as seen in the previous
commit. DuckDuckGo supports localisation, so this should make the search
experience nicer for visitors of the Ruby website.

I am unfamiliar with Google, so this may be a guess, but I have witnessed
that some CSE special codes were missing from the locale files. I can only
guess that these were previously being used for localisation, e.g. choosing
a specific language for the search box.

If so, this should be a massive win for users of this site that are: not fluent
in the English language; do not have a Google account tailored to their language.

Moreover, this change will be a brilliant win for the privacy of the users of
your site. As Google is an advertising company, we can only guess what they do
with the data they collect on millions of users every day.

In my personal opinion, tackling this abhorrent abuse of data should also be
peformed by FOSS projects. Just think: every time someone searches, you've just
saved their online privacy! :D

Theoretically, DuckDuckGo should in fact be more performant than a Google search,
too. I have friends who have just confirmed this, which speaks volumes of
DuckDuckGo as a service.

I can't wait to see what happens!
This commit removes the Google Analytics 'functionality' from this page. Following on
from the previous commit, this change also greatly improves the privacy of
unsuspecting users.

If you must have an analytics system, might I suggest either:
- Plausible: https://plausible.io (offers a 50% discount for FOSS projects)
- Goatcounter: https://goatcounter.com
- Matomo: https://matomo.org
- Fathom: https://usefathom.org

These solutions are all well-tested and open-source. This, of course, means they
can be independently audited for privacy and security. Instead of using a proprietary
nonfree system such as Google Analytics, perhaps we could work together to replace
it with something slightly more ethical?

Furthermore, the majority of privacy features in evergreen browsers *block* Google
Analytics from being run. I can not say the same for solutions such as Plausible,
which suggests they are trusted for their privacy by independent persons.

Thankfully, this change is relatively easy to make, as you have a brilliant
taste in build tools! Jekyll is, thankfully, rather easy to work with.

If you need any more information, please contact me!
@resynth1943 resynth1943 requested a review from a team as a code owner June 26, 2020 18:08
@hsbt
Copy link
Member

hsbt commented Jul 20, 2020

It's good to migrate the internal search engine like Elasticsearch from company service. Therefore, I'm not sure what advance DuckDuckGo from Google CSE.

@hsbt hsbt closed this Jul 20, 2020
@resynth1943
Copy link
Author

It's good to migrate the internal search engine like Elasticsearch from company service. But I'm not sure what advance DuckDuckGo from Google CSE.

I mean, we could try a different search engine.


I'd like to talk more about your ElasticSearch idea. Would you be open to reopening this, so I could implement it if poss?

@resynth1943
Copy link
Author

Hey @hsbt, would you be happy for me to open an issue so we could discuss your Elasticsearch idea further?

@hsbt
Copy link
Member

hsbt commented Jul 21, 2020

I also maintain the infrastructure of *.ruby-lang.org. I have no time to handle it. I understood you have a concern to use Google product. But I don't have it. So, This issue is low priority for me.

@ruby ruby locked and limited conversation to collaborators Jul 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants