Explorar el Código

Use original text

Bob Mottram hace 7 años
padre
commit
4c5ef073f4
Se han modificado 2 ficheros con 73 adiciones y 73 borrados
  1. 10
    10
      doc/EN/mesh.org
  2. 63
    63
      website/EN/mesh.html

+ 10
- 10
doc/EN/mesh.org Ver fichero

@@ -28,16 +28,16 @@ Mesh networks are useful as a quick way to make a fully decentralised communicat
28 28
 
29 29
 The Freedombone mesh roughly follows MondoNet's ten social specifications:
30 30
 
31
- - *Decentralization*: The network cannot be consolodated or monopolized by design
32
- - *Accessibility*: low cost, freely downloadable, works on existing hardware, minimal learning curve
33
- - *Resistance*: to censorship
34
- - *Enables privacy*
35
- - *Secure*: against malicious attacks and also secure in terms of being reliable
36
- - *Scalable*: works for ten users or ten million
37
- - *Permanent*: even if users enter or exit the network remains viable
38
- - *Fast enough*: for at least "minimal participation in the political process". Enabling social uses like chat and VoIP
39
- - *Independence*: If every other network fails this system should still be usable
40
- - *Evolvable*: Software is open and modifiable over time as protocols change
31
+ - *Decentralized*: The network should not be operated, maintained, or in any way reliant upon a single or minimally differentiated set of entities or technologies. No individual, entity or group should be central to the network to the extent that their absence would measurably impact its functionality or scope. Network participation should not require access to fixed, physical infrastructure of any sort.
32
+ - *Universally Accessible*: The requisite technology and expertise required to participate in the network should be available at minimal cost and effort to every human being on the planet. Furthermore, all users should be able to extend the network’s content and functionality to suit their own needs, or those of others. No aspect of the network’s functioning should be reliant upon proprietary technologies, information or capital.
33
+ - *Censor-proof*: The network should be resistant to both regulatory and technical attempts to limit the nature of the information shared, restrict usage by given individuals or communities, or render the network, or any portion of it, inoperable or inaccessible.
34
+ - *Surveillance-proof*: The network should enable users to choose exactly what information they share with whom, and to participate anonymously if they so desire. Users should only have access to information if they are the designated recipients, or if it has been published openly.
35
+ - *Secure*: The network should be organized in a way that minimizes the risk of malicious attacks or engineering failure. Information exchanged on the network should meet or exceed the delivery rate and reliability of information exchanged via the Internet.
36
+ - *Scalable*: The network should be organized with the expectation that its scale could reach or even exceed that of today’s Internet. Special care should be taken to address to the challenge of maintaining efficiency without the presence of a centralized backbone.
37
+ - *Permanent*: The network’s density and redundancy should be great enough that, despite its ad hoc nature, it will persistently operate on a broad scale, and be available in full to any user within range of another peer.
38
+ - *Fast (enough)*: The network should always achieve whatever speed is required for a “bottom line” level of social and cultural participation. At present, we assert that the network’s data transfer rate should, at a minimum, be enough for voice-over-IP (VoIP) communications, and low-bitrate streaming video.
39
+ - *Independent*: While the network will have the capacity to exchange information with Internet users and nodes, it should be able to operate independently, as well. A large-scale failure or closure of Internet infrastructure and content should have minimal effect on the network’s operations.
40
+ - *Evolvable*: The network should be built with future development in mind. The platform should be flexible enough to support technologies, protocols and modes of usage that have not yet been developed.
41 41
 
42 42
 * What the system can do
43 43
 

+ 63
- 63
website/EN/mesh.html Ver fichero

@@ -3,7 +3,7 @@
3 3
 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
4 4
 <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
5 5
 <head>
6
-<!-- 2017-09-23 Sat 20:45 -->
6
+<!-- 2017-09-23 Sat 21:03 -->
7 7
 <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
8 8
 <meta name="viewport" content="width=device-width, initial-scale=1" />
9 9
 <title>&lrm;</title>
@@ -274,13 +274,13 @@ for the JavaScript code in this tag.
274 274
 </colgroup>
275 275
 <tbody>
276 276
 <tr>
277
-<td class="org-left"><a href="#org94582ff">What the system can do</a></td>
277
+<td class="org-left"><a href="#org64e0697">What the system can do</a></td>
278 278
 <td class="org-left">-</td>
279
-<td class="org-left"><a href="#orgbd7ef51">Disk Images</a></td>
279
+<td class="org-left"><a href="#orgdd28322">Disk Images</a></td>
280 280
 <td class="org-left">-</td>
281
-<td class="org-left"><a href="#org850e320">Building Disk Images</a></td>
281
+<td class="org-left"><a href="#orgba0cd17">Building Disk Images</a></td>
282 282
 <td class="org-left">-</td>
283
-<td class="org-left"><a href="#org5166206">How to use it</a></td>
283
+<td class="org-left"><a href="#orgfaea5db">How to use it</a></td>
284 284
 </tr>
285 285
 </tbody>
286 286
 </table>
@@ -298,21 +298,21 @@ The Freedombone mesh roughly follows MondoNet's ten social specifications:
298 298
 </p>
299 299
 
300 300
 <ul class="org-ul">
301
-<li><b>Decentralization</b>: The network cannot be consolodated or monopolized by design</li>
302
-<li><b>Accessibility</b>: low cost, freely downloadable, works on existing hardware, minimal learning curve</li>
303
-<li><b>Resistance</b>: to censorship</li>
304
-<li><b>Enables privacy</b></li>
305
-<li><b>Secure</b>: against malicious attacks and also secure in terms of being reliable</li>
306
-<li><b>Scalable</b>: works for ten users or ten million</li>
307
-<li><b>Permanent</b>: even if users enter or exit the network remains viable</li>
308
-<li><b>Fast enough</b>: for at least "minimal participation in the political process". Enabling social uses like chat and VoIP</li>
309
-<li><b>Independence</b>: If every other network fails this system should still be usable</li>
310
-<li><b>Evolvable</b>: Software is open and modifiable over time as protocols change</li>
301
+<li><b>Decentralized</b>: The network should not be operated, maintained, or in any way reliant upon a single or minimally differentiated set of entities or technologies. No individual, entity or group should be central to the network to the extent that their absence would measurably impact its functionality or scope. Network participation should not require access to fixed, physical infrastructure of any sort.</li>
302
+<li><b>Universally Accessible</b>: The requisite technology and expertise required to participate in the network should be available at minimal cost and effort to every human being on the planet. Furthermore, all users should be able to extend the network’s content and functionality to suit their own needs, or those of others. No aspect of the network’s functioning should be reliant upon proprietary technologies, information or capital.</li>
303
+<li><b>Censor-proof</b>: The network should be resistant to both regulatory and technical attempts to limit the nature of the information shared, restrict usage by given individuals or communities, or render the network, or any portion of it, inoperable or inaccessible.</li>
304
+<li><b>Surveillance-proof</b>: The network should enable users to choose exactly what information they share with whom, and to participate anonymously if they so desire. Users should only have access to information if they are the designated recipients, or if it has been published openly.</li>
305
+<li><b>Secure</b>: The network should be organized in a way that minimizes the risk of malicious attacks or engineering failure. Information exchanged on the network should meet or exceed the delivery rate and reliability of information exchanged via the Internet.</li>
306
+<li><b>Scalable</b>: The network should be organized with the expectation that its scale could reach or even exceed that of today’s Internet. Special care should be taken to address to the challenge of maintaining efficiency without the presence of a centralized backbone.</li>
307
+<li><b>Permanent</b>: The network’s density and redundancy should be great enough that, despite its ad hoc nature, it will persistently operate on a broad scale, and be available in full to any user within range of another peer.</li>
308
+<li><b>Fast (enough)</b>: The network should always achieve whatever speed is required for a “bottom line” level of social and cultural participation. At present, we assert that the network’s data transfer rate should, at a minimum, be enough for voice-over-IP (VoIP) communications, and low-bitrate streaming video.</li>
309
+<li><b>Independent</b>: While the network will have the capacity to exchange information with Internet users and nodes, it should be able to operate independently, as well. A large-scale failure or closure of Internet infrastructure and content should have minimal effect on the network’s operations.</li>
310
+<li><b>Evolvable</b>: The network should be built with future development in mind. The platform should be flexible enough to support technologies, protocols and modes of usage that have not yet been developed.</li>
311 311
 </ul>
312 312
 
313
-<div id="outline-container-org94582ff" class="outline-2">
314
-<h2 id="org94582ff">What the system can do</h2>
315
-<div class="outline-text-2" id="text-org94582ff">
313
+<div id="outline-container-org64e0697" class="outline-2">
314
+<h2 id="org64e0697">What the system can do</h2>
315
+<div class="outline-text-2" id="text-org64e0697">
316 316
 <ul class="org-ul">
317 317
 <li>Discovery of other users on the network</li>
318 318
 <li>Text based chat, one-to-one and in groups</li>
@@ -334,13 +334,13 @@ This system should be quite scalable. Both qTox and IPFS are based upon distribu
334 334
 </div>
335 335
 </div>
336 336
 
337
-<div id="outline-container-orgbd7ef51" class="outline-2">
338
-<h2 id="orgbd7ef51">Disk Images</h2>
339
-<div class="outline-text-2" id="text-orgbd7ef51">
337
+<div id="outline-container-orgdd28322" class="outline-2">
338
+<h2 id="orgdd28322">Disk Images</h2>
339
+<div class="outline-text-2" id="text-orgdd28322">
340 340
 </div>
341
-<div id="outline-container-orge807aa5" class="outline-3">
342
-<h3 id="orge807aa5">Writing many images quickly</h3>
343
-<div class="outline-text-3" id="text-orge807aa5">
341
+<div id="outline-container-org4767260" class="outline-3">
342
+<h3 id="org4767260">Writing many images quickly</h3>
343
+<div class="outline-text-3" id="text-org4767260">
344 344
 <p>
345 345
 There may be situations where you need to write the same disk image to multiple drives at the same time in order to maximize rate of deployment. In the instructions given below the <b>dd</b> command is used for writing to the target drive, but to write to multiple drives you can use a tool such as <a href="https://wiki.gnome.org/Apps/MultiWriter">GNOME MultiWriter</a>.
346 346
 </p>
@@ -364,9 +364,9 @@ Or on Debian based systems:
364 364
 </div>
365 365
 </div>
366 366
 </div>
367
-<div id="outline-container-org075c107" class="outline-3">
368
-<h3 id="org075c107">Client images</h3>
369
-<div class="outline-text-3" id="text-org075c107">
367
+<div id="outline-container-org186084e" class="outline-3">
368
+<h3 id="org186084e">Client images</h3>
369
+<div class="outline-text-3" id="text-org186084e">
370 370
 <div class="org-center">
371 371
 
372 372
 <div class="figure">
@@ -415,16 +415,16 @@ sudo dd <span class="org-variable-name">bs</span>=1M <span class="org-variable-n
415 415
 </div>
416 416
 </div>
417 417
 
418
-<div id="outline-container-orgfe93325" class="outline-3">
419
-<h3 id="orgfe93325">Router images</h3>
420
-<div class="outline-text-3" id="text-orgfe93325">
418
+<div id="outline-container-org91a4631" class="outline-3">
419
+<h3 id="org91a4631">Router images</h3>
420
+<div class="outline-text-3" id="text-org91a4631">
421 421
 <p>
422 422
 Routers are intended to build network coverage for an area using small and low cost hardware. You can bolt them to walls or leave them on window ledges. They don't have any user interface and their only job is to haul network traffic across the mesh and to enable peers to find each other via running bootstrap nodes for Tox and IPFS. Copy the image to a microSD card and insert it into the router, plug in an Atheros wifi dongle and power on. That should be all you need to do.
423 423
 </p>
424 424
 </div>
425
-<div id="outline-container-org75c8882" class="outline-4">
426
-<h4 id="org75c8882">Beaglebone Black</h4>
427
-<div class="outline-text-4" id="text-org75c8882">
425
+<div id="outline-container-orgfd78743" class="outline-4">
426
+<h4 id="orgfd78743">Beaglebone Black</h4>
427
+<div class="outline-text-4" id="text-orgfd78743">
428 428
 <div class="org-center">
429 429
 
430 430
 <div class="figure">
@@ -461,9 +461,9 @@ There is still a software freedom issue with the Beaglebone Black, but it doesn'
461 461
 </div>
462 462
 </div>
463 463
 
464
-<div id="outline-container-org850e320" class="outline-2">
465
-<h2 id="org850e320">Building Disk Images</h2>
466
-<div class="outline-text-2" id="text-org850e320">
464
+<div id="outline-container-orgba0cd17" class="outline-2">
465
+<h2 id="orgba0cd17">Building Disk Images</h2>
466
+<div class="outline-text-2" id="text-orgba0cd17">
467 467
 <p>
468 468
 It's better not to trust images downloaded from random places on the interwebs. Chances are that unless you are in the web of trust of the above GPG signatures then they don't mean very much to you. If you actually want something trustworthy then build the images from scratch. It will take some time. Here's how to do it.
469 469
 </p>
@@ -551,9 +551,9 @@ The resulting image can be copied to a microSD card, inserted into a Beaglebone
551 551
 </div>
552 552
 </div>
553 553
 
554
-<div id="outline-container-orgd61d85e" class="outline-2">
555
-<h2 id="orgd61d85e">Customisation</h2>
556
-<div class="outline-text-2" id="text-orgd61d85e">
554
+<div id="outline-container-org69c8170" class="outline-2">
555
+<h2 id="org69c8170">Customisation</h2>
556
+<div class="outline-text-2" id="text-org69c8170">
557 557
 <p>
558 558
 If you want to make your own specially branded version, such as for a particular event, then to change the default desktop backgrounds edit the images within <b>img/backgrounds</b> and to change the available avatars and desktop icons edit the images within <b>img/avatars</b>. Re-create disk images using the instructions shown previously.
559 559
 </p>
@@ -563,9 +563,9 @@ If you need particular <i>dconf</i> commands to alter desktop appearance or beha
563 563
 </p>
564 564
 </div>
565 565
 </div>
566
-<div id="outline-container-org5166206" class="outline-2">
567
-<h2 id="org5166206">How to use it</h2>
568
-<div class="outline-text-2" id="text-org5166206">
566
+<div id="outline-container-orgfaea5db" class="outline-2">
567
+<h2 id="orgfaea5db">How to use it</h2>
568
+<div class="outline-text-2" id="text-orgfaea5db">
569 569
 <p>
570 570
 When you first boot from the USB drive the system will create some encryption keys, assign a unique network address to the system and then reboot itself. When that's done you should see a prompt asking for a username. This username just makes it easy for others to initially find you on the mesh and will appear in the list of users.
571 571
 </p>
@@ -575,9 +575,9 @@ After a minute or two if you are within wifi range and there is at least one oth
575 575
 </p>
576 576
 </div>
577 577
 
578
-<div id="outline-container-orgd59bd1c" class="outline-3">
579
-<h3 id="orgd59bd1c">Boot trouble</h3>
580
-<div class="outline-text-3" id="text-orgd59bd1c">
578
+<div id="outline-container-org5f147aa" class="outline-3">
579
+<h3 id="org5f147aa">Boot trouble</h3>
580
+<div class="outline-text-3" id="text-org5f147aa">
581 581
 <p>
582 582
 If the system doesn't boot and reports an error which includes <b>/dev/mapper/loop0p1</b> then reboot with <b>Ctrl-Alt-Del</b> and when you see the grub menu press <b>e</b> and manually change <b>/dev/mapper/loop0p1</b> to <b>/dev/sdb1</b>, then press <b>Ctrl-x</b>. If that doesn't work then reboot and try <b>/dev/sdc1</b> instead.
583 583
 </p>
@@ -587,9 +587,9 @@ After the system has booted successfully the problem should resolve itself on su
587 587
 </p>
588 588
 </div>
589 589
 </div>
590
-<div id="outline-container-org3b0741c" class="outline-3">
591
-<h3 id="org3b0741c">Set the Date</h3>
592
-<div class="outline-text-3" id="text-org3b0741c">
590
+<div id="outline-container-orgfd3e367" class="outline-3">
591
+<h3 id="orgfd3e367">Set the Date</h3>
592
+<div class="outline-text-3" id="text-orgfd3e367">
593 593
 <p>
594 594
 On the ordinary internet the date and time of your system would be set automatically via NTP. But this is not the internet and so you will need to manually ensure that your date and time settings are correct. You might need to periodically do this if your clock drifts. It's not essential that the time on your system be highly accurate, but if it drifts too far or goes back to epoch then things could become a little confusing in regard to the order of blog posts.
595 595
 </p>
@@ -599,9 +599,9 @@ On the ordinary internet the date and time of your system would be set automatic
599 599
 </p>
600 600
 </div>
601 601
 </div>
602
-<div id="outline-container-org6008c57" class="outline-3">
603
-<h3 id="org6008c57">Check network status</h3>
604
-<div class="outline-text-3" id="text-org6008c57">
602
+<div id="outline-container-org323ecd1" class="outline-3">
603
+<h3 id="org323ecd1">Check network status</h3>
604
+<div class="outline-text-3" id="text-org323ecd1">
605 605
 <p>
606 606
 Unlike with ordinary wifi, on the mesh you don't get a signal strength icon and so it's not simple to see if you have a good connection.
607 607
 </p>
@@ -625,9 +625,9 @@ When you are finished close the window and then select the <i>Network Restart</i
625 625
 </div>
626 626
 </div>
627 627
 
628
-<div id="outline-container-org3edc276" class="outline-3">
629
-<h3 id="org3edc276">Chat System</h3>
630
-<div class="outline-text-3" id="text-org3edc276">
628
+<div id="outline-container-orgafa8a02" class="outline-3">
629
+<h3 id="orgafa8a02">Chat System</h3>
630
+<div class="outline-text-3" id="text-orgafa8a02">
631 631
 <p>
632 632
 Ensure that you're within wifi range of at least one other mesh peer (could be a router or client) and then you should see that the <i>Chat</i> and <i>Other Users</i> icons appear. Select the users icon and you should see a list of users on the mesh. Select the <i>Chat</i> icon and once you are connected you should see the status light turn green. If after a few minutes you don't get the green status light then try closing and re-opening the Tox chat application. Select the plus button to add a friend and then copy and paste in a Tox ID from the users list.
633 633
 </p>
@@ -686,9 +686,9 @@ At present video doesn't work reliably, but text and voice chat do work well.
686 686
 </div>
687 687
 </div>
688 688
 
689
-<div id="outline-container-org9d6ed6b" class="outline-3">
690
-<h3 id="org9d6ed6b">Social Network</h3>
691
-<div class="outline-text-3" id="text-org9d6ed6b">
689
+<div id="outline-container-orgb4914f7" class="outline-3">
690
+<h3 id="orgb4914f7">Social Network</h3>
691
+<div class="outline-text-3" id="text-orgb4914f7">
692 692
 <p>
693 693
 Patchwork is available as a social networking system for the mesh. Like all social network systems it has a stream of posts and you can follow or unfollow other users. You can also send private messages to other users with end-to-end encryption.
694 694
 </p>
@@ -723,9 +723,9 @@ The Secure Scuttlebutt protocol which Patchwork is based upon is intended to be
723 723
 </div>
724 724
 </div>
725 725
 
726
-<div id="outline-container-org12e7e50" class="outline-3">
727
-<h3 id="org12e7e50">Sharing Files</h3>
728
-<div class="outline-text-3" id="text-org12e7e50">
726
+<div id="outline-container-orgf20341a" class="outline-3">
727
+<h3 id="orgf20341a">Sharing Files</h3>
728
+<div class="outline-text-3" id="text-orgf20341a">
729 729
 <p>
730 730
 You can make files publicly available on the network simply by dragging and dropping them into the <i>Public</i> folder on the desktop. To view the files belonging to another user select the desktop icon called <i>Visit a site</i> and enter the username or Tox ID of the other user.
731 731
 </p>
@@ -740,9 +740,9 @@ You can make files publicly available on the network simply by dragging and drop
740 740
 </div>
741 741
 </div>
742 742
 
743
-<div id="outline-container-org1459c8a" class="outline-3">
744
-<h3 id="org1459c8a">Blogging</h3>
745
-<div class="outline-text-3" id="text-org1459c8a">
743
+<div id="outline-container-org01ecd64" class="outline-3">
744
+<h3 id="org01ecd64">Blogging</h3>
745
+<div class="outline-text-3" id="text-org01ecd64">
746 746
 <p>
747 747
 To create a blog post select the <i>Blog</i> icon on the desktop and then use the up and down cursor keys, space bar and enter key to add a new entry. Edit the title of the entry and add your text. You can also include photos if you wish - just copy them to the <b>CreateBlog/content/images</b> directory and then link to them as shown.
748 748
 </p>