To Everyone Who's Been Trying To Contact Me Over AIM
I frequently maintain two connections to my Jabber server: one from work, and one back on my personal laptop, which I’ll just call “home”.
The Jabber server runs an AOL Instant Messenger transport that proxies an AIM login session as another Jabber server, which is how I connect to AIM these days.
However, something is going wrong, and messages aren’t being correctly routed. In order of decreasing probability:
- The AIM transport (pyAIM-t, for those of you who are interested) isn’t routing the messages to the correct Jabber connection.
- The resource priorities I have set up (basically, which Jabber connection “gets the messages”) are wrong. I don’t think this is the case, as “normal” Jabber traffic is correctly routed, but I’m always willing to entertain the idea that I’ve screwed up.
- Something entirely different.
The upshot: If I’m not at work and you message me over AIM, I won’t get them until the next work day. If it’s really urgent, use Jabber/GTalk/whatever: trythil@ninjawedding.org, as I know that works. (Or call me, e-mail me — anything you have.) In the meantime, I’ll try to figure this out.
Post on that mysterious “second interaction problem” coming soon.