Tools  

bergie said

bergie  

Some API updates coming soon: link qaikus, replies by URL, Qaiku Data

6 comments bergie posted to #Qaiku-api Helsinki, Finland 18.06.2009 (en)

6 comments

Bottom

bergie  

Pinging @TomiS to get these rolled out

bergie commented on posted to #Qaiku-api 18.06.2009 (en)

bergie  

Qaiku Data is a way to embed some machine-readable data in your messages. See http://twitterdata.org for examples.

Our implementation is nicer, though, as the data is separated from the displayed message.

bergie commented on posted to #Qaiku-api 18.06.2009 (en)

ferrix  

Of course your API is nicer. Any use cases for the feature yet?

ferrix commented on posted to #Qaiku-api 18.06.2009 (en)

bergie  

@ferrix we were discussing embedded hour reports and other metadata when using Qaiku for workstreaming

bergie commented on posted to #Qaiku-api 18.06.2009 (en)

ferrix  

Nice, though I think I will not be working in a distributed way any time soon.

ferrix commented on posted to #Qaiku-api 18.06.2009 (en)

bergie  

As a teaser, here is an introduction to Qaiku Data:

Inspired by the Twitter Data initiative, Qaiku is starting to support machine-readable metadata in Qaiku messages. Unlike Twitter Data, Qaiku Data is stored as its own field alongside the message, in order not to clutter the actual message displayed on website and in Qaiku clients.

Qaiku Data is handled as key-value pairs marked by $key value. Multiple keys and values can be supplied by separating them with space, like in $key1 value1 $key2 value2.

In Qaiku JSON feeds, data is shown in the data field of the message. On website, they're shown in a qaiku:data attribute of the message <div />.

Qaiku data is limited to 256 characters per message.

bergie commented on posted to #Qaiku-api 22.06.2009 (en)