Archive for June, 2009

AIM Push Notification and Multiple Sessions, Who Wins?

Sunday, June 28th, 2009

A question was recently posed by a friend. He noticed that as long as his AIM client was signed in on the iPhone, actively or just for Push Notification, that messages would no longer be sent to his desktop client anymore. This sort of behavior could render the “always signed in” Push Notification useless if the desktop client can no longer receive messages while the iPhone application is considered to be signed in.

It turns out that AOL uses a precedence order in deciding which client should get the message, or in some cases both. Here is the precedence order:

Available (1)
Away (0)
Idle (-1)
Invisible (*)

AIM clients with the same precedence “score,” the number in parenthesis, will get the same message. If one client has a higher score, no other clients will get the message. Idle time will subtract one from the score. Available + Idle is the same thing as Away + Active.

For example if both clients are Available and not Idle, both will get the message. If one is Available and the other Away, the Available client will only get the message. Here is where things get interesting, if a client is Available and Idle, and the other is Away but Active both get the message.

The most effective way to use both the iPhone AIM client and a desktop client like Adium, iChat, or AIM, you need to have the desktop client set to Available and the iPhone client set to Away. The desktop client shouldn’t be set to artificially Idle, or both will get the message.

This is a little annoying because I tend to set Adium to Away all the time. Going forward to utilize AIM for the iPhone I’ll have to keep available and not idle, otherwise messages are going to start appearing on my phone. I guess this promotes some additional honesty about my actual status.

I hope this solves the mystery for someone. I couldn’t find anything too definitive elsewhere on the web.

*Note: Setting Invisible in one client changes your status in all logged in clients. It’s not possible to be Away in one, and invisible in another. I was hoping I could leverage this somehow by setting the iPhone to invisible so that it would only get messages if the desktop client went offline.

Now with Fancy

Thursday, June 25th, 2009

A quick post just to point out the obvious, the blog has a new look. More on this later, but Kenta is to thank for the design.

Enjoy.

When BS is so bad it hurts

Thursday, June 25th, 2009

It appears that Movable Type has been forked into a new project called “Melody.” Now this is why I love Open Source software, if something isn’t working right fracture the code, take some of the developers, and subdivide the user base. I understand that one piece of software can’t do everything. By all means it shouldn’t, but there doesn’t seem to be any driving goals of this project that aim to make it vastly different the Movable Type.

A quick read of the sparse About page and FAQ, seems to indicate that this fork is driven by the need to work with the community more. In other words they don’t have any unique design principles yet, but invoking the term “community” implies that we soon will have all that we’ve been missing from Movable Type. They suggest trying to be more like WordPress. Maybe that means documentation that isn’t habitually wrong. I’m not sure.

On face value it looks like some sort of internal fallout happened. When you drop all of the idealistic bullshit, thats the most common reason for a fork. Two people couldn’t agree and they go their own way but try to make it look all happy and mutual, as if this will somehow be “better for everyone.”

The way I see it, Movable Type has been trying to become a CMS and failing miserably. It’s once rapid rate of progress during the 3.x builds has become a snails pace under 4.x., and this fork may finally kill it or get SixApart off their asses and take a look at what their actually trying to accomplish.