January 25, 2010

A few comments after a long hiatus

mail2.im is still up, running, and approaching thirty thousand messages relayed in the year its been up.  Not bad, not bad….  Still a few snags occasionally but mostly we seem to be working.

I’ve noticed the following things:

  1. Our yahoo IM stuff is simply broken.  We connect through Bitlbee, and I think Bitlbee didn’t have Yahoo’s latest protocol changes.  I’d like to use something like Openfire instead when I get to it, hence the delay in fixing this.
  2. The IM clients do bounce a little bit.  Again, I think this is a bitlbee <-> mail2im thing, and will fix with the next upgrade.
  3. The twitter stuff still seems to confuse people.   Mail2im follows you, THEN you follow mail2im (or vice versa), THEN the messages can get relayed to twitter as a direct message.  This isn’t a mail2im thing - this is a Twitter thing.  You cannot send direct messages to people who don’t follow you. PLEASE follow mail2im on Twitter if you want to get direct messages from mail2im.
  4. Occasionally we break decoding an email, but I haven’t seen that for some time now.  If you notice something here, let me know.

Last night, for the first time in a year, the server actually crashed (or was restarted by the hosting people?) so I needed to do a complete restart.  Miraculously, this seemed to harm little and seems to be working.  I’ll keep monitoring to see if we’re staying up and not broken for some nefarious reason.

Thanks for using the product!

Comments (View)
blog comments powered by Disqus