davidbgk
/
larlet-fr-david-cache
Observar 1
Favorito 0
Fork 0
Código Versões 0 Atividade
A place to cache linked articles (think custom and personal wayback machine)
Você não pode selecionar mais de 25 tópicos Os tópicos devem começar com uma letra ou um número, podem incluir traços ('-') e podem ter até 35 caracteres.
81 Commits
1 Branch
Tag: e3ebffab27
Branches Tags
${ item.name }
Criar branch ${ searchTerm }
de e3ebffab27
${ noResults }
larlet-fr-david-cache/cache/d629418c0d8fcf72c54e0a3c27d.../index.html

index.html 47KB
Original Anotar Histórico

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697 
  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>How to Build a Low-tech 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="http://www.lowtechmagazine.com/2015/10/how-to-build-a-low-tech-internet.html">

  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.   How to Build a Low-tech 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="http://www.lowtechmagazine.com/2015/10/how-to-build-a-low-tech-internet.html">Source originale du contenu</a></h3>

  463.     <p>More than half of the global population does not have access to the "worldwide" web. Up to now, the internet is mainly an urban phenomenon, especially in "developing" countries. Telecommunication companies are usually reluctant to extend their network outside cities due to a combination of high infrastructure costs, low population density, limited ability to pay for services, and an unreliable or non-existent electricity infrastructure. Even in remote regions of "developed" countries, internet connectivity isn't always available.</p>

  464. 

  465. <p>Internet companies such as Facebook and Google regularly make headlines with plans for connecting these remote regions to the internet. Facebook tries to achieve this with drones, while Google counts on high-altitude balloons. There are major technological challenges, but the main objection to these plans is their commercial character. Obviously, Google and Facebook want to connect more people to the internet because that would increase their revenues. Facebook especially receives lots of criticism because their network promotes their own site in particular, and blocks most other internet applications. [<span>1</span>]</p>

  466. 

  467. <p>Meanwhile, several research groups and network enthusiasts have developed and implemented much cheaper alternative network technologies to solve these issues. Although these low-tech networks have proven their worth, they have received much less attention. Contrary to the projects of internet companies, they are set up by small organisations or by the users themselves. This guarantees an open network that benefits the users instead of a handful of corporations. At the same time, these low-tech networks are very energy efficient.</p>

  468. 

  469. <p><span><strong>WiFi-based Long Distance Networks</strong></span></p>

  470. 

  471. <p>Most low-tech networks are based on WiFi, the same technology that allows mobile access to the internet in most western households. As we have seen in the previous article, <a href="http://www.lowtechmagazine.com/2015/10/the-4g-network-thats-already-there.html" target="_self">sharing these devices could provide free mobile access across densely populated cities</a>. But the technology can be equally useful in sparsely populated areas. Although the WiFi-standard was developed for short-distance data communication (with a typical range of about 30 metres), its reach can be extended through modifications of the Media Access Control (MAC) layer in the networking protocol, and through the use of range extender amplifiers and directional antennas. [<span>2</span>]</p>

  472. 

  473. <blockquote>

  474. <p><span>Although the WiFi-standard was developed for short-distance data communication, its reach can be extended to cover distances of more than 100 kilometres.</span></p>

  475. </blockquote>

  476. 

  477. <p>The longest unamplified WiFi link is a 384 km wireless point-to-point connection between Pico El Águila and Platillón in Venezuela, established a few years ago. [<span>3,4</span>] However, WiFi-based long distance networks usually consist of a combination of shorter point-to-point links, each between a few kilometres and one hundred kilometers long at most. These are combined to create larger, multihop networks. Point-to-points links, which form the backbone of a long range WiFi network, are combined with omnidirectional antennas that distribute the signal to individual households (or public institutions) of a community.</p>

  478. 

  479. <p><a href="http://krisdedecker.typepad.com/.a/6a00e0099229e8883301b8d14fd748970c-pi"><img title="Tegola project low-tech internet" src="http://krisdedecker.typepad.com/.a/6a00e0099229e8883301b8d14fd748970c-500wi" alt="Tegola project low-tech internet"/></a><span>Picture: A relay with three point-to-point links and three sectoral antennae. <a href="http://www.tegola.org.uk/howto/network-planning.html" target="_blank">Tegola</a>.</span></p>

  480. 

  481. <p>Long-distance WiFi links require line of sight to make a connection -- in this sense, the technology resembles the <a href="http://www.lowtechmagazine.com/2007/12/email-in-the-18.html" target="_blank">18th century optical telegraph</a>. [<span>5</span>] If there's no line of sight between two points, a third relay is required that can see both points, and the signal is sent to the intermediate relay first. Depending on the terrain and particular obstacles, more hubs may be necessary. [<span>6</span>]</p>

  482. 

  483. <p>Point-to-point links typically consist of two directional antennas, one focused on the next node and the other on the previous node in the network. Nodes can have multiple antennas with one antenna per fixed point-to-point link to each neighbour. [<span>7</span>] This allows mesh routing protocols that can dynamically select which links to choose for routing among the available ones. [<span>8</span>]</p>

  484. 

  485. <blockquote>

  486. <p><span>Long-distance WiFi links require line of sight to make a connection -- in this sense, the technology resembles the 18th century optical telegraph.</span></p>

  487. </blockquote>

  488. 

  489. <p>Distribution nodes usually consist of a sectoral antenna (a small version of the things you see on mobile phone masts) or a conventional WiFi-router, together with a number of receivers in the community. [<span>6</span>] For short distance WiFi-communication, there is no requirement for line of sight between the transmitter and the receiver. [<span>9</span>]</p>

  490. 

  491. <p>To provide users with access to the worldwide internet, a long range WiFi network should be connected to the main backbone of the internet using at least one "backhaul" or "gateway node". This can be a dial-up or broadband connection (DSL, fibre or satellite). If such a link is not established, users would still be able to communicate with each other and view websites set up on local servers, but they would not be able to access the internet. [<span>10</span>]</p>

  492. 

  493. <p><span><strong>Advantages of Long Range WiFi</strong></span></p>

  494. 

  495. <p><a href="http://krisdedecker.typepad.com/.a/6a00e0099229e8883301b8d16a5210970c-pi"><img title="Litebeam M5" src="http://krisdedecker.typepad.com/.a/6a00e0099229e8883301b8d16a5210970c-200wi" alt="Litebeam M5"/></a>Long range WiFi offers high bandwidth (up to 54 Mbps) combined with very low capital costs. Because the WiFi standard enjoys widespread acceptance and has huge production volumes, off-the-shelf antennas and wireless cards can be bought for very little money. [<span>11</span>] Alternatively, components can be put together <a href="http://roelof.info/projects/%282014%29Pretty_Fly_For_A_Wifi/" target="_blank">from discarded materials</a> such as old routers, satellite dish antennas and laptops. Protocols like WiLDNet run on a 266 Mhz processor with only 128 MB memory, so an old computer will do the trick. [<span>7</span>]</p>

  496. 

  497. <p>The WiFi-nodes are lightweight and don't need expensive towers -- further decreasing capital costs, and minimizing the impact of the structures to be built. [<span>7</span>] More recently, single units that combine antenna, wireless card and processor have become available. These are very convenient for installation. To build a relay, one simply connects such units together with ethernet cables that carry both signal and power. [<span>6</span>] The units can be mounted in towers or slim masts, given that they offer little windload. [<span>3</span>] Examples of suppliers of long range WiFi components are <a href="https://www.ubnt.com/" target="_blank">Ubiquity</a>, <a href="http://www.alvarion.com/" target="_blank">Alvarion</a> and <a href="http://www.mikrotik.com/" target="_blank">MikroTik</a>, and <a href="https://www.simplewifi.com/" target="_blank">simpleWiFi</a>.</p>

  498. 

  499. <blockquote>

  500. <p><span>Long Range WiFi makes use of unlicensed spectrum and offers high bandwidth, low capital costs, easy installation, and low power requirements.</span></p>

  501. </blockquote>

  502. 

  503. <p>Long range WiFi also has low operational costs due to low power requirements. A typical mast installation consisting of two long distance links and one or two wireless cards for local distribution consumes around 30 watts. [<span>6,12</span>] In several low-tech networks, nodes are entirely powered by solar panels and batteries. Another important advantage of long range WiFi is that it makes use of unlicensed spectrum (2.4 and 5 GHz), and thus avoids negotiations with telecom operators and government. This adds to the cost advantage and allows basically anyone to start a WiFi-based long distance network. [<span>9</span>]</p>

  504. 

  505. <p><strong><span>Long Range WiFi Networks in Poor Countries</span></strong></p>

  506. 

  507. <p>The first long range WiFi networks were set up ten to fifteen years ago. In poor countries, two main types have been built. The first is aimed at providing internet access to people in remote villages. An example is the Akshaya network in India, which covers the entire Kerala State and is one of the largest wireless networks in the world. The infrastructure is built around approximately 2,500 "computer access centers", which are open to the local population -- direct ownership of computers is minimal in the region. [<span>13</span>]</p>

  508. 

  509. <p>Another example, also in India, are the AirJaldi networks which provide internet access to approximately 20,000 users in six states, all in remote regions and on difficult terrain. Most nodes in this network are solar-powered and the distance between them can range up to 50 km or more. [<span>14</span>] In some African countries, local WiFi-networks distribute internet access from a satellite gateway. [<span>15,16</span>]</p>

  510. 

  511. <p><a href="http://krisdedecker.typepad.com/.a/6a00e0099229e8883301b8d1579486970c-pi"><img title="Airjaldi" src="http://krisdedecker.typepad.com/.a/6a00e0099229e8883301b8d1579486970c-800wi" alt="Airjaldi" border="0"/></a></p>

  512. 

  513. <p><span>A node in the AirJaldi network. Picture: AirJaldi.<br/></span></p>

  514. 

  515. <p>A second type of long distance WiFi network in poor countries is aimed at providing telemedicine to remote communities. In remote regions, health care is often provided through health posts scarcely equipped and attended by health technicians who are barely trained. [<span>17</span>] Long-range WiFi networks can connect urban hospitals with these outlying health posts, allowing doctors to remotely support health technicians using high-resolution file transfers and real-time communication tools based on voice and video.</p>

  516. 

  517. <p>An example is the link between Cabo Pantoja and Iquitos in the Loreto province in Peru, which was established in 2007. The 450 km network consists of 17 towers which are 16 to 50 km apart. The line connects 15 medical outposts in remote villages with the main hospital in Iquitos and is aimed at remote diagnosis of patients. [<span>17,18</span>] All equipment is powered by solar panels. [<span>18,19</span>] Other succesful examples of long range WiFi telemedicine networks have been built in India, Malawi and Ghana. [<span>20,21</span>]</p>

  518. 

  519. <p><span><strong>WiFi-Based Community Networks in Europe<br/></strong></span></p>

  520. 

  521. <p>The low-tech networks in poor countries are set up by NGO's, governments, universities or businesses. In contrast, most of the WiFi-based long distance networks in remote regions of rich countries are so-called "community networks": the users themselves build, own, power and maintain the infrastructure. Similar to the shared wireless approach in cities, reciprocal resource sharing forms the basis of these networks: participants can set up their own node and connect to the network (for free), as long as their node also allows traffic of other members. Each node acts as a WiFi routing device that provides IP forwarding services and a data link to all users and nodes connected to it. [<span>8,22</span>]</p>

  522. 

  523. <blockquote>

  524. <p><span>In a community network, the users themselves build, own, power and maintain the infrastructure.</span></p>

  525. </blockquote>

  526. 

  527. <p>Consequently, with each new user, the network becomes larger. There is no a-priori overall planning. A community network grows bottom-up, driven by the needs of its users, as nodes and links are added or upgraded following demand patterns. The only consideration is to connect a node from a new participant to an existing one. As a node is powered on, it discovers it neighbours, attributes itself a unique IP adress, and then establishes the most appropriate routes to the rest of the network, taking into account the quality of the links. Community networks are open to participation to everyone, sometimes according to an open peering agreement. [<span>8,9,19,22</span>]</p>

  528. 

  529. <p><a class="asset-img-link" href="http://krisdedecker.typepad.com/.a/6a00e0099229e8883301b7c7e2d9d7970b-pi"><img class="asset  asset-image at-xid-6a00e0099229e8883301b7c7e2d9d7970b image-full img-responsive" title="Guifi in en rond barcelona" src="http://krisdedecker.typepad.com/.a/6a00e0099229e8883301b7c7e2d9d7970b-800wi" alt="Guifi in en rond barcelona" border="0"/></a></p>

  530. 

  531. <p><span>Wireless links in the Spanish Guifi network. <a href="http://iuliinet.github.io/presentazione_ottobre_2014/img/barcellona.jpg" target="_blank">Credit</a>.<br/></span></p>

  532. 

  533. <p>Despite the lack of reliable statistics, community networks seem to be rather succesful, and there are several large ones in Europe, such as <a href="https://guifi.net/" target="_blank">Guifi.net</a> (Spain), <a href="http://www.awmn.gr/content.php?s=ce506a41ab245641d6934638c6f6f107" target="_blank">Athens Wireless Metropolitan Network</a> (Greece), <a href="http://www.funkfeuer.at/" target="_blank">FunkFeuer</a> (Austria), and <a href="http://freifunk.net/en/" target="_blank">Freifunk</a> (Germany). [<span>8,22,23,24</span>] The Spanish network  is the largest WiFi-based long distance network in the world with more than 50,000 kilometres of links, although a small part is based on optic fibre links. Most of it is located in the Catalan Pyrenees, one of the least populated areas in Spain. The network was initiated in 2004 and now has close to 30,000 nodes, up from 17,000 in 2012. [<span>8,22</span>]</p>

  534. 

  535. <p>Guifi.net provides internet access to individuals, companies, administrations and universities. In principle, the network is installed, powered and maintained by its users, although volunteer teams and even commercial installers are present to help. Some nodes and backbone upgrades have been succesfully crowdfunded by indirect beneficiaries of the network. [<span>8,22</span>]</p>

  536. 

  537. <p><span><strong>Performance of Low-tech Networks</strong></span></p>

  538. 

  539. <p>So how about the performance of low-tech networks? What can you do with them? The available bandwidth per user can vary enormously, depending on the bandwidth of the gateway node(s) and the number of users, among other factors. The long-distance WiFi networks aimed at telemedicine in poor countries have few users and a good backhaul, resulting in high bandwidth (+ 40 Mbps). This gives them a similar performance to fibre connections in the developed world. A study of (a small part of) the Guifi.net community network, which has dozens of gateway nodes and thousands of users, showed an average throughput of 2 Mbps, which is comparable to a relatively slow DSL connection. Actual throughput per user varies from 700 kbps to 8 Mbps. [<span>25</span>]</p>

  540. 

  541. <blockquote>

  542. <p><span>The available bandwidth per user can vary enormously, depending on the bandwidth of the gateway node(s) and the number of users, among other factors</span></p>

  543. </blockquote>

  544. 

  545. <p>However, the low-tech networks that distribute internet access to a large user base in developing countries can have much more limited bandwidth per user. For example, a university campus in Kerala (India) uses a 750 kbps internet connection that is shared across 3,000 faculty members and students operating from 400 machines, where during peak hours nearly every machine is being used. </p>

  546. 

  547. <p>Therefore, the worst-case average bandwidth available per machine is approximately 1.9 kbps, which is slow even in comparison to a dial-up connection (56 kbps). And this can be considered a really good connectivity compared to typical rural settings in poor countries. [26] To make matters worse, such networks often have to deal with an intermittent power supply.</p>

  548. 

  549. <div id="photo-xid-6a00e0099229e8883301b8d16a5899970c" class="photo-wrap photo-xid-6a00e0099229e8883301b8d16a5899970c photo-full "><a class="asset-img-link" href="http://krisdedecker.typepad.com/.a/6a00e0099229e8883301b8d16a5899970c-pi"><img class="asset  asset-image at-xid-6a00e0099229e8883301b8d16a5899970c img-responsive" title="Antena-guifi-floresta" src="http://krisdedecker.typepad.com/.a/6a00e0099229e8883301b8d16a5899970c-800wi" alt="Antena-guifi-floresta" border="0"/></a>

  550. <p id="caption-xid-6a00e0099229e8883301b8d16a5899970c" class="photo-caption caption-xid-6a00e0099229e8883301b8d16a5899970c"><span>A node in the Spanish Guifi community network.</span></p>

  551. </div>

  552. 

  553. <p>Under these circumstances, even the most common internet applications have poor performance, or don't work at all. The communication model of the internet is based on a set of network assumptions, called the TCP/IP protocol suite. These include the existence of a bi-directional end-to-end path between the source (for example a website's server) and the destination (the user's computer), short round-trip delays, and low error rates.</p>

  554. 

  555. <p>Many low-tech networks in poor countries do not comform to these assumptions. They are characterized by intermittent connectivity or "network partitioning" -- the absence of an end-to-end path between source and destination -- long and variable delays, and high error rates. [<span>21,27,28</span>]</p>

  556. 

  557. <p><span><strong>Delay-Tolerant Networks</strong></span></p>

  558. 

  559. <p>Nevertheless, even in such conditions, the internet could work perfectly fine. The technical issues can be solved by moving away from the always-on model of traditional networks, and instead design networks based upon asynchronous communication and intermittent connectivity. These so-called "delay-tolerant networks" (DTNs) have their own specialized protocols overlayed on top of the lower protocols and do not utilize TCP. They overcome the problems of intermittent connectivity and long delays by using store-and-forward message switching.</p>

  560. 

  561. <p>Information is forwarded from a storage place on one node to a storage place on another node, along a path that <em>eventually</em> reaches its destination. In contrast to traditional internet routers, which only store incoming packets for a few milliseconds on memory chips, the nodes of a delay-tolerant network have persistent storage (such as hard disks) that can hold information indefinitely. [<span>27,28</span>]</p>

  562. 

  563. <blockquote>

  564. <p><span>Delay-tolerant networks combine well with renewable energy: solar panels or wind turbines could power network nodes only when the sun shines or the wind blows, eliminating the need for energy storage.</span></p>

  565. </blockquote>

  566. 

  567. <p>Delay-tolerant networks don't require an end-to-end path between source and destination. Data is simply transferred from node to node. If the next node is unavailable because of long delays or a power outage, the data is stored on the hard disk until the node becomes available again. While it might take a long time for data to travel from source to destination, a delay-tolerant network ensures that it will eventually arrive.</p>

  568. 

  569. <p>Delay-tolerant networks further decrease capital costs and energy use, leading to the most efficient use of scarce resources. They keep working with an intermittent energy supply and they combine well with renewable energy sources: solar panels or wind turbines could power network nodes only when the sun shines or the wind blows, eliminating the need for energy storage.</p>

  570. 

  571. <p><span><strong>Data Mules</strong></span></p>

  572. 

  573. <p>Delay-tolerant networking can take surprising forms, especially when they take advantage of some non-traditional means of communication, such as "data mules". [<span>11,29</span>] In such networks, conventional transportation technologies -- buses, cars, motorcycles, trains, boats, airplanes -- are used to ferry messages from one location to another in a store-and-forward manner.</p>

  574. 

  575. <p>Examples are DakNet and KioskNet, which use buses as data mules. [<span>30-34</span>] In many developing regions, rural bus routes regularly visit villages and towns that have no network connectivity. By equipping each vehicle with a computer, a storage device and a mobile WiFi-node on the one hand, and by installing a stationary WiFi-node in each village on the other hand, the local transport infrastructure can substitute for a wireless internet link. [<span>11</span>]</p>

  576. 

  577. <p><a href="http://krisdedecker.typepad.com/.a/6a00e0099229e8883301b7c7da1fc2970b-pi"><img title="Airjaldi epostman" src="http://krisdedecker.typepad.com/.a/6a00e0099229e8883301b7c7da1fc2970b-500wi" alt="Airjaldi epostman"/></a><span>Picture: AirJaldi.</span></p>

  578. 

  579. <p>Outgoing data (such as sent emails or requests for webpages) is stored on local computers in the village until the bus comes withing range. At this point, the fixed WiFi-node of the local computer automatically transmits the data to the mobile WiFi-node of the bus. Later, when the bus arrives at a hub that is connected to the internet, the outgoing data is transmitted from the mobile WiFi-node to the gateway node, and then to the internet. Data sent to the village takes the opposite route. The bus -- or data -- driver doesn't require any special skills and is completely oblivious to the data transfers taking place. He or she does not need to do anything other than come in range of the nodes. [<span>30,31</span>]</p>

  580. 

  581. <blockquote>

  582. <p><span>In a data mules network, the local transport infrastructure substitutes for a wireless internet link.</span></p>

  583. </blockquote>

  584. 

  585. <p>The use of data mules offers some extra advantages over more "sophisticated" delay-tolerant networks. A "drive-by" WiFi network allows for small, low-cost and low-power radio devices to be used, which don't require line of sight and consequently no towers -- further lowering capital costs and energy use compared to other low-tech networks. [<span>30,31,32</span>]</p>

  586. 

  587. <p>The use of short-distance WiFi-links also results in a higher bandwidth compared to long-distance WiFi-links, which makes data mules better suited to transfer larger files. On average, 20 MB of data can be moved in each direction when a bus passes a fixed WiFi-node. [<span>30,32</span>] On the other hand, latency (the time interval between sending and receiving data) is usually higher than on long-range WiFi-links. A single bus passing by a village once a day gives a latency of 24 hours.</p>

  588. 

  589. <p><strong><span>Delay-Tolerant Software</span><br/></strong></p>

  590. 

  591. <p>Obviously, a delay-tolerant network (DTN) -- whatever its form -- also requires new software: applications that function without a connected end-to-end networking path. [<span>11</span>] Such custom applications are also useful for synchronous, low bandwidth networks. Email is relatively easy to adapt to intermittent connectivity, because it's an asynchronous communication method by itself. A DTN-enabled email client stores outgoing messages until a connection is available. Although emails may take longer to reach their destination, the user experience doesn't really change.</p>

  592. 

  593. <p><a class="asset-img-link" href="http://krisdedecker.typepad.com/.a/6a00e0099229e8883301b7c7e07dac970b-pi"><img class="asset  asset-image at-xid-6a00e0099229e8883301b7c7e07dac970b img-responsive" title="Freifunk berlijn" src="http://krisdedecker.typepad.com/.a/6a00e0099229e8883301b7c7e07dac970b-500wi" alt="Freifunk berlijn"/></a></p>

  594. 

  595. <p><span>A Freifunk WiFi-node is installed in Berlin, Germany. Picture:<a href="https://upload.wikimedia.org/wikipedia/commons/5/51/Freifunk-Initiative_in_Berlin-Kreuzberg.jpg" target="_blank"> Wikipedia Commons</a>.</span></p>

  596. 

  597. <p>Browsing and searching the web requires more adaptations. For example, most search engines optimize for speed, assuming that a user can quickly look through the returned links and immediately run a second modified search if the first result is inadequate. However, in intermittent networks, multiple rounds of interactive search would be impractical. [<span>26,35</span>] Asynchronous search engines optimize for bandwith rather than response time. [<span>26,30,31,35,36</span>] For example, RuralCafe desynchronizes the search process by performing many search tasks in an offline manner, refining the search request based on a database of similar searches. The actual retrieval of information using the network is only done when absolutely necessary.</p>

  598. 

  599. <blockquote>

  600. <p><span>Many internet applications could be adapted to intermittent networks, such as webbrowsing, email, electronic form filling, interaction with e-commerce sites, blogsoftware, large file downloads, or social media.</span></p>

  601. </blockquote>

  602. 

  603. <p>Some DTN-enabled browsers download not only the explicitly requested webpages but also the pages that are linked to by the requested pages. [<span>30</span>] Others are optimized to return low-bandwidth results, which are achieved by filtering, analysis, and compression on the server site. A similar effect can be achieved through the use of a service like <a href="http://www.loband.org/loband/" target="_blank">Loband</a>, which strips webpages of images, video, advertisements, social media buttons, and so on, merely presenting the textual content. [<span>26</span>]</p>

  604. 

  605. <p>Browsing and searching on intermittent networks can also be improved by local caching (storing already downloaded pages) and prefetching (downloading pages that might be retrieved in the future). [206] Many other internet applications could also be adapted to intermittent networks, such as electronic form filling, interaction with e-commerce sites, blogsoftware, large file downloads, social media, and so on. [<span>11,30</span>] All these applications would remain possible, though at lower speeds.</p>

  606. 

  607. <p><span><strong>Sneakernets</strong></span></p>

  608. 

  609. <p>Obviously, real-time applications such as internet telephony, media streaming, chatting or videoconferencing are impossible to adapt to intermittent networks, which provide only asynchronous communication. These applications are also difficult to run on synchronous networks that have limited bandwidth. Because these are the applications that are in large part responsible for the growing energy use of the internet, one could argue that their incompatibility with low-tech networks is actually a good thing (see the <a href="http://www.lowtechmagazine.com/2015/10/can-the-internet-run-on-renewable-energy.html" target="_self">previous article</a>).</p>

  610. 

  611. <p>Furthermore, many of these applications could be organized in different ways. While real-time voice or video conversations won't work, it's perfectly possible to send and receive voice or video messages. And while streaming media can't happen, downloading music albums and video remains possible. Moreover, these files could be "transmitted" by the most low-tech internet technology available: a sneakernet. In a sneakernet, digital data is "wirelessly" transmitted using a storage medium such as a hard disk, a USB-key, a flash card, or a CD or DVD. Before the arrival of the internet, all computer files were exchanged via a sneakernet, using tape or floppy disks as a storage medium.</p>

  612. 

  613. <p><a class="asset-img-link" href="http://krisdedecker.typepad.com/.a/6a00e0099229e8883301b8d16a5d62970c-pi"><img class="asset  asset-image at-xid-6a00e0099229e8883301b8d16a5d62970c img-responsive" title="Freight train" src="http://krisdedecker.typepad.com/.a/6a00e0099229e8883301b8d16a5d62970c-500wi" alt="Freight train"/></a></p>

  614. 

  615. <p><span>Stuffing a cargo train full of digital storage media would beat any digital network in terms of speed, cost and energy efficiency. Picture: Wikipedia Commons.</span></p>

  616. 

  617. <p>Just like a data mules network, a sneakernet involves a vehicle, a messenger on foot, or an animal (such as a <a href="http://www.lowtechmagazine.com/2009/02/sneakernet-beats-internet.html" target="_self">carrier pigeon</a>). However, in a sneakernet there is no automatic data transfer between the mobile node (for instance, a vehicle) and the stationary nodes (sender and recipient). Instead, the data first have to be transferred from the sender's computer to a portable storage medium. Then, upon arrival, the data have to be transferred from the portable storage medium to the receiver's computer. [<span>30</span>] A sneakernet thus requires manual intervention and this makes it less convenient for many internet applications.</p>

  618. 

  619. <p>There are exceptions, though. For example, a movie doesn't have to be transferred to the hard disk of your computer in order to watch it. You play it straight from a portable hard disk or slide a disc into the DVD-player. Moreover, a sneakernet also offers an important advantage: of all low-tech networks, it has the most bandwidth available. This makes it perfectly suited for the distribution of large files such as movies or computer games. In fact, when very large files are involved, a sneakernet even beats the fastest fibre internet connection. At lower internet speeds, sneakernets can be advantageous for much smaller files.</p>

  620. 

  621. <p>Technological progress will not lower the advantage of a sneakernet. Digital storage media evolve at least as fast as internet connections and they both improve communication in an equal way.</p>

  622. 

  623. <p><span><strong>Resilient Networks<br/></strong></span></p>

  624. 

  625. <p>While most low-tech networks are aimed at regions where the alternative is often no internet connection at all, their usefulness for well-connected areas cannot be overlooked. The internet as we know it in the industrialized world is a product of an abundant energy supply, a robust electricity infrastructure, and sustained economic growth. This "high-tech" internet might offer some fancy advantages over the low-tech networks, but it cannot survive if these conditions change. This makes it extremely vulnerable.</p>

  626. 

  627. <blockquote>

  628. <p><span>The internet as we know it in the industrialized world is a product of an abundant energy supply, a robust electricity infrastructure, and sustained economic growth. It cannot survive if these conditions change.<br/></span></p>

  629. </blockquote>

  630. 

  631. <p>Depending on their level of resilience, low-tech networks can remain in operation when the supply of fossil fuels is interrupted, when the electricity infrastructure deteriorates, when the economy grinds to a halt, or if other calamities should hit. Such a low-tech internet would allow us to surf the web, send and receive e-mails, shop online, share content, and so on. Meanwhile, data mules and sneakernets could serve to handle the distribution of large files such as videos. Stuffing a cargo vessel or a train full of digital storage media would beat any digital network in terms of speed, cost and energy efficiency. And if such a transport infrastructure would no longer be available, we could still rely on messengers on foot, <a href="http://www.lowtechmagazine.com/2014/05/modular-cargo-cycles.html" target="_self">cargo bikes</a> and <a href="http://www.lowtechmagazine.com/sailing-ships/" target="_self">sailing vessels</a>.</p>

  632. 

  633. <p>Such a hybrid system of online and offline applications would remain a very powerful communication network -- unlike anything we had even in the late twentieth century. Even if we envision a doom scenario in which the wider internet infrastructure would disintegrate, isolated low-tech networks would still be very useful local and regional communication technologies. Furthermore, they could obtain content from other remote networks through the exchange of portable storage media. The internet, it appears, can be as low-tech or high-tech as we can afford it to be.</p>

  634.   </article>

  635. </section>

  636. 

  637. 

  638. <nav id="jumpto">

  639.   <p>

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

  641.     <a href="http://www.lowtechmagazine.com/2015/10/how-to-build-a-low-tech-internet.html">Source originale</a> |

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

  643.   </p>

  644. </nav>

  645. 

  646. <footer>

  647.   <div>

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

  649.     <p>

  650.       Bonjour/Hi!

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

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

  653.     </p>

  654.     <p>

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

  656.     </p>

  657.     

  658.     <p>

  659.       Voici quelques articles choisis :

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  676.     </p>

  677.     <p>

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

  679.     </p>

  680.     <p>

  681.       Je ne traque pas ta navigation mais mon

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

  683.       conserve des logs d’accès.

  684.     </p>

  685.   </div>

  686. </footer>

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

  688.   ;(_ => {

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

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

  691.       e.preventDefault()

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

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

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

  695.     })

  696.   })()

  697. </script>