jabber
Thursday, February 21 2013
IPv6 on Mobile
[03:40:59] matt [wronka.org]/Psi.generay T-Mobile supports native IPv6; I played around with it a bit on my N900 during their open beta phase. It's now mainstream, and rolled into their standard APN which anybody who's signed-up for an account in the last six years or so would probably be on (apparently some of my phones are still on the old Voicestream APNs which have at least recently still worked). According to them, only certain Android phones still work (half of them are Nexus brands). All recent Nokia phones (S40, Symbian) dating about at least five years should work fine too, the S40 phone I had has an option for it but I seem to recall it didn't work during the beta phase, and Nokia didn't want to support it.
Nokia Belle (S60) on the other hand was as easy as selecting "Advanced Options" from the network definition (when not connected) and changing the type from "IPv4" to "IPv6"; everything works from that point on. Well, except the native SIP client which wouldn't connect anymore (to my IPv4 server) and my J2ME Jabber client which wouldn't connect to (or resolve, I'm not sure which) the server. All synchronization, Opera Mobile, and in-built eMail worked fine; but the SIP client is a deal breaker.
[03:40:59] matt [wronka.org]/Psi.generay T-Mobile supports native IPv6; I played around with it a bit on my N900 during their open beta phase. It's now mainstream, and rolled into their standard APN which anybody who's signed-up for an account in the last six years or so would probably be on (apparently some of my phones are still on the old Voicestream APNs which have at least recently still worked). According to them, only certain Android phones still work (half of them are Nexus brands). All recent Nokia phones (S40, Symbian) dating about at least five years should work fine too, the S40 phone I had has an option for it but I seem to recall it didn't work during the beta phase, and Nokia didn't want to support it.
Nokia Belle (S60) on the other hand was as easy as selecting "Advanced Options" from the network definition (when not connected) and changing the type from "IPv4" to "IPv6"; everything works from that point on. Well, except the native SIP client which wouldn't connect anymore (to my IPv4 server) and my J2ME Jabber client which wouldn't connect to (or resolve, I'm not sure which) the server. All synchronization, Opera Mobile, and in-built eMail worked fine; but the SIP client is a deal breaker.
Thursday, October 20 2011
WebOS 3.0.4 Upgrade
[15:06:45] matt [wronka.org]/Psi.dementia WebOS 3.0.4 fixed a number of issues for sure, such as the fact that the web browser would crash Luna(?) on certain large pages. However, it also means a lot of patches that made the device usablish no longer worked, the bluetooth keyboard (which previously didn't have key repeat enabled by default) now drops more characters, and often gets stuck repeating in X. Tab doesn't work--it outputs '9', whereas shift-tab does produce a tab sometimes (also ctrl-shift-i). Escape is oddly ctrl-shift-[ now, which makes it seem like the ctrl key is by default broken, or something else, until it is shifted. I should probably xev that.
The tweaks to start X without the keyboard space reserved are gone--all of tweaks is currently broken. X also doesn't want to start vertically now, whether or not the keyboard is connected--this might actually have been an existing issue if there were any record of a keyboard connected. I hadn't spent much time with 3.0.2 with a keyboard stored in the bluetooth devices but not actively connected.
The default WebOS browser and mail client won't connect to my server, and die with unhelpful errors "Cannot load page" for the web browser, and "error code 990" being one of the errors for the mail client (the other being simply indicating a socket connection error). The mail client also doesn't indicate whether the problem is with the IMAP server or the SMTP server. The problem in all cases only happens with TLS or SSL; removing encryption works. I've installed the root certificate, but that hasn't seemed to fix the connection issues--my kingdom for useful error messages. Of course messaging doesn't work with Jabber, and athe existing (7 month old) messaging-plugins package doesn't seem to work with 3.0.4--I hadn't tried with 3.0.2 but it sounded as if it worked from the forums.
It's arguable if I feel like it make sense to look further into these issues. I'll admit a big part of my reluctance is no fault of HP, Palm, or the community but from the results I saw with Nokia where patches just sat stagnant on bugzilla until Maemo basically died. Unrelated to the software front, it's nice to see that HP offers 90 day service, but the actual page reminds me of why I stopped buying Palm which was because when I called them for support on a new device they basically tried as hard as possible to chargre me for the call. Later it turned out they knew there was a static electriciy discharge issue which would often cause the device to lose stored data. I should have gone with Handspring.
[15:06:45] matt [wronka.org]/Psi.dementia WebOS 3.0.4 fixed a number of issues for sure, such as the fact that the web browser would crash Luna(?) on certain large pages. However, it also means a lot of patches that made the device usablish no longer worked, the bluetooth keyboard (which previously didn't have key repeat enabled by default) now drops more characters, and often gets stuck repeating in X. Tab doesn't work--it outputs '9', whereas shift-tab does produce a tab sometimes (also ctrl-shift-i). Escape is oddly ctrl-shift-[ now, which makes it seem like the ctrl key is by default broken, or something else, until it is shifted. I should probably xev that.
The tweaks to start X without the keyboard space reserved are gone--all of tweaks is currently broken. X also doesn't want to start vertically now, whether or not the keyboard is connected--this might actually have been an existing issue if there were any record of a keyboard connected. I hadn't spent much time with 3.0.2 with a keyboard stored in the bluetooth devices but not actively connected.
The default WebOS browser and mail client won't connect to my server, and die with unhelpful errors "Cannot load page" for the web browser, and "error code 990" being one of the errors for the mail client (the other being simply indicating a socket connection error). The mail client also doesn't indicate whether the problem is with the IMAP server or the SMTP server. The problem in all cases only happens with TLS or SSL; removing encryption works. I've installed the root certificate, but that hasn't seemed to fix the connection issues--my kingdom for useful error messages. Of course messaging doesn't work with Jabber, and athe existing (7 month old) messaging-plugins package doesn't seem to work with 3.0.4--I hadn't tried with 3.0.2 but it sounded as if it worked from the forums.
It's arguable if I feel like it make sense to look further into these issues. I'll admit a big part of my reluctance is no fault of HP, Palm, or the community but from the results I saw with Nokia where patches just sat stagnant on bugzilla until Maemo basically died. Unrelated to the software front, it's nice to see that HP offers 90 day service, but the actual page reminds me of why I stopped buying Palm which was because when I called them for support on a new device they basically tried as hard as possible to chargre me for the call. Later it turned out they knew there was a static electriciy discharge issue which would often cause the device to lose stored data. I should have gone with Handspring.
Thursday, December 9 2010
[14:16:10]
matt [wronka.org]/Merch
Interstingly, Google's Jabber system just sent me two auth requests. I haven't changed anything on my side since before the summer; perhaps they have a six month heartbeat?
Tuesday, March 16 2010
Quec.es and Privacy
[22:58:18] matt [wronka.org]/kerberos In talking with dmcc [jabber.bigasterisk.com] earlier today, he voiced interest in the concept of quec.es (using Jabber as a means of microblogging) but didn't like the fact that it automatically scraped users' status.
To fix this concern, I've added an ad-hoc command configuration to enable or disable the logging of your status. There's also now a "watching" mode where you can be alerted in real-time to somebody else's posting.
[22:58:18] matt [wronka.org]/kerberos In talking with dmcc [jabber.bigasterisk.com] earlier today, he voiced interest in the concept of quec.es (using Jabber as a means of microblogging) but didn't like the fact that it automatically scraped users' status.
To fix this concern, I've added an ad-hoc command configuration to enable or disable the logging of your status. There's also now a "watching" mode where you can be alerted in real-time to somebody else's posting.