API Thoughts

Our medium to long term plans for Public Whip are to introduce an API (Application Programming Interface: if you don’t recognise the term, you can just gloss over this whole post) to help third parties integrate with Public Whip – without having to “screen scrap” the content. An example of a service currently utilising the content is “Keep track of how your MP votes” Boxee application.

Things we’d like to know:

  • What format of data would you prefer the data: CSV, TSV, XML, JSON, SQL, other?
  • How would you prefer to access it: SOAP, REST, HTTP GET, HTTP POST, data download (we do currently offer this!), other?
  • How often would you like to refresh the data: weekly, daily, hourly, “as live as possible”?
  • What sort of information would you like to be able to access?
  • Would you prefer, in the first instance, “documents” or “code” integration guides?
  • Would this be for a commercial or “open source/free access” project
  • What sort of volume of requests would you expect to push to us? (And would it be possible to introduce caching/proxying your end)
  • Would you like to “push” data to us? If so, what sort (comments, policy division revisions, etc etc)
  • Anything else you think relevant :-)

Basically, we’d just like to hear from you how you would like to use the data. At the moment, we’re not going to make any guarantees about anything, but if we can get ideas from YOU then we may be able to start making plans…

Weekend work: Security patches and forum access

Due to numerous inherited flaws in the codebase we’re seeing rather a lot of spam, both in the forums and in the email of registered users. As such this weekend we’ll be applying a number of patches, and stop-gap measures to tighten things up.

Our primary concern is the reports we’ve received from people who have begun to receive spam email to addresses that are only utilised on PublicWhip. We despise spammers and can categorically state that we have never, and will never, share or sell the personal data that our users entrust with us. If you have received spam email to an address that has only been used on PublicWhip, would you please let us know the address details (email team@publicwhip.org.uk) to help us identify where the data leak is coming from and to plug it.

One of the main culprits is a very out of date installation of PHPBB and whilst we look at alternatives, and gather input as to the usefulness of the forum (beyond acting as a changelog for divisions and policies), we’ll be taking the forum offline.

We’re still getting to grips with a system and a codebase that is relatively new to us, but we’re determined to make the site the best that it can be, and data security and data integrity will always be at the heart of what we do.