-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ignore Specific Players #10
Comments
Hi Pavan, |
One thing that's a bit tricky is that (at least on my system), Firefox messages posted to DBus don't have a useful
Although the
So, we can query for available MPRIS players via DBus'
and from there, figure out all of that bus' other "queued owners":
.. which we can use to map back to a MPRIS signal sender 🎉. So, the actual exclusion filter will look more like excluding an MPRIS Media Player's namespace (in your case, |
Hey, love this & use it to get desktop notifications for media players that either don't send dbus notifications or want to send their own, uniquely styled notifications that look out of place from the rest of my WM themeing!
The one annoyance is I don't care about some "players" and would like to ignore relaying their mpris notifications to desktop notifications. I.e., Firefox creates excessive messages, like watching a video in firefox will make it start sending mpris messages, and then it proceeds to send one notification for every sound that is made anywhere(like, per slack message, for each tick in a figma timer, etc).
Would love it if we could specify a config option for ignoring specific clients - maybe through the identifier in the bus name? Ideally it wouldn't care about the instance-specific identifier, I want to ignore all
*.firefox.*
messages, not just*.firefox.instance9001
.The text was updated successfully, but these errors were encountered: