On Tue, Jul 14, 2009 at 5:48 PM, Peter Saint-Andre<[email protected]> wrote: >> - It does a jabber:iq:roster request on gateway.example.com
> This is not limited to gateways, but also to shared groups services > (e.g., you get all the XSF members in a special "Members" group). This is so simple and solves the problem so well that I have no idea why we haven't been doing it from the start. Good catch. It solves a bunch of issues, like levels of trust with the transport to edit your roster, of migration between transports or servers, groups within the transport, contact naming, and jid escaping. So yes, let's use standard rosters for transports and shared groups, and let's keep roster item exchange just for sharing contacts. Yay. /K
