davidbgk
/
larlet-fr-david-cache


			
							123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317
							<!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>The forbidden topics (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://drewdevault.com/2023/09/29/The-forbidden-topics.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>The forbidden topics</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://drewdevault.com/2023/09/29/The-forbidden-topics.html" title="Lien vers le contenu original">Source originale</a>
    </p>
  </nav>
  <hr>
  <p>There are forbidden topics in the hacker community. One is sternly reprimanded
for bringing them up, by their peers, their leaders, and the community at large.
In private, one can expect threats and intimidation; in public, outcry and
censorship. The forbidden topics are enforced by the moderators of our spaces,
taken off of forums, purged from chat rooms, and cleaned up from GitHub issues
and mailing lists; the ban-hammers fall swiftly and resolutely. My last article
to touch these subjects was removed from Hacker News by the moderators within 30
minutes and landed several death threats in my inbox. The forbidden topics, when
raised, are met with a resounding, aggressive dismissal and unconditional
condemnation.</p>
<p>Some years ago, the hacker community possessed near-unanimous praise for the
ideals of free speech; the hacker position was generally that of what we would
now understand as “radical” free speech, which is to say the kind of “shout
‘fire’ in a crowded movie theater” radical, but more specifically the kind that
tolerates hate speech. The popular refrain went, “I disapprove of what you say,
but I will defend to the death your right to say it”. Many hackers hold this as
a virtue to this day. I once held this as a virtue for myself.</p>
<p>However, this was a kind of free speech which was unconsciously contingent on
being used for speech with which the listener was comfortable. The hacker
community at this time was largely homogeneous, and as such most of the speech
we were exposed to was of the comfortable sort. As the world evolved around us,
and more people found their voice, this homogeneity began to break down. Critics
of radical free speech, victims of hate speech, and marginalized people of
all kinds began to appear in hacker communities. The things they had to say were
not comfortable.</p>
<p>The free speech absolutists among the old guard, faced with this discomfort,
developed a tendency to defend hate speech and demean speech that challenged
them. They were not the target of the hate, so it did not make them personally
uncomfortable, and defending it would maintain the pretense of defending free
speech, of stalwartly holding the line on a treasured part of their personal
hacker ethic. Speech which challenged their preconceptions and challenged their
power structures was not so easily acceptable. The pretense is dropped and they
lash out in anger, calling for the speakers to be excluded from our communities.</p>
<p>Some of the once-forbidden topics are becoming less so. There are carefully
chalked-out spaces where we can talk about them, provided they are not too
challenging, such as LGBTQ identities or the struggles of women in our spaces.
Such discussions are subject to careful management by our leaders and
moderators, to the extent necessary to preserve power structures. Those who
speak on these topics are permitted to do so relatively free of retaliation
provided that they speak from a perspective of humility, a voice that “knows its
place”. Any speech which suggests that the listener may find themselves subject
to a non-majority-conforming person in a position of power, or even that of a
peer, will have crossed the line; one must speak as a victim seeking the pity
and grace of your superiors to be permitted space to air your grievances.</p>
<p>Similarly, space is made for opposition to progressive speech, again moderated
only insofar as it is necessary to maintain power structures. Some kinds of
overt hate speech may rouse a response from our leaders, but those who employ a
more subtle approach are permitted their voice. Thus, both progressive speech
and hate speech are permitted within a carefully regulated framework of power
preservation.</p>
<p>Some topics, however, remain strictly forbidden.</p>
<p>Our community has persistent and pervasive problems of a particular sort which
we are not allowed to talk about: sexual harassment and assault. Men who
assault, harass, and even rape women in our spaces, are protected. A culture of
silence is enforced, and those who call out rape, sexual assault, or harassment,
those who criticise they who enable and protect these behaviors, are punished,
swiftly and aggressively.</p>
<p>Men are terrified of these kinds of allegations. It seems like a life sentence:
social ostracization, limited work opportunities, ruined relationships. We may
have events in our past that weigh on our conscience; was she too drunk, did she
clearly consent, did she regret it in the morning? Some of us have events in our
past that we try not to think about, because if we think too hard, we might
realize that we crossed the line. This fills men with guilt and uncertainty, but
also fear. We know the consequences if our doubts became known.</p>
<p>So we lash out in this fear. We close ranks. We demand the most stringent
standards of evidence to prove anything, evidence that we know is not likely to
be there. We refuse to believe that our friends were not the men we thought they
were, or to confront that we might not be ourselves. We demand due process under
the law, we say they should have gone to the police, that they can’t make
accusations of such gravity without hard proof. Think of the alleged
perpetrator; we can’t ruin their lives over frivolous accusations.</p>
<p>For victims, the only recourse permitted by society is to suffer in silence.
Should they speak, victims are subject to similar persecutions: they are
ostracized, struggle to work, and lose their relationships. They have to manage
the consequences of a traumatic experience with support resources which are
absent or inadequate. Their trauma is disbelieved, their speech is punished, and
their assailants walk free among us as equals while they are subject to
retaliatory harassment or worse.</p>
<p>Victims have no recourse which will satisfy men. Reporting a crime is traumatic,
especially one of this nature. I have heard many stories of disbelief from the
authorities, disbelief in the face of overwhelming evidence. They were told it
was their fault. They were told they should have been in a different place, or
wearing something else, or should have simply been a different person. It’s
their fault, not the aggressor’s. It’s about what they, the victim, should
have done differently, never mind what the perpetrator should have done
differently. It’s estimated that less than 1% of rapes end with the rapist in
jail<sup id="fnref:1"></sup> – the remainder go unreported, unprosecuted or fail after years of
traumatic legal proceedings for the victims. The legal system does not provide
justice: it exacerbates harm. A hacker will demand this process is completed
before they will seek justice, or allow justice to be sought. Until then, we
will demand silence, and retaliate if our demands are not met.</p>
<p>The strict standards of evidence required by the justice system are there
because of the state monopoly on violence: a guilty verdict in a crime will lead
to the imprisonment of the accused. We have no such recourse available in
private, accordingly there is no need to hold ourselves to such standards. Our
job is not to punish the accused, but rather to keep our communities safe. We
can establish the need to take action to whatever standard <em>we</em> believe is
sufficient, and by setting these standards as strict as the courts we will fail
to resolve over 99% of the situations with which we are faced – a standard
which is clearly not sufficient to address the problem. I’m behind you if you
want to improve the justice system in this regard, but not if you set this as a
blocker to seeking any justice at all. What kind of hacker puts their faith in
authority?</p>
<p>I find the state of affairs detestable. The hypocrisy of the free speech
absolutist who demands censorship of challenging topics. The fact that the
famous hacker curiosity can suddenly dry up if satisfying it would question our
biases and preconceptions. The complicity of our moderators in censoring
progressive voices in the defense of decorum and the status quo. The duplicitous
characterization of “polite” hate speech as acceptable in our communities. Our
failure to acknowledge our own shortcomings, our fear of seeing the “other” in a
position of power, and the socially enforced ignorance of the “other” that
naturally leads to failing to curtail discrimination and harassment in our
communities. The ridiculously high standard of evidence we require from victims,
who simply ask for our <em>belief</em> at a minimum, before we’ll consider doing
anything about their grievance, if we could even be convinced in the first
place.</p>
<p>Meanwhile, the problems that these forbidden topics seek to discuss are present
in our community. That includes the “polite” problems, such as the conspicuous
lack of diversity in our positions of power, which may be discussed and
commiserated only until someone suggests doing something about it; and also the
impolite problems up to and including the protection of the perpetrators of
sexual harassment, sexual assault, and, yes, rape.</p>
<p>Most hackers live under the comfortable belief that it “can’t happen here”, but
it can and it does. I attended a hacker event this year – HiP Berlin – where I
discovered that some of the organizers had cooperated to make it possible for
multiple known rapists to participate, working together to find a way to
circumvent the event’s code of conduct – a document that they were tasked with
enforcing. One of the victims was in attendance, believing the event to be safe.
At every hacker event I have attended in recent memory, I have personally
witnessed or heard stories of deeply problematic behavior and protection for its
perpetrators from the leadership.</p>
<p>Our community has problems, important problems, that every hacker should care
about, and we need the bravery and humility to face them, not the cowardice to
retaliate against those who speak up. Talk to, listen to, and believe your peers
and their stories. Stand up for what’s right, and speak out when you see
something that isn’t. Demand that your leaders and moderators do the right
thing. Make a platform where people can safely speak about what our community
needs to do right by them, and have the courage to listen to them and confront
yourself.</p>
<p>You need to be someone who will <em>do something about it</em>.</p>
<hr>
<p><strong>Edit</strong>: Case in point: this post was quietly removed by Hacker News moderators
within 40 minutes of its submission.</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>