Comment 7 for bug 447417

There are 2 balcklists.
blacklists that dont allow insertion ito the DB in the first place.
blacklists that dont allow exposure of the events over dbus per default.

The first is no issue and could be implemented instantly, while the second
is a matter of definition. Should the profiling be done on the client side
or should that be in zeitgeist?

2009/11/25 Siegfried Gevatter <email address hidden>

> 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
> https://bugs.launchpad.net/bugs/447417
> You received this bug notification because you are a bug assignee.
>
> 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
>
>