loading . . . ActivityPub Trust & Safety Taskforce forum <p>Hi all, I'm Emelia, the co-lead of the <a href="https://github.com/swicg/activitypub-trust-and-safety/" rel="nofollow ugc">ActivityPub Trust & Safety Taskforce</a> operating under the Social Web CG. We're starting this forum to try to encourage a bit more asynchronous participation in the taskforce and provide a fediverse-native touch point for people interested in trust and safety.</p>
<p>This forum <em><strong>does not</strong></em> replace the <a href="https://github.com/swicg/activitypub-trust-and-safety/issues" rel="nofollow ugc">GitHub issues</a> for the taskforce, where we have specific discussion. We will still have our monthly meetings for the taskforce that happen via a video call with minutes taken and published in the repository.</p>
<p>However, we do want to help people get involved in the taskforce and better understand the taskforces' current areas of work. We've a pretty huge backlog of issues, and there's currently three main focus areas of work, these are:</p>
<ul>
<li>The <strong><a href="https://github.com/swicg/activitypub-trust-and-safety/issues/32" rel="nofollow ugc">Initial Report</a></strong> that aims to provide context for understanding trust and safety at a high-level and what features you may need to implement in fediverse software to foster good trust and safety and moderation.</li>
<li>Work on <strong><a href="https://github.com/swicg/activitypub-trust-and-safety/issues/38" rel="nofollow ugc">Improving Moderation Activities</a></strong>, this covers standardising Flag activities, ensuring that there is enough information in the activities to enable moderation teams, and ensuring the Flag activities reach the correct moderation team directly. At the same time, we're working on inter-server communication between moderation teams, without disclosing individual team members.</li>
<li>Finally, we have <strong><a href="https://github.com/swicg/activitypub-trust-and-safety/issues/41" rel="nofollow ugc">Content warnings, labels, and annotations</a></strong>: this is where we've had most work right now. We've previously reached a consensus that we <strong>won't</strong> be adding a new property for content warnings, but we will document how that is currently supported (hint: it's not just <code>summary</code> being present on an object, but rather <code>summary + as:sensitive</code> being present). We're also working on content labelling, which allows usage of well-known vocabularies as to enable better filtering that is not just keyword matching, eventually the goal is to support annotations, where a third-party can publish content labels on Objects and Actors, and interested parties can subscribe — this removes the burden from the author to label their posts (which for some author's is currently a self-censorship requirement)</li>
</ul>
<p>Once we've made significant progress in these identified areas of work, we may take on additional areas of work.</p>
<p>The taskforce meets virtually via a video call once a month, and you can <a href="https://www.w3.org/events/meetings/29a5bd4f-bb6e-4830-bbf7-7ba290e89afa/" rel="nofollow ugc">find the calendar</a> on the W3C website. It's free to participate in W3C community groups and taskforces, though you will want a W3C account with the CLA and IPR agreement in place, which can be done at:</p>
<ul>
<li>the <a href="https://www.w3.org/community/socialcg/join" rel="nofollow ugc">community group</a></li>
<li>the <a href="https://www.w3.org/community/about/agreements/cla/" rel="nofollow ugc">W3C Agreements</a></li>
</ul>
<p>I'll be monitoring this forum and providing answers / guidance where I can, however, as running the taskforce is unpaid work, I'm unfortunately not able to provide extensive amounts of time, so I may not always respond quickly.</p>
https://activitypub.space/post/1091
