Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blocking Command (for spam) #7

Open
mndrix opened this issue Jan 30, 2017 · 1 comment
Open

Blocking Command (for spam) #7

mndrix opened this issue Jan 30, 2017 · 1 comment

Comments

@mndrix
Copy link
Contributor

mndrix commented Jan 30, 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).

@mndrix
Copy link
Contributor Author

mndrix commented Feb 8, 2017

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 mndrix changed the title XEP-0191: Blocking Command (for spam) Blocking Command (for spam) Feb 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant