James & Daniel:
Well i know most of all client doesn't support the way
it handles this..
but if you give the option to old jabberd users to path the transport you
are giving more options to jabber developers..
for me it will be AMAZING to have the pymsn patched because i dont have to
suscribe to presence of every contact i have on my msn.roster.
Right now the client that im doing takes between 2-4 minnutes to have their
msn roster instead of having it as fast as yahoo (patched)
Thanks and i hope you get my point.
Fran
----- Original Message -----
From: "James Bunton" <[EMAIL PROTECTED]>
To: "PyAIM-t/PyICQ-t/PyMSN-t Discussion" <[email protected]>
Sent: Monday, April 24, 2006 9:23 PM
Subject: Re: [py-transports] PyMSNt & pyicq
> On 25/04/2006, at 12:13 AM, Daniel Henninger wrote:
>> *blink* James? Your thoughts on this? If I'm reading this right,
>> yahoo-transport is sending a "subscribed" presence to the client, and
>> subscribing itself to all of the user's presences. That doesn't make a
>> lot of sense to me. If it's actually ending up effecting the end user's
>> roster, my understanding of 'how things work' seems to dictate that the
>> jabber server should say "uh... no".
>
> Looks like some custom protocol similar to what I'm using with
> roster-subsync. Except that this takes advantage of a bug in Jabberd 1.4.2
> and old versions of Jabberd2. Basically if somebody sent you a presence
> type="subscribed" they would get pushed onto your roster without your
> authorisation. That's been fixed in recent versions (thankfully). Modern
> Jabber servers should ignore these packets.
>
>
>> Francisco, what Jabber server are you running? In the past, when I've
>> tried to "set" like that, I get flat out denied. And like I said, the
>> yahoo transport bugs me for everyone in my contact list (just like
>> PyICQ). I wonder if your Jabber server has special handling for this?
>> WEIRD! =)
>>
>>> Is some kind of way of avoiding acept every user .. (auto-import)
>>> contacts ? on pymsn and pyicq ?
>>
>> See my earlier post. =D
>>
>> I'd love to see the ability to kill the bazillion auth requests... but
>> just as far as I know we don't have a supported way of doing that. (aside
>> from that roster item exchange hooha, and I couldn't get that to work
>> with the clients I tested with) If what you are showing me above works
>> with some Jabber servers, then I'm certainly willing to add it in for
>> those servers to take advantage of. (or at least try, if it's reasonable
>> ;D )
>>
>> Daniel
>
> Yeah, I don't think any clients have support for the roster exchange JEP.
>
> ---
>
> James
>
> _______________________________________________
> py-transports mailing list
> [email protected]
> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
