Ability to filter forwarded messages more accurately

[eras]

Currently there are a few fixed categories (such as email and messaging) for filtering which notifys are forwarded to the Pebble. It would be nice if there was more accurate filtering available.

It could work as follows: pebbled would collect the unique client identifiers (possibly the .x-nemo-owner field and .category) into an sqlite database. For each new row a default value for the category is chosen (passed, filtered). Said list would then be possible to modify from the pebble user interface. And when in future a notify appears, the database would be consulted.

A simpler alternative that would probably work as well but would be an expert interface: white- and blacklist regular expressions. This feature might even make sense in the presence of the previous one :).

In practical terms, this feature would be beneficial for filtering the Jolla store update messages, jollatohkbd "keyboard inserted"-messages, and still allowing custom messages to pass through (ie. ones produced by the irssi-mqtt-notify).

[abranson]

The tohkbd one is annoying, but I wonder if that can be more simply filtered along with all of the notifications that appear in a thinner bar and don't leave an entry on the events screen.

[smokku]

BTW, this is exactly how Android app handles the notifications filtering

[abranson]

This would be simpler:

http://bazaar.launchpad.net/~mzanetti/rockwork/trunk/view/head:/rockworkd/notificationmanager.cpp