I'm not sure if the "reporting" bit should automatically go hand in hand with "blocking" specifically. There might be value in defining an entity that simply just receives spam reports. Obviously, end-users generally report spam because they want it to stop, but the goal of reporting could be broader. I'd not be opposed to a XEP that does just that: manage spam reports. The blocking bit is a logical extension to that, but there might be other extensions: things like analysis, and reports sharing with trusted other parties, etc.
On 11 September 2017 at 22:24, Sam Whited <[email protected]> wrote: > On Mon, Sep 11, 2017, at 15:21, Guus der Kinderen wrote: > > The integration with block is an optional part of the XEP, isn't it? I'm > > reading it as: spam can be reported to any entity that advertises > > support, > > and could be inlined with Block if/when desired. > > Right now the only mechanism for reporting is the blocking command. > However, the payload was described in such a way > that it could be reusable if we wanted it to have its own special IQ > later. > > In retrospect this flexibility feels poor to me; let's just have one way > to do things (which should be an extension of the blocking command, > IMO). > > —Sam > _______________________________________________ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: [email protected] > _______________________________________________ >
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
