Repository for a report on improving the trust, safety, and integrity of ActivityPub and related specifications by the W3C Social Web Community Group.
Latest editor's draft: https://swicg.github.io/activitypub-trust-and-safety/ (work in progress)
It is used:
- As an issue tracker for Trust and Safety related ideas, requests, and issues.
- As a repository of Reports, Notes, and other task force deliverables.
Note: we cannot directly change or improve various software that implements ActivityPub within the scope of this Taskforce, for that, please file issues with the respective project's issue trackers, potentially cross referencing issues here.
The initial scope of work for this task force is split into three workstreams, as follows:
- Initial Report (#32)
- Overview of current state of trust and safety on the Fediverse
- Documenting how ActivityPub functionality is currently used
- Best Practices & Recommendations
- Improving Moderation Activities (Flag and Blocks) (#38)
- Addressing for where to send these activities
- Additional properties to improve federation of moderation activities (e.g., category and evidence on Flag Activities)
- Inter-server communication on moderation activities
- Content warnings, labels, and annotations (#41)
This taskforce is intended to be ongoing, as the work of trust and safety is an ongoing matter. Additional work items may come in from the SocialCG or the taskforce, and be added to future workstreams.
In addition to this repository, conversation also occurs at:
- W3C
public-swicg
SocialWeb CG mailing list (for general discussion) - Fediverse Enhancement Protocols repository (for related specification under incubation)
Use the standard fork, branch, and pull request workflow to propose changes to the report. Please make branch names informative—by including the issue or bug number for example.
When contributing issues, please provide relevant references, links to existing FEPs and prior discussions. This will assist the task force in triaging issues.
Editorial changes that improve the readability of the spec or correct spelling or grammatical mistakes are welcome.
Please read CONTRIBUTING.md, about licensing contributions.
This repository operates under the W3C code of conduct.