No, this is not related to a blacklist mechanism discussed in bug 447417.
A blacklist system is on a per event basis whereas this bugreport asks for a
more global solution to manage dataprovider in general. This is esp. needed
when we have a gio dataprovider.
add a registry for Dataprovider
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Framework.
Status in Zeitgeist Framework: Confirmed
It should be possible to
* enable/disable some dataprovider (esp. useful for testing while developing
* define which dataprovider sends events for which application (right now it
is possible to have multiple DP per application, eg. are shipping a firefox
logger and on the other hand there is an external FF extension which sends
events. This can end in a race between both logger, and logging the same data
twice is also not useful)
The preferences should be stored in a user readable format (ini like text file)
but also be accessible over DBus.
Maybe this fits into a more general Configuration Interface I started some time
Mailing list: https://launchpad.net/~zeitgeist
Post to : email@example.com
Unsubscribe : https://launchpad.net/~zeitgeist
More help : https://help.launchpad.net/ListHelp