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] _______________________________________________
