Nobody else has subscribed to updates by AIM. I guess that's not exactly surprising, since it's something of a silly feature. Here are some other things to do with it. This doesn't include using IM in the cloud field of an RSS 0.92 feed, since it'd be difficult for anyone but UserLand to do that.
- Search. Tying Kit's search thing into IM would be one nice way to get across the firewall.
- Message repeating. Radio could bounce a message across two IM systems. Since the message once in the receiving system will have the Radio instance's login, I'm not sure when this might be useful.
- Comments. Something I thought about adding to BlogIM is instant commenting: BlogIM sends a message, then if you respond, it posts your response as a comment to the post. Implementationwise, I'm not sure what
conditionwould satisfy that: an item was sent in the last five minutes and the message isn't "unsubscribe?" Really it should be able to register as a fallback responder, but I don't know if tcp.im supports that. - IM Gopher. Especially with AIM's message size limit, being able to easy give several options in a menu would be peachy. (Insert I Am Weasel joke here.)
Here's another note on tcp.im: at first I was checking if a message was equal to, say, "subscribe", since it didn't have any arguments. It was coming through to Radio as "subscribe " with a trailing space, so I just went back to using beginsWith like the other responders.
