On 3/5/09 5:46 AM, Pedro Melo wrote:
> 
> On Mar 4, 2009, at 2:05 AM, Peter Saint-Andre wrote:
> 
>> Fabio Forno wrote:
>>> On Sat, Feb 28, 2009 at 5:57 PM, Jonathan Schleifer
>>> <[email protected]> wrote:
>>>
>>>> I agree that we need an alternative for privacy lists - but this is
>>>> definitely not partial roster retrival‼
>>>
>>> And what about partial activation? With partial activation you still
>>> manager the roster as usual, and in a separate iq you set on/off
>>> toggles for each group, at any time of the session.
>>
>> What is the definition of "activation"? Does that mean I receive
>> presence only from the groups I have activated, or that outbound
>> presence notifications are also filtered?
> 
> I understand the need for "activation" in the mobile world as a way to
> limit the initial presence storm, so I would say that "activation" is
> telling which groups in my roster I am interested in receiving presences
> from.
> 
> I still don't see the case to use "activation" as
> yet-another-privacy-list mechanism.

Right, I think we can do everything Fabio outlined using privacy lists.

> So far we have:
>  * incremental roster retrieval: useful to keep the client-copy of our
> roster in sync with the server;

That's XEP-0237.

>  * roster activation: useful to limit the presence broadcast to selected
> groups of contacts.

This can be done with XEP-0016, no?

> I would add the possibility of <presence type="probe"> to the client
> side. It would allow clients to "activate" a specific contact.

Robert Quattlebaum posted about this back in December:

http://mail.jabber.org/pipermail/standards/2008-December/020785.html

I'm embarrassed to say that I haven't read that thread yet. :(

> As for controlling presence-out (aka invisible mode), I don't see any
> value so far on adding that to the roster protocol.

I think the primary use case for mobile optimization is limiting inbound
presence. Perhaps there are use cases for limiting outbound presence but
I don't think they have anything to do with mobile optimization.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to