[Standards] Deprecating Privacy Lists

Sergei Golovan sgolovan at nes.ru
Thu Oct 1 04:04:44 UTC 2015


On Wed, Sep 30, 2015 at 4:54 PM, Sam Whited <sam at samwhited.com> wrote:
> On Wed, Sep 30, 2015 at 2:57 AM, Sergei Golovan <sgolovan at nes.ru> wrote:
>> Well, It's unfortunate, because XEP-0191 doesn't cover the following case
>> I'd consider important: it doesn't allow me to block all messages from
>> unknown contacts (contacts not in my roster). Recently, I received a
>> fair amount of
>> spam from random JIDs on public XMPP servers, so I had to block all
>> unknown JIDs. Is there any way to do that without privacy lists?
>
> That's a great use case; I can't say that I've ever used it myself
> (what client are you using that actually allows you to do this, by the
> way?), but I can see the value in it.

In my case it's Tkabber, but I think every client supporting XEP-0016
can block communications based on contacts subscription status.

>
> This seems like a great candidate to add to the blocking command, and
> something that we should persue if we think that it's a common enough
> use case. However, I don't see it as a blocker to deprecating privacy
> lists (it's not like deprecating privacy lists instantly means that
> all clients and servers will stop supporting it; it's just the XSF
> recommending that it not be implemented anymore for new
> implementations).

As long as server developers don't start removing Privacy lists
support. And as we can see, Prosody developers might.

Cheers!
-- 
Sergei Golovan


More information about the Standards mailing list