[Standards] publish+configure again

[Kevin Smith]

On 30 Mar 2007, at 17:12, Peter Saint-Andre wrote:
>> The reason I always look to XEP-0060, too, is that I envision that
>> people want more than what PEP provides now
> Yes, (some) people will eventually want all that. So we need to  
> provide a straightforward upgrade path from the PEP subset to  
> complete (or more complete) pubsub. And I think we have that with  
> all the discoverable features in XEP-0060.

Right, I think there's quite some value in a slightly more convenient  
(and by this I just mean pubsub-on-jid like pep) full pubsub service;  
things like blogs spring to mind

>> At this point I have some additional questions.
>> * If we decide to add p+c, will it be required to implement?
> In XEP-0163, I think yes. (Same for auto-create.) But totally  
> optional in XEP-0060.

Right, I've always thought there's been a divergence in needs between  
'regular' or 'full' pubsub and extended presence. In the same way as  
ep doesn't want all of the features of ps, I see no need to push all  
the features of ep on every ps service.

>> * Could someone explain this bit for me?
>> * If you don't trust the other client, how can you be sure it doesn't
>>   mess up other things like the roster, your password or misuse the
>>   nifty remote control support you might have added?
>
> I have to say that this worry continues to puzzle me.

For me, it's not about buggy clients, but just about differently  
configured clients.

FWIW (I don't think Remko's said this yet, maybe he has), Psi's now  
running with publish+configure tested against Legoscia's p+c enabled  
ejabberd.

/K
-- 
Kevin Smith
Psi XMPP Client Project Leader (http://psi-im.org)