davidbgk
/
larlet-fr-david-cache


			
							123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281
							<!doctype html><!-- This is a valid HTML5 document. -->
<!-- Screen readers, SEO, extensions and so on. -->
<html lang="fr">
<!-- Has to be within the first 1024 bytes, hence before the `title` element
  See: https://www.w3.org/TR/2012/CR-html5-20121217/document-metadata.html#charset -->
<meta charset="utf-8">
<!-- Why no `X-UA-Compatible` meta: https://stackoverflow.com/a/6771584 -->
<!-- The viewport meta is quite crowded and we are responsible for that.
  See: https://codepen.io/tigt/post/meta-viewport-for-2015 -->
<meta name="viewport" content="width=device-width,initial-scale=1">
<!-- Required to make a valid HTML5 document. -->
<title>I Was Wrong About Mastodon (archive) — David Larlet</title>
<meta name="description" content="Publication mise en cache pour en conserver une trace.">
<!-- That good ol' feed, subscribe :). -->
<link rel="alternate" type="application/atom+xml" title="Feed" href="/david/log/">
<!-- Generated from https://realfavicongenerator.net/ such a mess. -->
<link rel="apple-touch-icon" sizes="180x180" href="/static/david/icons2/apple-touch-icon.png">
<link rel="icon" type="image/png" sizes="32x32" href="/static/david/icons2/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="16x16" href="/static/david/icons2/favicon-16x16.png">
<link rel="manifest" href="/static/david/icons2/site.webmanifest">
<link rel="mask-icon" href="/static/david/icons2/safari-pinned-tab.svg" color="#07486c">
<link rel="shortcut icon" href="/static/david/icons2/favicon.ico">
<meta name="msapplication-TileColor" content="#f7f7f7">
<meta name="msapplication-config" content="/static/david/icons2/browserconfig.xml">
<meta name="theme-color" content="#f7f7f7" media="(prefers-color-scheme: light)">
<meta name="theme-color" content="#272727" media="(prefers-color-scheme: dark)">
<!-- Is that even respected? Retrospectively? What a shAItshow…
  https://neil-clarke.com/block-the-bots-that-feed-ai-models-by-scraping-your-website/ -->
<meta name="robots" content="noai, noimageai">
<!-- Documented, feel free to shoot an email. -->
<link rel="stylesheet" href="/static/david/css/style_2021-01-20.css">
<!-- See https://www.zachleat.com/web/comprehensive-webfonts/ for the trade-off. -->
<link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_regular.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
<link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_bold.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
<link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_italic.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
<link rel="preload" href="/static/david/css/fonts/triplicate_t3_regular.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
<link rel="preload" href="/static/david/css/fonts/triplicate_t3_bold.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
<link rel="preload" href="/static/david/css/fonts/triplicate_t3_italic.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
<script>
    function toggleTheme(themeName) {
        document.documentElement.classList.toggle(
            'forced-dark',
            themeName === 'dark'
        )
        document.documentElement.classList.toggle(
            'forced-light',
            themeName === 'light'
        )
    }
    const selectedTheme = localStorage.getItem('theme')
    if (selectedTheme !== 'undefined') {
        toggleTheme(selectedTheme)
    }
</script>

  <meta name="robots" content="noindex, nofollow">
  <meta content="origin-when-cross-origin" name="referrer">
  <!-- Canonical URL for SEO purposes -->
  <link rel="canonical" href="https://escapingtech.com/tech/opinions/i-was-wrong-about-mastodon-moderation.html">

<body class="remarkdown h1-underline h2-underline h3-underline em-underscore hr-center ul-star pre-tick" data-instant-intensity="viewport-all">


<article>
  <header>
    <h1>I Was Wrong About Mastodon</h1>
  </header>
  <nav>
    <p class="center">
      <a href="/david/" title="Aller à l’accueil"><svg class="icon icon-home">
        <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-home"></use>
      </svg> Accueil</a> •
      <a href="https://escapingtech.com/tech/opinions/i-was-wrong-about-mastodon-moderation.html" title="Lien vers le contenu original">Source originale</a>
    </p>
  </nav>
  <hr>
  <p>A few weeks ago, I made a tweet about how I thought Mastodon wouldn’t scale due to moderation issues. 
The tweet is since deleted (not because I deleted it individually, but because I later made the decision to purge my account and move to Mastodon).</p>

<p><img src="https://escapingtech.com/images/i-was-wrong-about-mastodon-moderation/tweet.png" alt=""></p>

<p>Mastodon is not a single social media platform, it is a federation. Think of it as a cross between email and Twitter.
You can sign up for an email account with GMail, Yahoo, or Outlook. No matter what provider you choose, you can still email with
people who are using a different provider. Mastodon applies this model to Twitter.
There are lots of different Twitters, and anyone can set up their own Twitter, but they’re all connected so users can communicate with people outside their provider, just like with email.</p>

<p>Mastodon providers are called instances, and a user on one instance can follow and interact with users on other instances.
For all intents and purposes, it seems like one big social media platform, but it’s not. 
The important difference is there’s not a single company controlling Mastodon. Anyone can set up a Mastodon instance and run 
it how they wish, just like a BBS or Message board.</p>

<p>Now, in my head I was seeing this as a problem. On Twitter, you can get banned from Twitter. On Mastodon, you can be banned from
individual Mastodon instances, but not from Mastodon itself (because anyone can set up their own instance). This seemed like it’d
be a huge moderation issue because if abusive users were banned from one instance, they could just move to another.
It was my belief that as Mastodon adoption grew, the moderators of whichever instance you chose to use would have to deal ever-increasing 
volumes of abuse. It’d be like how email providers have to develop spam filters to combat incoming spam from every other provider
(but so much still gets through).</p>

<p>After a month on Mastodon, I’ve realized I was wrong.</p>

<h2 id="a-different-culture">A different culture</h2>
<p>What I missed about Mastodon was its very different culture. 
Ad-driven social media platforms are willing to tolerate monumental volumes of abusive users. 
They’ve discovered the same thing the Mainstream Media did: negative emotions grip people’s attention harder than positive ones.
Hate and fear drives engagement, and engagement drives ad impressions.</p>

<p>Mastodon is not an ad-driven platform. There is absolutely zero incentives to let awful people run amok in the name of engagement.
The goal of Mastodon is to build a friendly collection of communities, not an attention leeching hate mill. As a result, most Mastodon
instance operators have come to a consensus that hate speech shouldn’t be allowed. Already, that sets it far apart from twitter, but wait, there’s more. 
When it comes to other topics, what is and isn’t allowed is on an instance-by-instance basis, so you can choose your own adventure.</p>

<p>You might be wondering, how can you maintain a friendly atmosphere if anyone can just start their own Mastodon instance and spew hate?
This is the part I misunderstood when I said Mastodon wouldn’t scale.</p>

<h2 id="the-accountability-economy">The accountability economy</h2>
<p>Most Mastodon servers run on donations, which creates a very different dynamic. 
It is very easy for a toxic platform to generate revenue through ad impressions, 
but most people are not willing to pay hard-earned money to get yelled at by extremists all day. 
This is why Twitter’s subscription model will never work. 
With Mastodon, people find a community they enjoy, and thus are happy to donate to maintain. Which add a new dynamic.</p>

<p>Since Mastodon is basically a network of communities, it is expected that moderators are responsible for their own community, lowering the burden for everyone.
Let’s say you run a Mastodon instance and a user of another instance has become problematic towards your users. You report them to their instance’s moderators, but the moderators decline to act.
What can you do? Well a lot, actually.</p>

<ol>
  <li>You can block the user’s account from communicating with your instance, so their posts cannot reach anyone on your instance.</li>
  <li>You can block the user’s entire instance from communicating with yours, so that nobody on that instance can communicate with anyone on your own.</li>
</ol>

<p>Now, #2 may sound excessive and overly dramatic, but it’s what makes Mastodon so beautiful. Let me explain.</p>

<p>Instead of expecting instance moderators to moderate incoming toxicity from thousands of other instances, instance owner 
can be held heavily accountable for their users. If an instance is blocked (de-federated) due to insufficient moderation,
everyone on that instance can no-longer reach anyone on any instance that has blocked them, which sucks. 
This not only impacts the experience of users on the de-federated instance, but also gives them a feeling of guilt by association. 
But, Marcus, how is collateral damage at all a good thing, you may ask.</p>

<h2 id="democratic-self-regulation">Democratic self-regulation</h2>
<p>Well, Mastodon users have the ability to transfer their accounts between instances. 
If your instance starts welcoming extremists, you can move. If your instance starts getting de-federated for abuse, you can move.
Many of us, myself included, left Twitter due to the proliferation of extremism. This had a huge personal cost as there is no other Twitter.
On Mastodon, there’s always another instance. You can move to another instance, have the same features, keep all your followers,
and still communicate with people on other instances via the fediverse.</p>

<p>The ability for users to choose if they wish to be collateral damage is what makes Mastodon work.
If an instance is de-federated due to extremism, the users can pressure their moderators to act in order to gain re-federation.
Otherwise, they must make the decision if to go down with the ship or simply move. This creates a healthy self-regulating ecosystem where 
once an instance starts to get de-federated, reasonable users will move their accounts, 
leaving behind unreasonable ones, which further justifies de-federation, and will lead to more and more instances choosing to de-federate the offending one.</p>

<p>Since instance owners are either running their instance for community purposes, or for profit via donations, user loss is very harmful.
As such, there is an economy of accountability which shifts moderation to the source, rather than the destination. 
It’s in an instance owner’s best interest to maintain the friendliest possible community, as this is what attracts new users and keeps exiting ones. 
With instance moderators held accountable for their own instances, this significantly reduces the moderation burden on other instances.
It also creates a double-moderation system, where if some badness does slip past the source instance’s moderators, moderators on the recipient instances can pick up the slack.</p>

<p>Obviously, de-federation can and does happen for asinine reasons. But this is also a good thing. 
Recently, the instance I use was blocked by a few smaller instances for working with the Cybersecurity and Infrastructure Security Agency (CISA).
CISA’s goal is to improve cybersecurity and protect organizations from hackers, but it’s also a part of the Department of Homeland Security (DHS).
DHS is also responsible for Immigrations and Customs Enforcement (ICE), an agency with a track record of rampant humans rights abuse. 
Understandably, people are hostile towards anyone working with DHS. The best we can do is explain that CISA is not ICE, it is a benevolent agency that serves to help us. If people still choose to maintain hostilities towards us,
then it is for the best that they block our instance, because clearly our views are fundamentally incompatible and will only lead to further unfriendliness on both side.</p>

<h2 id="happy-to-be-wrong">Happy to be wrong</h2>
<p>Having spent time on Mastodon, I now realize how hilariously wrong I was about how moderation would work. 
I was seeing Mastodon through the lenses of Twitter, rather than as a different culture with different technology. 
I’m now fairly confident in saying Mastodon is friendlier than Twitter and will remain so, regardless of who and how many join.</p>

<p>I enjoy that everyone is on the same page about not having rampant extremism. I can’t believe that is even a thing that has to be said in this day and age, but I digress (no really, I don’t).
But more, I like the choose-your-own-adventure nature of Mastodon. If something isn’t blocked, and you wish it was, you can move to an Instance where it is. 
On the flip side, if something is blocked, and you wish it wasn’t, you can move to an instance where it isn’t.</p>

<p>The crucial mistake of social media was trying to force people with wildly incompatible views to co-exist in the same space. 
In real-life, I can choose who I associate with. Now, I’m most certainly not looking for an echo chamber. I need my views to be questioned and debated, but it must be by people capable of civil discourse. 
We should discuss, we should reassess, we should admit when we’re wrong. That is not the status quo online.</p>

<p>Traditional social media does not promote diversity of thought, it is for all intents and purposes an echo chamber, albeit, one that encourages piling on passers-by who possess different opinions.
Mastodon feels much closer to hanging out with reasonable friends and acquaintances, whereas Twitter is equivalent to having 15 racists drunk uncles assigned to follow you wherever you go.</p>

<p>I really hope federated networks can be the future of social media.</p>

<p><a href="https://escapingtech.com/tech/guides/a-twitter-users-guide-to-mastodon.html">A Quick-start Guide to Mastodon</a></p>
</article>


<hr>

<footer>
  <p>
    <a href="/david/" title="Aller à l’accueil"><svg class="icon icon-home">
        <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-home"></use>
      </svg> Accueil</a> •
    <a href="/david/log/" title="Accès au flux RSS"><svg class="icon icon-rss2">
        <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-rss2"></use>
      </svg> Suivre</a> •
    <a href="http://larlet.com" title="Go to my English profile" data-instant><svg class="icon icon-user-tie">
        <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-user-tie"></use>
      </svg> Pro</a> •
    <a href="mailto:david%40larlet.fr" title="Envoyer un courriel"><svg class="icon icon-mail">
        <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-mail"></use>
      </svg> Email</a> •
    <abbr class="nowrap" title="Hébergeur : Alwaysdata, 62 rue Tiquetonne 75002 Paris, +33184162340"><svg class="icon icon-hammer2">
        <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-hammer2"></use>
      </svg> Légal</abbr>
  </p>
  <template id="theme-selector">
      <form>
          <fieldset>
              <legend><svg class="icon icon-brightness-contrast">
                <use xlink:href="/static/david/icons2/symbol-defs-2021-12.svg#icon-brightness-contrast"></use>
              </svg> Thème</legend>
              <label>
                  <input type="radio" value="auto" name="chosen-color-scheme" checked> Auto
              </label>
              <label>
                  <input type="radio" value="dark" name="chosen-color-scheme"> Foncé
              </label>
              <label>
                  <input type="radio" value="light" name="chosen-color-scheme"> Clair
              </label>
          </fieldset>
      </form>
  </template>
</footer>
<script src="/static/david/js/instantpage-5.1.0.min.js" type="module"></script>
<script>
    function loadThemeForm(templateName) {
        const themeSelectorTemplate = document.querySelector(templateName)
        const form = themeSelectorTemplate.content.firstElementChild
        themeSelectorTemplate.replaceWith(form)

        form.addEventListener('change', (e) => {
            const chosenColorScheme = e.target.value
            localStorage.setItem('theme', chosenColorScheme)
            toggleTheme(chosenColorScheme)
        })

        const selectedTheme = localStorage.getItem('theme')
        if (selectedTheme && selectedTheme !== 'undefined') {
            form.querySelector(`[value="${selectedTheme}"]`).checked = true
        }
    }

    const prefersColorSchemeDark = '(prefers-color-scheme: dark)'
    window.addEventListener('load', () => {
        let hasDarkRules = false
        for (const styleSheet of Array.from(document.styleSheets)) {
            let mediaRules = []
            for (const cssRule of styleSheet.cssRules) {
                if (cssRule.type !== CSSRule.MEDIA_RULE) {
                    continue
                }
                // WARNING: Safari does not have/supports `conditionText`.
                if (cssRule.conditionText) {
                    if (cssRule.conditionText !== prefersColorSchemeDark) {
                        continue
                    }
                } else {
                    if (cssRule.cssText.startsWith(prefersColorSchemeDark)) {
                        continue
                    }
                }
                mediaRules = mediaRules.concat(Array.from(cssRule.cssRules))
            }

            // WARNING: do not try to insert a Rule to a styleSheet you are
            // currently iterating on, otherwise the browser will be stuck
            // in a infinite loop…
            for (const mediaRule of mediaRules) {
                styleSheet.insertRule(mediaRule.cssText)
                hasDarkRules = true
            }
        }
        if (hasDarkRules) {
            loadThemeForm('#theme-selector')
        }
    })
</script>
</body>
</html>