-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
referer.spoofSource breaks Google Hangouts #96
Comments
Almost every setting which prevents such data to be sent has the potential to break something. There are plans to create "breaks: xy" notifications (https://github.com/allo-/userjs-schema/blob/master/prefs.json), but this needs to be implemented first ... Can you test with the RefControl extension and this article what are the maximum privacy settings where it still works?
|
Ran into this too - |
RefControl does not work with recent firefox as far as I know. Have you tried other combinations of the options in https://www.ghacks.net/2015/01/22/improve-online-privacy-by-controlling-referrer-information/? |
Anything Google related needs most tracking entries untouched: that's exactly the opposite of what this repo is doing. I suggest either a new profile or another browser for using Google services. |
Hey guys, I recently switched from Chrome to Firefox, happily leveraging some options in ffprofile.com. I noticed a random, seemingly unrelated problem in Firefox, where hangouts.google.com wasn't delivering my text messages - it was just hanging and eventually failing to deliver. What this looks like: https://gfycat.com/ifr/GleefulBlaringHarpyeagle
Through some trial and error, I eventually confirmed that it was due solely to "network.http.referer.spoofSource" being set to the non-default of "true" by the prefs.js ffprofile.com gave to me. Setting it back to "false" fixed Google Hangouts and it no longer has trouble sending text messages.
I forget exactly what I checked on ffprofile.com for that settings to be set to true, but a more explicit warning about it breaking some sites, potentially even an explicit warning about it breaking Google Hangouts itself, would be useful so others don't run into this issue as well.
Cheers.
The text was updated successfully, but these errors were encountered: