Yeah, roster-subsync doesn't look like it'll become a JEP any time soon.
JEP-0144, the proposed replacement will work ok, even if it doesn't 
support a few of the situations that will come up.
I'll maintain support for roster-subsync though because clients still 
always need a way to get these contacts. A mass amount of subscription 
requests they have to handle by hand is better than not seeing any 
contacts at all :)

This is documentation of "Roster Item Exchange". No implementation for 
this exists anywhere as far as I know.
http://www.jabber.org/jeps/jep-0144.html

Have a look here for documentation about the extensions to XMPP that 
PyMSNt uses, including roster-subsync.
http://msn-transport.jabberstudio.org/docs/developer.html

And here is the web registration utility. It provides client support 
for roster-subsync. That is, if you use it to do your gateway 
registrations, then you won't have to manually auth all your contacts.

---

James


On 19/07/2005, at 6:26 AM, Daniel Henninger wrote:

> *chuckle*  I still need to catch up with what I've got so far.  I'm not
> really thinking much about brand new features yet until I get some 
> time to
> evaluate what I've currently got and get back in the swing of things.
> That said:
>
>> 1) It seems like official ICQ use unicode in messages, rich text also
>> supported. A topic about native unicode in PyICQt without encoding to
>> local charset, and converting rich text to XHTML-IM (JEP-0071).
>
> Not all of them support unicode, unfortunately.  Some of the older
> clients, or ones based on older clients, get veeerrryy confused when 
> they
> receive unicode.  If it worked across the board, I'd have done
> unicode-only already.  =D
>
>> 2) As you can see miranda-im and sim are able to detect client
>> software and protocol versions, ip address. They properly detect
>> native icq clients, other miranda, libicq2000, centericq, but give no
>> version information on PyICQt (only external ip address of PyICQt
>> host). Does it bug or feature? Also there was some information about
>> dropping by aol oscar protocol prior to 9 version on several
>> icq-related sites.
>
> Feature.  ;D  (well  a feature request anyway)  I'd be happy to add 
> that
> in.  Just post it on blathersource.  I'm not sure what's up with the
> dropping of the protocol to 9.  What was this in reference to?  Were 
> there
> problems creeping up with newer versions?
>
>> 3) PyICQt doesn't have some features which present in JIT (I wrote
>> some about it a couple of month ago): support for searching in ICQ,
>> diverting messages to parallel session, adding a jabber adverting and
>> real jids info to such messages. May be features of other
>> transports/clients/libs is also useful?  May be it's possible to
>> create ?bsolutely fantastic feature: PyICQt to PyICQt direct sending
>> of messages and dicovering other jabber users on other PyICQts.
>
> Yeah, simply haven't gotten to most of these.  They're on my todo list 
> but
> no real progress yet.  I do not want to add jabber advertising or 
> anything
> like that.  I'm not out to bother people.  I'm not sure what this 
> parallel
> session is unless you just mean being logged into ICQ twice?
>
>> 4) Is it possible to make import/export of ICQ contact list with
>> groups and nicknames, vcard information? Storm of subscribe requests
>> (after registration) is very annoying. It looks shocking for newbies
>> who wants to migrate to jabber and stay connected to friends on ICQ.
>
> I can't do anything about he storm of requests.  James and others have 
> had
> ways of handling these situations in the works but James got shot down,
> unfortunately.  I thought it was a good way to handle the situation.
> James, do you have any more info on how this is going to go down 
> anymore?
> Basically, regardless of the type, it's going to require client support
> which is unlikely available in any current clients.. since as far as I
> know, the protocol hasn't been decided on.  (I might just be out of the
> loop though)  James also had a cool utility (I think?  would be
> misremembering) that would help you import easily.
>
> As for groups and nicknames... that gets tricky.  I seem to recall 
> having
> no success with that in the past.  (ie, a jabber server would have to 
> be
> hacked to allow it)  But I might be mixing up which "direction" the
> subscription was.  None-the-less, if I could have done it, I'm almost
> certain I would have done it already.  I hate having to organize
> everything myself like that.  ;D
>
> Anyway, wish me luck stabilizing my home live post-move so I can get 
> back
> in the swing.  Maaann there's a lot of things to do.  =(  I've begun
> looking over patches and such though, going to start importing probably
> tonight.
>
> Daniel
>
> _______________________________________________
> py-transports mailing list
> py-transports@blathersource.org
> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
>

Reply via email to