I'm getting: <presence from="[EMAIL PROTECTED]" to="[EMAIL PROTECTED]/Psi" > <status>User's status message</status> <x xmlns="vcard-temp:x:update"> <photo>94f6af1054b14b953f05cebdddb669fbf7abcdf6</photo> <nickname>Display Name</nickname> </x> </presence>
although I havn't done a CVS update in quite a while :-) On 19/08/05, James Bunton <[EMAIL PROTECTED]> wrote: > The XML snippet you've pasted there is correct :) > <show/> contains your status, and <status/> contains your status > message. Kinda weird, but that's how it is. > > --- > > James > > > > On 19/08/2005, at 7:39 AM, Nathan Palmer wrote: > > > I'm getting some very strange behavior when using PyMSN-t. I'm not > > getting this with PyAIM-t. When I get presence information it seems > > like the <show> and <status> fields are swapped. Here is a dump from > > Pandion with the actual usernames replaced. But you should get the > > idea. > > > > <presence to="[EMAIL PROTECTED]" > > from="[EMAIL PROTECTED]"> > > <show>away</show> > > <status>Display Name</status> > > </presence> > > > > Now I don't know if this is being caused by PyMSN or somehow my jabber > > server (Jive Messenger) is causing it. Has anyone encountered this? > > Can anyone tell me where in the source of PyMSN it's composing the > > message to the jabber server with the presence information? > > > > Nathan > > > > _______________________________________________ > > 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 > -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/ From [EMAIL PROTECTED] Fri Aug 19 12:28:53 2005 From: [EMAIL PROTECTED] (Etienne LAVANANT) Date: Fri Aug 19 12:29:02 2005 Subject: [py-transports] Strange Status behavior with PyMSN-t In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Selon Norman Rasmussen <[EMAIL PROTECTED]>: > I'm getting: > > <presence from="[EMAIL PROTECTED]" to="[EMAIL PROTECTED]/Psi" > > <status>User's status message</status> > <x xmlns="vcard-temp:x:update"> > <photo>94f6af1054b14b953f05cebdddb669fbf7abcdf6</photo> > <nickname>Display Name</nickname> > </x> > </presence> > The <nickname /> is not mentioned in the JEP-0153 but the rest of the presence stanza seems to be ok. The <show /> element is optional, no <show /> element means "online and available" (cf RFC 3921 2.2.2.1). -- Etienne ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. From [EMAIL PROTECTED] Fri Aug 19 12:40:54 2005 From: [EMAIL PROTECTED] (Matthias Wimmer) Date: Fri Aug 19 12:41:02 2005 Subject: [py-transports] Strange Status behavior with PyMSN-t In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Hi Etienne! Etienne LAVANANT wrote: >><presence from="[EMAIL PROTECTED]" to="[EMAIL PROTECTED]/Psi" > >><status>User's status message</status> >><x xmlns="vcard-temp:x:update"> >><photo>94f6af1054b14b953f05cebdddb669fbf7abcdf6</photo> >><nickname>Display Name</nickname> >></x> >></presence> >> >> >> >The <nickname /> is not mentioned in the JEP-0153 but the rest of the presence >stanza seems to be ok. The <show /> element is optional, no <show /> element >means "online and available" (cf RFC 3921 2.2.2.1). > > But the <nickname/> element is scoped in another namespace (vcard-temp:x:update) because it is contained in the <x/> element. As it is not in the jabber:client namespace, I'd say this is okay with the RFCs. I just don't like the used namespace, but that's another thing. Matthias From [EMAIL PROTECTED] Fri Aug 19 12:47:32 2005 From: [EMAIL PROTECTED] (Etienne LAVANANT) Date: Fri Aug 19 12:47:35 2005 Subject: [py-transports] Strange Status behavior with PyMSN-t In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Selon Matthias Wimmer <[EMAIL PROTECTED]>: > Hi Etienne! > > Etienne LAVANANT wrote: > > >><presence from="[EMAIL PROTECTED]" to="[EMAIL PROTECTED]/Psi" > > >><status>User's status message</status> > >><x xmlns="vcard-temp:x:update"> > >><photo>94f6af1054b14b953f05cebdddb669fbf7abcdf6</photo> > >><nickname>Display Name</nickname> > >></x> > >></presence> > >> > >> > >> > >The <nickname /> is not mentioned in the JEP-0153 but the rest of the > presence > >stanza seems to be ok. The <show /> element is optional, no <show /> element > >means "online and available" (cf RFC 3921 2.2.2.1). > > > > > But the <nickname/> element is scoped in another namespace > (vcard-temp:x:update) because it is contained in the <x/> element. That's why I talked about JEP-0153, it is the JEP which defines the namespace vcard-temp:x:update. Sorry you don't like the namespace but now that iChat and several other client support this JEP, it will be hard to change it ;-) -- Etienne ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. From [EMAIL PROTECTED] Fri Aug 19 13:08:59 2005 From: [EMAIL PROTECTED] (Matthias Wimmer) Date: Fri Aug 19 13:09:03 2005 Subject: [py-transports] Strange Status behavior with PyMSN-t In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Hi Etienne! Sorry ... I completely misread your posting ... (the namespace choice was just a personal remark, I don't care that much about that). Matthias Etienne LAVANANT wrote: >That's why I talked about JEP-0153, it is the JEP which defines the namespace >vcard-temp:x:update. Sorry you don't like the namespace but now that iChat and >several other client support this JEP, it will be hard to change it ;-) > > > From [EMAIL PROTECTED] Fri Aug 19 14:44:59 2005 From: [EMAIL PROTECTED] (Nathan Palmer) Date: Fri Aug 19 14:45:02 2005 Subject: [py-transports] Strange Status behavior with PyMSN-t Message-ID: <[EMAIL PROTECTED]> Ok. I believe you. Kind of strange, but that's ok. I actually found out what the problem was. Something in the configuration of Pandion was doing it. Once I removed my profile from C:\Documents and Settings\username\Application Data\Pandion\Profiles then the names and status lines came up perfectly. Thanks for the responses though everyone. Nathan -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of James Bunton Sent: Thursday, August 18, 2005 5:27 PM To: PyAIM-t/PyICQ-t/PyMSN-t Discussion Subject: Re: [py-transports] Strange Status behavior with PyMSN-t The XML snippet you've pasted there is correct :) <show/> contains your status, and <status/> contains your status message. Kinda weird, but that's how it is. --- James On 19/08/2005, at 7:39 AM, Nathan Palmer wrote: > I'm getting some very strange behavior when using PyMSN-t. I'm not > getting this with PyAIM-t. When I get presence information it seems > like the <show> and <status> fields are swapped. Here is a dump from > Pandion with the actual usernames replaced. But you should get the > idea. > > <presence to="[EMAIL PROTECTED]" > from="[EMAIL PROTECTED]"> > ? <show>away</show> > ? <status>Display Name</status> > </presence> > > Now I don't know if this is being caused by PyMSN or somehow my jabber > server (Jive Messenger) is causing it. Has anyone encountered this? > Can anyone tell me where in the source of PyMSN it's composing the > message to the jabber server with the presence information? > > Nathan > > _______________________________________________ > 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 From [EMAIL PROTECTED] Sat Aug 20 10:46:39 2005 From: [EMAIL PROTECTED] (James Bunton) Date: Sat Aug 20 10:46:48 2005 Subject: [py-transports] Small PyAIMt patch In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> On 17/08/2005, at 9:53 PM, Daniel Henninger wrote: > I'm responding to like four separate messages here instead of > responding to them all individually. =D > >>> What clients support ad-hoc commands at this point? I tried with my >>> "latest versions of Psi" and I was able to browse down until I saw >>> PyAIMt Commands, but at that point I was left with sitting there >>> going. "oookay, now what?" =) Is the problem that the version of >>> Psi I am using doesn't support ad-hoc or do I just not know what I'm >>> doing? >>> >> >> Yeah, I don't know of any clients other than tkabber (I think) which >> support it. Basic support shouldn't be too difficult though. >> http://spike.ulyssis.org/psi/ >> That's Remko's Psi page. It has some patches for Psi to support >> ad-hoc commands. >> > > So is the concept here similar to how one might have implemented > something where you "talk" to the gateway itself? Like I might IM > aim.jabber.vorpalcloud.org and say "help" and "restart" or something, > but instead you are sending structured stanza directly to the gateway? > I think part of my confusion is that I thought that ad-hoc was > directly related to disco in some way. Doesn't sound like that's > true? It sort of is. You're probably best off reading the JEP itself. It's quite straightforward if you just stick to the single page commands. It can get quite complicated with back/forward buttons, etc, but I haven't implemented any of that. > > So basically it's sounding like, judging from Norman's response, that > what I'm looking for is basically to "right click" on the gateway to > send ad-hoc commands. Plus, I do have some Windows boxes, I'll try > out the pre-build he mentioned and see what I can do! > >> >> >> >>> As for storage, I hadn't actually thought about SQLite but that >>> doesn't sound like a bad idea at all. And it would "translate >>> easily" into a mysql or postgres or sybase or whatever you might >>> have database layout as well. Question is, are there good SQLite >>> implementations for Python? I see a couple mentioned on google that >>> lead to empty pages. lol Not really what I would call functional. >>> So far my experience with SQLite has been favorable though. Have >>> others had any feelings about it? >>> >>> Also, assuming it's an extension, do we want to throw -more- >>> requirements at the Py's? (I'm not saying the answer to that is no >>> ;) ) >>> >> >> Yeah, the extension is in C so it would be another requirement. >> However there are Debian and Mandrake packages in the standard >> repository for it, so it would actually be easier to install than >> pycrypto, etc (needed for PyMSNt). >> >> It's still a much easier requirement than asking for a mysql or >> postgresql DB installation. We could keep the spool files as default >> too. > > Looks like Pedro likes the concept of the hashed spool you mention > below a lot better anyway. I have been asked to implement MySQL > before, so I'm definitely going to offer that as an option regardless, > but it's sounding like the hashed spool is the way to go for default. > The primary thing I am aiming to change in mine is the structure of > said spool files to accomodate user preferences and stuff like that. > If I "just add it" to the spool then aim-transport may get highly > confused if you switch back to it. > > I guess one question is, do you want SQLite as an option at all? Like > let others choose if they'd like it? I'm a fan of options, but if it > would be a tremendous amount of work then... yeah. > > What I'm thinking about is a new xdb.py with "hooks" for various > information requests and xdb.py would hand off to probably a > xdb/mysql.py or xdb/file.py (whichever you chose) to do the real work. > Any objections? Sounds like a good idea :) I've got hashed directories implemented in CVS for PyMSNt right now, but other DB backends would be useful I'm sure. > >> >> >> >>> *chuckle* If we do this, I think we should agree to either let me >>> or you do it, and not both be working on it at the same time with >>> different implementations. ;D I'm sure you've got plenty to do! >>> I'd love to work on it if you don't mind. I'll chat with you >>> directly a bit about what your requirements/feelings are about the >>> layout and such. However, if you are hell bent on doing it (or have >>> already started lol) I'll find other things to work on. >>> >> >> Sure, you go for it :) >> >> In the mean time I'll just split the spool files up into a hashed >> directory structure to speed things up a bit. > > =) I'll work on the 'real database' side of things and the ability to > choose what format you want... and some conversion scripts... and > merge in what you do into something that's hopefully cool. > > BTW, I haven't played much with your statistics gatherer stuff, but I > am probably going to adjust my own statistics that are used in the web > interface to use yours instead so they are both pulling and showing > the same stats. > >> >> >> >>> >>> Btw, is the avatar support done or are aspects of it still not >>> working? Last I had heard it was working one way and not the other. >>> And I noticed you are supporting only PNG . . . Is that what jabber >>> supports and only what jabber supports or did you just choose to >>> only do PNG? I haven't the slightest idea what AIM hands you yet. >>> >> >> The transport tries to use the python image libraries to support any >> format on the Jabber side, if you don't have it installed then you're >> stuck with PNG. Strangely Psi doesn't even let me select non-PNG >> images so I haven't tested this yet. >> Doubly strangely on Microsoft's part, they had the good sense to >> restrict the avatar format to only PNG. Which makes things easy :) >> (They could've easily used something crazy like that ink format they >> have). > > > Oh! Ok, I didn't realize it was just a "because you don't have the > imaging library installed . . . " thing. =) Ok, that makes things > much easier. :) > Daniel > > >> >> >> >> >>> >>> Sorry to bombard you with questions and such, but being on opposite >>> ends of the world doesn't lend well to chatting live. ;D >>> >> >> No worries :) >> >> >> >> >>> >>> Daniel >>> >>> -- >>> "The most addictive drug in the world is music." >>> - The Lost Boyz >>> >>> >>> >>> On Aug 16, 2005, at 7:57 PM, James Bunton wrote: >>> >>> >>>> Ad-hoc commands are pretty easy. At least what I've implemented of >>>> them. >>>> They have the potential to work just like form-based web >>>> applications, with multiple pages, back/forward buttons. However >>>> I'm just using them like this. >>>> >>>> User queries service for list of commands >>>> List of commands is received >>>> User triggers a command >>>> Result of command is returned >>>> >>>> >>>> For the file storage, I've been wanting to do something like that >>>> for a while. I've heard that having 10000+ files in the one >>>> directory makes things slow :) >>>> What do you reckon? Something like SQLite? Relatively easy to >>>> setup, but still more than powerful enough for us I would think. >>>> >>>> --- >>>> >>>> James >>>> >>>> >>>> On 17/08/2005, at 1:11 AM, Daniel Henninger wrote: >>>> >>>> >>>> >>>>> There's actually quite a few things I'd like to make into >>>>> user-specific >>>>> options. I don't know enough about ad-hoc commands yet, so I'm >>>>> hoping >>>>> that after I implement James's changes, that I can see how they >>>>> work and >>>>> play with them a tad. >>>>> >>>>> BTW, I'm kicking around the idea of, instead of making my spool >>>>> file 100% >>>>> compatible with aim-transport (same goes for PyICQt and JIT), >>>>> offering >>>>> some back and forth conversion scripts. Would folk have a real >>>>> objection >>>>> to having the spools be incompatible? If so, I can come up with >>>>> something >>>>> else. ;) >>>>> >>>>> Daniel >>>>> >>>>> -- >>>>> "The most addictive drug in the world is music." >>>>> - The Lost Boyz >>>>> >>>>> >>>>> >>>>>> What about making this a per-user configurable option? (via >>>>>> ad-hoc or >>>>>> register - ad-hoc preferred) >>>>>> >>>>>> On 16/08/05, James Bunton <[EMAIL PROTECTED]> wrote: >>>>>> >>>>>> >>>>>>> Nice idea, unfortunately it would also mean that anybody who'd >>>>>>> been >>>>>>> logged off the gateway at the time would become unexpectedly >>>>>>> logged in. >>>>>>> Depending on the user, and how often the restarts were, that >>>>>>> could get >>>>>>> annoying. >>>>>>> >>>>>>> I think I'll implement it as an ad-hoc command, so the >>>>>>> administrator >>>>>>> can trigger it manually if they wish. >>>>>>> >>>>>>> Thanks :) >>>>>>> >>>>>>> --- >>>>>>> >>>>>>> James >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 15/08/2005, at 1:47 AM, Robert B Quattlebaum, Jr. wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>>> The following patch will cause PyAIMt to send out "probe" >>>>>>>> presence >>>>>>>> packets to everyone registered to it when it starts up. This >>>>>>>> makes it >>>>>>>> so that anyone who is currently logged in willautomagicly be >>>>>>>> brought >>>>>>>> back online in the transport. This patch should also be able to >>>>>>>> be >>>>>>>> applied to PyMSNt with no >>>>>>>> problems.http://www.deepdarc.com/PyAIMt-darco-invite.dif >>>>>>>> >>>>>>>> This is a very simple and useful feature. I have implemented it >>>>>>>> on >>>>>>>> every transport on my server. >>>>>>>> >>>>>>>> __________________ >>>>>>>> Robert Quattlebaum >>>>>>>> Mobile: +1(425)443-6785 >>>>>>>> eMail: [EMAIL PROTECTED] >>>>>>>> Jabber: [EMAIL PROTECTED] >>>>>>>> MSN: [EMAIL PROTECTED] >>>>>>>> AIM: rquat2 >>>>>>>> yahoo: robert_quattlebaum >>>>>>>> ICQ: 1454810 >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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 >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> - 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 >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>>> >>>> >>>> >>>> >>> >>> _______________________________________________ >>> 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 >> >> >> > > _______________________________________________ > py-transports mailing list > py-transports@blathersource.org > http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports >
