Twitter Client with Filter and Parser Functionality – Part 2

Since everyone is writing in english on this blog, I’ ll do the same and from now on. In the Meeting of 18.10.2010 we discussed the following functionality/requirements:

  1. Grouping of  Twitter users
  2. Showing the Tweets of groups
  3. Filtering of Tweets with regular expressions
  4. Creation of webservice-triggers
  5. Execution of triggers
  6. Last but not least (already discussed in the first meeting): shall run in the browser.

Ad 1. and 4.:
The configured groups and triggers shall be persisted and at least survive a browser cleanup. The first thing that came to my mind was the use of a database. But Martin mentioned html 5 persistence, a buzzword I stumbled upon earlier when reading some blog entries here before. It offers a nice API and much space for “temporary data”. But it didn’t turn on godmode for the twitter client’s data. So if we stay with the godmode requirement we need to use a database on the webhost.

Ad 2.:
Twitters API can’t be accessed infinitely. You can read a short summary here. At the moment it is like this:

  • Anonymous: based on the IP of the host and are permitted 150 requests per hour.
  • OAuth: calls are permitted 350 requests per hour

Then there is another API, the Search API, which has it’s own secret rate limit, higher then the normal APIs limit. It doesn’t require or even offer authentication. But the Search API is very limited. I didn’t manage to retrieve Tweets older than a week. So we have to use the normal API with OAuth.

OAuth via javascript doesn’t seem to be a good idea. Twitter even states: “javascript really shouldn’t be used for OAuth 1.0A with respect to websites in web browsers.”. That seems to be one of the reasons why you don’t find good resources when searching for “js oauth”.

I will choose PHP to do the job. We need a backend for data persistence anyway…

Ad 3.:
Regular expressions will do the job nicely. Filtering the geeky way is sufficient.
The regex pro gains speed of light. The newbie gets some education. I guess everyone who will ever use this tool can at least formulate some simple patterns…

Ad 5.:
Here we/I still need to choose where the triggers are executed. Since we will use server-side storage either client or webhost could execute triggers.

Ad 6.:
javascript, ajax, uki-js

The developement progress is good and I already have a prototype with parts of the functionality. I will prettify the UI in the next days. As soon as that’s done i am going to present some screenshots here.

- Andreas Breschneider

, , ,
  • Delicious
  • Facebook
  • Digg
  • Reddit
  • StumbleUpon
  • Twitter

Leave a Reply

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>