[Psi-devel] Re: Transport roster pushes

[Francisco Joaquín Rodríguez Prados]

> James Bunton wrote:
> | At the moment the Python transports all support a proposal I came up
> | with a while ago, roster-subsync, which is basically just the current
> | protocol, except with an extra flag to notify the client that this
> | subscription should be handled automatically.
> 
> I don't know if this addressed in your JEP or not, but when we implement
> this be sure that the subscription is from a registered transport. We
> don't need random entities getting preapproved subscriptions.

Ok, that's what the PyMSN transport sends:

<presence from="someone%hotmail.com at msn.pandion.be" type="subscribed"
to="franqui at jabber.dk" >
<x xmlns="http://jabber.org/protocol/roster-subsync">
<item subscription="both" name="Someone" >
<group>Individuals</group>
</item>
</x>
</presence>

So as the subscription entity is included in that x element it is
easily recognizable that it comes from a transport. Tell me if I'm
wrong, but the idea of this jep is to automatize this subscription if
the transport entity ("msn.pandion.be" in the example) is allowed to
send roster-subsync tags.

Then:

1. Transport are recongnizable in Psi, as they are in the roster
without username in the JID.

2. An "Auto-authorize contacts from transports" option could be a good
start (actually this is Remko's idea about the topic)

3. Thus, an "Ignore 'you are now authorized' messages from transport"
option should be duable, as the second group of 80 windows that we are
talking about are generated when the <presence type="subscribed"> item
arrives from the transport. Tell me if I'm wrong - I'm not quite sure
of what generates those windows -.

So, with two (useful) options that could came activated by default,
the 2x80 messages could be easily avoided. I think :D

Cheers,

Fran.

-- 
Francisco Joaquín Rodríguez Prados
Fachbereich Informatik,
Fachhochschule Darmstadt,
Darmstadt, Germany