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
[BUG/FEATURE] Bypass EU cookie consent #243
Comments
This seems some kind of change from goog. I am also facing the same on my docker instance. |
That's annoying. I'll try to replicate on my end and see what I can do. @readall I assume your instance is also running in the EU? |
Mine is too |
From a cursory bit of testing, it looks like accepting this dialog sets a Examples: Netherlands (UK English) -- Sweden (Swedish) -- I tried manually swapping the Sweden and Netherlands cookies, and it didn't seem to have a problem with that, so I'm curious if there's just a default value that can be set in I'll try to look into this some more soon. Thanks everyone for reporting it! |
@benbusby ok, here is a strange one. Set cookie Don't explicitly know how it is tied together, but that one cookie seems to keep the consent away for a duration of time. |
@benbusby Yes, my VPS is hosted within EU. |
@Suika if you don't mind, where is code can this setting be done. I would like to try that. |
Quick and dirty would be https://github.com/benbusby/whoogle-search/blob/develop/app/request.py#L210-L212 just slap another entry in like |
|
You saw that probably just after you changed it. That is normal. Any consequent searches should not show anything. At least it doesn't for me. |
Just pushed a hotfix that includes @Suika's fix while I look into this a bit more. It's available on the |
From today on it's not possibile anymore to search in EU, this pops up anytime on 0.3.1, can we get a new release? Thanks! |
@federicotorrielli |
same for me, it used to show every few searches, but now it shows every single time I click search. |
@federicotorrielli I can relate, I have this bug since I updated my fork. |
use beta tag in docker compose or docker cli in order to pull the corresponding image. |
buildx-experimental works again, thanks. docker pull benbusby/whoogle-search:buildx-experimental |
The |
Is it just me or the beta and buildx-experimental docker tag stuck at starting for anyone else? I tried with both compose and run directly on 2 different servers and all stuck at starting then change to unhealthy after a while. But when I revert to the latest tag, it works (but with EU cookie consent ofc). Running it with -it produces the same log for latest and beta/buildx-experimental |
@inlophe no problem for me running beta version since yesterday |
Sooo, did this fix it? Well, if the non-consensual searching ever breaks the only way will be, is to give consent ytdl-org/youtube-dl@14f29f0. |
Currently the 4.0 release seems to work again for me |
I also did not experience issues after the fix was pushed, seems like it is indeed fixed |
In the EU there exists a "General Data Protection Regulation" [1] aka GDPR (BTW: very user friendly!) which requires consent to tracking. To get the consent from the user, google-news requests are redirected to confirm and get a CONSENT Cookie from https://consent.google.de/s?continue=... This patch adds a CONSENT Cookie to the google-news request to avoid redirection. The behavior of the CONTENTS cookies over all google engines seems similar but the pattern is not yet fully clear to me, here are some random samples from my analysis .. Using common google search from different domains:: google.com: CONSENT=YES+cb.{{date}}-14-p0.de+FX+816 google.de: CONSENT=YES+cb.{{date}}-14-p0.de+FX+333 google.fr: CONSENT=YES+srp.gws-{{date}}-0-RC2.fr+FX+826 When searching about videos (google-videos):: google.es: CONSENT=YES+srp.gws-{{date}}-0-RC2.es+FX+076 google.de: CONSENT=YES+srp.gws-{{date}}-0-RC2.de+FX+171 Google news has only one domain for all languages:: news.google.com: CONSENT=YES+cb.{{date}}-14-p0.de+FX+816 Using google-scholar search from different domains:: scholar.google.de: CONSENT=YES+cb.{{date}}-14-p0.de+FX+333 scholar.google.fr: does not use such a cookie / did not ask the user scholar.google.es: does not use such a cookie / did not ask the user Interim summary: Pattern is unclear and I won't apply the CONSENT cookie to all google engines. More experience is need before we generalize the CONSENT cookies over all google engines. Related: - e9a6ab4 [fix] youtube - send CONSENT Cookie to not be redirected - benbusby/whoogle-search#311 - benbusby/whoogle-search#243 [1] https://en.wikipedia.org/wiki/General_Data_Protection_Regulation Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
Describe the bug
I use proxy setup that rotates the proxing in the background and from time to time, when I connect to EU in this particular instance DE, whoogle will display a "Cookie consent" form from google.
After reloading the pages 2-3 times it vanishes, nonetheless it shows up every ~1-3 request via the addressbar search.
To Reproduce
Steps to reproduce the behavior:
Deployment Method
run
executableVersion of Whoogle Search
Desktop (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: