Removing events after their insertion is not the answer, they should
never be inserted at all if they are blacklisted. If they get inserted
they are broadcasted to all listening programs (possibly including
stuff like Teamgeist) so it's too late to delete them.

I'd like to have filtersets defined (just like in Teamgeist for
deciding what is send out) and InsertEvents should check stuff against
the blacklist and reject it (returning None -ie. ""- in the event's
position in the the list of event ids resulting from the InsertEvents
call). The code for this (checking if an event matches the filters)
should probably go into a public module so that other applications can
use it too.

Better ideas are welcome, of course!

Zeitgeist should have any kind of system to protect users privacy
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 

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to