question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Hello, I recently switched to using vanilla FF from a fork, and I started getting a bunch of DNS queries to push.services.mozilla.com that I never got on the fork, even though notification permissions have always been blocked. I was befuddled, until I realized I had an ass-ton of service workers. Are these not a privacy risk? The old browser had them disabled by default, and I guess I assumed without really thinking about it that the custom user.js would too.

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:9 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
fxbritcommented, Apr 7, 2022

for reference https://support.mozilla.org/en-US/kb/push-notifications-firefox

a few highlights:

Push messages are encrypted per the IETF spec, and only your copy of Firefox can decipher them. The encrypted messages are stored on the server until they are delivered or expired.

Firefox maintains an active connection to a push service in order to receive push messages as long as it is open. The connection ends when Firefox is closed. We store a randomized identifier (User Agent IDentifier or UAID) on our server for your browser, along with a random client-generated identifier for each push subscription.

If you don’t have any active push notification subscriptions, Firefox rotates the UAID on each new connection.

We store your IP address for 90 days as part of this service. The stored information is invalidated when either the IP Address or UAID is changed

very good implementation imo.

0reactions
Thorin-Oakenpantscommented, Apr 7, 2022

Assuming it’s an intentional slight and getting angry at people over minutiae is no way to live life

I’m not angry at all, I’m just being REALLY HARD on making people read the wiki and user.js before asking for help

Read more comments on GitHub >

github_iconTop Results From Across the Web

Service Worker API - MDN Web Docs
Service workers essentially act as proxy servers that sit between web applications, the browser, and the network (when available).
Read more >
Service worker overview - Chrome Developers
Service workers are specialized JavaScript assets that act as proxies between web browsers and web servers. They aim to improve reliability by ...
Read more >
Service workers - web.dev
Service workers are a fundamental part of a PWA. They enable fast loading (regardless of the network), offline access, push notifications, and other ......
Read more >
Service Workers - W3C
A service worker is a type of web worker. A service worker executes in the registering service worker client's origin. A service worker...
Read more >
Service worker - Wikipedia
Social service worker, a person engaged in social work · Pink-collar worker, a person in the service industry whose labour is related to...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found