That’s in fact one of the gripes I have with certain MacOS software. It would be far better if menu bar icons were opt-in rather than opt-out. The average non-technical user eventually ends up having tons of these icons in the menu bar.
The existence of a menubar icon as an option implies it’s a service that needs to run all the time. I compare that perception to what uBOL mentions in the App Store description.
> uBOL is entirely declarative, meaning there is no need for a permanent uBOL process for the filtering to occur, and CSS/JS injection-based content filtering is performed reliably by the browser itself rather than by the extension. This means that uBOL itself does not consume CPU memory resources while content blocking is ongoing -- uBOL's service worker process is required _only_ when you interact with the popup panel or the option pages.
If you disable it, you can still see (silently delivered) notifications about filter updates.
EDIT: On a fresh install, AdGuard prompts to run in the background for extension updates. I also tend to separately toggle "launch AdGuard for Safari at Login" option.
That’s in fact one of the gripes I have with certain MacOS software. It would be far better if menu bar icons were opt-in rather than opt-out. The average non-technical user eventually ends up having tons of these icons in the menu bar.
The latest version will let you remove them even if the app itself doesn't let you.
I mean, that’s great, but it would be even better if MacOS required explicit permissions before allowing an app to place an icon in the menu bar.
The existence of a menubar icon as an option implies it’s a service that needs to run all the time. I compare that perception to what uBOL mentions in the App Store description.
> uBOL is entirely declarative, meaning there is no need for a permanent uBOL process for the filtering to occur, and CSS/JS injection-based content filtering is performed reliably by the browser itself rather than by the extension. This means that uBOL itself does not consume CPU memory resources while content blocking is ongoing -- uBOL's service worker process is required _only_ when you interact with the popup panel or the option pages.
I believe if you do that, the filter lists don't auto-update. That's the reason for the menu bar app.
If you disable it, you can still see (silently delivered) notifications about filter updates.
EDIT: On a fresh install, AdGuard prompts to run in the background for extension updates. I also tend to separately toggle "launch AdGuard for Safari at Login" option.