[Standards-JIG] Re: JEP-126 (Invisibility)

Peter Saint-Andre stpeter at jabber.org
Mon Apr 17 17:38:37 UTC 2006


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Remko Troncon wrote:
> 
>> Indeed, it's not clear to me how important any of this is in the real
>> world since I never used <presence type='invisible'/> when it was more
>> widely supported. But I may not be a typical end user.
> 
> Me neither, but we have quite some users using it.
> 
>> <iq type='set'>
>>   <block xmlns='http://jabber.org/protocol/block'>user at host</block>
>> </iq>
>>
>> Similarly for invisibility:
>>
>> <iq type='set'>
>>   <invisible xmlns='http://jabber.org/protocol/invisible'/>
>> </iq>
> 
> Yes, this seems like the simplest and most uncontroversial change to get
> blocking and invisibility done. It takes a lot of the burden off the
> client, and allows you to do these operations in one atomic operation
> (instead of determining + requesting + changing + setting the privacy
> list). It's also a lot easier to implement this on the server side
> (sounds trivial even).

OK, we seem to have consensus, so I will write something up or modify
JEP-0018. I now agree that invisibility is a bad fit for privacy lists,
sorry it took me so long to realize it.

Peter

- --
Peter Saint-Andre
Jabber Software Foundation
http://www.jabber.org/people/stpeter.shtml

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEQ9KdNF1RSzyt3NURAmOTAKCTSgYHbxx0KcYEO56HWLi0wqp7vwCeI4qB
O4oCYp3hNkbwVY2ZUVaJ7PI=
=ohX0
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3641 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20060417/37ac350a/attachment.bin>


More information about the Standards mailing list