I'm not arguing that the XEP should define anything but the payload (and how entities do the initial reporting to their domain).
Although there's no harm in blocking the sender of the spam that you reported, tying the two XEPs together implies that there are no other ways to prevent the spam after the report. To draw a parallel: when I mark an email as spam, I don't get a new inbound mail filter rule. I'm depending on my service provider to ensure that I, but perhaps also others, won't be bothered by the reported spam. I'd propose to modify this XEP a little to do only pretty basic reporting (to allow an end-user to send in a spam report) and have some recommendations on what implementations could do with such reports (blocking, sharing, what not), but leave the details of those actions to be described in XEPs. On 11 September 2017 at 22:32, Sam Whited <[email protected]> wrote: > On Mon, Sep 11, 2017, at 15:29, Guus der Kinderen wrote: > > 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. > > That's fair, and maybe you could reuse the same payload for that, but I > don't think this XEP should be expanded to cover anything else like > report sharing. It's just about sending the report to the server in the > first place. I don't see why you'd want to report spam without also > blocking the sender personally. > > —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] _______________________________________________
