You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Users should be able to block messages. The most common use case is for preventing SMS spam. Ideally a block action can trigger an external script for adding the phone number to a blacklist (presumably to block phone calls through a PBX).
The text was updated successfully, but these errors were encountered:
Upon further reading, XEP-0191 doesn't make sense for an external component. A client sends stanzas without a to attribute so the server handles them directly. An external component has no way of knowing when one entity has blocked another. Clients can still use XEP-0191 to block spam SMS locally but we can't use it to notify an external blacklist.
I'd still like the component to facilitate blocking of abusive phone numbers, but we'll need another way to do it. Maybe a "/block" command or something.
mndrix
changed the title
XEP-0191: Blocking Command (for spam)
Blocking Command (for spam)
Feb 8, 2017
Users should be able to block messages. The most common use case is for preventing SMS spam. Ideally a block action can trigger an external script for adding the phone number to a blacklist (presumably to block phone calls through a PBX).
The text was updated successfully, but these errors were encountered: