Good, in a way, but will Microsoft change they're licence to allow us to create applications (such as MSN Messenger Robots and 3rd Party MSN Messenger Clients) that will connect to the .NET Messenger Network , because if not, then this is really just for refrence....
Clarification
So if i'm right, Microsoft is releasing MSN Messenger Activity API's for the protocol 
Good, in a way, but will Microsoft change they're licence to allow us to create applications (such as MSN Messenger Robots and 3rd Party MSN Messenger Clients) that will connect to the .NET Messenger Network , because if not, then this is really just for refrence....
Good, in a way, but will Microsoft change they're licence to allow us to create applications (such as MSN Messenger Robots and 3rd Party MSN Messenger Clients) that will connect to the .NET Messenger Network , because if not, then this is really just for refrence....

Clarification
Pedro Pinto
Yes, I understand that, but like Jonathan said the idea is to allow more 3rd party applications and as quote Mess.be:
Hatem Rabie
Well, yes, but you could remake bot2k3 as an activity :)
Not seeing that issue with IE here..
PPrabhu.NET
Well, I think the idea is they don't want people re-doing what's already in Messenger. Since the API does allow receiving/sending IMs, files et al, I think they want you to use that instead, not just because they don't want you treading on their own turf, but because it keeps user experience consistant (yadda yadda yadda).
I think there's still plenty of ideas whch aren't covered under these restrictions, although to be fair, I wish some of them were more relaxed (I'd love to make a "doodle pad"). Although if I'm guessing, I think we'll see people do games for the most part though.
Jim_Martin
You can use flash for psuedo-inking.You really have to think web-wise for these activities and be creative.
A_Y
OT: Working fine in IE, i'm importing a CD. Also works fine in Firefox and Opera, dont see your problem.
captain_semtex
Well I think encryption would be fine, given that translation is an example in the documentation. Photo Sharing is probably out of the question -if- it works like the current Photo Swap (aka, some sort of flickr viewer/sharer would probably be fine -- wow I'm giving out my ideas). I'm sure more clarification is forthcoming.
I believe the source mention was to validate needs for specific permissions; I believe this is mainly for flash (or other ActiveX-enabled activities). However, I think they're trying to avoid someone throwing in something malicious into something that appears to be legitimate.
For the actual contest anyway, Flash/ActiveX isn't allowed, so that's not an issue there :)
emari
Agreed then
zhaounknown
The other confusing part is, for these questions, how does a person find out before spending the time to make it and then submit it For example, lets say an encrypted widget or logging... what is the turn around on even getting an answer - as it appears you have to make it and then hope for the best.
Finally, it appears to be rather open ended when looking at what will be needed when you finish the app. For example, it states in the SDK docs that you may be required to submit your source code... That is a death knell for many things. I have already heard the conspiracy theorists, not so incorrectly suggest, that by doing so an app can be submitted, rejected for the sole purpose of taking the idea and putting it into the actual app. In other words a more formalized way of getting ideas, code etc. to take. While I am not saying this is true at all, what I do suggest is the way the system is structured makes it certainly appear that it could be and is a PR snafu. Imagine if Windows development was run this way.
Ben
Andy_1979
My question is what sort of apps like add-ons are you even allowed to make Looking at the documentation - take a look at the restrictions:
Activity API Restrictions
Your MSN Messenger Activity must not contain any functionality that would normally be controlled by the MSN Messenger client. This includes (but is not limited to) the following items:
- Instant messaging
- File transfer (for example, digital photos or sound files)
- Audio conversation capabilities
- Control of a Web camera or use of a video conferencing session
- Application sharing
- Creation of a white board space
That is take directly from the help file. Moreoever, you have to submit any application so that the Messenger group can enable it... how long will that take The most important though are the restrictions listed above - what sort of app are you allowed to make It would seem to me most of the add-ons you see out there are out of the running. Some others I have talked to also seem to agree. What do you thinkBen
Brian Cordell
Elver
Definitely an idea, and it's great they are opening up MSN Messenger development :)
As for BOT2K3, no it will stay the way it is, but this will open up some opportunities for us (new ideas, etc). As for ink etc, it's possible -- I've already looked into things like it for MjSN. It's a matter of time rather than intelligence :P
I bet you this API will be popular ;)
Jim Galasyn
To be fair, I really wouldn't expect them to and I like it the way it is now. However, it is a possibility and not to mention an idea for other people
.
Zim
Yes, although the protocol itself you don't have to worry about, which is part of the coolness of this.
Yes, the idea is to allow more third-party apps.
T. McClung
Licensing a robot will still cost hundreds/thousands of dolors a month. Too expensive for almost anyone. I wish MS would do something about that.
OT:
This whole edit box thing stinks. Just typing makes IE garble up 99% of my CPU. What happened to the nice and light weight edit boxes with regular BBCode