[wishlist] Qaiku support for Gwibber

@Henri: It looks like Qaiku doesn't have an API yet. It would be ideal if Qaiku could implement a Twitter-compatible API. That would significantly reduce the barriers for adapting existing client implementations. Software that supports Laconi.ca would be able to support it out of the box. Relevant documentation is here: http://laconi.ca/trac/wiki/TwitterCompatibleAPI You might want to pass that suggestion along to the Qaiku team.

Henri and the Qaiku team have done a great job so far with the API. I implemented support for it in the latest trunk revision of Gwibber.

@Ryan: I just installed latest Gwibber from the "Gwibber Daily" PPA (http://ppa.launchpad.net/gwibber-daily/ppa/ubuntu karmic main), and can't see Qaiku as an account option. Has the support been removed?

@Henri: I recently rewrote the Gwibber backend and haven't gotten around to making sure all of the services work with it yet. There are several that are a high priority, including generic StatusNet support and Qaiku. It will probably be fixed soon, definitely before the official release of Gwibber 2.30.

@Henri: I've reimplemented support for Qaiku in the latest Gwibber, but sending doesn't work. When I try to POST the Qaiku API gives me an error message.

@Ryan couple of questions to clarify this:

* Are you using Basic or APIkey authentication?
* Are you making a HTTP POST?
* What exact error message are you getting?
* What POST variables are you sending? Here are the ones Qaiku accepts:

  - "status" contains the message you're posting. If it is a Qaiku starting a thread it must be under 140 chars. Replies can be longer
  - "data" can contain additional machine-readable QaikuData (see the Twitter data format)
  - "external_url" can contain an URL if you're posting a link Qaiku
  - "lat" and "long" can contain user's coordinates in decimal format
  - "location" can contain user's textual location
  - "source" can contain app name, say 'gwibber'
  - "channel" can contain name of a Qaiku channel (without # in front) if you want to post to a channel
  - "in_reply_to_status_id" can contain the ID of a Qaiku message if you're posting a reply. ID is a Midgard GUID value
  - "lang" can contain the two-letter language code for the message ('en', 'fi', 'de', ...)

Please set only the variables you're going to put something in.

Figured this out. The issue with posting is that Gwibber uses http://qaiku.com when the correct URL would be http://www.qaiku.com

Changing this in sources fixes making initial posts.

However, some additional notes:

* Please set "source" as "gwibber"
* Replying doesn't seem to work. I'm looking at qaiku.py to figure out why

Replying was an issue on Qaiku's end and has now been fixed. So, Gwibber will work fully with Qaiku by just changing the URL (and adding source as "gwibbernet" when posting).

Quick patch attached.

Updated and combined qaiku.py with all the necessary patches applied against latest nightly PPA is available in http://gist.github.com/359045

Thank you, Henri! I've committed this to Gwibber trunk.

This bug was fixed in the package gwibber - 2.30.0.1-0ubuntu1

---------------
gwibber (2.30.0.1-0ubuntu1) lucid; urgency=low

  * New upstream release
    - Fixed account creation for accounts previously deleted (LP: #535263)
    - Fixed support for Qaiku (LP: #342536) (LP: #544129)
    - Fixed identi.ca search URL
 -- Ken VanDine <email address hidden> Thu, 15 Apr 2010 09:31:50 -0400

i keep getting Authenticating Qaiku... i can view my latest post but not post.. it sometimes randomly works and sometimes it doesn't! twitter is working fine so it aint the key string problem