From 5d8aa047feda0401c13bce36c04aa6db8177ed68 Mon Sep 17 00:00:00 2001
From: Jaz-Michael King <141073565+jmking-iftas@users.noreply.github.com>
Date: Tue, 15 Oct 2024 09:53:59 -0400
Subject: [PATCH] Create Cross-Platform Abuse

---
 dtsp-trust_safety_glossary_of_terms/Cross-Platform Abuse | 9 +++++++++
 1 file changed, 9 insertions(+)
 create mode 100644 dtsp-trust_safety_glossary_of_terms/Cross-Platform Abuse

diff --git a/dtsp-trust_safety_glossary_of_terms/Cross-Platform Abuse b/dtsp-trust_safety_glossary_of_terms/Cross-Platform Abuse
new file mode 100644
index 0000000..99ff7d9
--- /dev/null
+++ b/dtsp-trust_safety_glossary_of_terms/Cross-Platform Abuse	
@@ -0,0 +1,9 @@
+Cross-Platform Abuse
+
+Instances where a bad actor or group will organize a campaign of abuse (such as harassment, trolling or disinformation) using multiple online services.
+
+This has the effect of making it more difficult and time-consuming for affected persons to have the abusive content removed, as they will be required to contact each service separately and explain the situation.
+
+Sometimes, the same content will simply be re-posted across multiple platforms. In other cases, bad actors will divide content or conduct such that no one service carries the full abusive content. As a result, lacking full context of the entire campaign, or if a service’s policy restricts its inquiry only to content or conduct that directly involves that service, a given service may determine that no violation has taken place.
+
+Typically, such situations require research and integration of data from multiple services, and investigation of the background context of the bad actor(s) and affected person(s) to make more meaningful assessments and respond appropriately.