On Saturday 29 April 2006 18:30, James Bunton wrote:
> On 26/04/2006, at 1:08 AM, Alexey Nezhdanov wrote:
> > Hello.
> > I have old question in a bit different form.
> > Description:
> > MSN requires users to have auth before sending messages.
> > I.e. I can't just send message to some random user [EMAIL PROTECTED]
> > First I should send <presence type='subscribe'
> > to='[EMAIL PROTECTED]'/>,
> > wait for user to authorise me and send only then.
> > This works not so stable but still usable when used personally.
> > Though when it comes to writing automated program this unreliability
> > becomes a
> > problem.
> > F.e.: I need to write script that will randomly chat with thousands of
> > different MSN contacts (not spim - it will be dialogs for several
> > minutes
> > each). To not clobber jabber's and MSN's rosters I choosed to do the
> > following:
> > 1) send "subscribe"
> > 2) wait for "subscribed"
> > 3) chat
> > 4) remove item from roster
> > That way appeared to be not good because of two problems:
> > a) chatting with same contact lately becomes a problem - it seems that
> > step
> > (4) sets the user as "blocked" but step (1) not removes the block
> > b) Typing notifications _from_ MSN not work. The interesting thing is
> > if we
> > stop script somewhere in step (3) then on next start it sees contact as
> > online and TN starting to work.
> >
> > Question:
> > If there is some recipe to achieve my task?
> > I'l shortly reevaluate:
> > I need the reliable (doh!) way to chat with MSN contact using TNs and
> > not
> > keeping this contact constantly in roster.
> > --
> > Respectfully
> > Alexey Nezhdanov
>
> Can you tell me if applying this patch fixes your problem please?
>
> Whenever a user sends <presence type="subscribe"/> to a contact, it
> will unblock it (if its blocked), and that contact will send you a
> <presence type="subscribe"/> if the contact still has the user on their
> list.
>
> Hope that makes sense. Try it out :)
>
> Wrt the typing notifications. They should work as soon as ordinary
> messages can be exchanged.
> Note that typing notifications are only exchanged after the first
> message has been sent.
Thank you, patch solved problem (a). But the problem (b) still persists
unfortunately.
I'll re-describe it:
two contacts, A(GAIM) and B(pyMSN-t) are online. they already tested problem
(a) several times and it fixed (thank you once again).
Now test for problem (b):
1) contact B sends <presence type='subscribe'/>
2) contact B receives <presence type='subscribed'/> (A is not bugged, contact
of B in the A roster is silently going online)
3) contact B sends message to A, A receives it
4) contact A sends message to B, B receives it
5) goto (3)
If I understand correctly - then after we reached step (5) for first time, TN
should start working. But they works only one way: if contact B typing - GAIM
receives it. If contact A typing - pyMSN-t never issuing TNs onto jabber
network.
Please, take a look at this problem once again
--
Respectfully
Alexey Nezhdanov
From [EMAIL PROTECTED] Mon May 1 11:09:35 2006
From: [EMAIL PROTECTED] (Pedro Melo)
Date: Mon May 1 11:09:54 2006
Subject: [py-transports] pymsnt: very small bug in jabber:iq:version
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Hi,
On Apr 29, 2006, at 8:56 PM, Norman Rasmussen wrote:
> On 4/29/06, Pedro Melo <[EMAIL PROTECTED]> wrote:
>> In reply to a jabber:iq:version, pymsnt replies:
>>
>> <iq from="my_msn_buddy" type="result" id="aae0a"
>> to="[EMAIL PROTECTED]/SAPO" >
>> <query xmlns="jabber:iq:version">
>> <name>Gateway para MSN</name>
>> <version>0.11-dev - SVN r0</version>
>> <os>Python2.3.5 - linux2</os>
>> </query>
>> </iq>
>>
>> The <version>, the SVN release is missing.
>>
>
> It works fine for me.
>
> Is it possible that PyMSNt couldn't find the svn status xml file? Are
> you using .svn or _svn dirs?
Yes, we remove them when we push to production. I was expecting that
the pyMSNt would somehow have that information on the code itself.
Sorry bout that.
> PS: Just a heads up, the Psi devs have removed support for iq:version
> in 0.11 and will only be displaying the client caps details.
I know, i use psi. They are also supporting PEP-based avatars, with
read-only support for JEP-0153, so you should be able to see MSN
avatars in Psi, if you compile the code in the repo. Nice :) ... Psi
is speeding up nicely.
Best regards,
--
HIId: Pedro Melo
SMTP: [EMAIL PROTECTED]
XMPP: [EMAIL PROTECTED]
