From XMPP.org, a couple of choice extension specifications:
XEP-0161: Abuse Reporting
Abstract: This document specifies an XMPP protocol extension for reporting abusive XMPP stanzas. Status: Deferred
WARNING: This document has been automatically Deferred after 12 months of inactivity in its previous Experimental state.
Superseded By: XEP-0268
XEP-0268: Incident Handling
Status: Deferred
WARNING: This document has been automatically Deferred after 12 months of inactivity in its previous Experimental state. Last Updated: 2012-05-29
Internet communication is not a simple thing, I greatly respect the need for standards to be defined and measured. And these specification documents provide really good guidance on considerations. But it is not feasible to find wide-spread success if there isn’t even basic consensus on how to report spam after a hiatus of 10 years on v0.6 of a spec. There is a whole lot of process involved for a protocol that has very little decided.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !privacyguides@lemmy.one
In the digital age, protecting your personal information might seem like an impossible task. We’re here to help.
This is a community for sharing news about privacy, posting information about cool privacy tools and services, and getting advice about your privacy journey.
You can subscribe to this community from any Kbin or Lemmy instance:
Check out our website at privacyguides.org before asking your questions here. We’ve tried answering the common questions and recommendations there!
Want to get involved? The website is open-source on GitHub, and your help would be appreciated!
This community is the “official” Privacy Guides community on Lemmy, which can be verified here. Other “Privacy Guides” communities on other Lemmy servers are not moderated by this team or associated with the website.
Moderation Rules:
We prefer posting about open-source software whenever possible.
No soliciting engagement: Don’t ask for upvotes, follows, etc.
Surveys, Fundraising, and Petitions must be pre-approved by the mod team.
Be civil, no violence, hate speech. Assume people here are posting in good faith.
Don’t repost topics which have already been covered here.
News posts must be related to privacy and security, and your post title must match the article headline exactly. Do not editorialize titles, you can post your opinions in the post body or a comment.
Memes/images/video posts that could be summarized as text explanations should not be posted. Infographics and conference talks from reputable sources are acceptable.
No help vampires: This is not a tech support subreddit, don’t abuse our community’s willingness to help. Questions related to privacy, security or privacy/security related software and their configurations are acceptable.
No misinformation: Extraordinary claims must be matched with evidence.
Do not post about VPNs or cryptocurrencies which are not listed on privacyguides.org. See Rule 2 for info on adding new recommendations to the website.
General guides or software lists are not permitted. Original sources and research about specific topics are allowed as long as they are high quality and factual. We are not providing a platform for poorly-vetted, out-of-date or conflicting recommendations.
From XMPP.org, a couple of choice extension specifications:
Internet communication is not a simple thing, I greatly respect the need for standards to be defined and measured. And these specification documents provide really good guidance on considerations. But it is not feasible to find wide-spread success if there isn’t even basic consensus on how to report spam after a hiatus of 10 years on v0.6 of a spec. There is a whole lot of process involved for a protocol that has very little decided.