I Made Pharos: A Firefox and Chrome Extension That Reports New Notifications Across Different Services

I have notifications turned off for almost every app on my phone. It's not that I'm a hardliner, it's that one thing bugs me: apart from handling notifications, it's unclear what else an app is doing in the background. I don't want to dig into that, so it's easier not to allow them at all
On a computer it doesn't work that way. I sit at it almost all day, and everything important lives in my browser: mail, GitHub, replies on social networks, etc. Without notifications it looks like this: you keep about ten tabs open and go around them every half hour. They eat memory, constantly catch your eye, and most of the time there is nothing new in them. I wanted something that tells me on its own where a new notification appeared, so I could close the tabs, and I did not want to hand my accounts over to someone else's server for that. I looked for something ready-made and found nothing that fit
This became the reason for creating Pharos — an extension that does exactly that, and that I can vouch for, because it has no server of its own and its code is open
🔔 What is it?
Pharos is a Firefox and Chrome extension that checks your connected accounts every few minutes and shows where a new notification appeared. Everything works in the browser: the project has no server of its own, and nothing is sent to the developer. The code is open, so anything Pharos does can be checked in the sources
For most services it uses your regular browser sign-in: it asks the site for the same thing the page itself asks for and takes the number of unread notifications from the answer. Where an official API is available, it works through that instead
👤 Who is it for?
For people who spend whole days at the computer and have turned off notifications on their phone, but still want to know when something somewhere has arrived
🖥️ Screenshots
⚙️ How does it work?
You press Add, pick a service, and the browser asks for access only to that service's site. Right after that the first check runs, but it shows nothing: it's the starting point, otherwise the whole old pile of unread items would hit you at once
After that, checks run every five minutes (the interval is configurable) and anything new is sorted by type: direct messages, replies, reactions, followers and the rest. For each type you decide what to do: notify right away (with a sound if you like), collect into a digest once an hour, or stay silent. The toolbar icon shows a number for what is important, and the Mark as read button changes nothing on the site: Pharos just remembers how much you have already seen and counts only the new things from then on
There is also a quiet mode. You turn it on manually or on a schedule (11 PM to 8 AM by default): nothing makes a sound, and everything that piled up arrives as a single digest when the mode ends
🛠️ What if something breaks?
Sites change their pages and sessions expire, so sooner or later something breaks. Pharos doesn't keep quiet about it: the service row is marked Not working or Sign in with an explanation of what happened, and the notification about the problem arrives once, not on every check. Usually the fix arrives with a rules update, with no need for a new version of the extension
🔒 What about your data?
Everything is stored in your browser: the list of connected services, settings, notification counts, a week of check history and access keys for working through official APIs. Pharos doesn't save passwords. Only counts are taken from the answers (and the sender's name, if it is in the answer), while message texts, feeds and contacts are never stored or shown. Access to sites can be revoked at any time, and everything saved is erased with one button in the Data and permissions section
✨ Key Features:
🔔 Notification Types
Direct messages, replies, reactions, followers and the rest are counted separately🎚️ Notify, Digest or Silence
A mode for every service and every type🌙 Quiet Hours
Silence on a schedule, with everything delivered as one digest afterwards🛠️ Honest Breakage
A broken service is marked, and the reason is written next to it🔒 Access Per Site
The browser is asked for one site at a time, and access can be revoked📖 Open Source
Read exactly what it does, or build it yourself
📦 Where to get it
The Firefox version is currently under review at Mozilla, and once it is approved you will be able to install it from the Firefox Add-ons store. The Chrome Web Store will have to wait a bit. Until then you can build the extension from source: the instructions are in the repository README
🗺️ Roadmap:
New Services — The list will grow, and you can suggest one in the repository
Custom Services — A way to describe the rules yourself



