[API] Windows Messenger JavaScript API

[Adam Nemeth]

Hi,
Just a quick answer, seems everyone got crazy here today ..erggh.
yesterday.. (but today also). Surely spring comes or I don't know...

This is also a respond to Fabio's letters...

On Mon, Mar 3, 2008 at 1:45 PM, Pedro Melo <melo at simplicidade.org> wrote:
>
> >>  I'm trying to gather all data about security approaches of these
> >>  experiments by other communities. I think will need some external
> >>  input to validate our security model.
> >
>

Could you look at the MSN examples with an eye of security too?

(I'm unfortunately sure that this will be a force which will affect the
market)

Besides, I still strongly recommend to review the security technologies
behind widget systems llike opensocial gadgets, UWA and others.

They will also help us to define a manifesto:a  simple XML file which
contains the first state of the HTML body too.

(And of course, we don't want to make applications able to send messages
out-of-context, but what is out of context and what isn't  is not as an easy
question maybe, like: "Hi, XYZ user who you don't know just beat your world
record highscore! Maybe you could gain your position back, or maybe not?" -
a message from a typoical facebook app.)


>
> > Besides msn, sameplace and meboo other relevant communities?
>
> Yes, and the kool appz OpenSocial and what not. We might want to have
> a "profile" or "mode" in which our Xiclets become a OpenSocial
> container.
>

Maybe you tried to say application instead of container? I mean, Xiclets are
(or can be) real-time social gadgets, although surely it's in a container
environment (the social graph is your roster).

Remember that your IM client is still a social environment, and those are
well-hyped in the last 3-4 years, and maybe they'll stay with us longer.

That's why I may find it reasonable sometimes to allow roster access, but
certainly not without a lot of careful analysis.

Sure, there're still two options to think of: html inside jabber and jabber
inside html to be short.


Other relevant communities are gaming communities like kongregate (runs on
openfire!), or chesspark, workgroup/ enterprise /collaborative
 applications, like Zimbra/Thinkfree/Thinkature/Conceptshare and others,
there's a LOT!

>
> > btw: we need a wiki where to put these considerations once
> > discussed on the ML
>
> What about a geek aproach? A shared subversion repo where you can
> write those docs?
>
> It would be nice because we could also commit examples ...
>
> But a wiki is also fine. I suggest wiki.jabber.org.
>

+1 for wiki.jabber.org

>
>
One last suggestion: Could we PLEASE forget the mere existence of
publish-subscribe at least for version 1.0? It isn't deployed on GTalk
servers, which gives a large amount of the actually online userbase of the
jabber network, and I still haven't seen anything useful in production on
top of it yet.

3 AM, heading to bed, sorry for the very late and very short answer... :(
-- 
Aadaam <aadaam at gmail.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.jabber.org/pipermail/api/attachments/20080304/f1872aa3/attachment.htm