Tools

bergie said

6 comments

Bottom

bergie  

Also interesting: The performance problems in Gwibber 2.29 are largely a side-effect of the program's dependence on CouchDB. (ping #midgard)

bergie commented on posted to #gwibber São Paulo - SP, Brazil 02.03.2010 (en)

bergie  

Tried the Gwibber daily with Qaiku and seems to be working pretty well. Couple of things that could make it better (ping @segphault):

  • Markdown visualization for Qaiku messages
  • Showing something about the original message when message is a reply (like we do in the Qaiku stream)
  • When adding the Qaiku account the field for API key is called "Password". Would be better if it said "API key"
Oh yeah, and posting to Qaiku doesn't do anything. No error messages either.

bergie commented on posted to #gwibber São Paulo - SP, Brazil 02.03.2010 (en)

bergie  

Again testing Gwibber nightly:

  • Posted a ticket about Markdown support (544129)
  • Posted a ticket about char limits when posting commits (544133)
And yeah, posting a message to Qaiku still doesn't work. Now we debugged it enough that it results in a 301 redirect, which is weird.

bergie commented on posted to #gwibber Krämetsskog 22.03.2010 (en)

bergie  

Ping @segphault figured why Gwibber posting doesn't work. It is using qaiku.com instead of www.qaiku.com, which passes the requests through a redirect. Fixing the URL makes initial posts work. See Launchpad

bergie commented on posted to #gwibber Krämetsskog 22.03.2010 (en)

bergie  

Sent a patch for Gwibber. This should make things work properly.

bergie commented on posted to #gwibber Krämetsskog 22.03.2010 (en)

bergie  

Maybe python-markdown would solve message formatting.

bergie commented on posted to #gwibber Krämetsskog 22.03.2010 (en)

Login or register to leave a comment

Publicity
These messages are public and can be seen by anyone.