[Operators] R: Re: Announce: Jabber Spam Fighting Manifesto (for public servers)

Marco Cirillo maranda at lightwitch.org
Thu Feb 8 15:11:08 UTC 2018

Yes that's how *I* currently do it, the server sends a message back to the user telling how to unlock communication.

And WhatsUp when you receive a message from someone not in your list holds the first message with a warning giving you the option to add to your contacts, block, or report as spam.. So it's not that the messages just passthrough. 

---- Denver Gingerich ha scritto ----

>> ---- Denver Gingerich ha scritto ----
>> >On Thu, Feb 08, 2018 at 02:27:50PM +0100, Jan Pinkas wrote:
>> >> We need technical solutions:
>> >> 1. Default behavior: don't accept messages from contacts without
>> >> subscription. This is default for other IM systems.
>> >
>> >This is not the default for the most popular IM system: SMS.
>> >
>> >Please do not implement this on your server, otherwise many useful services (such as those that emulate or integrate with SMS) will not work anymore, and your users will have no idea why.
>On Thu, Feb 08, 2018 at 03:23:22PM +0100, Marco Cirillo wrote:
>> SMS being popular where exactly..?
>If SMS is not popular where you live, then replace "SMS" with "WhatsApp".  There are blocking features in WhatsApp, but by default you receive messages from contacts not in your roster/contact list (per the "Report spam" section of https://faq.whatsapp.com/en/general/21197244 ).
>> Beside that I don't suppose you'd just block period, without giving a legit human user the way to authenticate as such and unlock communication.
>I'm not sure what you mean here.  Are you talking about the policy of JMP specifically?  Or are you saying that the "don't accept messages from contacts without subscription" strategy suggested earlier should be non-silent, i.e. that not accepting the message implies sending a response back to the sender saying it was not accepted and why?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/operators/attachments/20180208/dc33f68e/attachment.html>

More information about the Operators mailing list