I think that Siegfried has an important point. Since we like to relay events around the system the Zeitgeist core will need a blacklisting mechanism. There are several steps in such a solution as I see it...
We need a matches_template(event_templ) method on the Event class. This will be mighty handy for lots of things. Then we we should IMHO not just broadcast any old event over the bus. We should do some kind of subscription service where apps register event templates they want to listen for. And then we only notify apps that have registered matching templates. Embedded in this subscription system should be a blacklisting mechanism. -- Zeitgeist should have any kind of system to protect users privacy https://bugs.launchpad.net/bugs/447417 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 Bug description: Zeitgeist should respect the following use cases: * Tim has a directory ~/Videos/pr0n, he does not want zeitgeist to track any events regarding this directory * Tina played a card game at work and found out that this event is shown in her zeitgeist client, she would like to remove this event to hide it from her boss _______________________________________________ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
