08.03.08
Mauku goes to .5.1 – official release
The previous mention of Mauku was an unstable version supporting Twitter concurrently with Jaiku. Today though we get a nice update to the official release in .5.1 which seems far more stable and able to handle the volume of connections both services require.
If you participate in either or both Twitter and Jaiku, Mauku is the gold standard for staying in touch. While twitter offers considerably less organization than Jaiku, Mauku makes it easy to stay connected.
Technorati Tags: Mauku maemo twitter jaiku n800 n810
turn.self.off said,
August 3, 2008 at 9:20 pm
its twitter support is basic at best. no ability to open links in twitts. and it seems to have some issue with updating ones own twitts. you write one, fine. you write another, nothing happens. then you write 3 more and suddenly all 4 shows up…
Henrik Hedberg said,
August 4, 2008 at 1:31 am
Hi turn.self.off, and thanks for your comment. If a tweet contains link, it should appear in the context menu. Just tap and hold for a while or use the left-down gesture. When you post a tweet, it is sent right a way. The thing is that Twitter does not update your feed on real time but every, say, 30 seconds. May be I should add some kind of feedback if the sending succeeded or failed.
turn.self.off said,
August 4, 2008 at 3:19 am
heh, i keep forgetting to check for long-tap menus…
as for the check interval, i take it the update setting do nothing? and what about the refresh button on the toolbar?
thing is that it takes some 2-3 minutes for anything after the first outgoing to register, but the first shows up near instantly.
also, it seems nearly constant that the 4th in a chain will “shake free” the 3 “missing” before it. even if one or more is written using a different interface.
turn.self.off said,
August 4, 2008 at 3:24 am
oh, and the gesture seems to be right-down, not left-down.
Henrik Hedberg said,
August 4, 2008 at 9:58 am
Jaiku and Twitter APIs are pull, not push. It means that the client updates the state in regular intervals. Between those updates (pulls), no new item is received. The interval is set via the settings dialog.
When you write a new Jaiku or Tweet, Mauku updates the window immediately. However, sometimes Jaiku or Twitter have not yet updated the actual feed, but give a cached copy of the feed. It may take even 30 seconds to refresh the cache. If you write many Jaikus or Tweets, Mauku updates the window every time. After some updates, also Jaiku/Twitter has updated its cache and gives latest items as expected. If you write only one Jaiku or Tweet, first update may not contain your latest status. It may appear only after, for example, 2 minutes. This is because next scheduled update has happened after 2 minutes interval.
Unfortunately this behaviour is due to Jaiku/Twitter API limitations, and not controllable by an external third party developer / client application. All we can do is to enhance an user interface to inform user that the message has really been sent, but appears some time later. I will try to do that later.
(Earlier versions of Mauku had a more visible hint when a window was updated. However, most of users did not like it. Now only the update button is dimmed when Mauku is updating a window.)
turn.self.off said,
August 4, 2008 at 11:19 am
ok. yep, i guess some way to tell that the message got delivered is the best way forward then…
and i see now how i missed the menu and gestures, they dont seem to be talked about in the usage instructions…
Henrik Hedberg said,
August 5, 2008 at 3:33 pm
Yes, the usage instructions are very old and not complete. It would be a nice job for a volunteer…
Mauku goes to .5.1 – official release - on Drippler Nokia N900 Updates said,
May 15, 2010 at 2:40 am