Merge computering and thoughtpile blogs into thoughtpile.
Doesn't make much sense to keep 2 blogs with my low publishing frequency.
This commit is contained in:
parent
8b76c7bf64
commit
bb1c0eece0
GPG Key ID:
CFC39497F1B26E07
12
config.toml
12
config.toml
|
|
@ -1,6 +1,6 @@
|
|||
baseURL = "https://computering.tastytea.de/"
|
||||
baseURL = "https://thoughtpile.tastytea.de/"
|
||||
languageCode = "en"
|
||||
title = "Computering"
|
||||
title = "Thoughtpile"
|
||||
theme = [ "nocolor" ]
|
||||
copyright = "CC BY-NC 4.0"
|
||||
|
||||
|
|
@ -15,7 +15,7 @@ PaginatePath = "page"
|
|||
enableGitInfo = true
|
||||
|
||||
[params]
|
||||
subtitle = "I write things about computering here."
|
||||
subtitle = "A pile of thoughts."
|
||||
favicon = "favicon.png"
|
||||
datefmt = "2006-01-02"
|
||||
showfullcontent = false
|
||||
|
|
@ -64,3 +64,9 @@ enableGitInfo = true
|
|||
name = "Sourcecode"
|
||||
url = "https://schlomp.space/tastytea/blog"
|
||||
weight = 2
|
||||
|
||||
[markup]
|
||||
[markup.tableOfContents]
|
||||
startLevel = 2
|
||||
endLevel = 4
|
||||
ordered = false
|
||||
|
|
|
|||
|
|
@ -0,0 +1,138 @@
|
|||
---
|
||||
title: "Ideas on a better content warning system for the Fediverse"
|
||||
slug: Ideas-on-a-better-content-warning-system-for-the-Fediverse
|
||||
description: "Content warnings in the Fediverse are a pain to use. Here are a few ideas how to do them better."
|
||||
date: 2020-12-27T17:20:00+01:00
|
||||
type: posts
|
||||
draft: false
|
||||
tags:
|
||||
- Fediverse
|
||||
- ActivityPub
|
||||
comtodon: A2dFPz1XlA6JZYdAAa
|
||||
toc: true
|
||||
---
|
||||
|
||||
:source-highlighter: pygments
|
||||
:toc:
|
||||
:toclevels: 2
|
||||
|
||||
:fn-Masto-cw-original: footnote:[https://github.com/tootsuite/mastodon/issues/239]
|
||||
:fn-AP-cw-subject: footnote:AP-cw-subject[https://github.com/w3c/activitypub/issues/232]
|
||||
:fn-Masto-cw-improve-1: footnote:[https://github.com/tootsuite/mastodon/issues/8681]
|
||||
:fn-Masto-cw-improve-2: footnote:[https://github.com/tootsuite/mastodon/issues/10761]
|
||||
|
||||
:url-WP-tw: https://en.wikipedia.org/wiki/Trauma_trigger#Trigger_warnings
|
||||
:url-WP-activitypub: https://en.wikipedia.org/wiki/ActivityPub
|
||||
:url-Masto-spoiler: https://docs.joinmastodon.org/entities/status/#spoiler_text
|
||||
:url-AP-summary: https://www.w3.org/TR/activitystreams-vocabulary/#dfn-summary
|
||||
:url-AP-tag: https://www.w3.org/TR/activitystreams-vocabulary/#dfn-tag
|
||||
|
||||
|
||||
Content warnings are a more general form of link:{url-WP-tw}[trigger
|
||||
warnings]. They are notices that precede potentially sensitive content, so
|
||||
readers can prepare themselves to adequately engage or, if necessary, disengage
|
||||
for their own well-being.
|
||||
|
||||
== How content warnings are handled by current implementations
|
||||
|
||||
Mastodon and Pleroma abuse the “link:{url-AP-summary}[summary]” field in
|
||||
link:{url-WP-activitypub}[ActivityPub] for content
|
||||
warnings.{fn-Masto-cw-original}{fn-AP-cw-subject} The field returned by the
|
||||
Mastodon API is called “link:{url-Masto-spoiler}[spoiler_text]”. It's a simple
|
||||
text field. There are no mechanisms to ensure that content warnings are
|
||||
predictable and they clash with real summaries.
|
||||
|
||||
There is no consensus as to how to name these warnings. Some use abbreviations
|
||||
like “mh”, “ec”, “alc” and so on, others use “mental health”, “eye contact” and
|
||||
“alcohol”. Negativity is expressed with “negative”, “neg”, “-” or “--”. Words
|
||||
get misspelled. It makes filtering unnecessary hard.
|
||||
|
||||
== How to make content warnings better
|
||||
|
||||
=== The goal
|
||||
|
||||
The purpose of content warnings is to allow people to decide if they want to see
|
||||
the content. Maybe you don't want to look at cats under any circumstances, only
|
||||
want to look at nudity sometimes and want to see as much pictures of squirrels
|
||||
as possible. You should be able to filter out all cat pictures, have all posts
|
||||
with nudity collapsed and all posts with squirrels expanded.
|
||||
|
||||
=== Problems and solutions
|
||||
|
||||
==== Different people name content warnings differently
|
||||
|
||||
Content warnings should auto-complete. Each server could have a database with
|
||||
all previously used content warnings. If you type “cat”, a little list pops up
|
||||
showing that “cat” was used 17 times and “cats” was used 2 times. You see that
|
||||
most people expect cat pictures to be labeled with “cat”. It could be useful to
|
||||
be able to synchronize the content warning database between servers.
|
||||
|
||||
==== How does the server know where one content warning ends and another begins?
|
||||
|
||||
Content warnings should be arrays, not one text field. They could be implemented
|
||||
as their own type or as special link:{url-AP-tag}[tags].
|
||||
|
||||
.Example for ActivityPub-tags with type “content_warning”:
|
||||
[source,json]
|
||||
--------------------------------------------------------------------------------
|
||||
"tag": [
|
||||
{
|
||||
"type": "content_warning",
|
||||
"name": "nudity",
|
||||
"id": "https://example.com/content_warnings/nudity"
|
||||
},
|
||||
{
|
||||
"type": "content_warning",
|
||||
"name": "eye contact",
|
||||
"id": "https://example.com/content_warnings/eye%20contact"
|
||||
}
|
||||
]
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
==== What about posts without content warnings?
|
||||
|
||||
This is a social problem that can not be solved technically. However, there are
|
||||
ways to better the situation somewhat. Some posts can be understood good enough
|
||||
by machines to add automatic content warnings. Say for example, you write a
|
||||
post with the text “Look at these cute squirrels! 😍” and an image
|
||||
attached. The server could have an algorithm like this: _If “squirrel” is in
|
||||
text and an attachment is present, add content warning “squirrel”._ Automatic
|
||||
content warnings should have a different type than user selected content
|
||||
warnings to make it possible for users to ignore these.
|
||||
|
||||
==== What about the compatibility to existing implementations?
|
||||
|
||||
If a post (“status” in ActivityPub terms) does not have a content warning field,
|
||||
the “summary” could be translated, either by looking for words that match
|
||||
content warnings in our database or by simply splitting the text on “,” and
|
||||
“;”footnote:[The latter approach will lead to errors for posts that actually use
|
||||
the summary field for a summary.]. These should also use the type for automatic
|
||||
content warnings.
|
||||
|
||||
.Example of an automatically translated status with summary:
|
||||
[source,json]
|
||||
--------------------------------------------------------------------------------
|
||||
"summary": "squirrels, eye contact",
|
||||
"tag": [
|
||||
{
|
||||
"type": "content_warning_auto",
|
||||
"name": "squirrels",
|
||||
"id": "https://example.com/content_warnings/squirrels"
|
||||
},
|
||||
{
|
||||
"type": "content_warning_auto",
|
||||
"name": "eye contact",
|
||||
"id": "https://example.com/content_warnings/eye%20contact"
|
||||
}
|
||||
]
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
==== How likely is it that existing Fediverse servers change their implementation?
|
||||
|
||||
ActivityPub seems to specify whatever Mastodon doesfootnote:AP-cw-subject[] and
|
||||
Mastodon does not seem interested to improve the
|
||||
situation.{fn-Masto-cw-improve-1}{fn-Masto-cw-improve-2} Pleroma seems to copy
|
||||
whatever Mastodon does. I don't know about the other server implementations. The
|
||||
best route right now appears to be to try to get a proper content warning
|
||||
feature into ActivityPub and then hope the servers implement it. Or develop
|
||||
something better than ActivityPub.
|
||||
Loading…
Reference in New Issue