#Qaiku-api

Because it's a Twitter client, not a Qaiku client. And for Twitter, there are better apps than Seesmic for Android.

But surely Seesmic should do better than what it does if the API is compatible? And talking of "better" Twitter clients, do your suggestions support multiple accounts?

@myrtti many Twitter clients fail because we use GUIDs as message IDs instead of integers.

But if you can debug this somehow from client end we can probably try to do something

We discussed about this issue about GUIDs vs. numeric IDs with @bergie IRL. @bergie let us know if you find solution for this, it would probably open Qaiku to many clients...

@bergie Check this - I think this might be important new information and give some implementation ideas... Maybe Qaiku could have both ID's at least if you implement another API url.

@Ile according to ReadWriteWeb, the new Twitter "snowflake" IDs will be presented to clients as strings, which probably would mean we don't have to change anything. Though making the API support OAuth would probably help

@bergie What I've learned about snowflake and new str_id's: Most client will still continue to use integer id's. str_id:s are added to side as a dirty hack to support java script that can handle only 54 bit integers when 64 bits are needed.

Native apps written in java, objective-c, c, etc. will not use str_id's at all.

Could qaiku api publish both integer id + str_id just like Twitter does. In qaiku str_id would be current GUID and numeric id the one you already have in a database (and it's not unique between different qaiku instances)

Sounds reasonable @Ile. @tepheikk, what do you think? This would be almost a one-liner

@myrtti @Ile @bergie I've modified the api. It now contains numeric id in field id_int.

I can switch id (guid) => id_str and id_int => id as soon as some confirms that existing qaiku supporting clients do not break up :-)

now if only I had Seesmic for Android... GODDAMMIT

@tepheikk Can you provide "twitrer compatible" version of api in different url?

How about adopting Twitter snowflake algorithm to Qaiku API to provide better twitter client support?