Ok, now it is working. I probably started the transport before moving the
folder. Thank you for your answer.
Regards
Jorge
El Lun 03 Oct 2005 17:42, James Bunton escribi?:
> If you do an update in place then the transport will migrate your spool
> directory automatically.
> You must have installed a fresh copy and started it before moving your
> spool directory over?
>
> If you want to force another migrate, edit
> spool/msn.host.com/notes_to_myself
> Remove the line, doHashDirUpgrade
> That will cause it to redo the migrate when you next start the
> transport.
>
> ---
>
> James
>
> On 04/10/2005, at 6:23 AM, Jorge Merlino wrote:
> > Well that didn't worked :(
> > What I did was to copy the msn.xxxx folder from my previous
> > instalation to the
> > new one, and when I tried to log in the transport told me that I was
> > not
> > registered. I registered again and the it created my xml file inside a
> > new
> > subfolder.
> > Did I do something wrong?
> >
> > Regards
> > Jorge
> >
> > El Lun 03 Oct 2005 17:13, Norman Rasmussen escribi?:
> >> the transport should automatically upgrade your spool files for you.
> >>
> >> On 03/10/05, Jorge Merlino <[EMAIL PROTECTED]> wrote:
> >>> I have tried to update my msn transport today but I found that the
> >>> spool
> >>> files now are different. How did you do to update them to the new
> >>> version?
> >>>
> >>> Regards
> >>> Jorge
> >>>
> >>> El Lun 03 Oct 2005 08:02, Oscar Hellstr?m escribi?:
> >>>> Upgraded my (nondev) msn transport just this minute and everything
> >>>> seems to have went very smooth, including transformation of the
> >>>> spool
> >>>> files and such. Am I right to assume I can just do a cvs update if
> >>>> there will be any 0.10.x?
> >>>>
> >>>> How will things be in the feature, will file transfers be the focus
> >>>> of
> >>>> 0.11?
> >
> > _______________________________________________
> > py-transports mailing list
> > py-transports@blathersource.org
> > http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
>
> _______________________________________________
> py-transports mailing list
> py-transports@blathersource.org
> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
--
Ing. Jorge Merlino
Teledata Comunicaciones
Canelones 2101 - Montevideo - Uruguay
[EMAIL PROTECTED]
From [EMAIL PROTECTED] Tue Oct 4 12:56:21 2005
From: [EMAIL PROTECTED] (Nikos Kouremenos)
Date: Tue Oct 4 12:56:23 2005
Subject: [py-transports] PyMSNt (and maybe rest of Py company) does badly
MUC presences and invitations
Message-ID: <[EMAIL PROTECTED]>
<presence from='[EMAIL PROTECTED]/[EMAIL PROTECTED]'
to='[EMAIL PROTECTED]'><x
xmlns='vcard-temp:x:update'/></presence><presence
from='[EMAIL PROTECTED]/[EMAIL PROTECTED]'
to='[EMAIL PROTECTED]'><x
xmlns='vcard-temp:x:update'/></presence>
<message from='[EMAIL PROTECTED]'
to='[EMAIL PROTECTED]'><body>You have been invited into a
groupchat on the legacy service. You must join this room to switch
into groupchat mode [EMAIL PROTECTED]
If you do not join this room you will not be able to participate in
the groupchat, but you will still appear to have joined it to contacts
on the MSN service.</body><x jid='[EMAIL PROTECTED]'
xmlns='jabber:x:conference'/></message><message
to='[EMAIL PROTECTED]' type='chat' id='290'
from='[EMAIL PROTECTED]/Gajim'><composing
xmlns='http://jabber.org/protocol/chatstates'/></message>
that is a NOT RECOMMENDED invitation. where is <invite> etc..
I know MUC JEP allows everything, but it's wrong to expect that
clients will do the NOT RECOMMENDED stanzas
more on http://www.jabber.org/jeps/jep-0045.html#invite
and that is not a valid MUC presence!:
<presence from='[EMAIL PROTECTED]/nkour'
to='[EMAIL PROTECTED]'><x
xmlns='vcard-temp:x:update'/></presence>
more on http://www.jabber.org/jeps/jep-0045.html#enter-pres
and also vcard-temp:x:update should not be send in MUC too.
Congratulations on the new release, and please fix that for your next release
PS. If rest Py* suffer, please guys fix those too for your next
release. It's time for Jabber transports to rock!
--
Nikos Kouremenos | Jabber ID: [EMAIL PROTECTED] | http://members.hellug.gr/nkour
From [EMAIL PROTECTED] Tue Oct 4 14:27:41 2005
From: [EMAIL PROTECTED] (Trejkaz)
Date: Tue Oct 4 14:27:52 2005
Subject: [py-transports] PyMSNt (and maybe rest of Py company) does badly
MUC presences and invitations
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
On Tue, 4 Oct 2005 22:56, Nikos Kouremenos wrote:
> that is a NOT RECOMMENDED invitation. where is <invite> etc..
> I know MUC JEP allows everything, but it's wrong to expect that
> clients will do the NOT RECOMMENDED stanzas
>
> more on http://www.jabber.org/jeps/jep-0045.html#invite
Actually, if you'll read the service discovery information for the transport
you'll see that PyMSNt doesn't even advertise as MUC capable. If it doesn't
support MUC at all, it goes without saying that it doesn't have to follow the
JEP.
> and that is not a valid MUC presence!:
> <presence from='[EMAIL PROTECTED]/nkour'
> to='[EMAIL PROTECTED]'><x
> xmlns='vcard-temp:x:update'/></presence>
Why not?
> and also vcard-temp:x:update should not be send in MUC too.
Wouldn't you lose avatars over groupchat if you took that out? How else are
people going to receive notifications until pubsub rocks up?
TX
--
Email: Trejkaz Xaoza <[EMAIL PROTECTED]>
Web site: http://trypticon.org/
Jabber ID: [EMAIL PROTECTED]
GPG Fingerprint: 9EEB 97D7 8F7B 7977 F39F A62C B8C7 BC8B 037E EA73
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :
http://modevia.com/pipermail/py-transports/attachments/20051005/3cf4c9d8/attachment.pgp
From [EMAIL PROTECTED] Tue Oct 4 14:43:23 2005
From: [EMAIL PROTECTED] (Norman Rasmussen)
Date: Tue Oct 4 14:43:26 2005
Subject: [py-transports] PyMSNt (and maybe rest of Py company) does badly
MUC presences and invitations
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
On 04/10/05, Trejkaz <[EMAIL PROTECTED]> wrote:
> On Tue, 4 Oct 2005 22:56, Nikos Kouremenos wrote:
> > and that is not a valid MUC presence!:
> > <presence from='[EMAIL PROTECTED]/nkour'
> > to='[EMAIL PROTECTED]'><x
> > xmlns='vcard-temp:x:update'/></presence>
>
> Why not?
because MUC requires that the invite goes from invitor to room to
invitee. And the room does the invite on behalf of the invitor.
--
- Norman Rasmussen
- Email: [EMAIL PROTECTED]
- Home page: http://norman.rasmussen.co.za/
From [EMAIL PROTECTED] Tue Oct 4 14:43:42 2005
From: [EMAIL PROTECTED] (Andreas van Cranenburgh)
Date: Tue Oct 4 14:43:49 2005
Subject: [py-transports] PyMSNt (and maybe rest of Py company) does badly
MUC presences and invitations
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
On Wed, Oct 05, 2005 at 12:27:41AM +1000, Trejkaz wrote:
> On Tue, 4 Oct 2005 22:56, Nikos Kouremenos wrote:
> > that is a NOT RECOMMENDED invitation. where is <invite> etc..
> > I know MUC JEP allows everything, but it's wrong to expect that
> > clients will do the NOT RECOMMENDED stanzas
> >
> > more on http://www.jabber.org/jeps/jep-0045.html#invite
>
> Actually, if you'll read the service discovery information for the transport
> you'll see that PyMSNt doesn't even advertise as MUC capable. If it doesn't
> support MUC at all, it goes without saying that it doesn't have to follow the
> JEP.
We live in 2005. If the transport doesn't support MUC yet, let's make it
support that ...
--
Andreas [ http://unstable.nl | xmpp:[EMAIL PROTECTED] ]
[ callto:ils.seconix.com/[EMAIL PROTECTED] ]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url :
http://modevia.com/pipermail/py-transports/attachments/20051004/c2180425/attachment.pgp
From [EMAIL PROTECTED] Tue Oct 4 14:49:00 2005
From: [EMAIL PROTECTED] (Andreas van Cranenburgh)
Date: Tue Oct 4 14:49:03 2005
Subject: [py-transports] [patch] JEP-0085 support for PyMSNt
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
On Sun, Sep 25, 2005 at 08:49:30PM +0200, Andreas van Cranenburgh wrote:
> But now the PyAIM transport also includes the patch, with some
> modifications, so maybe that version is already good enough to commit?
>
> I think the 'contact closed conversation window' feature would be very
> nice as a future addition though, mainly because right now it shows
> "contact is paying attention" forever. But then I'd have to dive into
> the python part of the transport. Any hints?
Can you give me an update on this James? Will you commit PyAIMt's
version, which is already in SVN? [1] Or were you waiting for me to
write a new patch, and if so, how would it be different from PyAIMt's
way of doing it?
[1]
http://svn.blathersource.org/diff.php?repname=pyaim-t&path=%2Ftrunk%2Fsrc%2Fjabw.py&rev=147&sc=0
--
Andreas [ http://unstable.nl | xmpp:[EMAIL PROTECTED] ]
[ callto:ils.seconix.com/[EMAIL PROTECTED] ]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url :
http://modevia.com/pipermail/py-transports/attachments/20051004/c0628bf0/attachment.pgp
From [EMAIL PROTECTED] Tue Oct 4 14:51:22 2005
From: [EMAIL PROTECTED] (Norman Rasmussen)
Date: Tue Oct 4 14:51:23 2005
Subject: [py-transports] PyMSNt (and maybe rest of Py company) does badly
MUC presences and invitations
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Hey! James has been sweating his ass off getting avatar's working, and
I thank him for that. (Thanks James!)
There's a road map that needs to be drawn out here:
What's more important: File Transfer (or any sort), or upgrading a
_working_ groupchat to multiuser chat?
Personally I'd rather see FT. It's still the most
'oh-sorry-your-msn-doesn't-do-that' scorn I get from people using the
official client.
P.S. I could be reading Andreas's statement as a volunteer to fix the
MUC part of the transport.
On 04/10/05, Andreas van Cranenburgh <[EMAIL PROTECTED]> wrote:
> On Wed, Oct 05, 2005 at 12:27:41AM +1000, Trejkaz wrote:
> > On Tue, 4 Oct 2005 22:56, Nikos Kouremenos wrote:
> > > that is a NOT RECOMMENDED invitation. where is <invite> etc..
> > > I know MUC JEP allows everything, but it's wrong to expect that
> > > clients will do the NOT RECOMMENDED stanzas
> > >
> > > more on http://www.jabber.org/jeps/jep-0045.html#invite
> >
> > Actually, if you'll read the service discovery information for the transport
> > you'll see that PyMSNt doesn't even advertise as MUC capable. If it doesn't
> > support MUC at all, it goes without saying that it doesn't have to follow
> > the
> > JEP.
>
> We live in 2005. If the transport doesn't support MUC yet, let's make it
> support that ...
>
> --
> Andreas [ http://unstable.nl | xmpp:[EMAIL PROTECTED] ]
> [ callto:ils.seconix.com/[EMAIL PROTECTED] ]
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (GNU/Linux)
>
> iD8DBQFDQpUeAcXr2MrY86MRAtQCAJ0SPAJBgNs6SaYXFOnm6CxHi3pVwwCgpdL9
> PatigODAogP+GiiU1SJvWoE=
> =DMub
> -----END PGP SIGNATURE-----
>
>
> _______________________________________________
> py-transports mailing list
> py-transports@blathersource.org
> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
>
>
>
--
- Norman Rasmussen
- Email: [EMAIL PROTECTED]
- Home page: http://norman.rasmussen.co.za/
From [EMAIL PROTECTED] Tue Oct 4 15:05:43 2005
From: [EMAIL PROTECTED] (Nikos Kouremenos)
Date: Tue Oct 4 15:05:45 2005
Subject: [py-transports] PyMSNt (and maybe rest of Py company) does badly
MUC presences and invitations
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
On 10/4/05, Trejkaz <[EMAIL PROTECTED]> wrote:
the rest have been already answered.
and yes it means PyMSNT now that it has avatars should look at MUC
compatibility and FT. those I think will make it (msn) killer app
after:
<presence>
<x xmlns='vcard-temp:x:update'/>
</presence>
u should send:
either:
<presence>
<x xmlns='vcard-temp:x:update'>
<photo/>
</x>
</presence>
or
<presence from='[EMAIL PROTECTED]/balcony'>
<x xmlns='vcard-temp:x:update'><photo>sha1-hash-of-image</photo></x>
</presence>
you cannot stay in not ready, but JEP can be better. I bug for this Peter
> Wouldn't you lose avatars over groupchat if you took that out? How else are
> people going to receive notifications until pubsub rocks up?
yes it's not good to lose them. We (as in Gajim) had them but then
removed them because of jabberd1 (see
http://trac.gajim.org/ticket/782)
I will try to get Peter's opinion on that
--
Nikos Kouremenos | Jabber ID: [EMAIL PROTECTED] | http://members.hellug.gr/nkour
From [EMAIL PROTECTED] Tue Oct 4 19:57:33 2005
From: [EMAIL PROTECTED] (Andreas van Cranenburgh)
Date: Tue Oct 4 19:57:40 2005
Subject: [py-transports] PyMSNt (and maybe rest of Py company) does badly
MUC presences and invitations
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
On Tue, Oct 04, 2005 at 04:51:22PM +0200, Norman Rasmussen wrote:
> Hey! James has been sweating his ass off getting avatar's working, and
> I thank him for that. (Thanks James!)
>
> There's a road map that needs to be drawn out here:
> What's more important: File Transfer (or any sort), or upgrading a
> _working_ groupchat to multiuser chat?
>
> Personally I'd rather see FT. It's still the most
> 'oh-sorry-your-msn-doesn't-do-that' scorn I get from people using the
> official client.
Ok excuse me, my tone might have been wrong. I totally agree with you,
FT is much more important. And other MSN features too, if they have a
working Jabber counterpart.
--
Andreas [ http://unstable.nl | xmpp:[EMAIL PROTECTED] ]
[ callto:ils.seconix.com/[EMAIL PROTECTED] ]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url :
http://modevia.com/pipermail/py-transports/attachments/20051004/5d7062d7/attachment-0001.pgp
From [EMAIL PROTECTED] Tue Oct 4 20:23:44 2005
From: [EMAIL PROTECTED] (Norman Rasmussen)
Date: Tue Oct 4 20:24:16 2005
Subject: [py-transports] Re: [jdev] PyMSNt 0.10 released! Now with avatars!
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Would it be possible to hack an addition to the transport to handle
sending the word 'stats' to the transport as a message?
I'm thinking hook it in the same place you're currently doing 'end'.
In fact at the same time I think 'end' should become an adhoc command.
(This kinda tends towards that common infrastructure for adhoc
commands -yuck-)
Adhoc is generally nicer, because you can parse it and add it to popup
menus, see what the available list is, etc, but it looks like that
until we get more clients that can handle it, we need a legacy message
mode too :-(
On 04/10/05, Norman Rasmussen <[EMAIL PROTECTED]> wrote:
> you need to use a client that support ad-hoc commands. otherwise you
> could send raw xml like this:
>
> <iq type="set" to="msn.transport" id="randomid">
> <command xmlns="http://jabber.org/protocol/commands"; node="stats" />
> </iq>
>
> On 04/10/05, Nahuel ANGELINETTI <[EMAIL PROTECTED]> wrote:
> > I added myself on the admin list, and then ? what must be done ?
> > send "stats" to the msn transport ?
> >
> >
> > On Tue, 4 Oct 2005 10:55:11 +0200
> > Norman Rasmussen <[EMAIL PROTECTED]> wrote:
> >
> > > set your config --> admins --> jid value(s).
> > >
> > > On 04/10/05, Nahuel ANGELINETTI <[EMAIL PROTECTED]> wrote:
> > > > Hi,
> > > >
> > > > thanks for this new release :)
> > > >
> > > > Juste a question, browsing services, under msn transport it have
> > > > "connect all registered users" and "stats of pymsnt".
> > > > Can we use it ?
> > > > if yes, how ?
> > > >
> > > > Thanks
> > > >
> > > > On Mon, 3 Oct 2005 11:31:10 +1000
> > > > James Bunton <[EMAIL PROTECTED]> wrote:
> > > >
> > > > > Hi everybody.
> > > > >
> > > > > PyMSNt 0.10 has been released and declared stable. Its handling
> > > > > several thousand concurrent users on SAPO
> > > > > (http://messenger.sapo.pt) servers right now.
> > > > >
> > > > > This release brings all sorts of niceties:
> > > > > * Limited ad-hoc commands
> > > > > * More stability
> > > > > * Fixes to contact list handling (this may mean you have to
> > > > > redelete a few contacts as a once-off)
> > > > > * Clustering support (requires an extra component. Join
> > > > > py-transports if you're interested)
> > > > > * MSN7 personal message -> Jabber status, and MSN nick -> Jabber
> > > > > vCard nick
> > > > > * <nickname> tag in presence for willing clients.
> > > > > * And of course, vCard and (limited) JEP-8 avatars!
> > > > >
> > > > > Grab it from: http://msn-transport.jabberstudio.org
> > > > >
> > > > > Have a look at the developer docs to see how to make sure your
> > > > > client works well with the transport.
> > > > > At the moment the user guide isn't fully up to date.
> > > > >
> > > > > As always, please mail me, (or preferably
> > > > > py-transports@blathersource.org) with any bug reports or requests
> > > > > for assistance, or just to let me know its all working :)
> > > > >
> > > > > Enjoy!
> > > > >
> > > > > ---
> > > > >
> > > > > James
> > > > >
> > > >
> > > >
> > > > --
> > > > Nahuel ANGELINETTI
> > > > Jabber/XMPP : [EMAIL PROTECTED]
> > > >
> > >
> > >
> > > --
> > > - Norman Rasmussen
> > > - Email: [EMAIL PROTECTED]
> > > - Home page: http://norman.rasmussen.co.za/
> >
>
>
> --
> - Norman Rasmussen
> - Email: [EMAIL PROTECTED]
> - Home page: http://norman.rasmussen.co.za/
>
--
- Norman Rasmussen
- Email: [EMAIL PROTECTED]
- Home page: http://norman.rasmussen.co.za/
From [EMAIL PROTECTED] Tue Oct 4 21:56:08 2005
From: [EMAIL PROTECTED] (Trejkaz)
Date: Tue Oct 4 21:55:59 2005
Subject: [py-transports] PyMSNt (and maybe rest of Py company) does badly
MUC presences and invitations
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
On Wed, 5 Oct 2005 00:43, Andreas van Cranenburgh wrote:
> We live in 2005. If the transport doesn't support MUC yet, let's make it
> support that ...
Oh, I agree... the small number of features that are actually needed to
support MSN's incredibly limited groupchat support are probably well within
the transport's reach.
But my point was just that any comments regarding non-compliance with any JEP
not advertised in service discovery are void.
TX
--
Email: Trejkaz Xaoza <[EMAIL PROTECTED]>
Web site: http://trypticon.org/
Jabber ID: [EMAIL PROTECTED]
GPG Fingerprint: 9EEB 97D7 8F7B 7977 F39F A62C B8C7 BC8B 037E EA73
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :
http://modevia.com/pipermail/py-transports/attachments/20051005/d72f566c/attachment.pgp
From [EMAIL PROTECTED] Wed Oct 5 10:42:56 2005
From: [EMAIL PROTECTED] (James Bunton)
Date: Wed Oct 5 10:43:12 2005
Subject: [py-transports] Re: [jdev] PyMSNt 0.10 released! Now with avatars!
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Good idea :)
---
James
On 05/10/2005, at 6:23 AM, Norman Rasmussen wrote:
> Would it be possible to hack an addition to the transport to handle
> sending the word 'stats' to the transport as a message?
>
> I'm thinking hook it in the same place you're currently doing 'end'.
> In fact at the same time I think 'end' should become an adhoc command.
> (This kinda tends towards that common infrastructure for adhoc
> commands -yuck-)
>
> Adhoc is generally nicer, because you can parse it and add it to popup
> menus, see what the available list is, etc, but it looks like that
> until we get more clients that can handle it, we need a legacy message
> mode too :-(
>
> On 04/10/05, Norman Rasmussen <[EMAIL PROTECTED]> wrote:
>> you need to use a client that support ad-hoc commands. otherwise you
>> could send raw xml like this:
>>
>> <iq type="set" to="msn.transport" id="randomid">
>> <command xmlns="http://jabber.org/protocol/commands"; node="stats" />
>> </iq>
>>
>> On 04/10/05, Nahuel ANGELINETTI <[EMAIL PROTECTED]> wrote:
>>> I added myself on the admin list, and then ? what must be done ?
>>> send "stats" to the msn transport ?
>>>
>>>
>>> On Tue, 4 Oct 2005 10:55:11 +0200
>>> Norman Rasmussen <[EMAIL PROTECTED]> wrote:
>>>
>>>> set your config --> admins --> jid value(s).
>>>>
>>>> On 04/10/05, Nahuel ANGELINETTI <[EMAIL PROTECTED]> wrote:
>>>>> Hi,
>>>>>
>>>>> thanks for this new release :)
>>>>>
>>>>> Juste a question, browsing services, under msn transport it have
>>>>> "connect all registered users" and "stats of pymsnt".
>>>>> Can we use it ?
>>>>> if yes, how ?
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Mon, 3 Oct 2005 11:31:10 +1000
>>>>> James Bunton <[EMAIL PROTECTED]> wrote:
>>>>>
>>>>>> Hi everybody.
>>>>>>
>>>>>> PyMSNt 0.10 has been released and declared stable. Its handling
>>>>>> several thousand concurrent users on SAPO
>>>>>> (http://messenger.sapo.pt) servers right now.
>>>>>>
>>>>>> This release brings all sorts of niceties:
>>>>>> * Limited ad-hoc commands
>>>>>> * More stability
>>>>>> * Fixes to contact list handling (this may mean you have to
>>>>>> redelete a few contacts as a once-off)
>>>>>> * Clustering support (requires an extra component. Join
>>>>>> py-transports if you're interested)
>>>>>> * MSN7 personal message -> Jabber status, and MSN nick -> Jabber
>>>>>> vCard nick
>>>>>> * <nickname> tag in presence for willing clients.
>>>>>> * And of course, vCard and (limited) JEP-8 avatars!
>>>>>>
>>>>>> Grab it from: http://msn-transport.jabberstudio.org
>>>>>>
>>>>>> Have a look at the developer docs to see how to make sure your
>>>>>> client works well with the transport.
>>>>>> At the moment the user guide isn't fully up to date.
>>>>>>
>>>>>> As always, please mail me, (or preferably
>>>>>> py-transports@blathersource.org) with any bug reports or requests
>>>>>> for assistance, or just to let me know its all working :)
>>>>>>
>>>>>> Enjoy!
>>>>>>
>>>>>> ---
>>>>>>
>>>>>> James
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Nahuel ANGELINETTI
>>>>> Jabber/XMPP : [EMAIL PROTECTED]
>>>>>
>>>>
>>>>
>>>> --
>>>> - Norman Rasmussen
>>>> - Email: [EMAIL PROTECTED]
>>>> - Home page: http://norman.rasmussen.co.za/
>>>
>>
>>
>> --
>> - Norman Rasmussen
>> - Email: [EMAIL PROTECTED]
>> - Home page: http://norman.rasmussen.co.za/
>>
>
>
> --
> - Norman Rasmussen
> - Email: [EMAIL PROTECTED]
> - Home page: http://norman.rasmussen.co.za/
> _______________________________________________
> py-transports mailing list
> py-transports@blathersource.org
> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
>
