Skip to content
This repository has been archived by the owner on Jun 24, 2022. It is now read-only.

🌐 Website Issue | There's no need for "browser.send_pings = false" for it's already the default setting #686

Closed
ghost opened this issue Dec 23, 2018 · 4 comments · Fixed by #865
Labels
high priority 🌐 website issue *Technical* issues with the website.

Comments

@ghost
Copy link

ghost commented Dec 23, 2018

Description

Default elsewhere & Firefox nightlies since 2008-02-01. from http://kb.mozillazine.org/Browser.send_pings

@ghost ghost added high priority 🌐 website issue *Technical* issues with the website. labels Dec 23, 2018
@ghost ghost closed this as completed Dec 23, 2018
@ghost ghost reopened this Dec 23, 2018
@hasanalizxc
Copy link

Maybe someone loves to use the old one and didn't update. This can be useful for her/him.

@beerisgood
Copy link

It's still in gHacks user.js: arkenfox/user.js#242 (comment)

@Thorin-Oakenpants

@Atavic
Copy link

Atavic commented Dec 29, 2018

And it's in pyllyukko's repo. I looked into installed firefox and forks via about:config and issuer is right. Default value is False.

BTW, do not ever trust kb.mozillazine as it appears semi-abandoned (look the last update on bottom page), use searchfox.org instead:

https://searchfox.org/mozilla-central/search?q=browser.send_pings&case=true&path=

privacytoolsIO pushed a commit that referenced this issue Apr 17, 2019
It defaults to false already and is not necessary here.

Closes #686
@Mikaela
Copy link
Contributor

Mikaela commented Apr 20, 2019

It appears to be becoming true by default https://www.bleepingcomputer.com/news/software/mozilla-firefox-to-enable-hyperlink-ping-tracking-by-default/ .

Yay me for having to open https://github.com/privacytoolsIO/privacytools.io/pull/876 after having fixed this issue only four days ago.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
high priority 🌐 website issue *Technical* issues with the website.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants