davidbgk
/
larlet-fr-david-cache

<!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>
  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,minimum-scale=1,initial-scale=1,shrink-to-fit=no">
<!-- Required to make a valid HTML5 document. -->
<title>Requiem for a data: imagining speculative rituals to cope with a data loss (archive) — David Larlet</title>
<!-- Generated from https://realfavicongenerator.net/ such a mess. -->
<link rel="apple-touch-icon" sizes="180x180" href="/static/david/icons/apple-touch-icon.png">
<link rel="icon" type="image/png" sizes="32x32" href="/static/david/icons/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="16x16" href="/static/david/icons/favicon-16x16.png">
<link rel="manifest" href="/manifest.json">
<link rel="mask-icon" href="/static/david/icons/safari-pinned-tab.svg" color="#5bbad5">
<link rel="shortcut icon" href="/static/david/icons/favicon.ico">
<meta name="apple-mobile-web-app-title" content="David Larlet">
<meta name="application-name" content="David Larlet">
<meta name="msapplication-TileColor" content="#da532c">
<meta name="msapplication-config" content="/static/david/icons/browserconfig.xml">
<meta name="theme-color" content="#f0f0ea">
<!-- That good ol' feed, subscribe :p. -->
<link rel=alternate type="application/atom+xml" title=Feed href="/david/log/">

  <meta name="robots" content="noindex, nofollow">
  <meta content="origin-when-cross-origin" name="referrer">
  <!-- Canonical URL for SEO purposes -->
  <link rel="canonical" href="https://medium.com/design-friction/requiem-for-a-data-imagining-speculative-rituals-to-cope-with-a-data-loss-32175e6c4c08">

<style>
/* http://meyerweb.com/eric/tools/css/reset/ */
html, body, div, span,
h1, h2, h3, h4, h5, h6, p, blockquote, pre,
a, abbr, address, big, cite, code,
del, dfn, em, img, ins,
small, strike, strong, tt, var,
dl, dt, dd, ol, ul, li,
fieldset, form, label, legend,
table, caption, tbody, tfoot, thead, tr, th, td,
article, aside, canvas, details, embed,
figure, figcaption, footer, header, hgroup,
menu, nav, output, ruby, section, summary,
time, mark, audio, video {
  margin: 0;
  padding: 0;
  border: 0;
  font-size: 100%;
  font: inherit;
  vertical-align: baseline;
}
/* HTML5 display-role reset for older browsers */
article, aside, details, figcaption, figure,
footer, header, hgroup, menu, nav, section { display: block; }
body { line-height: 1; }
blockquote, q { quotes: none; }
blockquote:before, blockquote:after,
q:before, q:after {
  content: '';
  content: none;
}
table {
  border-collapse: collapse;
  border-spacing: 0;
}

/* http://practicaltypography.com/equity.html */
/* https://calendar.perfplanet.com/2016/no-font-face-bulletproof-syntax/ */
/* https://www.filamentgroup.com/lab/js-web-fonts.html */
@font-face {
  font-family: 'EquityTextB';
  src: url('/static/david/css/fonts/Equity-Text-B-Regular-webfont.woff2') format('woff2'),
       url('/static/david/css/fonts/Equity-Text-B-Regular-webfont.woff') format('woff');
  font-weight: 300;
  font-style: normal;
  font-display: swap;
}
@font-face {
  font-family: 'EquityTextB';
  src: url('/static/david/css/fonts/Equity-Text-B-Italic-webfont.woff2') format('woff2'),
       url('/static/david/css/fonts/Equity-Text-B-Italic-webfont.woff') format('woff');
  font-weight: 300;
  font-style: italic;
  font-display: swap;
}
@font-face {
  font-family: 'EquityTextB';
  src: url('/static/david/css/fonts/Equity-Text-B-Bold-webfont.woff2') format('woff2'),
       url('/static/david/css/fonts/Equity-Text-B-Bold-webfont.woff') format('woff');
  font-weight: 700;
  font-style: normal;
  font-display: swap;
}

@font-face {
  font-family: 'ConcourseT3';
  src: url('/static/david/css/fonts/concourse_t3_regular-webfont-20190806.woff2') format('woff2'),
       url('/static/david/css/fonts/concourse_t3_regular-webfont-20190806.woff') format('woff');
  font-weight: 300;
  font-style: normal;
  font-display: swap;
}


/* http://practice.typekit.com/lesson/caring-about-opentype-features/ */
body {
  /* http://www.cssfontstack.com/ Palatino 99% Win 86% Mac */
  font-family: "EquityTextB", Palatino, serif;
  background-color: #f0f0ea;
  color: #07486c;
  font-kerning: normal;
  -moz-osx-font-smoothing: grayscale;
  -webkit-font-smoothing: subpixel-antialiased;
  text-rendering: optimizeLegibility;
  font-variant-ligatures: common-ligatures contextual;
  font-feature-settings: "kern", "liga", "clig", "calt";
}
pre, code, kbd, samp, var, tt {
  font-family: 'TriplicateT4c', monospace;
}
em {
  font-style: italic;
  color: #323a45;
}
strong {
  font-weight: bold;
  color: black;
}
nav {
  background-color: #323a45;
  color: #f0f0ea;
  display: flex;
  justify-content: space-around;
  padding: 1rem .5rem;
}
  nav:last-child {
    border-bottom: 1vh solid #2d7474;
  }
  nav a {
    color: #f0f0ea;
  }
  nav abbr {
    border-bottom: 1px dotted white;
  }

h1 {
  border-top: 1vh solid #2d7474;
  border-bottom: .2vh dotted #2d7474;
  background-color: #e3e1e1;
  color: #323a45;
  text-align: center;
  padding: 5rem 0 4rem 0;
  width: 100%;
  font-family: 'ConcourseT3';
  display: flex;
  flex-direction: column;
}
  h1.single {
    padding-bottom: 10rem;
  }
  h1 span {
    position: absolute;
    top: 1vh;
    left: 20%;
    line-height: 0;
  }
    h1 span a {
      line-height: 1.7;
      padding: 1rem 1.2rem .6rem 1.2rem;
      border-radius: 0 0 6% 6%;
      background: #2d7474;
      font-size: 1.3rem;
      color: white;
      text-decoration: none;
    }
h2 {
  margin: 4rem 0 1rem;
  border-top: .2vh solid #2d7474;
  padding-top: 1vh;
}
h3 {
  text-align: center;
  margin: 3rem 0 .75em;
}
hr {
  height: .4rem;
  width: .4rem;
  border-radius: .4rem;
  background: #07486c;
  margin: 2.5rem auto;
}
time {
  display: bloc;
  margin-left: 0 !important;
}
ul, ol {
  margin: 2rem;
}
ul {
  list-style-type: square;
}
a {
  text-decoration-skip-ink: auto;
  text-decoration-thickness: 0.05em;
  text-underline-offset: 0.09em;
}
article {
  max-width: 50rem;
  display: flex;
  flex-direction: column;
  margin: 2rem auto;
}
  article.single {
    border-top: .2vh dotted #2d7474;
    margin: -6rem auto 1rem auto;
    background: #f0f0ea;
    padding: 2rem;
  }
  article p:last-child {
    margin-bottom: 1rem;
  }
p {
  padding: 0 .5rem;
  margin-left: 3rem;
}
  p + p,
  figure + p {
    margin-top: 2rem;
  }

blockquote {
  background-color: #e3e1e1;
  border-left: .5vw solid #2d7474;
  display: flex;
  flex-direction: column;
  align-items: center;
  padding: 1rem;
  margin: 1.5rem;
}
  blockquote cite {
    font-style: italic;
  }
  blockquote p {
    margin-left: 0;
  }

figure {
  border-top: .2vh solid #2d7474;
  background-color: #e3e1e1;
  text-align: center;
  padding: 1.5rem 0;
  margin: 1rem 0 0;
  font-size: 1.5rem;
  width: 100%;
}
  figure img {
    max-width: 250px;
    max-height: 250px;
    border: .5vw solid #323a45;
    padding: 1px;
  }
figcaption {
  padding: 1rem;
  line-height: 1.4;
}
aside {
  display: flex;
  flex-direction: column;
  background-color: #e3e1e1;
  padding: 1rem 0;
  border-bottom: .2vh solid #07486c;
}
  aside p {
    max-width: 50rem;
    margin: 0 auto;
  }

/* https://fvsch.com/code/css-locks/ */
p, li, pre, code, kbd, samp, var, tt, time, details, figcaption {
  font-size: 1rem;
  line-height: calc( 1.5em + 0.2 * 1rem );
}
h1 {
  font-size: 1.9rem;
  line-height: calc( 1.2em + 0.2 * 1rem );
}
h2 {
  font-size: 1.6rem;
  line-height: calc( 1.3em + 0.2 * 1rem );
}
h3 {
  font-size: 1.35rem;
  line-height: calc( 1.4em + 0.2 * 1rem );
}
@media (min-width: 20em) {
  /* The (100vw - 20rem) / (50 - 20) part
     resolves to 0-1rem, depending on the
     viewport width (between 20em and 50em). */
  p, li, pre, code, kbd, samp, var, tt, time, details, figcaption {
    font-size: calc( 1rem + .6 * (100vw - 20rem) / (50 - 20) );
    line-height: calc( 1.5em + 0.2 * (100vw - 50rem) / (20 - 50) );
    margin-left: 0;
  }
  h1 {
    font-size: calc( 1.9rem + 1.5 * (100vw - 20rem) / (50 - 20) );
    line-height: calc( 1.2em + 0.2 * (100vw - 50rem) / (20 - 50) );
  }
  h2 {
    font-size: calc( 1.5rem + 1.5 * (100vw - 20rem) / (50 - 20) );
    line-height: calc( 1.3em + 0.2 * (100vw - 50rem) / (20 - 50) );
  }
  h3 {
    font-size: calc( 1.35rem + 1.5 * (100vw - 20rem) / (50 - 20) );
    line-height: calc( 1.4em + 0.2 * (100vw - 50rem) / (20 - 50) );
  }
}
@media (min-width: 50em) {
  /* The right part of the addition *must* be a
     rem value. In this example we *could* change
     the whole declaration to font-size:2.5rem,
     but if our baseline value was not expressed
     in rem we would have to use calc. */
  p, li, pre, code, kbd, samp, var, tt, time, details, figcaption {
    font-size: calc( 1rem + .6 * 1rem );
    line-height: 1.5em;
  }
  p, li, pre, details {
    margin-left: 3rem;
  }
  h1 {
    font-size: calc( 1.9rem + 1.5 * 1rem );
    line-height: 1.2em;
  }
  h2 {
    font-size: calc( 1.5rem + 1.5 * 1rem );
    line-height: 1.3em;
  }
  h3 {
    font-size: calc( 1.35rem + 1.5 * 1rem );
    line-height: 1.4em;
  }
  figure img {
    max-width: 500px;
    max-height: 500px;
  }
}

figure.unsquared {
  margin-bottom: 1.5rem;
}
  figure.unsquared img {
    height: inherit;
  }


@media print {
  body { font-size: 100%; }
  a:after { content: " (" attr(href) ")"; }
  a, a:link, a:visited, a:after {
    text-decoration: underline;
    text-shadow: none !important;
    background-image: none !important;
    background: white;
    color: black;
  }
  abbr[title] { border-bottom: 0; }
  abbr[title]:after { content: " (" attr(title) ")"; }
  img { page-break-inside: avoid; }
  @page { margin: 2cm .5cm; }
  h1, h2, h3 { page-break-after: avoid; }
  p3 { orphans: 3; widows: 3; }
  img {
    max-width: 250px !important;
    max-height: 250px !important;
  }
  nav, aside { display: none; }
}

ul.with_columns {
  column-count: 1;
}
@media (min-width: 20em) {
  ul.with_columns {
    column-count: 2;
  }
}
@media (min-width: 50em) {
  ul.with_columns {
    column-count: 3;
  }
}
ul.with_two_columns {
  column-count: 1;
}
@media (min-width: 20em) {
  ul.with_two_columns {
    column-count: 1;
  }
}
@media (min-width: 50em) {
  ul.with_two_columns {
    column-count: 2;
  }
}

.gallery {
  display: flex;
  flex-wrap: wrap;
  justify-content: space-around;
}
  .gallery figure img {
    margin-left: 1rem;
    margin-right: 1rem;
  }
  .gallery figure figcaption {
    font-family: 'ConcourseT3'
  }

footer {
  font-family: 'ConcourseT3';
  display: flex;
  flex-direction: column;
  border-top: 3px solid white;
  padding: 4rem 0;
  background-color: #07486c;
  color: white;
}
  footer > * {
    max-width: 50rem;
    margin: 0 auto;
  }
  footer a {
    color: #f1c40f;
  }
  footer .avatar {
    width: 200px;
    height: 200px;
    border-radius: 50%;
    float: left;
    -webkit-shape-outside: circle();
    shape-outside: circle();
    margin-right: 2rem;
    padding: 2px 5px 5px 2px;
    background: white;
    border-left: 1px solid #f1c40f;
    border-top: 1px solid #f1c40f;
    border-right: 5px solid #f1c40f;
    border-bottom: 5px solid #f1c40f;
  }
</style>

<h1>
  <span><a id="jumper" href="#jumpto" title="Un peu perdu ?">?</a></span>
  Requiem for a data: imagining speculative rituals to cope with a data loss (archive)
  <time>Pour la pérennité des contenus liés. Non-indexé, retrait sur simple email.</time>
</h1>
<section>
  <article>
    <h3><a href="https://medium.com/design-friction/requiem-for-a-data-imagining-speculative-rituals-to-cope-with-a-data-loss-32175e6c4c08">Source originale du contenu</a></h3>
    <blockquote name="b85f" id="b85f" class="graf graf--blockquote graf-after--h3">The idea was maturing in our minds: if we are about to become a digital civilisation as it has been stated so many times, and funerals being considered by anthropologists one of the foundations of a civilisation, should we start to imagine funerals for our precious data? We seized the opportunity of the upcoming <a href="https://interaction18.ixda.org/program/workshop-requiem-for-a-data-bastien-kerspern/" data-href="https://interaction18.ixda.org/program/workshop-requiem-for-a-data-bastien-kerspern/" class="markup--anchor markup--blockquote-anchor" rel="noopener nofollow" target="_blank"><strong class="markup--strong markup--blockquote-strong">Interaction18</strong></a><strong class="markup--strong markup--blockquote-strong"> </strong>design week to put out a call for participation in a collaborative workshop exploring this <em class="markup--em markup--blockquote-em">“what if”</em> question — “What if data had funerals too?” — through the approach of design fiction.</blockquote>

<h3 name="a538" id="a538" class="graf graf--h3 graf-after--blockquote">Setting the stage: a near-future data-centred civilisation</h3>

<p name="d221" id="d221" class="graf graf--p graf-after--h3">Data tend to play a crucial role in our life nowadays and have become a digital extension of ourselves. In fact, they have become the essential building blocks of our so-called digital-driven society, but they are still fragile, volatile and vulnerable pieces of our digital self even in an era of generalised backup. Leaks, hacking, misuses, startup bankruptcy, even if they look immaterial and then eternal, data are exposed to a wide range of existential risks.</p>

<p name="e60a" id="e60a" class="graf graf--p graf-after--p">However, do we value them enough to consider funerals for these once beloved traces of our life when they are gone? Through this workshop, participants learnt to use design fiction as a method to explore emerging and speculative rituals helping users to cope with failing data-driven services.</p>

<h3 name="1e2d" id="1e2d" class="graf graf--h3 graf-after--p">Live-predictions from the Maraboot</h3>

<p name="bdae" id="bdae" class="graf graf--p graf-after--h3">Groups of participants were given each a first piece of context: a “moment” they could use as a start for their speculations. Three of them were available:</p>

<p name="39fb" id="39fb" class="graf graf--p graf-after--p">In the first one, “<em class="markup--em markup--p-em">Who wants to live forever</em>”, data were safe so far. But, forecasting or dreading an upcoming data loss, how would near-future inhabitants of the data-centred world prepare themselves, mentally and physically, online and offline ? How would they ward off the threat? How would this question data dependency and superstition towards technologies?</p>

<p name="0f88" id="0f88" class="graf graf--p graf-after--p">The second one, “<em class="markup--em markup--p-em">Another one bites the dust</em>”, places the group right after the dreaded moment: the precious data are now gone. But a doubt remains: are they really gone? Traces of their existence are still warm ; could they resurrect some day? How would they face a resuscitated zombie-data, especially in the case of the most private ones?</p>

<p name="3117" id="3117" class="graf graf--p graf-after--p">In the last one, “<em class="markup--em markup--p-em">The show must go on</em>”, time has passed, but the sad event is stored in the collective human memory. How would this change the way they live and interact with technologies? Do they take it as a lesson and multiply back-ups? Do they carefully and emotionally keep the corpses of their beloved hard drives and other data canopic jars somewhere?</p>

<p name="a9b7" id="a9b7" class="graf graf--p graf-after--p">Groups did not really choose their contextual card, fate chose it for them. Indeed, we had brought our mysterious Maraboot kit with us, and gave it one throw per group, to reveal what the future held for their respective data.</p>

<figure name="bc59" id="bc59" class="graf graf--figure graf-after--p"><figcaption class="imageCaption">The Maraboot kit helps in divining futures for one’s data.</figcaption></figure>

<h3 name="55f9" id="55f9" class="graf graf--h3 graf-after--figure">Time to be hands on: punishment rituals, occult gatherings and data purging sessions to train one’s resiliency</h3>

<p name="c9ba" id="c9ba" class="graf graf--p graf-after--h3">The first group was assigned the “<em class="markup--em markup--p-em">Another one bite the dust</em>” posture, strangely in line with the fact that one of its members had precisely lost her smartphone a few weeks ago, and all her locally stored data; the Maraboot Future Tellers did see it right.</p>

<p name="7881" id="7881" class="graf graf--p graf-after--p">After a short introduction to Design Fiction and a few examples on how to build speculative scenarios, workshop participants, at first a bit puzzled, actively started to exchange their first ideas and intuitions. They got inspired by the various personas we gave them, especially the “datassisted”, a kind of extreme-users heavily relying on data-driven services for their personal or professional lives — lives that would be infinitely more complex for them without the beloved data. Facing this dramatic loss, almost a part of themselves, would they commit a complete data-suicide and erase all their accounts and data, hoping for their next rebirth? Would they go to an Anonymous Datalcoolic circle, to seek support and share their pain with others? Would they try to evacuate, in one way or another, irritation, anger, fear or distrust? Would this happen through the action of building or buying something, as a symbol, or a catharsis? Or a digital detox? Would they blame themselves and accomplish a self-inflicted punishment? Would they organise a funeral party, and try to restore part of the lost data by taking inputs from different sources and friends?</p>

<figure name="e165" id="e165" class="graf graf--figure graf-after--p"/><p name="507e" id="507e" class="graf graf--p graf-after--figure">These last two synopses were the chosen ones. They imagined that in this speculative world, if you lose your data, whether personal or business data, you will have to go through a punishment ritual. Indeed, data are a precious element, constitutive of oneself, prized by major players and stored at a costly environmental price: if you lose it, you have to “carry the weight of the loss”. In a religious and pawnshop-like way, the ritual takes place as follows:</p><p name="c85d" id="c85d" class="graf graf--p graf-after--p">1. You promise that you won’t do it again ; from now on, you will be more careful.<br/>2. You wear the shameful crown which will suck out something out of your head in exchange for the lost data, like a memory, a skill (like a language for example). However you can choose a third way: the “suicide mode”: in this case you simply choose to kill yourself.<br/>3. The sucked-out content is stored in some secure and secret place, and if / once you have“learned the lesson”, you can get it back.</p><figure name="bfba" id="bfba" class="graf graf--figure graf-after--p"><figcaption class="imageCaption"><em class="markup--em markup--figure-em">The data-punishment uses a sort of crown of thorns.</em></figcaption></figure><p name="6ffc" id="6ffc" class="graf graf--p graf-after--figure">A second ritual performs “ghosts raising from collective memory”. The traumatised user invites its relatives to a collective remembrance session. Families and friends are reunited around the table, where personal devices are gathered. They all put their hands together, in a circle, and focus on their shared memories. All the data related to the ones lost by the victim are sourced among all the devices of others and their content (text messages, pictures, Instagram photos…) flow to a shared and mysterious storage piece in the middle of the circle. Finally, although original data could not come back from death, a partial image is restored, and like a ghost, comes to relieve the victim of loss, born again through this “crowdsourced biography” of the data, written by many.</p><figure name="8591" id="8591" class="graf graf--figure graf-after--p"><figcaption class="imageCaption">Data ghosts rising from collective memory.</figcaption></figure><p name="bee7" id="bee7" class="graf graf--p graf-after--figure">The second group was evolving in the frightening “<em class="markup--em markup--p-em">Who wants to live forever</em>” pre-loss context. All participants, being from different nationalities, started by exchanging on typical funerary rites in their respective cultures. Their minds quickly aligned on a particular <em class="markup--em markup--p-em">“what if”</em> scenario: “what if instead of enduring the loss or the perspective of it, inhabitants trained their resiliency by provoking periodic and intentional losses?” How being more in control would change one’s relationship to a data death? Would you feel relieved by such a cleansing ritual, and be more ready for the upcoming death? Would this help prepare to the second death, the one that happens when you are no longer remembered? Do you finally end up with what matters the most, a distillate of the massive digital content accumulated through years? Here is their final scenario:</p><p name="acea" id="acea" class="graf graf--p graf-after--p">In this world, you train yourself to prepare for the upcoming data loss. This ritual allows you to increase your own resiliency when facing the loss, and to accept more easily that ”everything wonderful comes to an end”.</p><p name="dbd8" id="dbd8" class="graf graf--p graf-after--p">All your digital memories are stored in a “Time Box Machine” and are displayed in front of your eyes — you “see your life flash by” — before being erased, one by one. It is time for a final goodbye, before you move to the next life, or the next step of your life. You learn to let it go, and afterwards you feel reborn, purged, with a new space inside you to welcome the future. Everyone has its own pace when it comes to performing this ritual: some can do it every year, some can do it every decade.</p><p name="989b" id="989b" class="graf graf--p graf-after--p">The machine is equipped with a fingerprint sensor and detects your strongest emotional reactions while watching your memories scrolling. In the end, the machine will automatically decide which (very few) memories to preserve, embodied in symbolic tangible artefacts. From a thousand images, you end up with one image that move you, which you can physically hold in your hand. The most is preserved.</p><figure name="656a" id="656a" class="graf graf--figure graf-after--p"><figcaption class="imageCaption">The Time Box Machine is showing you data that will be erased for a last goodbye.</figcaption></figure><figure name="32b0" id="32b0" class="graf graf--figure graf-after--figure"><figcaption class="imageCaption">Data are materialised as concrete artefacts that can be kept as a memory.</figcaption></figure><h3 name="5861" id="5861" class="graf graf--h3 graf-after--figure">Feedback, next steps and retrospective learning</h3><p name="24d9" id="24d9" class="graf graf--p graf-after--h3">It was unclear for us what would emerge from a workshop with such a mystical issue; we were pleasantly surprised by the amazing responsiveness of the participants, and by the quality of their reflections as well as of their productions given the allocated time. They brightly seized and played with the speculation, avoiding the simplistic anthropomorphisation of data to explore new rituals tailored to them, with a deep concern for the psychological component. In other words, when it comes to imagine funerals for data, we aren’t talking about a direct transposition of the classic rituals such as burials or commemorations, but it is more about envisaging a sort of hybridisation between the actual standards of funerals — dealing with the tangibility of the lost element — and the very specific immateriality of data.</p><p name="7ead" id="7ead" class="graf graf--p graf-after--p">The scenarios built by participants and the collective discussion that followed highlighted some particular tendencies when it comes to digital data:</p><ul class="postList"><li name="edcd" id="edcd" class="graf graf--li graf-after--p">They all experienced the need to make digital data tangible. This probably expresses a kind of distrust towards data and/or those whom are storing them.</li><li name="53b8" id="53b8" class="graf graf--li graf-after--li">Templates of computer, smartphones and tablet screens were at their disposal to prototype, as well as explicit objects like cardboard hashtag and arrobas, yet they all chose a blue ice cube-like to picture data embodiment in a broad sense.</li><li name="6192" id="6192" class="graf graf--li graf-after--li">If some of the rituals might seem to be absurd at a first sight, we have to admit they are just the reflect of how each of us builds her or his very own strategy to cope with a loss.</li></ul><p name="1f5b" id="1f5b" class="graf graf--p graf-after--li">In the end, envisioning funerals for data can be justified because the value of data isn’t based on its materiality, but on the emotional charge we place in them. At this point, it is easy, and quite logical, to say “so what?”. If one of the purposes of design fiction is to inspire new perspectives and think about socio-technological implications beyond a productivist imperative, there are still actionable insights to gather from this exercise: data loss is an unavoidable experience at some point. Exploring and understanding how users try to overcome the loss of their cherished data can help us in designing better answers when the many data-driven services we have already adopted are failing us.</p><p name="843b" id="843b" class="graf graf--p graf-after--p graf--trailing"><strong class="markup--strong markup--p-strong">Requiem for a data</strong> was the first experiment of our broader project <strong class="markup--strong markup--p-strong">Data Funerals</strong>, designed to be a participatory project. The next phases of this speculative exploration will be summarised and displayed on a dedicated website.</p>
  </article>
</section>


<nav id="jumpto">
  <p>
    <a href="/david/blog/">Accueil du blog</a> |
    <a href="https://medium.com/design-friction/requiem-for-a-data-imagining-speculative-rituals-to-cope-with-a-data-loss-32175e6c4c08">Source originale</a> |
    <a href="/david/stream/2019/">Accueil du flux</a>
  </p>
</nav>

<footer>
  <div>
    <img src="/static/david/david-larlet-avatar.jpg" loading="lazy" class="avatar" width="200" height="200">
    <p>
      Bonjour/Hi!
      Je suis <a href="/david/" title="Profil public">David&nbsp;Larlet</a>, je vis actuellement à Montréal et j’alimente cet espace depuis 15 ans. <br>
      Si tu as apprécié cette lecture, n’hésite pas à poursuivre ton exploration. Par exemple via les <a href="/david/blog/" title="Expériences bienveillantes">réflexions bimestrielles</a>, la <a href="/david/stream/2019/" title="Pensées (dés)articulées">veille hebdomadaire</a> ou en t’abonnant au <a href="/david/log/" title="S’abonner aux publications via RSS">flux RSS</a> (<a href="/david/blog/2019/flux-rss/" title="Tiens c’est quoi un flux RSS ?">so 2005</a>).
    </p>
    <p>
      Je m’intéresse à la place que je peux avoir dans ce monde. En tant qu’humain, en tant que membre d’une famille et en tant qu’associé d’une coopérative. De temps en temps, je fais aussi des <a href="https://github.com/davidbgk" title="Principalement sur Github mais aussi ailleurs">trucs techniques</a>. Et encore plus rarement, <a href="/david/talks/" title="En ce moment je laisse plutôt la place aux autres">j’en parle</a>.
    </p>
    
    <p>
      Voici quelques articles choisis :
      <a href="/david/blog/2019/faire-equipe/" title="Accéder à l’article complet">Faire équipe</a>,
      <a href="/david/blog/2018/bivouac-automnal/" title="Accéder à l’article complet">Bivouac automnal</a>,
      <a href="/david/blog/2018/commodite-effondrement/" title="Accéder à l’article complet">Commodité et effondrement</a>,
      <a href="/david/blog/2017/donnees-communs/" title="Accéder à l’article complet">Des données aux communs</a>,
      <a href="/david/blog/2016/accompagner-enfant/" title="Accéder à l’article complet">Accompagner un enfant</a>,
      <a href="/david/blog/2016/senior-developer/" title="Accéder à l’article complet">Senior developer</a>,
      <a href="/david/blog/2016/illusion-sociale/" title="Accéder à l’article complet">L’illusion sociale</a>,
      <a href="/david/blog/2016/instantane-scopyleft/" title="Accéder à l’article complet">Instantané Scopyleft</a>,
      <a href="/david/blog/2016/enseigner-web/" title="Accéder à l’article complet">Enseigner le Web</a>,
      <a href="/david/blog/2016/simplicite-defaut/" title="Accéder à l’article complet">Simplicité par défaut</a>,
      <a href="/david/blog/2016/minimalisme-esthetique/" title="Accéder à l’article complet">Minimalisme et esthétique</a>,
      <a href="/david/blog/2014/un-web-omni-present/" title="Accéder à l’article complet">Un web omni-présent</a>,
      <a href="/david/blog/2014/manifeste-developpeur/" title="Accéder à l’article complet">Manifeste de développeur</a>,
      <a href="/david/blog/2013/confort-convivialite/" title="Accéder à l’article complet">Confort et convivialité</a>,
      <a href="/david/blog/2013/testament-numerique/" title="Accéder à l’article complet">Testament numérique</a>,
      et <a href="/david/blog/" title="Accéder aux archives">bien d’autres…</a>
    </p>
    <p>
      On peut <a href="mailto:david%40larlet.fr" title="Envoyer un courriel">échanger par courriel</a>. Si éventuellement tu souhaites que l’on travaille ensemble, tu devrais commencer par consulter le <a href="http://larlet.com">profil dédié à mon activité professionnelle</a> et/ou contacter directement <a href="http://scopyleft.fr/">scopyleft</a>, la <abbr title="Société coopérative et participative">SCOP</abbr> dont je fais partie depuis six ans. Je recommande au préalable de lire <a href="/david/blog/2018/cout-site/" title="Attention ce qui va suivre peut vous choquer">combien coûte un site</a> et pourquoi je suis plutôt favorable à une <a href="/david/pro/devis/" title="Discutons-en !">non-demande de devis</a>.
    </p>
    <p>
      Je ne traque pas ta navigation mais mon
      <abbr title="Alwaysdata, 62 rue Tiquetonne 75002 Paris, +33.184162340">hébergeur</abbr>
      conserve des logs d’accès.
    </p>
  </div>
</footer>
<script type="text/javascript">
  ;(_ => {
    const jumper = document.getElementById('jumper')
    jumper.addEventListener('click', e => {
      e.preventDefault()
      const anchor = e.target.getAttribute('href')
      const targetEl = document.getElementById(anchor.substring(1))
      targetEl.scrollIntoView({behavior: 'smooth'})
    })
  })()
</script>