The first problem we encountered is that the response was so huge that the protocol started to mess up and we were getting commands in a different order. Also, MSN has a limit for the allow list, even though it's not a fixed value (like the contact list, limit set at 300). The allow list will start acting weird and returning errors at about 1000 contacts.
Of course we had no idea this would happen when we tried it with our beta testing team that consited of 20 people.
About the typing notification: It's there to prevent the session from being closed if you don't say anything for a few minutes. I put it there because if you were to say something to the bot after a certain idle time, the session would be restarted and the bot would send you the welcome message again. Some people found this very annoying and thought the TypingNotification was a cool workaround.
About people not allowing OM on their lists: Well, it's their coice. If they do not wish to use the service, they can block the bots.
About some messages not being delivered: We are running heavy debugging on both, the bot and the protocol engine. Some messages have gotten lost in the middle. We moved the project to a debugging server too, so that made the bots lose a fair amount of messages.
About the service not being reliable: It's a beta. You don't have to use it if you don't want to. Email being reinvented? We like to call it an alternative to email. Imagine a world without alternatives. Not pretty.
