I've managed to set up aim, msn, sip and jablet correctly with Zerojays server. What questions do you have and I'll see about answering them? I havn't seen his howto I just pretty much hacked my way through things.
Yeah, you must be missing a lot, Seth... RTCOMM does not allow direct connecting to those services whatsoever.
EDIT: Actually, it's *ME* that's missing a lot. RTCOMM just released an update that allows you to basically use libpurple to directly connect to the services... basically rendering Jablet moot once it goes final.
I'll try it out in a bit.
This was something that I heard was being ported a few weeks ago. Kind of surprised to see it in an RTCOMM update. Happy to see it built-in.
Seth, Jablet was kind of meant as a stop-gap measure until an official solution was completed, which we all doubted would happen anytime soon... thanks for bringing it to my attention.
a) is from Nokia,
b) uses the Maemo Contacts application, and
c) directly supports AIM, Yahoo, and MSN?
I wouldn't say jablet becomes moot at that point, as connecting via jabber means you can seamlessly move between devices (home desktop to NIT to work desktop) without dropping a conversation. When it works. But it does make jablet a little less unique.
After not being able to connect yesterday, I waited a bit, and everything went back to normal (I think it was an intermediate network hop that was the problem, but I don't know). Then my problem was different:
1) AIM reported me as "available" even if I set my N810 to "away" -- my other services (Yahoo and MSN) all reported my disposition correctly, so I don't think it was the N810.
2) If I set myself to invisible, jablet told my services I was away, instead. (I have a nagging itch in my brain that says this one was a known problem, though)
3) I was having trouble just having conversations with some people via AIM ... messages would just not show up, in either direction. I made sure I was signed off from all other locations/clients, in case things were being misrouted ... but no luck. I would open a dialog, and no messages would go through. Yet, if I talked to them via TXT, we were both sending and not receiving.
Not sure how much of that is jabber, jablet, the aim gateway, or aim...
I would not suggest installing RTCOMM unless you are an experienced user. It breaks functionality of the Application Manager and not all features are implemented yet (such as adding new friends). When it is installed, it is very simple to use. You just have to go to your accounts portion of the Control Panel and create a new account. You will see the various account types have grown quite a bit. Not all work correctly yet, apparently. Yahoo does not appear to work as far as I can see (or it can be the same issue I have on Jablet with really old accounts made back when everything was case-sensitive).
Jablet is not going away.
John: Sometimes AIM ignores status requests. This is a problem even in the official client, just that the average user never notices it. I believe that the IM Gateway may not support invisible mode, but do not quote me on that. I have also had the problem with messages not showing up on AIM, however it was extremely rarely and showed up when I was directly connecting to AIM through Kopete, so it might be a server or protocol issue. If it keeps being an issue, let me know and I will push it towards the IM gateway guys.
