3 ms·

The crucial part is missing in the Readme - how it works. Nothing else matters until this bit is explained. From the looks of it, it's just a proxy that forwa

The crucial part is missing in the Readme - how it works. Nothing else matters until this bit is explained. From the looks of it, it's just a proxy that forwards search requests to Google. Unless these happen to go out via Tor or similar anonymizer tech, that's hardly a "privacy-respective alternative to Google search".

tyingq 6y ago
It does appear to strip cookies, and either some or all of Google's JS, depending the config. So, Google wouldn't see your client IP, any cookies, etc. Perhaps not fully private, but they do seem to provide better privacy.
- rovr138 6y ago
  > So, Google wouldn’t see your client IP Yes they would. You can’t sent them a request without giving them your IP. - If you’re self hosting it on your device, they have that device’s current public IP - If you’re self hosting at a server you have, you’re giving them that (and will be easier to track).
  - tyingq 6y ago
    "Yes they would. You can’t sent them a request without giving them your IP." I suspect you know what I meant. They can't see the IP of your browser. Rather, they see a Heroku, DO, whatever IP.
    - rovr138 6y ago
      I actually tried it on my laptop. That’s why I pointed out the 2 cases.
justaj 6y ago
If that's the case, then why not just use googler [0] since it only appears to send IP address, user-agent (which is set to Google Chrome) and search term to Google [1] Edit: Forgot to add, also supports proxies. 0: https://github.com/jarun/googler https://github.com/jarun/googler 1: https://old.reddit.com/r/linux/comments/gayf4i/googler_v41_is_released_google_from_the_terminal/fp4rctl/ https://old.reddit.com/r/linux/comments/gayf4i/googler_v41_i...