Zeitgeist Blacklist

From Zeitgeist

Contents 1 Current finalized API 2 History 2.1 API Proposal 2.2 Signals 2.3 Storage of blacklists 2.4 Miscellaneous 2.5 Discussion on the current status of Blacklist 2.5.1 RainCT 2.5.2 thekorn 2.5.3 RainCT

Current finalized API

   Let 'E' define the event dbus signature.
   Methods:
    - GetTemplates() -> ({sE})
    - AddTemplate(s, E)
    - RemoveTemplate(s)
   Signals:
    - TemplatesAdded(sE)
    - TemplatesDeleted(sE)

History

API Proposal

Mikkel proposed the Blacklist API

   Let 'E' define the event dbus signature.
   Methods:
    - GetTemplates() -> ({sE})
    - AddTemplate(s, E)
    - RemoveTemplate(s)
   Signals:
    - Changed({sE})

Signals

Then it was proposed that we should have two signals

• TemplatesAdded
• TemplatesDeleted

Storage of blacklists

Markus proposed to use JSON instead of pickeling

Miscellaneous

{sE} is a dictionary and DBus also supports it

Discussion on the current status of Blacklist

RainCT

I still don't see why blacklist templates would need a manually-constructed identifier...

thekorn

How do you want to identify a template in the collection of all templates, for example, what do you propose as an argument for the RemoveTemplate() method?

Do you want automatically generated identifier (e.g. auto-integer-id, maybe in combination with sender string)? or do you have a system in mind which does not use identifiers at all?

RainCT

Sending the template (like we're doing now) would be an option. If you're not happy with that, we could do something like Zeitgeist itself uses: automatically assigned unique identifiers (be it a number, or whatever).

The problem I see with clients supplying a name is that it just seems too random to me. How are they supposed to choose a name? If I was to write some application using the proposed API, I'd probably end up just using "<my-application's-name>-<current timestamp>" or something like that and hope it isn't already in use.