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

[Enhancement] Anonymizing Google results #11

Open
readtedium opened this issue May 23, 2024 · 1 comment
Open

[Enhancement] Anonymizing Google results #11

readtedium opened this issue May 23, 2024 · 1 comment

Comments

@readtedium
Copy link
Owner

Mastodon user Artmesia had this idea:

Sorry, I was unclear. I'm not worried about what you might see, my concern is that google knows so much else about me from other google products I use, that I would prefer not to give them my search stream. So I'm wondering if your udm14.com, which I understand acts as a kind of search relay, could be used to somewhat anonymize its users from google. Obviously browser fingerprinting and cookie lookups will continue to work on any clickthrus. Maybe it's hopeless.

(In the department of no good deed going unpunished, you give us udm14 to deshittify google's search results, and I come along and whine that I also want it to anonymize me)

This sounds like an intriguing service that could help people but it potentially would not be cheap to implement.

@xerz-one
Copy link
Contributor

xerz-one commented May 23, 2024

There are FOSS proxy implementations of Google working in the wild. In particular, SearX(NG) exists, and all it seemingly does is do a GET query and parse its HTML... I wonder if Google will eventually break the HTML however, or simply delay or block requests based in IPs or user agents

See:
https://docs.searxng.org/dev/engines/online/google.html#google-engines
https://github.com/searxng/searxng/blob/master/searx/engines/google.py

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants