Enter your Jaiku user name. (If you have already your name here, you may want to enter an invalid name first to reset cached authentication data, click OK, and then come back and enter the valid name, but this is not usually necessary.)
Click OK.
Update the overview feed.
=> A web browser should be launched and directed into the Jaiku web site.
Log in using your credientials.
Authorize Mauku to access Jaiku API.
=> Jaiku web site should tell you to go back to the application.
Click "Authorization done" button in Mauku (in the the dialog popped up earlier).
If the process took too long, the previous update may have failed. Update the feed again.
=> Done. (Hopefully...)
I am not getting the web browser pop when I refresh the Overview pane. Even with changing to a bogus name and then back. I also tried disabling the Twitter support in case that was interfering.
But nothing else after that. Tried changing to bogus Jaiku name, refresh. Nothing displayed. Changed back to correct name. Refresh. Again nothing emitted.
Did the gconftool thing. Started mauku with run-standalone.sh. Settings were indeed gone. Put in my Jaiku username. Hit Refresh. Nada. Only thing emitted is the same ConIc debug message as before.
I do not have any idea what is causing that. I have tested Mauku in three devices with slighly different OS version and configuration. Everything went well after upgrade and also fresh install. So, I just have to review the code once again. Thank you very much for your efforts. You gave me valuable information anyway.
I would like to hear if anybody else have success with this latest version of Mauku.
@CAW: Are you sure you were using the version 0.6.0? I mean you were so quick that the latest version may not had been propagated into Extras repository yet. It may take even one hour after promotion.
I have made further tests, and Mauku version 0.6.0 should work fine after upgrade or after fresh install in Diablo.
@hhedberg, it worked for me without problems. The first time I launched Mauku it opened the browser and the authentication was well. I was upgrading for the last version.
Yes, it says 0.6.0 when starting. But just to make sure, I uninstalled it and then reinstalled it and it still does not pop a web browser to authenticate. It just says failed to update Jaiku.
working fine for me on Diablob after an upgrade; initially got the failed to update error but worked fine after a few seconds. I assume OAuth for Twitter will be next...?
Update: I disabled jaiku and it runs fine. Re-enabled and still runs fine. Restarted mauku and it is still running fine.
Is it possible my issue was with the authorization of mauku taking a while to go?
Anyways, seems to be working fine now. Thanks for the update and keep up the great work.
@hhedberg update to 0.6 and authorization via browser worked perfectly on my N800, but with a N810 with same setup I have the same problems as @CAW (tried all the things you suggested, no luck).
Fresh install of Mauku 0.6.0 from Extras, with freshly flashed Diablo 43-7 on an N800: Twitter works, Jaiku simply fails to update. Doesn't ask password or anything. No amount of messing with username changes things. Web pages pops up for "join Jaiku". Sounds like the same problem as CAW. Suggestions?
Another note about my Mauku 0.6 Jaiku difficulties. I cleared the settings with "gconftool --recursive-unset /apps/mauku" and then went into Mauku. Mauku activated the Network Connection box, even though nothing was set up. Jaiku was already checked as enabled, but there was no user name. Twitter was not enabled. Tried the run-standalone.sh method, no web page shown in terminal.
Hmm. Tried Mauku again tonight and this time it magically worked, where every time I've (periodically) tried it in the past has failed. Maybe the problem was something on the Jaiku server's side that got fixed?
My Mauku is now authenticated, which is great. Tested closing and re-starting Mauku and it remembers my authentication successfully.
Alas, my Mauku still displays the same symptoms. Is there any way to enter something manually, using gconf-editor, to bypass the missing browser-based authentication? I just want a chance to enter my password!
Mauku still fails most of the time since the switch to OAuth. It just displays "Failed to update items." I've tried deleting the API key and forcing it to re-sync by changing my username, quitting and restarting Mauku, changing it back to the proper name, etc. Running it with run-standalone.sh, I don't see it spitting out an authorize link. It does this at home, at work, and via my Verizon MiFi portable WiFi.
Loss of Mauku is one of the main reasons I don't participate over here on Jaiku much any more. Is there ANY way I get get more debug info out of Mauku to help try and figure out why OAuth isn't working?
I don't have an answer, but I wonder if this is the same reason why mJaiku for the iPhone doesn't recognize my password? Gut feeling says yes.
It's pretty annoying that the dev for mJaiku hasn't fixed the issue (perhaps he's not aware of it), but some people paid for the app, and I think we deserve a working app.
mJaiku used the old-style login system for Jaiku, which was depreciated when they switched Jaiku over to App Engine. So mJaiku, like most 3rd party Jaiku apps is completely broken unless it gets updated to use OAuth.
I've just done a Wireshark capture of Mauku trying to log into Jaiku, and it looks like the problem may be on the Jaiku side. Jaiku requests "/api/request_token?oauth..." (huge long string of OAuth goodness) to which Jaiku responds with a "Something Broke" error page.
So on the one hand, Jaiku is having some issue with Mauku's OAuth query. And on the other hand, Mauku is silently failing on the "Something Broke" response from Jaiku, rather than displaying the error.
31 comments so far
So just how exactly are we supposed to get this OAuth stuff to work and actually log us in? I keep getting "Failed to update jaiku items."
7 months, 3 weeks ago by CAW
7 months, 3 weeks ago by hhedberg
I am not getting the web browser pop when I refresh the Overview pane. Even with changing to a bogus name and then back. I also tried disabling the Twitter support in case that was interfering.
7 months, 3 weeks ago by CAW
@CAW, is Mauku able to popup the web browser from the About dialog?
7 months, 3 weeks ago by hhedberg
Yes. And the 'Join Jaiku' button on the Jaiku pane of the settings dialog also pops the web browser without issue.
7 months, 3 weeks ago by CAW
If Mauku is not popping the web browser window, you can do the following to authorize Mauku to access Jaiku API:
Start Mauku from the terminal window:
run-standalone.sh mauku
When the overview feed (or any other Jaiku feed) is updated the first time, the following should appear into the terminal window:
=> http://www.jaiku.com/api/authorize ...something else...
Go to the specified web page manually and follow the instructions. After completed the authorization, go back to Mauku and click "Authorization done".
7 months, 3 weeks ago by hhedberg
It is not displaying an authorize string. When Mauku first started, it emitted:
GLIB DEBUG ConIc - conicconnectionsendevent(0x51418, MySSID, WLAN_INFRA, 0)
But nothing else after that. Tried changing to bogus Jaiku name, refresh. Nothing displayed. Changed back to correct name. Refresh. Again nothing emitted.
7 months, 3 weeks ago by CAW
One change still: quit Mauku, and try to unset all settings related to Mauku using the following command:
gconfclient --recursive-unset /apps/mauku
7 months, 3 weeks ago by hhedberg
gconfclient installed by default? "find / -name gconfclient -print" doesn't find it...
7 months, 3 weeks ago by CAW
Sorry, I meant gconftool.
7 months, 3 weeks ago by hhedberg
Did the gconftool thing. Started mauku with run-standalone.sh. Settings were indeed gone. Put in my Jaiku username. Hit Refresh. Nada. Only thing emitted is the same ConIc debug message as before.
7 months, 3 weeks ago by CAW
I do not have any idea what is causing that. I have tested Mauku in three devices with slighly different OS version and configuration. Everything went well after upgrade and also fresh install. So, I just have to review the code once again. Thank you very much for your efforts. You gave me valuable information anyway.
I would like to hear if anybody else have success with this latest version of Mauku.
7 months, 3 weeks ago by hhedberg
Will Mauku be available through the Maemo SSU or would a fresh install be advised?
7 months, 3 weeks ago by Devastator
Thanks for fixing Jaiku integration! :)
7 months, 3 weeks ago by timsamoff
@Devastator, both ways should be working.
7 months, 3 weeks ago by hhedberg
@CAW: Are you sure you were using the version 0.6.0? I mean you were so quick that the latest version may not had been propagated into Extras repository yet. It may take even one hour after promotion.
I have made further tests, and Mauku version 0.6.0 should work fine after upgrade or after fresh install in Diablo.
7 months, 3 weeks ago by hhedberg
@hhedberg, it worked for me without problems. The first time I launched Mauku it opened the browser and the authentication was well. I was upgrading for the last version.
7 months, 3 weeks ago by yerga
Yes, it says 0.6.0 when starting. But just to make sure, I uninstalled it and then reinstalled it and it still does not pop a web browser to authenticate. It just says failed to update Jaiku.
7 months, 3 weeks ago by CAW
mauku 0.6 is crashing for me too. It is doing it during feed update after the authorization.
7 months, 3 weeks ago by gcole
working fine for me on Diablob after an upgrade; initially got the failed to update error but worked fine after a few seconds. I assume OAuth for Twitter will be next...?
7 months, 3 weeks ago by swing
Update: I disabled jaiku and it runs fine. Re-enabled and still runs fine. Restarted mauku and it is still running fine. Is it possible my issue was with the authorization of mauku taking a while to go? Anyways, seems to be working fine now. Thanks for the update and keep up the great work.
7 months, 3 weeks ago by gcole
@hhedberg update to 0.6 and authorization via browser worked perfectly on my N800, but with a N810 with same setup I have the same problems as @CAW (tried all the things you suggested, no luck).
7 months, 2 weeks ago by henso
Fresh install of Mauku 0.6.0 from Extras, with freshly flashed Diablo 43-7 on an N800: Twitter works, Jaiku simply fails to update. Doesn't ask password or anything. No amount of messing with username changes things. Web pages pops up for "join Jaiku". Sounds like the same problem as CAW. Suggestions?
7 months, 1 week ago by qole
Another note about my Mauku 0.6 Jaiku difficulties. I cleared the settings with "gconftool --recursive-unset /apps/mauku" and then went into Mauku. Mauku activated the Network Connection box, even though nothing was set up. Jaiku was already checked as enabled, but there was no user name. Twitter was not enabled. Tried the run-standalone.sh method, no web page shown in terminal.
7 months, 1 week ago by qole
Hmm. Tried Mauku again tonight and this time it magically worked, where every time I've (periodically) tried it in the past has failed. Maybe the problem was something on the Jaiku server's side that got fixed?
My Mauku is now authenticated, which is great. Tested closing and re-starting Mauku and it remembers my authentication successfully.
7 months, 1 week ago by CAW
Oh, how I wish Mauku would be ported to the iPhone/iPod touch...
7 months ago by jezlyn
Alas, my Mauku still displays the same symptoms. Is there any way to enter something manually, using gconf-editor, to bypass the missing browser-based authentication? I just want a chance to enter my password!
7 months ago by qole
Mauku still fails most of the time since the switch to OAuth. It just displays "Failed to update items." I've tried deleting the API key and forcing it to re-sync by changing my username, quitting and restarting Mauku, changing it back to the proper name, etc. Running it with run-standalone.sh, I don't see it spitting out an authorize link. It does this at home, at work, and via my Verizon MiFi portable WiFi.
Loss of Mauku is one of the main reasons I don't participate over here on Jaiku much any more. Is there ANY way I get get more debug info out of Mauku to help try and figure out why OAuth isn't working?
4 months, 2 weeks ago by CAW
I don't have an answer, but I wonder if this is the same reason why mJaiku for the iPhone doesn't recognize my password? Gut feeling says yes.
It's pretty annoying that the dev for mJaiku hasn't fixed the issue (perhaps he's not aware of it), but some people paid for the app, and I think we deserve a working app.
4 months, 2 weeks ago by jezlyn
mJaiku used the old-style login system for Jaiku, which was depreciated when they switched Jaiku over to App Engine. So mJaiku, like most 3rd party Jaiku apps is completely broken unless it gets updated to use OAuth.
I've just done a Wireshark capture of Mauku trying to log into Jaiku, and it looks like the problem may be on the Jaiku side. Jaiku requests "/api/request_token?oauth..." (huge long string of OAuth goodness) to which Jaiku responds with a "Something Broke" error page.
So on the one hand, Jaiku is having some issue with Mauku's OAuth query. And on the other hand, Mauku is silently failing on the "Something Broke" response from Jaiku, rather than displaying the error.
4 months, 2 weeks ago by CAW
er, I meant to say that Mauku requests "/api/..."
4 months, 2 weeks ago by CAW