davidbgk
/
larlet-fr-david-cache
Наблюдаван 1
Харесван 0
Разклонения 0
Код Версии 0 Activity
A place to cache linked articles (think custom and personal wayback machine)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
24 Ревизии
1 Клон
ИН на ревизия: f77cf90681
Клонове Маркери
${ item.name }
Create branch ${ searchTerm }
от 'f77cf90681'
${ noResults }
larlet-fr-david-cache/cache/feb30a892b67bd8233bdaed6bdd.../index.html

index.html 41KB
Директен файл Blame История

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633 
  1. <!doctype html><!-- This is a valid HTML5 document. -->

  2. <!-- Screen readers, SEO, extensions and so on. -->

  3. <html lang=fr>

  4. <!-- Has to be within the first 1024 bytes, hence before the <title>

  5.   See: https://www.w3.org/TR/2012/CR-html5-20121217/document-metadata.html#charset -->

  6. <meta charset=utf-8>

  7. <!-- Why no `X-UA-Compatible` meta: https://stackoverflow.com/a/6771584 -->

  8. <!-- The viewport meta is quite crowded and we are responsible for that.

  9.   See: https://codepen.io/tigt/post/meta-viewport-for-2015 -->

  10. <meta name=viewport content="width=device-width,minimum-scale=1,initial-scale=1,shrink-to-fit=no">

  11. <!-- Required to make a valid HTML5 document. -->

  12. <title>The Planet Needs a New Internet (archive) — David Larlet</title>

  13. <!-- Generated from https://realfavicongenerator.net/ such a mess. -->

  14. <link rel="apple-touch-icon" sizes="180x180" href="/static/david/icons/apple-touch-icon.png">

  15. <link rel="icon" type="image/png" sizes="32x32" href="/static/david/icons/favicon-32x32.png">

  16. <link rel="icon" type="image/png" sizes="16x16" href="/static/david/icons/favicon-16x16.png">

  17. <link rel="manifest" href="/manifest.json">

  18. <link rel="mask-icon" href="/static/david/icons/safari-pinned-tab.svg" color="#5bbad5">

  19. <link rel="shortcut icon" href="/static/david/icons/favicon.ico">

  20. <meta name="apple-mobile-web-app-title" content="David Larlet">

  21. <meta name="application-name" content="David Larlet">

  22. <meta name="msapplication-TileColor" content="#da532c">

  23. <meta name="msapplication-config" content="/static/david/icons/browserconfig.xml">

  24. <meta name="theme-color" content="#f0f0ea">

  25. <!-- That good ol' feed, subscribe :p. -->

  26. <link rel=alternate type="application/atom+xml" title=Feed href="/david/log/">

  27. 

  28.   <meta name="robots" content="noindex, nofollow">

  29.   <meta content="origin-when-cross-origin" name="referrer">

  30.   <!-- Canonical URL for SEO purposes -->

  31.   <link rel="canonical" href="https://earther.gizmodo.com/the-planet-needs-a-new-internet-1837101745">

  32. 

  33. <style>

  34. /* http://meyerweb.com/eric/tools/css/reset/ */

  35. html, body, div, span,

  36. h1, h2, h3, h4, h5, h6, p, blockquote, pre,

  37. a, abbr, address, big, cite, code,

  38. del, dfn, em, img, ins,

  39. small, strike, strong, tt, var,

  40. dl, dt, dd, ol, ul, li,

  41. fieldset, form, label, legend,

  42. table, caption, tbody, tfoot, thead, tr, th, td,

  43. article, aside, canvas, details, embed,

  44. figure, figcaption, footer, header, hgroup,

  45. menu, nav, output, ruby, section, summary,

  46. time, mark, audio, video {

  47.   margin: 0;

  48.   padding: 0;

  49.   border: 0;

  50.   font-size: 100%;

  51.   font: inherit;

  52.   vertical-align: baseline;

  53. }

  54. /* HTML5 display-role reset for older browsers */

  55. article, aside, details, figcaption, figure,

  56. footer, header, hgroup, menu, nav, section { display: block; }

  57. body { line-height: 1; }

  58. blockquote, q { quotes: none; }

  59. blockquote:before, blockquote:after,

  60. q:before, q:after {

  61.   content: '';

  62.   content: none;

  63. }

  64. table {

  65.   border-collapse: collapse;

  66.   border-spacing: 0;

  67. }

  68. 

  69. /* http://practicaltypography.com/equity.html */

  70. /* https://calendar.perfplanet.com/2016/no-font-face-bulletproof-syntax/ */

  71. /* https://www.filamentgroup.com/lab/js-web-fonts.html */

  72. @font-face {

  73.   font-family: 'EquityTextB';

  74.   src: url('/static/david/css/fonts/Equity-Text-B-Regular-webfont.woff2') format('woff2'),

  75.        url('/static/david/css/fonts/Equity-Text-B-Regular-webfont.woff') format('woff');

  76.   font-weight: 300;

  77.   font-style: normal;

  78.   font-display: swap;

  79. }

  80. @font-face {

  81.   font-family: 'EquityTextB';

  82.   src: url('/static/david/css/fonts/Equity-Text-B-Italic-webfont.woff2') format('woff2'),

  83.        url('/static/david/css/fonts/Equity-Text-B-Italic-webfont.woff') format('woff');

  84.   font-weight: 300;

  85.   font-style: italic;

  86.   font-display: swap;

  87. }

  88. @font-face {

  89.   font-family: 'EquityTextB';

  90.   src: url('/static/david/css/fonts/Equity-Text-B-Bold-webfont.woff2') format('woff2'),

  91.        url('/static/david/css/fonts/Equity-Text-B-Bold-webfont.woff') format('woff');

  92.   font-weight: 700;

  93.   font-style: normal;

  94.   font-display: swap;

  95. }

  96. 

  97. @font-face {

  98.   font-family: 'ConcourseT3';

  99.   src: url('/static/david/css/fonts/concourse_t3_regular-webfont-20190806.woff2') format('woff2'),

  100.        url('/static/david/css/fonts/concourse_t3_regular-webfont-20190806.woff') format('woff');

  101.   font-weight: 300;

  102.   font-style: normal;

  103.   font-display: swap;

  104. }

  105. 

  106. 

  107. /* http://practice.typekit.com/lesson/caring-about-opentype-features/ */

  108. body {

  109.   /* http://www.cssfontstack.com/ Palatino 99% Win 86% Mac */

  110.   font-family: "EquityTextB", Palatino, serif;

  111.   background-color: #f0f0ea;

  112.   color: #07486c;

  113.   font-kerning: normal;

  114.   -moz-osx-font-smoothing: grayscale;

  115.   -webkit-font-smoothing: subpixel-antialiased;

  116.   text-rendering: optimizeLegibility;

  117.   font-variant-ligatures: common-ligatures contextual;

  118.   font-feature-settings: "kern", "liga", "clig", "calt";

  119. }

  120. pre, code, kbd, samp, var, tt {

  121.   font-family: 'TriplicateT4c', monospace;

  122. }

  123. em {

  124.   font-style: italic;

  125.   color: #323a45;

  126. }

  127. strong {

  128.   font-weight: bold;

  129.   color: black;

  130. }

  131. nav {

  132.   background-color: #323a45;

  133.   color: #f0f0ea;

  134.   display: flex;

  135.   justify-content: space-around;

  136.   padding: 1rem .5rem;

  137. }

  138.   nav:last-child {

  139.     border-bottom: 1vh solid #2d7474;

  140.   }

  141.   nav a {

  142.     color: #f0f0ea;

  143.   }

  144.   nav abbr {

  145.     border-bottom: 1px dotted white;

  146.   }

  147. 

  148. h1 {

  149.   border-top: 1vh solid #2d7474;

  150.   border-bottom: .2vh dotted #2d7474;

  151.   background-color: #e3e1e1;

  152.   color: #323a45;

  153.   text-align: center;

  154.   padding: 5rem 0 4rem 0;

  155.   width: 100%;

  156.   font-family: 'ConcourseT3';

  157.   display: flex;

  158.   flex-direction: column;

  159. }

  160.   h1.single {

  161.     padding-bottom: 10rem;

  162.   }

  163.   h1 span {

  164.     position: absolute;

  165.     top: 1vh;

  166.     left: 20%;

  167.     line-height: 0;

  168.   }

  169.     h1 span a {

  170.       line-height: 1.7;

  171.       padding: 1rem 1.2rem .6rem 1.2rem;

  172.       border-radius: 0 0 6% 6%;

  173.       background: #2d7474;

  174.       font-size: 1.3rem;

  175.       color: white;

  176.       text-decoration: none;

  177.     }

  178. h2 {

  179.   margin: 4rem 0 1rem;

  180.   border-top: .2vh solid #2d7474;

  181.   padding-top: 1vh;

  182. }

  183. h3 {

  184.   text-align: center;

  185.   margin: 3rem 0 .75em;

  186. }

  187. hr {

  188.   height: .4rem;

  189.   width: .4rem;

  190.   border-radius: .4rem;

  191.   background: #07486c;

  192.   margin: 2.5rem auto;

  193. }

  194. time {

  195.   display: bloc;

  196.   margin-left: 0 !important;

  197. }

  198. ul, ol {

  199.   margin: 2rem;

  200. }

  201. ul {

  202.   list-style-type: square;

  203. }

  204. a {

  205.   text-decoration-skip-ink: auto;

  206.   text-decoration-thickness: 0.05em;

  207.   text-underline-offset: 0.09em;

  208. }

  209. article {

  210.   max-width: 50rem;

  211.   display: flex;

  212.   flex-direction: column;

  213.   margin: 2rem auto;

  214. }

  215.   article.single {

  216.     border-top: .2vh dotted #2d7474;

  217.     margin: -6rem auto 1rem auto;

  218.     background: #f0f0ea;

  219.     padding: 2rem;

  220.   }

  221.   article p:last-child {

  222.     margin-bottom: 1rem;

  223.   }

  224. p {

  225.   padding: 0 .5rem;

  226.   margin-left: 3rem;

  227. }

  228.   p + p,

  229.   figure + p {

  230.     margin-top: 2rem;

  231.   }

  232. 

  233. blockquote {

  234.   background-color: #e3e1e1;

  235.   border-left: .5vw solid #2d7474;

  236.   display: flex;

  237.   flex-direction: column;

  238.   align-items: center;

  239.   padding: 1rem;

  240.   margin: 1.5rem;

  241. }

  242.   blockquote cite {

  243.     font-style: italic;

  244.   }

  245.   blockquote p {

  246.     margin-left: 0;

  247.   }

  248. 

  249. figure {

  250.   border-top: .2vh solid #2d7474;

  251.   background-color: #e3e1e1;

  252.   text-align: center;

  253.   padding: 1.5rem 0;

  254.   margin: 1rem 0 0;

  255.   font-size: 1.5rem;

  256.   width: 100%;

  257. }

  258.   figure img {

  259.     max-width: 250px;

  260.     max-height: 250px;

  261.     border: .5vw solid #323a45;

  262.     padding: 1px;

  263.   }

  264. figcaption {

  265.   padding: 1rem;

  266.   line-height: 1.4;

  267. }

  268. aside {

  269.   display: flex;

  270.   flex-direction: column;

  271.   background-color: #e3e1e1;

  272.   padding: 1rem 0;

  273.   border-bottom: .2vh solid #07486c;

  274. }

  275.   aside p {

  276.     max-width: 50rem;

  277.     margin: 0 auto;

  278.   }

  279. 

  280. /* https://fvsch.com/code/css-locks/ */

  281. p, li, pre, code, kbd, samp, var, tt, time, details, figcaption {

  282.   font-size: 1rem;

  283.   line-height: calc( 1.5em + 0.2 * 1rem );

  284. }

  285. h1 {

  286.   font-size: 1.9rem;

  287.   line-height: calc( 1.2em + 0.2 * 1rem );

  288. }

  289. h2 {

  290.   font-size: 1.6rem;

  291.   line-height: calc( 1.3em + 0.2 * 1rem );

  292. }

  293. h3 {

  294.   font-size: 1.35rem;

  295.   line-height: calc( 1.4em + 0.2 * 1rem );

  296. }

  297. @media (min-width: 20em) {

  298.   /* The (100vw - 20rem) / (50 - 20) part

  299.      resolves to 0-1rem, depending on the

  300.      viewport width (between 20em and 50em). */

  301.   p, li, pre, code, kbd, samp, var, tt, time, details, figcaption {

  302.     font-size: calc( 1rem + .6 * (100vw - 20rem) / (50 - 20) );

  303.     line-height: calc( 1.5em + 0.2 * (100vw - 50rem) / (20 - 50) );

  304.     margin-left: 0;

  305.   }

  306.   h1 {

  307.     font-size: calc( 1.9rem + 1.5 * (100vw - 20rem) / (50 - 20) );

  308.     line-height: calc( 1.2em + 0.2 * (100vw - 50rem) / (20 - 50) );

  309.   }

  310.   h2 {

  311.     font-size: calc( 1.5rem + 1.5 * (100vw - 20rem) / (50 - 20) );

  312.     line-height: calc( 1.3em + 0.2 * (100vw - 50rem) / (20 - 50) );

  313.   }

  314.   h3 {

  315.     font-size: calc( 1.35rem + 1.5 * (100vw - 20rem) / (50 - 20) );

  316.     line-height: calc( 1.4em + 0.2 * (100vw - 50rem) / (20 - 50) );

  317.   }

  318. }

  319. @media (min-width: 50em) {

  320.   /* The right part of the addition *must* be a

  321.      rem value. In this example we *could* change

  322.      the whole declaration to font-size:2.5rem,

  323.      but if our baseline value was not expressed

  324.      in rem we would have to use calc. */

  325.   p, li, pre, code, kbd, samp, var, tt, time, details, figcaption {

  326.     font-size: calc( 1rem + .6 * 1rem );

  327.     line-height: 1.5em;

  328.   }

  329.   p, li, pre, details {

  330.     margin-left: 3rem;

  331.   }

  332.   h1 {

  333.     font-size: calc( 1.9rem + 1.5 * 1rem );

  334.     line-height: 1.2em;

  335.   }

  336.   h2 {

  337.     font-size: calc( 1.5rem + 1.5 * 1rem );

  338.     line-height: 1.3em;

  339.   }

  340.   h3 {

  341.     font-size: calc( 1.35rem + 1.5 * 1rem );

  342.     line-height: 1.4em;

  343.   }

  344.   figure img {

  345.     max-width: 500px;

  346.     max-height: 500px;

  347.   }

  348. }

  349. 

  350. figure.unsquared {

  351.   margin-bottom: 1.5rem;

  352. }

  353.   figure.unsquared img {

  354.     height: inherit;

  355.   }

  356. 

  357. 

  358. 

  359. @media print {

  360.   body { font-size: 100%; }

  361.   a:after { content: " (" attr(href) ")"; }

  362.   a, a:link, a:visited, a:after {

  363.     text-decoration: underline;

  364.     text-shadow: none !important;

  365.     background-image: none !important;

  366.     background: white;

  367.     color: black;

  368.   }

  369.   abbr[title] { border-bottom: 0; }

  370.   abbr[title]:after { content: " (" attr(title) ")"; }

  371.   img { page-break-inside: avoid; }

  372.   @page { margin: 2cm .5cm; }

  373.   h1, h2, h3 { page-break-after: avoid; }

  374.   p3 { orphans: 3; widows: 3; }

  375.   img {

  376.     max-width: 250px !important;

  377.     max-height: 250px !important;

  378.   }

  379.   nav, aside { display: none; }

  380. }

  381. 

  382. ul.with_columns {

  383.   column-count: 1;

  384. }

  385. @media (min-width: 20em) {

  386.   ul.with_columns {

  387.     column-count: 2;

  388.   }

  389. }

  390. @media (min-width: 50em) {

  391.   ul.with_columns {

  392.     column-count: 3;

  393.   }

  394. }

  395. ul.with_two_columns {

  396.   column-count: 1;

  397. }

  398. @media (min-width: 20em) {

  399.   ul.with_two_columns {

  400.     column-count: 1;

  401.   }

  402. }

  403. @media (min-width: 50em) {

  404.   ul.with_two_columns {

  405.     column-count: 2;

  406.   }

  407. }

  408. 

  409. .gallery {

  410.   display: flex;

  411.   flex-wrap: wrap;

  412.   justify-content: space-around;

  413. }

  414.   .gallery figure img {

  415.     margin-left: 1rem;

  416.     margin-right: 1rem;

  417.   }

  418.   .gallery figure figcaption {

  419.     font-family: 'ConcourseT3'

  420.   }

  421. 

  422. footer {

  423.   font-family: 'ConcourseT3';

  424.   display: flex;

  425.   flex-direction: column;

  426.   border-top: 3px solid white;

  427.   padding: 4rem 0;

  428.   background-color: #07486c;

  429.   color: white;

  430. }

  431.   footer > * {

  432.     max-width: 50rem;

  433.     margin: 0 auto;

  434.   }

  435.   footer a {

  436.     color: #f1c40f;

  437.   }

  438.   footer .avatar {

  439.     width: 200px;

  440.     height: 200px;

  441.     border-radius: 50%;

  442.     float: left;

  443.     -webkit-shape-outside: circle();

  444.     shape-outside: circle();

  445.     margin-right: 2rem;

  446.     padding: 2px 5px 5px 2px;

  447.     background: white;

  448.     border-left: 1px solid #f1c40f;

  449.     border-top: 1px solid #f1c40f;

  450.     border-right: 5px solid #f1c40f;

  451.     border-bottom: 5px solid #f1c40f;

  452.   }

  453. </style>

  454. 

  455. <h1>

  456.   <span><a id="jumper" href="#jumpto" title="Un peu perdu ?">?</a></span>

  457.   The Planet Needs a New Internet (archive)

  458.   <time>Pour la pérennité des contenus liés. Non-indexé, retrait sur simple email.</time>

  459. </h1>

  460. <section>

  461.   <article>

  462.     <h3><a href="https://earther.gizmodo.com/the-planet-needs-a-new-internet-1837101745">Source originale du contenu</a></h3>

  463.     <p>When climate change comes for our <a href="https://earther.gizmodo.com/more-than-half-of-wild-coffee-species-could-go-extinct-1831807896" rel="nofollow">coffee</a> and our <a href="https://earther.gizmodo.com/move-over-rose-climate-change-will-mean-new-wines-1821740888" rel="nofollow">wine</a>, we’ll moan about it on Twitter, read about it on our favorite websites, and watch diverting videos on YouTube to fill the icy hole in our hearts. We’ll do all this until the websites go dark and the networks go down because eventually, climate change will come for our internet, too.<br/></p>

  464. 

  465. <p>That is, unless we can get the web ready for the coming storms. </p>

  466. 

  467. <p>Huge changes will be needed because right now, the internet is unsustainable. On the one hand, rising sea levels threaten to swamp the cables and stations that transmit the web to our homes; rising temperatures could make it more costly to run the data centers handling ever-increasing web traffic; wildfires could burn it all down. On the other, all of those data centers, computers, smartphones, and other internet-connected devices take a prodigious amount of energy to build and to run, thus contributing to global warming and hastening our collective demise.</p>

  468. 

  469. <p>To save the internet and ourselves, we’ll need to harden and relocate the infrastructure we’ve built, find cleaner ways to power the web, and reimagine how we interact with the digital world. Ultimately, we need to recognize that our tremendous consumption of online content isn’t free of consequences—if we’re not paying, the planet is.</p>

  470. 

  471. <aside class="pullquote align--center"><span class="pullquote__helper"/><span class="pullquote__content">To save the internet and ourselves, we’ll need to harden and relocate the infrastructure we’ve built, find cleaner ways to power the web, and reimagine how we interact with the digital world.</span><span class="pullquote__helper"/></aside>

  472. 

  473. <h3><strong>Drowning infrastructure</strong></h3>

  474. 

  475. <p>You probably don’t think about it when you’re liking a photo or reading an article, but everything you do online is underpinned by a globe-spanning labyrinth of <a href="http://internetatlas.org/" target="_blank" rel="noopener">physical infrastructure</a>. There are the data centers hosting the web and managing enormous flows of information on the daily. There are the fiber cables transmitting data to into our homes and offices, and even across oceans. There are cell towers sending and receiving countless calls and texts on the daily.</p>

  476. 

  477. <p>By and large, this infrastructure wasn’t built with a changing climate in mind. Researchers and companies are only now starting to explore how threatened it is, but what they’ve found so far is alarming. </p>

  478. 

  479. <p>Take a <a href="https://ix.cs.uoregon.edu/~ram/papers/ANRW-2018.pdf" target="_blank" rel="noopener">study</a> published last year by researchers at the University of Oregon and the University of Wisconsin-Madison. The authors decided to examine the internet’s vulnerability to sea level rise by overlaying projections of coastal inundation from the National Oceanic Atmospheric Administration with internet infrastructure data compiled by <a href="http://internetatlas.org/" target="_blank" rel="noopener">Internet Atlas</a>. They found that within the next 15 years, in a scenario that projects about a foot of sea level rise by then, 4,067 miles of fiber conduit cables are likely to be permanently underwater. In New York, Los Angeles, and Seattle, the rising seas could drown roughly 20 percent of all metro fiber conduit. These are the lines that physically ferry our Internet traffic from place to place. Another 1,101 “nodes”—the buildings or places where cables rise out of the ground, which often house computer servers, routers, and network switches to move our data around—are also expected to be swamped. </p>

  480. 

  481. <p>And that’s just in the United States. As far as senior study author Paul Barford knows, this vulnerability hasn’t been systematically studied elsewhere. But he expects to find a similar situation around the world. </p>

  482. 

  483. <p>“There’s a huge amount of human population that lives within close proximity of coastlines, and communications infrastructure has been deployed to support their needs,” Barford told Gizmodo. <strong> </strong></p>

  484. 

  485. <p>Barford was reluctant to speculate how big of an internet disruption the coming cable inundation could cause. Conduits are <a href="https://www.idacs.uk.com/images/uploads/downloads/Datwyler_WP_Water_Impact_FO_2014.pdf" target="_blank" rel="noopener">typically sheathed in a tough, water-resistant</a> polyethylene tube, and unlike electrical wires, the fiber ribbons inside <a href="https://www.idacs.uk.com/images/uploads/downloads/Datwyler_WP_Water_Impact_FO_2014.pdf" target="_blank" rel="noopener">can handle some water intrusion</a>. But, as the study puts it, “most of the deployed conduits are not designed to be under water permanently.” If water molecules work their way into fiber micro-cracks, that could cause their signal to degrade. Electrical connections to the fiber cables could be fried, and if a submerged cable froze, the fibers could physically break.</p>

  486. 

  487. <p>Nobody knows how long it would take the damage to unfold. But Barford suspects that much of the at-risk infrastructure ultimately will have to be hardened in place or redeployed on higher ground. “It’s gonna be a major amount of work,” he said.</p>

  488. 

  489. <p>Gizmodo reached out to telecommunications companies flagged by the study as having the most vulnerable infrastructure to learn if this issue was on their radar. Several didn’t respond, one said they aren’t doing anything about the threat, and another indicated their networks would be fine because of “proper redundancy and route diversity.”</p>

  490. 

  491. <p>Dave Schaeffer, CEO of telecommunications company Cogent, expressed confidence in the fortitude of the cables. But Schaeffer did say there’s reason to worry about those places<strong> </strong>where the cables come out of the ground. </p>

  492. 

  493. <p>“Those would be impacted directly if those buildings came underwater,” he said, adding that while most nodes in their network sit least 20 feet above sea level, more powerful storm surges could pose a growing threat. The company got a taste of what may be to come during superstorm Sandy, when a network hub housed at 10 Pine Street in New York City was inundated by storm surge and the company was forced to move its generator and a fuel tank to a higher floor, a process that took several months.</p>

  494. 

  495. <p>At least one telecommunications company is now explicitly planning for future climate disruptions. Earlier this year AT&amp;T <a href="https://gizmodo.com/at-t-uses-supercomputer-to-map-out-how-climate-change-w-1834056763" target="_blank" rel="noopener">partnered with Argonne National Labs</a> to build a “Climate Change Analysis Tool,” which Chief Sustainability Officer Charlene Lake told Gizmodo will allow the company “to visualize the risks of sea-level rise—at the neighborhood level and 30 years into the future—so we can make the adaptations that are necessary today in order to help ensure resilience.” Lake added that AT&amp;T is also piloting the tool for high winds and storm surges, and in the future plans to incorporate other climate impacts, like drought and more severe wildfires. </p>

  496. 

  497. <p>Barford also flagged the threat of wildfires and storm surges as two areas of future investigation for his group. Then there’s the fact that climate change is driving temperatures up, which could  increase the need for cooling at data centers, particularly those built in warm climates.</p>

  498. 

  499. <p>Ironically, in a world where these energy-intensive facilities have to draw even <em>more</em> power to stay cool during, say, a heat wave, local grids potentially could be placed at greater risk of brownouts, like the one that <a href="https://www.nytimes.com/2019/07/21/nyregion/nyc-heat-wave.html" target="_blank" rel="noopener">affected 50,000 customers in New York City last month</a>. And while it’s purely hypothetical,<strong> </strong>if a major data center went dark, that could lead to widespread service disruptions. </p>

  500. 

  501. <p>As Barford put it, “there are cascading effects here that are complicated and deserve attention.”</p>

  502. 

  503. <h3><strong>Skyrocketing energy use</strong></h3>

  504. 

  505. <p>The internet may be threatened by climate change, but it’s hardly an innocent victim. Our collective addiction to the digital realm has an enormous climate impact. </p>

  506. 

  507. <p>“The digital mythology is built on words like cloud,” <a href="https://theshiftproject.org/en/team/" target="_blank" rel="noopener">Maxime Efoui</a>, an engineer and researcher at the French think-tank Shift Project, told Gizmodo. “Something that isn’t really real. That’s how we picture it.”</p>

  508. 

  509. <p>The reality, though, is that it takes loads of energy to stream all those on-demand videos and back up all those photos to the cloud. Anders Andrae, Senior Expert of Life Cycle Assessment at Huawei, told Gizmodo that the internet as a whole—including the energy used to power data centers, networks, and individual devices, as well as the energy used during the manufacturing of those devices—is responsible for about 7 percent of global electricity consumption, with power demands growing at around 8 percent per year. A <a href="https://theshiftproject.org/en/article/unsustainable-use-online-video/" target="_blank" rel="noopener">report</a> the Shift Project published in July found that digital technologies now accounts for 4 percent of the world’s greenhouse gas emissions—more than the entire aviation sector. And that footprint could double to 8 percent by 2025. </p>

  510. 

  511. <aside class="pullquote align--center"><span class="pullquote__helper"/><span class="pullquote__content">“...people seem to be astonished by the fact that servers run on electricity and electricity comes often from fossil fuels.” </span><span class="pullquote__helper"/></aside>

  512. 

  513. <p>Gary Cook, an IT sector analyst with Greenpeace, said this footprint is being driven by skyrocketing data demands, particularly in more affluent countries. There are numerous culprits here, including the shift to next-generation networks like 5G which will allow for greater data flows, the rise of artificial intelligence, the proliferation of an internet of things, all those energy-gobbling Bitcoin transactions, and online video streaming, which accounted for a full 60 percent of global web traffic in 2018, per the Shift Project. From storing the videos in data centers to transferring them to our computers and smartphones via cables and mobile networks, everything about watching videos online requires electricity, so much so that our collective streaming <a href="https://earther.gizmodo.com/your-binge-watching-of-netflix-and-porn-is-contributing-1836311475" rel="nofollow">emitted as much carbon</a> as all of Spain last year. </p>

  514. 

  515. <p>If these numbers seem shocking to you, well, you’re not alone. “Every single time I speak to people who work in tech, people seem to be astonished by the fact that servers run on electricity and electricity comes often from fossil fuels,” <a href="https://twitter.com/mrchrisadams" target="_blank" rel="noopener">Chris Adams</a>, a director at the <a href="https://www.thegreenwebfoundation.org/" target="_blank" rel="noopener">The Green Web Foundation</a>, a group that helps companies shift to renewable web hosting, told Gizmodo. </p>

  516. 

  517. <p>Clearly, the internet’s reliance on fossil fuels needs to change if we’re to stave off climate change’s worst impacts. An obvious place to start greening the energy supply is at those data centers, a huge and fast-growing piece of the pie that currently accounts for about 2 percent of global electricity use, according to a <a href="https://docs.google.com/document/d/1eCCb3rgqtQxcRwLdTr0P_hCK_drIZrm1Dpb4dlPeG6M/edit" target="_blank" rel="noopener">recent white paper</a>. </p>

  518. 

  519. <p>Encouragingly, some tech companies have begun to do so. Apple now <a href="https://earther.gizmodo.com/so-about-apples-100-percent-renewable-energy-announcem-1825173930" rel="nofollow">runs all of its data centers on renewables</a> that it either owns or purchases in local markets.<strong> </strong><a href="https://cloud.google.com/sustainability/" target="_blank" rel="noopener">Google</a> and <a href="https://blogs.microsoft.com/green/category/data-centers/" target="_blank" rel="noopener">Microsoft Azure</a>, two of the biggest cloud companies, are purchasing renewable energy credits to match their data center growth. This means as their electricity use rises, the companies are paying for an <a href="https://storage.googleapis.com/gweb-sustainability.appspot.com/pdf/24x7-carbon-free-energy-data-centers.pdf" target="_blank" rel="noopener">equal amount of renewable energy</a> to be built elsewhere. While this so-called offsetting strategy doesn’t eliminate the use of fossil fuel energy to power the data centers directly, both Google and Microsoft Azure say they have a long term goal of getting there. Google told Gizmodo that many of the company’s data centers already see “a strong degree of hourly matching with regional carbon-free energy,” while Microsoft Azure said it expects to source 60 percent of its data center electricity needs directly from renewables by the end of the year.</p>

  520. 

  521. <p>Because it boosts their bottom line, tech companies are also constantly improving data centers’ power use efficiency, and there’s <a href="https://www.mdpi.com/journal/electronics/special_issues/data_centers" target="_blank" rel="noopener">no shortage of ideas</a> for how to push things further. Google is now using AI to automate data center cooling, while Alibaba Cloud, a major cloud service in China, boasts an “<a href="https://www.alizila.com/alicloud-unveils-energy-efficient-data-center-video-2/" target="_blank" rel="noopener">immersion liquid cooling technology</a>” that it says can reduce data center cooling needs by up to 90 percent. Some researchers have even suggested new <a href="https://www.infoq.com/presentations/vision-climate-change/" target="_blank" rel="noopener">data centers be built in Greenland</a>, where A.C. needs would be minimal and clean hydropower is abundant.</p>

  522. 

  523. <p>However,<strong> </strong>Anne Currie, an engineer, science fiction author, and advocate for greening data centers, cautioned that efficiency improvements alone won’t clean up the internet, because the more efficient things are, the more <a href="https://en.wikipedia.org/wiki/Jevons_paradox" target="_blank" rel="noopener">we use them</a>.<strong> </strong>“We just need to make it socially unacceptable to be hosting the internet on fossil fuels,” Currie said.</p>

  524. 

  525. <p>And most experts Gizmodo spoke with agreed that the tech industry isn’t moving in that direction fast enough. Disturbingly, Amazon Web Services, the world’s largest cloud provider, has since late 2014 tripled its data center operations in Virginia, a state gets just a <a href="https://www.eia.gov/state/print.php?sid=VA" target="_blank" rel="noopener">small fraction of its power</a> from renewable wind and solar, according to a <a href="https://www.greenpeace.org/usa/reports/click-clean-virginia/" target="_blank" rel="noopener">recent report</a> by Greenpeace.<strong> </strong>AWS has also come under fire for its lack of transparency surrounding climate issues, including failing to report energy consumption and carbon emissions figures. (Amazon has said it will <a href="https://www.cnbc.com/2019/03/08/jeff-bezos-to-end-secrecy-over-amazons-role-in-carbon-emissions.html" target="_blank" rel="noopener">start reporting its carbon footprint</a> this year.)</p>

  526. 

  527. <p>Reached for comment, Amazon Web Services called the Greenpeace report’s data on its energy consumption and renewables mix “inaccurate”, adding that the report overstates “both AWS’s current and projected energy use” and “does not properly highlight” the company’s <a rel="nofollow" data-amazonasin="" data-amazonsubtag="[t|link[p|1837101745[au|1506793228[b|gizmodo[lt|text" data-amazontag="earther-20" href="https://aws.amazon.com/about-aws/sustainability/?tag=earther-20&amp;ascsubtag=71da5491bfead53031899bf25a8035789a8d9bd3">investments in solar projects</a> in Virginia. (Greenpeace asserts AWS’ data center growth in Virginia “far exceeds” these investments.) AWS added that it remains “firmly committed” to achieving its goal of 100 percent renewable energy for its global infrastructure, noting that it exceeded 50 percent renewable energy in 2018. </p>

  528. 

  529. <p>AWS has not stated when it aims to reach its 100 percent goal, and did not offer a target date, nor a date when one might be announced, when Gizmodo asked. Orion Stanger, a software engineer and member of Amazon Employees for Climate Justice, an employee-led organization that sprung up late last year to push Amazon to take more aggressive action on climate change, said Amazon’s continued failure to put a date on that goal is a problem.</p>

  530. 

  531. <p> “We could even go backwards to 20 percent [renewables] and then by some later date hit 100 percent and that would still qualify under the goal we’ve set,” Stanger told Gizmodo. He’d like to see his company set science-based targets around emissions reductions throughout its operation, including at data centers.</p>

  532. 

  533. <p>“We really want Amazon to lead on climate,” Stanger went on. “It’s been very much a follower in this space.”</p>

  534. 

  535. <p><a href="https://medium.com/@PaulDJohnston" target="_blank" rel="noopener">Paul Johnston</a>, a former AWS employee and green data center advocate,<strong> </strong>felt that unless companies are fined for their impact or otherwise incentivized to switch to renewables, the energy transition won’t keep pace with what science says is needed to avoid the worst impacts of climate change. </p>

  536. 

  537. <p>“I don’t think there’s any way around it,” he said when asked if government regulation will be necessary to compel companies to make the necessary shifts. </p>

  538. 

  539. <p>For some data centers, more regulation finally may be on the horizon. In July, Amsterdam, reportedly the <a href="https://www.dutchdatacenters.nl/en/dutchdatacenters2019/" target="_blank" rel="noopener">largest data center hub</a> in Europe, placed a temporary moratorium on building new data centers until some ground rules could be established concerning their operation. The city <a href="https://www.amsterdam.nl/bestuur-organisatie/college/wethouder/marieke-doorninck/persberichten/regie-vestiging-datacenters-amsterdam/" target="_blank" rel="noopener">wants to set requirements</a> that data centers use clean energy, and it wants the facilities to capture the prodigious waste heat they produce—yet another way data centers contribute to warming—and provide it to local citizens for free. </p>

  540. 

  541. <p>Amsterdam’s decision to pump the brakes on new data centers comes after the city’s data center power usage grew by a staggering <a href="https://www.dutchdatacenters.nl/en/dutchdatacenters2019/" target="_blank" rel="noopener">20 percent</a> last year. Cook was glad to see the city “stepping in and trying to do a reset on how to manage growth.”</p>

  542. 

  543. <p>“Voluntary stuff has taken us so far,” he said. “Ultimately we need to have government step in and level the playing field.”</p>

  544. 

  545. <h3><strong>Digital “sobriety”</strong></h3>

  546. 

  547. <p>Powering our data centers, networks, and cities with more renewable energy would go a long way toward reducing the internet’s climate impact. But the uncomfortable reality that it’s going to be hard to keep up in a world where we’re spending ever-increasing amounts of time watching videos and playing games online, browsing the web and scrolling our social media feeds (four activities that, together, make up nearly 90 percent of traffic downloaded from the web, according to a <a href="https://www.sandvine.com/hubfs/downloads/phenomena/2018-phenomena-report.pdf" target="_blank" rel="noopener">2018 report</a> by networking company Sandvine).</p>

  548. 

  549. <p>Some advocates say we need to pump the brakes on all this consumption. In its recent report about online video, the Shift Project is called for a revolution of “digital sobriety”, which Efoui described as implementing policies to constrain the internet’s growth in a world of finite resources.<br/></p>

  550. 

  551. <p>“If we really understand the gravity of the constraints that are coming to us and to our systems that we built... we have to take them into account,” he said. </p>

  552. 

  553. <p>How we’d actually go about constraining the web is an open question. Should governments impose emissions limits on server farms and data centers, and fine companies that exceed them? Should streaming services like Netflix encourage us to watch in standard definition over HD? Will grassroots campaigns to unplug spring up around the world, similarly to the emerging movement to <a href="https://www.theguardian.com/travel/2019/may/22/could-you-give-up-flying-meet-the-no-plane-pioneers" target="_blank" rel="noopener">give up flying</a>? Efoui thinks we will need to gather “a lot of solutions together” and that different places will adopt different strategies depending on their infrastructure and society’s needs.</p>

  554. 

  555. <p>The changes don’t all have to be huge. In fact, a burgeoning field of research known as sustainable interaction design is showing that small tweaks to apps and websites can have a serious impact on consumption. A <a href="https://research-information.bristol.ac.uk/en/publications/evaluating-sustainable-interaction-design-of-digital-services(e11edf4c-9676-4608-a122-38ff031ffdbc).html" target="_blank" rel="noopener">recent study</a> on YouTube found that simply allowing users to turn off video streaming when they’re listening to music could slash the service’s 11-million ton a year carbon footprint by up to 5 percent. As the researchers note, that’s “comparable in scale” to the climate benefits Google has achieved by purchasing renewables to power YouTube’s servers.</p>

  556. 

  557. <p>And it’s just one intervention. A notification that encourage social media users to take a break from feed-scrolling is another possibility. Or, websites could get rid of all those autoplay ads nobody asked for. <a href="https://www.lancaster.ac.uk/scc/about-us/people/kelly-widdicks" target="_blank" rel="noopener">Kelly Widdicks</a>, a PhD student at Lancaster University whose studies the impact of internet-enabled device use on society and the environment, noted that Facebook’s decision to start <a href="https://gizmodo.com/facebook-messenger-will-now-include-autoplaying-ads-wit-1826947581" target="_blank" rel="noopener">autoplaying ads everywhere</a> “increased traffic massively” for many users. </p>

  558. 

  559. <p>“Before you had to interact with the platform to watch something,” Efoui said. “Now you have to interact with the platform to stop watching. That’s actually a big change.”</p>

  560. 

  561. <p>Widdicks felt that companies might roll out some changes voluntarily if their customers made enough noise over, say, the health benefits of watching less. But she also saw value in thinking about what sorts of limits and restrictions ought to be imposed. Mike Hazas, a Reader at Lancaster University who studies the relationship between technology and sustainability, agreed, noting that researchers have estimated the internet could consume <a href="https://www.mdpi.com/2078-1547/6/1/117/htm" target="_blank" rel="noopener">more than a fifth</a> of the world’s electricity by 2030. </p>

  562. 

  563. <p>“If we were to double the airline industry by 2030, that’d be a major topic of discussion,” he said. (Indeed, it <a href="https://www.nationalgeographic.com/environment/urban-expeditions/transportation/air-travel-fuel-emissions-environment/" target="_blank" rel="noopener">has</a> <a href="https://www.forbes.com/sites/greatspeculations/2016/08/30/what-are-the-factors-behind-soaring-air-travel-growth/#61e4920d258d" target="_blank" rel="noopener">been</a>, <a href="https://www.theguardian.com/business/2013/jun/11/boeing-commercial-planes-double-asia-pacific" target="_blank" rel="noopener">for years</a>.)</p>

  564. 

  565. <p>No one can say what shape the future internet will take, but things can’t go on the way they are now. And while individual actions alone won’t get us out of this mess, if enough of us change our behavior it will make a difference. And there are plenty of places to start.</p>

  566. 

  567. <p>We can ease up on our social media use. We can think twice before letting that next episode autoplay, or kick it old school and return to broadcast, which Hazas described as “very efficient” compared to streaming. We can make sure to host websites and buy cloud space with companies that have demonstrated a real commitment to clean energy.</p>

  568. 

  569. <p>Most of all, Hazas said, it’s important that we “make a conscious decision” rather than allowing ourselves get swept along through an endless buffet of content. “These are very well designed services,” he said. “They keep us using them.”</p>

  570.   </article>

  571. </section>

  572. 

  573. 

  574. <nav id="jumpto">

  575.   <p>

  576.     <a href="/david/blog/">Accueil du blog</a> |

  577.     <a href="https://earther.gizmodo.com/the-planet-needs-a-new-internet-1837101745">Source originale</a> |

  578.     <a href="/david/stream/2019/">Accueil du flux</a>

  579.   </p>

  580. </nav>

  581. 

  582. <footer>

  583.   <div>

  584.     <img src="/static/david/david-larlet-avatar.jpg" loading="lazy" class="avatar" width="200" height="200">

  585.     <p>

  586.       Bonjour/Hi!

  587.       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>

  588.       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>).

  589.     </p>

  590.     <p>

  591.       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>.

  592.     </p>

  593.     

  594.     <p>

  595.       Voici quelques articles choisis :

  596.       <a href="/david/blog/2019/faire-equipe/" title="Accéder à l’article complet">Faire équipe</a>,

  597.       <a href="/david/blog/2018/bivouac-automnal/" title="Accéder à l’article complet">Bivouac automnal</a>,

  598.       <a href="/david/blog/2018/commodite-effondrement/" title="Accéder à l’article complet">Commodité et effondrement</a>,

  599.       <a href="/david/blog/2017/donnees-communs/" title="Accéder à l’article complet">Des données aux communs</a>,

  600.       <a href="/david/blog/2016/accompagner-enfant/" title="Accéder à l’article complet">Accompagner un enfant</a>,

  601.       <a href="/david/blog/2016/senior-developer/" title="Accéder à l’article complet">Senior developer</a>,

  602.       <a href="/david/blog/2016/illusion-sociale/" title="Accéder à l’article complet">L’illusion sociale</a>,

  603.       <a href="/david/blog/2016/instantane-scopyleft/" title="Accéder à l’article complet">Instantané Scopyleft</a>,

  604.       <a href="/david/blog/2016/enseigner-web/" title="Accéder à l’article complet">Enseigner le Web</a>,

  605.       <a href="/david/blog/2016/simplicite-defaut/" title="Accéder à l’article complet">Simplicité par défaut</a>,

  606.       <a href="/david/blog/2016/minimalisme-esthetique/" title="Accéder à l’article complet">Minimalisme et esthétique</a>,

  607.       <a href="/david/blog/2014/un-web-omni-present/" title="Accéder à l’article complet">Un web omni-présent</a>,

  608.       <a href="/david/blog/2014/manifeste-developpeur/" title="Accéder à l’article complet">Manifeste de développeur</a>,

  609.       <a href="/david/blog/2013/confort-convivialite/" title="Accéder à l’article complet">Confort et convivialité</a>,

  610.       <a href="/david/blog/2013/testament-numerique/" title="Accéder à l’article complet">Testament numérique</a>,

  611.       et <a href="/david/blog/" title="Accéder aux archives">bien d’autres…</a>

  612.     </p>

  613.     <p>

  614.       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>.

  615.     </p>

  616.     <p>

  617.       Je ne traque pas ta navigation mais mon

  618.       <abbr title="Alwaysdata, 62 rue Tiquetonne 75002 Paris, +33.184162340">hébergeur</abbr>

  619.       conserve des logs d’accès.

  620.     </p>

  621.   </div>

  622. </footer>

  623. <script type="text/javascript">

  624.   ;(_ => {

  625.     const jumper = document.getElementById('jumper')

  626.     jumper.addEventListener('click', e => {

  627.       e.preventDefault()

  628.       const anchor = e.target.getAttribute('href')

  629.       const targetEl = document.getElementById(anchor.substring(1))

  630.       targetEl.scrollIntoView({behavior: 'smooth'})

  631.     })

  632.   })()

  633. </script>