The entire 'block messages from strangers' thing is a poor mans workaround for the spam problem. I don't think there is a use case for this outside of fighting spam. And it's not even very effective in fighting spam as spammers could just move over to subscription spam. I personally couldn't even use it, because blocking messages from strangers would it turn mean that I would have to allow presence subscription for random people on the Internet who want to contact me.
And yes there are a few users out there for which blocking strangers is an effective way of fighting spam. However so is blocking messages with Cyrillic letters in them. This doesn't mean we should make a standard for this. The spam problem needs to be addressed. But not in this way. And deprecating privacy lists doesn't mean the current implementations will go away. So everybody for whom this is a good enough work around for now can still use it until we come up with something better. On Jan 11, 2017 9:43 PM, "Sam Whited" <s...@samwhited.com> wrote: > Wed, 11 Jan 2017 14:41:51 -0600 > Sam Whited <s...@samwhited.com> wrote: > > > Currently the blocking command blocks > > *everything* from blocked JIDs; so if you block all JIDs not on your > > roster, you could never receive a subscription request to add them to > > your roster. > > Furthermore, with such blocking you cannot even join a MUC room. > _______________________________________________ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: standards-unsubscr...@xmpp.org > _______________________________________________ >
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________
