Posted by guest at 2005-07-24 20:30:26
Sending message from one PyICQt's user to another via loop not
via aol server. See
http://modevia.com/pipermail/py-transports/2005-February/000204.html
Posted by maxbritov at 2005-08-01 07:54:09
my +1 fot this feature
Posted by jadestorm at 2005-08-01 11:50:50
*chuckle* alright this should be easy actually James already did this with
PyMSN, I just need to port the code over.
Posted by motienko at 2005-08-04 06:24:02
Maybe it's possible to forward not only <message> but some <iq> via
loop (like in JIT), so users will be able to user jabber features like file
transfer and so such.
Posted by jadestorm at 2005-08-08 11:48:40
Oh yeah, good point. If I'm going to NOT send them through the real ICQ
servers, I need to completely emulate the behavior they would normally see.
Hrm...
Posted by Z_God at 2005-09-11 00:18:00
Note that PyMSN-t does not do this via a loop, since for PyMSN-t the detection
also works when two users are on a different server and using a different MSN
transport.
Posted by jadestorm at 2005-12-31 17:36:24
Z_God, how does PyMSN go about doing this across multiple servers?
Posted by legoscia at 2006-01-19 01:25:51
PyMSN adds a header "JabberID" when sending client capabilites; see
sendClientCaps and gotMessage in msnw.py. Could something similar be done for
ICQ?
Posted by motienko at 2006-02-11 07:13:33
Adding jid information is possible, but it can be a key for AOL for banning
pyicqt users.
Posted by motienko at 2006-02-11 07:15:48
P.S. I think it's two feature requests: first is looping messages inside
transport, second is an announce of JID to other transports via OSCAR.
Posted by jadestorm at 2006-02-11 12:53:03
Well, I'm not real worried about adding the extra info. I mean it's not like
Trillian didn't add it's own secure im stuff as well. =)