Ver código fonte

Merge branch 'stretch' of https://github.com/bashrc/freedombone

Bob Mottram 7 anos atrás
pai
commit
685b9da446
46 arquivos alterados com 2572 adições e 1004 exclusões
  1. 9
    331
      doc/EN/mesh.org
  2. 35
    0
      doc/EN/mesh_capabilities.org
  3. 19
    0
      doc/EN/mesh_custom.org
  4. 149
    0
      doc/EN/mesh_images.org
  5. 51
    0
      doc/EN/mesh_philosophic.org
  6. 189
    0
      doc/EN/mesh_usage.org
  7. BIN
      img/avatars/icon_blog.png
  8. BIN
      img/avatars/icon_connect.png
  9. BIN
      img/avatars/icon_cryptpad.png
  10. BIN
      img/avatars/icon_help.png
  11. BIN
      img/avatars/icon_new_identity.png
  12. BIN
      img/avatars/icon_restart_network.png
  13. BIN
      img/avatars/icon_sites.png
  14. BIN
      img/avatars/icon_social.png
  15. BIN
      img/avatars/icon_users.png
  16. BIN
      img/avatars/icon_wifi.png
  17. BIN
      img/avatars/icons_chat.png
  18. BIN
      img/avatars/icons_invite.png
  19. BIN
      img/icon_blog.png
  20. BIN
      img/icon_connect.png
  21. BIN
      img/icon_cryptpad.png
  22. BIN
      img/icon_help.png
  23. BIN
      img/icon_new_identity.png
  24. BIN
      img/icon_restart_network.png
  25. BIN
      img/icon_sites.png
  26. BIN
      img/icon_social.png
  27. BIN
      img/icon_users.png
  28. BIN
      img/icon_wifi.png
  29. BIN
      img/icons_chat.png
  30. BIN
      img/icons_invite.png
  31. BIN
      img/logo_blue.png
  32. BIN
      img/logo_white_large.png
  33. BIN
      img/mesh_architecture1.jpg
  34. BIN
      img/mesh_architecture2.jpg
  35. BIN
      img/mesh_architecture3.jpg
  36. BIN
      img/mesh_architecture_vpn.jpg
  37. BIN
      img/postactiv_sprite2.png
  38. 16
    20
      src/freedombone-image-customise
  39. 6
    6
      src/freedombone-image-mesh
  40. 1
    1
      src/meshavahi
  41. 10
    646
      website/EN/mesh.html
  42. 300
    0
      website/EN/mesh_capabilities.html
  43. 282
    0
      website/EN/mesh_custom.html
  44. 495
    0
      website/EN/mesh_images.html
  45. 374
    0
      website/EN/mesh_philosophic.html
  46. 636
    0
      website/EN/mesh_usage.html

+ 9
- 331
doc/EN/mesh.org Ver arquivo

@@ -14,345 +14,23 @@
14 14
 <center><h1>Mesh Network</h1></center>
15 15
 #+end_export
16 16
 
17
-#+BEGIN_CENTER
18
-[[file:images/mesh_screenshot.jpg]]
19
-#+END_CENTER
20
-
21
-|------------------------+---+-------------+---+----------------------+---+---------------|
22
-| [[What the system can do]] | - | [[Disk Images]] | - | [[Building Disk Images]] | - | [[How to use it]] |
23
-|------------------------+---+-------------+---+----------------------+---+---------------|
24
-
25
-#+begin_quote
26
- "/I see mesh networks naturally evolving to become the dominant form of network over the next few decades, because it’s the most practical solution to a number of problems that will have to be solved in order to build the VR web as well as to connect the entire world to the internet. Centralized networks are only possible in highly developed countries with existing infrastructures like power and telephone grids, as well as roads. You can’t build a tower where you don’t have either power or access. For vast areas of the world, mesh networks will be the only feasible solution./" -- Valkyrie Ice
27
-#+end_quote
28
-
29 17
 The Freedombone Mesh is a wireless solution for autonomous or internet connected communication that can be rapidly deployed in temporary, emergency or post-disaster situations where internet access is unavailable or compromised.
30 18
 
31
-Mesh networks are useful as a quick way to make a fully decentralised communications system which is not connected to or reliant upon the internet. Think festivals, hacker conferences, onboard ships at sea, disaster/war zones, small businesses who don't want the overhead of server maintenance, protests, remote areas of the world, temporary "digital blackouts", scientific expeditions and off-world space colonies.
32
-
33
-If an internet connection is available then it can make use of that, but otherwise it can still work regardless of whether the internet exists. So it's not dependent upon ISPs and additional infrastructure other than USB drives isn't required.
34
-
35
-Systems only need to be within wifi range of each other for the mesh to be created, so it can be an very convenient way to create a local communications network.
36
-
37
-The Freedombone mesh roughly follows MondoNet's ten social specifications:
38
-
39
- - *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.
40
- - *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.
41
- - *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.
42
- - *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.
43
- - *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.
44
- - *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.
45
- - *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.
46
- - *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.
47
- - *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.
48
- - *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.
49
-
50
-* What the system can do
51
-
52
- - Discovery of other users on the network
53
- - Text based chat, one-to-one and in groups
54
- - Voice chat (VoIP) and video calls
55
- - Private and public sharing of files
56
- - Blogging
57
- - Collaborative editing of documents and presentations
58
- - Creating and broadcasting audio media/podcasts
59
- - Social network stream. Follow/unfollow other peers
60
- - No network administration required
61
- - No servers
62
- - Internet connection is optional
63
- - Works from bootable USB drives or microSD drives
64
- - Data is mesh routed between systems
65
- - Private communications is end-to-end secured and forward secret
66
- - Publicly shared data is /content addressable/
67
-
68
-This system should be quite scalable. Both qTox and IPFS are based upon distributed hash tables (DHT) so that each peer does not need to store the full index of data for the entire network. Gossiping between SSB peers may be slower, but the [[https://en.wikipedia.org/wiki/Small-world_network][small world effect]] will presumably still make for quite efficient delivery in a large network. Caching or pinning of IPFS data and its content addressability means that if a file or blog becomes popular then performance should improve as the number of downloads increases, which is the opposite of the client/server paradigm.
69
-
70
-* Disk Images
71
-** Writing many images quickly
72
-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 *dd* command is used for writing to the target drive, but to write to multiple drives you can use a tool such as [[https://wiki.gnome.org/Apps/MultiWriter][GNOME MultiWriter]].
73
-
74
-For example on Arch/Parabola:
75
-
76
-#+begin_src bash
77
-sudo pacman -S gnome-multi-writer
78
-#+end_src
79
-
80
-Or on Debian based systems:
81
-
82
-#+begin_src bash
83
-sudo apt-get install gnome-multi-writer
84
-#+end_src
85
-
86
-The MultiWriter tool is also available within mesh client images, so that you can use mesh systems to create more copies of the same system.
87
-** Client images
19
+ * [[./mesh_philosophic.html][Philosophic]]
20
+ * [[./mesh_capabilities.html][Capabilities]]
21
+ * [[./mesh_images.html][Disk images and how to build them]]
22
+ * [[./mesh_custom.html][Customisation]]
23
+ * [[./mesh_usage.html][How to use it]]
88 24
 
89 25
 #+BEGIN_CENTER
90
-[[file:images/mesh_netbook.jpg]]
26
+[[file:images/mesh_architecture1.jpg]]
91 27
 #+END_CENTER
92 28
 
93
-"Client" isn't exactly the right term, but it's a mesh peer with a user interface. These images can be copied to a USB drive, then you can plug it into a laptop/netbook/desktop machine and boot from it. You will probably also need an Atheros USB wifi dongle (the black protruding object on the left side of the netbook in the picture above), because most built-in wifi usually requires proprietary firmware. In the commands below substitute /dev/sdX with the USB drive device, excluding any trailing numbers (eg. /dev/sdb). The USB drive you're copying to will need to be at least 8GB in size.
94
-
95
-#+begin_src bash
96
-sudo apt-get install xz-utils wget
97
-wget https://freedombone.net/downloads/current/freedombone-meshclient-i386.img.xz
98
-wget https://freedombone.net/downloads/current/freedombone-meshclient-i386.img.xz.sig
99
-gpg --verify freedombone-meshclient-i386.img.xz.sig
100
-sha256sum freedombone-meshclient-i386.img.xz
101
-61e474afae14774d7aa479b6727fd5e77bdc1854e547b3c5b630bf10542a9581
102
-unxz freedombone-meshclient-i386.img.xz
103
-sudo dd if=/dev/zero of=/dev/sdX bs=1M count=8
104
-sudo dd bs=1M if=freedombone-meshclient-i386.img of=/dev/sdX conv=fdatasync
105
-#+end_src
106
-
107
-To get a number of systems onto the mesh repeat the /dd/ command to create however many bootable USB drives you need.
108
-
109
-If you're in an emergency and don't have Atheros wifi dongles then there is also an "insecure" image which contains some proprietary wifi drivers which may work with a wider range of laptops. Proprietary drivers *are not recommended* because they're unsupportable and may be exploitable or contain malicious antifeatures which fundamentally compromise the security of the network. However, the trade-off between security/maintainability and simply having the ability to communicate at all may be a valid one in some situations.
110
-
111
-#+begin_src bash
112
-sudo apt-get install xz-utils wget
113
-wget https://freedombone.net/downloads/current/freedombone-meshclient-insecure-i386.img.xz
114
-wget https://freedombone.net/downloads/current/freedombone-meshclient-insecure-i386.img.xz.sig
115
-gpg --verify freedombone-meshclient-insecure-i386.img.xz.sig
116
-sha256sum freedombone-meshclient-insecure-i386.img.xz
117
-fec843303d7d280859f75f7a8edccd70512915a34d4cc0787b5de7d8fbde5c81
118
-unxz freedombone-meshclient-insecure-i386.img.xz
119
-sudo dd if=/dev/zero of=/dev/sdX bs=1M count=8
120
-sudo dd bs=1M if=freedombone-meshclient-insecure-i386.img of=/dev/sdX conv=fdatasync
121
-#+end_src
122
-
123
-** Router images
124
-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.
125
-*** Beaglebone Black
126
-#+BEGIN_CENTER
127
-[[file:images/mesh_router.jpg]]
128
-#+END_CENTER
129
-
130
-The above picture shows a Beaglebone Black with the image copied onto a microSD card (there's no need to do anything with the internal EMMC). A USB Atheros wifi adaptor with a large antenna is attached and in this case power is from the mains, although it could be from a battery or solar power system capable of supplying 5 volts and maybe 1A (depending upon how active the router is).
131
-
132
-#+begin_src bash
133
-sudo apt-get install xz-utils wget
134
-wget https://freedombone.net/downloads/current/freedombone-mesh_beaglebone-armhf.img.xz
135
-wget https://freedombone.net/downloads/current/freedombone-mesh_beaglebone-armhf.img.xz.sig
136
-gpg --verify freedombone-mesh_beaglebone-armhf.img.xz.sig
137
-sha256sum freedombone-mesh_beaglebone-armhf.img.xz
138
-45f131995e2f77188e7ddaf2b42ca3d8d48d821d37c7a31a21e2e6dcceaf510d
139
-unxz freedombone-mesh_beaglebone-armhf.img.xz
140
-sudo dd bs=1M if=freedombone-mesh_beaglebone-armhf.img of=/dev/sdX conv=fdatasync
141
-#+end_src
142
-
143
-If you have a few Beaglebone Blacks to use as routers then repeat the /dd/ command to create however many microSD cards you need.
144
-
145
-There is still a software freedom issue with the Beaglebone Black, but it doesn't prevent you from running a fully free system on the board. The TI AM335X SOC has a PowerVR SGX530 GPU which will only run with a proprietary blob, but this would only be an issue for systems with a monitor or LCD screen attached running a desktop environment which also needs GPU acceleration. For "headless" systems such as servers or mesh routers this isn't a problem.
146
-
147
-* Building Disk Images
148
-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.
149
-
150
-First you will need to create an image. On a Debian based system (tested on Debian Stretch):
151
-
152
-#+begin_src bash
153
-sudo apt-get -y install git wget build-essential
154
-wget https://freedombone.net/downloads/current/freedombone.tar.gz
155
-wget https://freedombone.net/downloads/current/freedombone.tar.gz.sig
156
-gpg --verify freedombone.tar.gz.sig
157
-sha256sum freedombone.tar.gz
158
-e2715e27b142a21fa257eab15778ddc96f86fda70f8d91d47c4c9aa19f22e272
159
-tar -xzvf freedombone.tar.gz
160
-cd freedombone
161
-git checkout stretch
162
-sudo make install
163
-freedombone-image --setup debian
164
-freedombone-image -t i386 -v meshclient
165
-#+end_src
166
-
167
-If you don't have Atheros or free software compatible wifi adapter then you can include proprietary wifi drivers which will work with most laptops. This is *NOT RECOMMENDED* because proprietary drivers are unsupportable and may contain either malware or be exploitable in a way which can't be fixed. However, if you're in an emergency and don't have any Atheros or free software wifi USB dongles then you can use the following command to make the image:
168
-
169
-#+begin_src bash
170
-freedombone-image -t i386 -v meshclient --insecure yes
171
-#+end_src
172
-
173
-This takes a while. Maybe an hour or so, depending on the speed of your system and the internets. The good news though is that once created you can use the resulting image any number of times, and you don't need to trust some pre-built image.
174
-
175
-List what drives are on your system with:
176
-
177
-#+begin_src bash
178
-ls /dev/sd*
179
-#+end_src
180
-
181
-Now plug in the USB thumb drive, and do the same again. Notice which drive letter gets added.
182
-
183
-You can now copy the image to the USB thumb drive, replacing *sdX* with the identifier of the USB thumb drive. Don't include any numbers (so for example use *sdc* instead of *sdc1*).
184
-
185
-#+begin_src bash
186
-sudo dd if=/dev/zero of=/dev/sdX bs=1M count=8
187
-sudo dd bs=1M if=myimagefile.img of=/dev/sdX conv=fdatasync
188
-#+end_src
189
-
190
-And wait. Again it will take a while to copy over. When that's done plug it into the laptop or netbook which you want to use on the mesh, power on and set the BIOS to boot from the USB stick.
191
-
192
-On first boot you'll be asked to set a username, and then you can open the chat client and select the *users* icon to show the Tox IDs for other users on the mesh. When folks join they will be announced.
193
-
194
-Rinse, repeat, for any number of laptops that you want to get onto the mesh or to build out coverage within an area. There are no servers. Just peer-to-peer communications routed through the network which are end-to-end secure after a friend request is accepted. By default the chat client doesn't log anything.
195
-
196
-You can also use single board computers (SBCs) such as the BeagleBone Black to make mesh routers which can be bolted to walls or the sides of buildings and consume minimal electrical power, so could be solar or battery powered for short term events such as festivals. To do that use the following command to make the image:
197
-
198
-#+begin_src bash
199
-freedombone-image -t beaglebone -v mesh
200
-#+end_src
201
-
202
-The resulting image can be copied to a microSD card, inserted into a Beaglebone Black and booted. Don't forget to plug in an Atheros USB wifi dongle.
203
-
204
-* Customisation
205
-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 *img/backgrounds* and to change the available avatars and desktop icons edit the images within *img/avatars*. Re-create disk images using the instructions shown previously.
206
-
207
-If you need particular /dconf/ commands to alter desktop appearance or behavior then see the function /mesh_client_startup_applications/ within *src/freedombone-image-customise*.
208
-* How to use it
209
-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.
210
-
211
-After a minute or two if you are within wifi range and there is at least one other user on the network then you should see additional icons appear on the desktop, such as /Other Users/ and /Chat/.
212
-
213
-** Boot trouble
214
-If the system doesn't boot and reports an error which includes */dev/mapper/loop0p1* then reboot with *Ctrl-Alt-Del* and when you see the grub menu press *e* and manually change */dev/mapper/loop0p1* to */dev/sdb1*, then press *Ctrl-x*. If that doesn't work then reboot and try */dev/sdc1* instead.
215
-
216
-After the system has booted successfully the problem should resolve itself on subsequent reboots.
217
-** Set the Date
218
-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.
219
-
220
-*Right click on the date* in the top right corner of the screen. Select *preferences*, then click the *Time Settings* button. You can then select the date from the calendar and set the time, then click the *Set System Time* button. Enter the default password, which is /freedombone/.
221
-** Check network status
222
-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.
223
-
224
-Select the wifi icon on the desktop and enter the password '/freedombone/'. The network configuration will go into a monitoring mode and in the bottom right side of the window you will be able to see signal strength and other parameters. This can help you to locate systems or adjust antennas to get the best wifi performance.
225
-
226
-
227
-#+BEGIN_CENTER
228
-[[file:images/mesh_signal.jpg]]
229
-#+END_CENTER
230
-
231
-When you are finished close the window and then select the /Network Restart/ desktop icon, which will restart the B.A.T.M.A.N. network. You can also use the restart icon if you are within range of the mesh network but the /Chat/ and /Other Users/ icons do not automatically appear after a few minutes.
232
-** Connecting to the internet
233
-If you need to be able to access the internet from the mesh then connect one of the peers to an internet router using an ethernet cable, then reboot it. Other peers in the mesh, including any attached mobile devices, will then be able to access the internet using the ethernet attached peer as a gateway. [[https://en.wikipedia.org/wiki/Freifunk][Freifunk]] works in a similar way.
234
-
235
-After connecting one peer to the internet you may need to reboot other peers in order to update their network configurations.
236
-
237
-If for legal reasons you need to connect to the internet via a VPN then openvpn is preinstalled and you can run the command:
238
-
239
-#+begin_src bash
240
-sudo openvpn myclient.ovpn
241
-#+end_src
242
-
243
-Where /myclient.ovpn/ comes from your VPN provider and with the password "/freedombone/".
244
-** Connecting two meshes over the internet via a VPN tunnel
245
-Maybe the internet exists, but you don't care about getting any content from it and just want to use it as a way to connect mesh networks from different geographical locations together.
246
-
247
-In your home directory on a system connected via ethernet to an internet router you'll find a file called *vpn.tar.gz*. If you want another mesh to be able to connect to yours then send them this file and get them to uncompress it into their home directory also on an internet gateway machine. If they have an external IP address or domain name for your router then they will be able to VPN connect using the *Connect Meshes* icon. They should also forward port 653 from their internet router to the mesh gateway machine.
248
-
249
-#+BEGIN_CENTER
250
-[[file:images/mesh_connect.jpg]]
251
-#+END_CENTER
252
-
253
-You should create a new *vpn.tar.gz* file for every other mesh which wants to be able to connect to yours. If you are prompted for a password it is 'freedombone'.
254
-
255
-From a deep packet inspection point of view the traffic going over the internet between mesh gateways will just look like any other TLS connection to a server.
256
-
257
-** Mobile devices (phones, etc)
258
-To allow mobile devices to connect to the mesh you will need a second wifi adapter connected to your laptop/netbook/SBC. Plug in a second wifi adapter then reboot the system. The second adaptor will then create a wifi hotspot which mobile devices can connect to. The hotspot name also contains its local IP address (eg. "/mesh-192.168.1.83/").
259
-
260
-On a typical Android device go to *Settings* then *Security* and ensure that *Unknown sources* is enabled. Also within *Wifi* from the *Settings* screen select the mesh hotspot. The password is "/freedombone/". Open a non-Tor browser and navigate to the IP address showing in the hotspot name. You can then download and install mesh apps.
261
-
262
-#+BEGIN_CENTER
263
-[[file:images/mesh_mobileapps.jpg]]
264
-#+END_CENTER
265
-
266
-On some android devices you may need to move the downloaded APK file from the *Downloads* directory to your *home* directory before you can install it.
267
-** Chat System
268
-
269
-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 /Chat/ and /Other Users/ icons appear. Select the users icon and you should see a list of users on the mesh. Select the /Chat/ 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.
270
-
271
-#+BEGIN_CENTER
272
-[[file:images/mesh_paste_tox_id.jpg]]
273
-#+END_CENTER
274
-
275
-The other user can then accept or decline your friend request.
276
-
277
-#+BEGIN_CENTER
278
-[[file:images/mesh_friend_request.jpg]]
279
-#+END_CENTER
280
-
281
-You can also select an avatar by selecting the grey head and shoulders image.
282
-
283
-#+BEGIN_CENTER
284
-[[file:images/mesh_choose_avatar.jpg]]
285
-#+END_CENTER
286
-
287
-And by selecting the user from the list on the left hand side the chat can begin.
288
-
289
-#+BEGIN_CENTER
290
-[[file:images/mesh_text_chat.jpg]]
291
-#+END_CENTER
292
-
293
-One important point is that by default the microphone is turned off. When doing voice chat you can select the microphone volume with the drop down slider in the top right corner of the screen.
294
-
295
-At present video doesn't work reliably, but text and voice chat do work well.
296
-
297
-** Collaborative document editing
298
-The mesh system includes the ability to collaboratively edit various sorts of documents using CryptPad. CryptPad is an almost peer-to-peer system in that it is designed for a client/server environment but that the server aspect of it is very minimal and limited to orchestrating the connected clients. With CryptPad installed on each mesh peer it effectively enables peer-to-peer collaborative editing. Documents are ephemeral and forgotten unless they're exported or copy-pasted to permanent storage.
299
-
300
-#+BEGIN_CENTER
301
-[[file:images/mesh_cryptpad1.jpg]]
302
-#+END_CENTER
303
-
304
-To create a document click on the CryptPad icon. Depending upon the specifications of your system it may take a few seconds to load, so don't be too disturned if the browser contents look blank for a while. Select _Rich Text Pad_ and give yourself a username.
305
-
306
-#+BEGIN_CENTER
307
-[[file:images/mesh_cryptpad2.jpg]]
308
-#+END_CENTER
309
-
310
-If you have the chat system running you can then copy and paste the URL for your pad into the chat, and the other user can then open the link and edit the document with you. You can repeat that for however many other users you wish to be able to edit.
311
-
312
-** Social Network
313
-
314
-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.
315
-
316
-Double click on the "Social" icon to open the app, then add your nickname and optionally a description. If you want to choose an avatar image some can be found within the directory */usr/share/freedombone/avatars*. On older systems or systems without a hardware random number generator, Patchwork sometimes takes a long time (a few minutes) to open for the first time after clicking the icon. This is most likely due to the initial generation of encryption keys, so be patient.
317
-
318
-#+BEGIN_CENTER
319
-[[file:images/patchwork_setup.jpg]]
320
-#+END_CENTER
321
-
322
-Other Patchwork users on the mesh will appear automatically under the *local* list and you can select and follow them if you wish. It's also possible to select the dark theme from *settings* on the drop down menu if you prefer.
323
-
324
-#+BEGIN_CENTER
325
-[[file:images/patchwork_public.jpg]]
326
-#+END_CENTER
327
-
328
-The Secure Scuttlebutt protocol which Patchwork is based upon is intended to be robust to intermittent network connectivity, so you can write posts when out of range and they will sync once you are back in the network.
329
-
330
-** Sharing Files
331
-You can make files publicly available on the network simply by dragging and dropping them into the /Public/ folder on the desktop. To view the files belonging to another user select the desktop icon called /Visit a site/ and enter the username or Tox ID of the other user.
332
-
333
-#+BEGIN_CENTER
334
-[[file:images/mesh_share_files.jpg]]
335
-#+END_CENTER
336
-
337
-** Blogging
338
-To create a blog post select the /Blog/ 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 *CreateBlog/content/images* directory and then link to them as shown.
339
-
340
-#+BEGIN_CENTER
341
-[[file:images/mesh_new_blog.jpg]]
342
-#+END_CENTER
343
-
344
-To finish your blog entry just select /Save/ and then close the editor. On older hardware it may take a while to publish the results, and this depends upon the amount of computation needed by IPFS to create file hashes. If you make no changes to the default text then the new blog entry will not be saved.
345
-
346
-#+BEGIN_CENTER
347
-[[file:images/mesh_new_blog2.jpg]]
348
-#+END_CENTER
349
-
350
-#+BEGIN_CENTER
351
-[[file:images/mesh_view_blog.jpg]]
352
-#+END_CENTER
29
+Mesh networks are useful as a quick way to make a fully decentralised communications system which is not connected to or reliant upon the internet. Think festivals, hacker conferences, onboard ships at sea, disaster/war zones, small businesses who don't want the overhead of server maintenance, protests, remote areas of the world, temporary "digital blackouts", scientific expeditions and off-world space colonies.
353 30
 
354
-You can also visit other blogs, edit or delete your previous entry and also change your blog theme.
31
+If an internet connection is available then it can make use of that, but otherwise it can still work regardless of whether the internet exists. So it's not dependent upon ISPs and additional infrastructure other than USB drives isn't required.
355 32
 
33
+Systems only need to be within wifi range of each other for the mesh to be created, so it can be an very convenient way to create a local communications network.
356 34
 
357 35
 #+BEGIN_CENTER
358 36
 This site can also be accessed via a Tor browser at http://pazyv7nkllp76hqr.onion

+ 35
- 0
doc/EN/mesh_capabilities.org Ver arquivo

@@ -0,0 +1,35 @@
1
+#+TITLE:
2
+#+AUTHOR: Bob Mottram
3
+#+EMAIL: bob@freedombone.net
4
+#+KEYWORDS: freedombox, debian, beaglebone, red matrix, email, web server, home server, internet, censorship, surveillance, social network, irc, jabber
5
+#+DESCRIPTION: Turn the Beaglebone Black into a personal communications server
6
+#+OPTIONS: ^:nil toc:nil
7
+#+HTML_HEAD: <link rel="stylesheet" type="text/css" href="freedombone.css" />
8
+
9
+#+BEGIN_CENTER
10
+[[file:images/logo.png]]
11
+#+END_CENTER
12
+
13
+#+begin_export html
14
+<center><h1>Mesh Network: Capabilities</h1></center>
15
+#+end_export
16
+
17
+The mesh system has the following capabilities:
18
+
19
+ - Discovery of other users on the network
20
+ - Text based chat, one-to-one and in groups
21
+ - Voice chat (VoIP) and video calls
22
+ - Private and public sharing of files
23
+ - Blogging
24
+ - Collaborative editing of documents and presentations
25
+ - Creating and broadcasting audio media/podcasts
26
+ - Social network stream. Follow/unfollow other peers
27
+ - No network administration required
28
+ - No servers
29
+ - Internet connection is optional
30
+ - Works from bootable USB drives or microSD drives
31
+ - Data is mesh routed between systems
32
+ - Private communications is end-to-end secured and forward secret
33
+ - Publicly shared data is /content addressable/
34
+
35
+This system should be quite scalable. Both qTox and IPFS are based upon distributed hash tables (DHT) so that each peer does not need to store the full index of data for the entire network. Gossiping between SSB peers may be slower, but the [[https://en.wikipedia.org/wiki/Small-world_network][small world effect]] will presumably still make for quite efficient delivery in a large network. Caching or pinning of IPFS data and its content addressability means that if a file or blog becomes popular then performance should improve as the number of downloads increases, which is the opposite of the client/server paradigm.

+ 19
- 0
doc/EN/mesh_custom.org Ver arquivo

@@ -0,0 +1,19 @@
1
+#+TITLE:
2
+#+AUTHOR: Bob Mottram
3
+#+EMAIL: bob@freedombone.net
4
+#+KEYWORDS: freedombox, debian, beaglebone, red matrix, email, web server, home server, internet, censorship, surveillance, social network, irc, jabber
5
+#+DESCRIPTION: Turn the Beaglebone Black into a personal communications server
6
+#+OPTIONS: ^:nil toc:nil
7
+#+HTML_HEAD: <link rel="stylesheet" type="text/css" href="freedombone.css" />
8
+
9
+#+BEGIN_CENTER
10
+[[file:images/logo.png]]
11
+#+END_CENTER
12
+
13
+#+begin_export html
14
+<center><h1>Mesh Network: Customisation</h1></center>
15
+#+end_export
16
+
17
+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 *img/backgrounds* and to change the available avatars and desktop icons edit the images within *img/avatars*. Re-create disk images using the instructions shown previously.
18
+
19
+If you need particular /dconf/ commands to alter desktop appearance or behavior then see the function /mesh_client_startup_applications/ within *src/freedombone-image-customise*.

+ 149
- 0
doc/EN/mesh_images.org Ver arquivo

@@ -0,0 +1,149 @@
1
+#+TITLE:
2
+#+AUTHOR: Bob Mottram
3
+#+EMAIL: bob@freedombone.net
4
+#+KEYWORDS: freedombox, debian, beaglebone, red matrix, email, web server, home server, internet, censorship, surveillance, social network, irc, jabber
5
+#+DESCRIPTION: Turn the Beaglebone Black into a personal communications server
6
+#+OPTIONS: ^:nil toc:nil
7
+#+HTML_HEAD: <link rel="stylesheet" type="text/css" href="freedombone.css" />
8
+
9
+#+BEGIN_CENTER
10
+[[file:images/logo.png]]
11
+#+END_CENTER
12
+
13
+#+begin_export html
14
+<center><h1>Mesh Network: Images</h1></center>
15
+#+end_export
16
+
17
+* Pre-built Disk Images
18
+** Writing many images quickly
19
+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 *dd* command is used for writing to the target drive, but to write to multiple drives you can use a tool such as [[https://wiki.gnome.org/Apps/MultiWriter][GNOME MultiWriter]].
20
+
21
+For example on Arch/Parabola:
22
+
23
+#+begin_src bash
24
+sudo pacman -S gnome-multi-writer
25
+#+end_src
26
+
27
+Or on Debian based systems:
28
+
29
+#+begin_src bash
30
+sudo apt-get install gnome-multi-writer
31
+#+end_src
32
+
33
+The MultiWriter tool is also available within mesh client images, so that you can use mesh systems to create more copies of the same system.
34
+** Client images
35
+
36
+#+BEGIN_CENTER
37
+[[file:images/mesh_netbook.jpg]]
38
+#+END_CENTER
39
+
40
+"Client" isn't exactly the right term, but it's a mesh peer with a user interface. These images can be copied to a USB drive, then you can plug it into a laptop/netbook/desktop machine and boot from it. You will probably also need an Atheros USB wifi dongle (the black protruding object on the left side of the netbook in the picture above), because most built-in wifi usually requires proprietary firmware. In the commands below substitute /dev/sdX with the USB drive device, excluding any trailing numbers (eg. /dev/sdb). The USB drive you're copying to will need to be at least 8GB in size.
41
+
42
+#+begin_src bash
43
+sudo apt-get install xz-utils wget
44
+wget https://freedombone.net/downloads/current/freedombone-meshclient-i386.img.xz
45
+wget https://freedombone.net/downloads/current/freedombone-meshclient-i386.img.xz.sig
46
+gpg --verify freedombone-meshclient-i386.img.xz.sig
47
+sha256sum freedombone-meshclient-i386.img.xz
48
+61e474afae14774d7aa479b6727fd5e77bdc1854e547b3c5b630bf10542a9581
49
+unxz freedombone-meshclient-i386.img.xz
50
+sudo dd if=/dev/zero of=/dev/sdX bs=1M count=8
51
+sudo dd bs=1M if=freedombone-meshclient-i386.img of=/dev/sdX conv=fdatasync
52
+#+end_src
53
+
54
+To get a number of systems onto the mesh repeat the /dd/ command to create however many bootable USB drives you need.
55
+
56
+If you're in an emergency and don't have Atheros wifi dongles then there is also an "insecure" image which contains some proprietary wifi drivers which may work with a wider range of laptops. Proprietary drivers *are not recommended* because they're unsupportable and may be exploitable or contain malicious antifeatures which fundamentally compromise the security of the network. However, the trade-off between security/maintainability and simply having the ability to communicate at all may be a valid one in some situations.
57
+
58
+#+begin_src bash
59
+sudo apt-get install xz-utils wget
60
+wget https://freedombone.net/downloads/current/freedombone-meshclient-insecure-i386.img.xz
61
+wget https://freedombone.net/downloads/current/freedombone-meshclient-insecure-i386.img.xz.sig
62
+gpg --verify freedombone-meshclient-insecure-i386.img.xz.sig
63
+sha256sum freedombone-meshclient-insecure-i386.img.xz
64
+fec843303d7d280859f75f7a8edccd70512915a34d4cc0787b5de7d8fbde5c81
65
+unxz freedombone-meshclient-insecure-i386.img.xz
66
+sudo dd if=/dev/zero of=/dev/sdX bs=1M count=8
67
+sudo dd bs=1M if=freedombone-meshclient-insecure-i386.img of=/dev/sdX conv=fdatasync
68
+#+end_src
69
+
70
+** Router images
71
+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.
72
+*** Beaglebone Black
73
+#+BEGIN_CENTER
74
+[[file:images/mesh_router.jpg]]
75
+#+END_CENTER
76
+
77
+The above picture shows a Beaglebone Black with the image copied onto a microSD card (there's no need to do anything with the internal EMMC). A USB Atheros wifi adaptor with a large antenna is attached and in this case power is from the mains, although it could be from a battery or solar power system capable of supplying 5 volts and maybe 1A (depending upon how active the router is).
78
+
79
+#+begin_src bash
80
+sudo apt-get install xz-utils wget
81
+wget https://freedombone.net/downloads/current/freedombone-mesh_beaglebone-armhf.img.xz
82
+wget https://freedombone.net/downloads/current/freedombone-mesh_beaglebone-armhf.img.xz.sig
83
+gpg --verify freedombone-mesh_beaglebone-armhf.img.xz.sig
84
+sha256sum freedombone-mesh_beaglebone-armhf.img.xz
85
+45f131995e2f77188e7ddaf2b42ca3d8d48d821d37c7a31a21e2e6dcceaf510d
86
+unxz freedombone-mesh_beaglebone-armhf.img.xz
87
+sudo dd bs=1M if=freedombone-mesh_beaglebone-armhf.img of=/dev/sdX conv=fdatasync
88
+#+end_src
89
+
90
+If you have a few Beaglebone Blacks to use as routers then repeat the /dd/ command to create however many microSD cards you need.
91
+
92
+There is still a software freedom issue with the Beaglebone Black, but it doesn't prevent you from running a fully free system on the board. The TI AM335X SOC has a PowerVR SGX530 GPU which will only run with a proprietary blob, but this would only be an issue for systems with a monitor or LCD screen attached running a desktop environment which also needs GPU acceleration. For "headless" systems such as servers or mesh routers this isn't a problem.
93
+
94
+* Building Disk Images
95
+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.
96
+
97
+First you will need to create an image. On a Debian based system (tested on Debian Stretch):
98
+
99
+#+begin_src bash
100
+sudo apt-get -y install git wget build-essential
101
+wget https://freedombone.net/downloads/current/freedombone.tar.gz
102
+wget https://freedombone.net/downloads/current/freedombone.tar.gz.sig
103
+gpg --verify freedombone.tar.gz.sig
104
+sha256sum freedombone.tar.gz
105
+e2715e27b142a21fa257eab15778ddc96f86fda70f8d91d47c4c9aa19f22e272
106
+tar -xzvf freedombone.tar.gz
107
+cd freedombone
108
+git checkout stretch
109
+sudo make install
110
+freedombone-image --setup debian
111
+freedombone-image -t i386 -v meshclient
112
+#+end_src
113
+
114
+If you don't have Atheros or free software compatible wifi adapter then you can include proprietary wifi drivers which will work with most laptops. This is *NOT RECOMMENDED* because proprietary drivers are unsupportable and may contain either malware or be exploitable in a way which can't be fixed. However, if you're in an emergency and don't have any Atheros or free software wifi USB dongles then you can use the following command to make the image:
115
+
116
+#+begin_src bash
117
+freedombone-image -t i386 -v meshclient --insecure yes
118
+#+end_src
119
+
120
+This takes a while. Maybe an hour or so, depending on the speed of your system and the internets. The good news though is that once created you can use the resulting image any number of times, and you don't need to trust some pre-built image.
121
+
122
+List what drives are on your system with:
123
+
124
+#+begin_src bash
125
+ls /dev/sd*
126
+#+end_src
127
+
128
+Now plug in the USB thumb drive, and do the same again. Notice which drive letter gets added.
129
+
130
+You can now copy the image to the USB thumb drive, replacing *sdX* with the identifier of the USB thumb drive. Don't include any numbers (so for example use *sdc* instead of *sdc1*).
131
+
132
+#+begin_src bash
133
+sudo dd if=/dev/zero of=/dev/sdX bs=1M count=8
134
+sudo dd bs=1M if=myimagefile.img of=/dev/sdX conv=fdatasync
135
+#+end_src
136
+
137
+And wait. Again it will take a while to copy over. When that's done plug it into the laptop or netbook which you want to use on the mesh, power on and set the BIOS to boot from the USB stick.
138
+
139
+On first boot you'll be asked to set a username, and then you can open the chat client and select the *users* icon to show the Tox IDs for other users on the mesh. When folks join they will be announced.
140
+
141
+Rinse, repeat, for any number of laptops that you want to get onto the mesh or to build out coverage within an area. There are no servers. Just peer-to-peer communications routed through the network which are end-to-end secure after a friend request is accepted. By default the chat client doesn't log anything.
142
+
143
+You can also use single board computers (SBCs) such as the BeagleBone Black to make mesh routers which can be bolted to walls or the sides of buildings and consume minimal electrical power, so could be solar or battery powered for short term events such as festivals. To do that use the following command to make the image:
144
+
145
+#+begin_src bash
146
+freedombone-image -t beaglebone -v mesh
147
+#+end_src
148
+
149
+The resulting image can be copied to a microSD card, inserted into a Beaglebone Black and booted. Don't forget to plug in an Atheros USB wifi dongle.

+ 51
- 0
doc/EN/mesh_philosophic.org Ver arquivo

@@ -0,0 +1,51 @@
1
+#+TITLE:
2
+#+AUTHOR: Bob Mottram
3
+#+EMAIL: bob@freedombone.net
4
+#+KEYWORDS: freedombox, debian, beaglebone, mesh
5
+#+DESCRIPTION: Turn any laptop or a Beaglebone Black into an off-the-grid mesh peer
6
+#+OPTIONS: ^:nil toc:nil
7
+#+HTML_HEAD: <link rel="stylesheet" type="text/css" href="freedombone.css" />
8
+
9
+#+BEGIN_CENTER
10
+[[file:images/logo.png]]
11
+#+END_CENTER
12
+
13
+#+begin_export html
14
+<center><h1>Mesh Network: Philosophic</h1></center>
15
+#+end_export
16
+
17
+#+begin_quote
18
+ "/I see mesh networks naturally evolving to become the dominant form of network over the next few decades, because it’s the most practical solution to a number of problems that will have to be solved in order to build the VR web as well as to connect the entire world to the internet. Centralized networks are only possible in highly developed countries with existing infrastructures like power and telephone grids, as well as roads. You can’t build a tower where you don’t have either power or access. For vast areas of the world, mesh networks will be the only feasible solution./" -- Valkyrie Ice
19
+#+end_quote
20
+
21
+The Freedombone mesh roughly follows MondoNet's ten social specifications:
22
+
23
+* Decentralized
24
+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.
25
+
26
+* Universally Accessible
27
+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.
28
+
29
+* Censor-proof
30
+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.
31
+
32
+* Surveillance-proof
33
+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.
34
+
35
+* Secure
36
+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.
37
+
38
+* Scalable
39
+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.
40
+
41
+* Permanent
42
+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.
43
+
44
+* Fast (enough)
45
+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.
46
+
47
+* Independent
48
+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.
49
+
50
+* Evolvable
51
+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.

+ 189
- 0
doc/EN/mesh_usage.org Ver arquivo

@@ -0,0 +1,189 @@
1
+#+TITLE:
2
+#+AUTHOR: Bob Mottram
3
+#+EMAIL: bob@freedombone.net
4
+#+KEYWORDS: freedombox, debian, beaglebone, red matrix, email, web server, home server, internet, censorship, surveillance, social network, irc, jabber
5
+#+DESCRIPTION: Turn the Beaglebone Black into a personal communications server
6
+#+OPTIONS: ^:nil toc:nil
7
+#+HTML_HEAD: <link rel="stylesheet" type="text/css" href="freedombone.css" />
8
+
9
+#+BEGIN_CENTER
10
+[[file:images/logo.png]]
11
+#+END_CENTER
12
+
13
+#+begin_export html
14
+<center><h1>Mesh Network: How to use it</h1></center>
15
+#+end_export
16
+
17
+ * [[Boot trouble]]
18
+ * [[Set the Date]]
19
+ * [[Check network status]]
20
+ * [[Connecting to the internet]]
21
+ * [[Connecting two meshes over the internet via a VPN tunnel]]
22
+ * [[Mobile devices (phones, etc)]]
23
+ * [[Chat System]]
24
+ * [[Collaborative document editing]]
25
+ * [[Social Network]]
26
+ * [[Sharing Files]]
27
+ * [[Blogging]]
28
+
29
+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.
30
+
31
+After a minute or two if you are within wifi range and there is at least one other user on the network then you should see additional icons appear on the desktop, such as /Other Users/ and /Chat/.
32
+
33
+* Boot trouble
34
+If the system doesn't boot and reports an error which includes */dev/mapper/loop0p1* then reboot with *Ctrl-Alt-Del* and when you see the grub menu press *e* and manually change */dev/mapper/loop0p1* to */dev/sdb1*, then press *Ctrl-x*. If that doesn't work then reboot and try */dev/sdc1* instead.
35
+
36
+After the system has booted successfully the problem should resolve itself on subsequent reboots.
37
+* Set the Date
38
+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.
39
+
40
+*Right click on the date* in the top right corner of the screen. Select *preferences*, then click the *Time Settings* button. You can then select the date from the calendar and set the time, then click the *Set System Time* button. Enter the default password, which is /freedombone/.
41
+* Check network status
42
+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.
43
+
44
+Select the wifi icon on the desktop and enter the password '/freedombone/'. The network configuration will go into a monitoring mode and in the bottom right side of the window you will be able to see signal strength and other parameters. This can help you to locate systems or adjust antennas to get the best wifi performance.
45
+
46
+
47
+#+BEGIN_CENTER
48
+[[file:images/mesh_signal.jpg]]
49
+#+END_CENTER
50
+
51
+When you are finished close the window and then select the /Network Restart/ desktop icon, which will restart the B.A.T.M.A.N. network. You can also use the restart icon if you are within range of the mesh network but the /Chat/ and /Other Users/ icons do not automatically appear after a few minutes.
52
+* Connecting to the internet
53
+
54
+#+BEGIN_CENTER
55
+[[file:images/mesh_architecture2.jpg]]
56
+#+END_CENTER
57
+
58
+If you need to be able to access the internet from the mesh then connect one of the peers to an internet router using an ethernet cable (shown as yellow above), then reboot it. Other peers in the mesh, including any attached mobile devices, will then be able to access the internet using the ethernet attached peer as a gateway. [[https://en.wikipedia.org/wiki/Freifunk][Freifunk]] works in a similar way.
59
+
60
+After connecting one peer to the internet you may need to reboot other peers in order to update their network configurations.
61
+
62
+If for legal reasons you need to connect to the internet via a VPN then openvpn is preinstalled and you can run the command:
63
+
64
+#+begin_src bash
65
+sudo openvpn myclient.ovpn
66
+#+end_src
67
+
68
+Where /myclient.ovpn/ comes from your VPN provider and with the password "/freedombone/".
69
+* Connecting two meshes over the internet via a VPN tunnel
70
+
71
+#+BEGIN_CENTER
72
+[[file:images/mesh_architecture_vpn.jpg]]
73
+#+END_CENTER
74
+
75
+Maybe the internet exists, but you don't care about getting any content from it and just want to use it as a way to connect mesh networks from different geographical locations together.
76
+
77
+In your home directory on a system connected via ethernet to an internet router you'll find a file called *vpn.tar.gz*. If you want another mesh to be able to connect to yours then send them this file and get them to uncompress it into their home directory also on an internet gateway machine. If they have an external IP address or domain name for your router then they will be able to VPN connect using the *Connect Meshes* icon. They should also forward port 653 from their internet router to the mesh gateway machine.
78
+
79
+#+BEGIN_CENTER
80
+[[file:images/mesh_connect.jpg]]
81
+#+END_CENTER
82
+
83
+You should create a new *vpn.tar.gz* file for every other mesh which wants to be able to connect to yours. If you are prompted for a password it is 'freedombone'.
84
+
85
+From a deep packet inspection point of view the traffic going over the internet between mesh gateways will just look like any other TLS connection to a server.
86
+
87
+* Mobile devices (phones, etc)
88
+
89
+#+BEGIN_CENTER
90
+[[file:images/mesh_architecture3.jpg]]
91
+#+END_CENTER
92
+
93
+To allow mobile devices to connect to the mesh you will need a second wifi adapter connected to your laptop/netbook/SBC. Plug in a second wifi adapter then reboot the system. The second adaptor will then create a wifi hotspot (the connection shown in green above) which mobile devices can connect to. The hotspot name also contains its local IP address (eg. "/mesh-192.168.1.83/").
94
+
95
+On a typical Android device go to *Settings* then *Security* and ensure that *Unknown sources* is enabled. Also within *Wifi* from the *Settings* screen select the mesh hotspot. The password is "/freedombone/". Open a non-Tor browser and navigate to the IP address showing in the hotspot name. You can then download and install mesh apps.
96
+
97
+#+BEGIN_CENTER
98
+[[file:images/mesh_mobileapps.jpg]]
99
+#+END_CENTER
100
+
101
+On some android devices you may need to move the downloaded APK file from the *Downloads* directory to your *home* directory before you can install it.
102
+* Chat System
103
+
104
+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 /Chat/ and /Other Users/ icons appear. Select the users icon and you should see a list of users on the mesh. Select the /Chat/ 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.
105
+
106
+#+BEGIN_CENTER
107
+[[file:images/mesh_paste_tox_id.jpg]]
108
+#+END_CENTER
109
+
110
+The other user can then accept or decline your friend request.
111
+
112
+#+BEGIN_CENTER
113
+[[file:images/mesh_friend_request.jpg]]
114
+#+END_CENTER
115
+
116
+You can also select an avatar by selecting the grey head and shoulders image.
117
+
118
+#+BEGIN_CENTER
119
+[[file:images/mesh_choose_avatar.jpg]]
120
+#+END_CENTER
121
+
122
+And by selecting the user from the list on the left hand side the chat can begin.
123
+
124
+#+BEGIN_CENTER
125
+[[file:images/mesh_text_chat.jpg]]
126
+#+END_CENTER
127
+
128
+One important point is that by default the microphone is turned off. When doing voice chat you can select the microphone volume with the drop down slider in the top right corner of the screen.
129
+
130
+At present video doesn't work reliably, but text and voice chat do work well.
131
+
132
+* Collaborative document editing
133
+The mesh system includes the ability to collaboratively edit various sorts of documents using CryptPad. CryptPad is an almost peer-to-peer system in that it is designed for a client/server environment but that the server aspect of it is very minimal and limited to orchestrating the connected clients. With CryptPad installed on each mesh peer it effectively enables peer-to-peer collaborative editing. Documents are ephemeral and forgotten unless they're exported or copy-pasted to permanent storage.
134
+
135
+#+BEGIN_CENTER
136
+[[file:images/mesh_cryptpad1.jpg]]
137
+#+END_CENTER
138
+
139
+To create a document click on the CryptPad icon. Depending upon the specifications of your system it may take a few seconds to load, so don't be too disturned if the browser contents look blank for a while. Select _Rich Text Pad_ and give yourself a username.
140
+
141
+#+BEGIN_CENTER
142
+[[file:images/mesh_cryptpad2.jpg]]
143
+#+END_CENTER
144
+
145
+If you have the chat system running you can then copy and paste the URL for your pad into the chat, and the other user can then open the link and edit the document with you. You can repeat that for however many other users you wish to be able to edit.
146
+
147
+* Social Network
148
+
149
+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.
150
+
151
+Double click on the "Social" icon to open the app, then add your nickname and optionally a description. If you want to choose an avatar image some can be found within the directory */usr/share/freedombone/avatars*. On older systems or systems without a hardware random number generator, Patchwork sometimes takes a long time (a few minutes) to open for the first time after clicking the icon. This is most likely due to the initial generation of encryption keys, so be patient.
152
+
153
+#+BEGIN_CENTER
154
+[[file:images/patchwork_setup.jpg]]
155
+#+END_CENTER
156
+
157
+Other Patchwork users on the mesh will appear automatically under the *local* list and you can select and follow them if you wish. It's also possible to select the dark theme from *settings* on the drop down menu if you prefer.
158
+
159
+#+BEGIN_CENTER
160
+[[file:images/patchwork_public.jpg]]
161
+#+END_CENTER
162
+
163
+The Secure Scuttlebutt protocol which Patchwork is based upon is intended to be robust to intermittent network connectivity, so you can write posts when out of range and they will sync once you are back in the network.
164
+
165
+* Sharing Files
166
+You can make files publicly available on the network simply by dragging and dropping them into the /Public/ folder on the desktop. To view the files belonging to another user select the desktop icon called /Visit a site/ and enter the username or Tox ID of the other user.
167
+
168
+#+BEGIN_CENTER
169
+[[file:images/mesh_share_files.jpg]]
170
+#+END_CENTER
171
+
172
+* Blogging
173
+To create a blog post select the /Blog/ 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 *CreateBlog/content/images* directory and then link to them as shown.
174
+
175
+#+BEGIN_CENTER
176
+[[file:images/mesh_new_blog.jpg]]
177
+#+END_CENTER
178
+
179
+To finish your blog entry just select /Save/ and then close the editor. On older hardware it may take a while to publish the results, and this depends upon the amount of computation needed by IPFS to create file hashes. If you make no changes to the default text then the new blog entry will not be saved.
180
+
181
+#+BEGIN_CENTER
182
+[[file:images/mesh_new_blog2.jpg]]
183
+#+END_CENTER
184
+
185
+#+BEGIN_CENTER
186
+[[file:images/mesh_view_blog.jpg]]
187
+#+END_CENTER
188
+
189
+You can also visit other blogs, edit or delete your previous entry and also change your blog theme.

BIN
img/avatars/icon_blog.png Ver arquivo


BIN
img/avatars/icon_connect.png Ver arquivo


BIN
img/avatars/icon_cryptpad.png Ver arquivo


BIN
img/avatars/icon_help.png Ver arquivo


BIN
img/avatars/icon_new_identity.png Ver arquivo


BIN
img/avatars/icon_restart_network.png Ver arquivo


BIN
img/avatars/icon_sites.png Ver arquivo


BIN
img/avatars/icon_social.png Ver arquivo


BIN
img/avatars/icon_users.png Ver arquivo


BIN
img/avatars/icon_wifi.png Ver arquivo


BIN
img/avatars/icons_chat.png Ver arquivo


BIN
img/avatars/icons_invite.png Ver arquivo


BIN
img/icon_blog.png Ver arquivo


BIN
img/icon_connect.png Ver arquivo


BIN
img/icon_cryptpad.png Ver arquivo


BIN
img/icon_help.png Ver arquivo


BIN
img/icon_new_identity.png Ver arquivo


BIN
img/icon_restart_network.png Ver arquivo


BIN
img/icon_sites.png Ver arquivo


BIN
img/icon_social.png Ver arquivo


BIN
img/icon_users.png Ver arquivo


BIN
img/icon_wifi.png Ver arquivo


BIN
img/icons_chat.png Ver arquivo


BIN
img/icons_invite.png Ver arquivo


BIN
img/logo_blue.png Ver arquivo


BIN
img/logo_white_large.png Ver arquivo


BIN
img/mesh_architecture1.jpg Ver arquivo


BIN
img/mesh_architecture2.jpg Ver arquivo


BIN
img/mesh_architecture3.jpg Ver arquivo


BIN
img/mesh_architecture_vpn.jpg Ver arquivo


BIN
img/postactiv_sprite2.png Ver arquivo


+ 16
- 20
src/freedombone-image-customise Ver arquivo

@@ -779,18 +779,11 @@ function mesh_client_startup_applications {
779 779
     echo '' >> $START_DESKTOP
780 780
     echo 'INITIAL_TOX_USERNAME=""' >> $START_DESKTOP
781 781
     echo 'while [ ${#INITIAL_TOX_USERNAME} -eq 0 ]; do' >> $START_DESKTOP
782
-    echo '  data=$(tempfile 2>/dev/null)' >> $START_DESKTOP
783
-    echo '  trap "rm -f $data" 0 1 2 5 15' >> $START_DESKTOP
784
-    echo -n "   dialog --title \"${MESH_TITLE}\" " >> $START_DESKTOP
785
-    echo -n "--backtitle \"${MESH_TITLE}\" " >> $START_DESKTOP
786
-    echo -n "--inputbox \"${MESH_SET_USERNAME}\" 12 60 Anon " >> $START_DESKTOP
787
-    echo '2>$data' >> $START_DESKTOP
788
-    echo '  sel=$?' >> $START_DESKTOP
789
-    echo '  case $sel in' >> $START_DESKTOP
790
-    echo '      0)' >> $START_DESKTOP
791
-    echo '          INITIAL_TOX_USERNAME=$(<$data)' >> $START_DESKTOP
792
-    echo '          ;;' >> $START_DESKTOP
793
-    echo '  esac' >> $START_DESKTOP
782
+    echo "  data=\$(zenity --forms --title=\"$MESH_TITLE\" --text=\"$MESH_SET_USERNAME\" --separator=\",\" --add-entry=\"Username\")" >> $START_DESKTOP
783
+    echo '  accepted=$?' >> $START_DESKTOP
784
+    echo '  if ((accepted == 0)); then' >> $START_DESKTOP
785
+    echo "      INITIAL_TOX_USERNAME=\$(awk -F, '{print \$1}' <<<\$data)" >> $START_DESKTOP
786
+    echo '  fi' >> $START_DESKTOP
794 787
     echo 'done' >> $START_DESKTOP
795 788
     echo '' >> $START_DESKTOP
796 789
     echo 'toxid --setuser "$INITIAL_TOX_USERNAME"' >> $START_DESKTOP
@@ -892,6 +885,9 @@ function configure_user_interface {
892 885
     # audio recording
893 886
     chroot "$rootdir" apt-get -yq install audacity
894 887
 
888
+    # for gtk dialog entry
889
+    chroot "$rootdir" apt-get -yq install zenity
890
+
895 891
     # Produce a text file on the desktop listing users on the mesh
896 892
     cat <<EOF > $rootdir/usr/bin/list-tox-users
897 893
 #!/bin/bash
@@ -923,7 +919,7 @@ if [ \$no_of_users -gt 0 ]; then
923 919
     echo 'Type=Application' >> /home/$MY_USERNAME/Desktop/Users.desktop
924 920
     echo 'Comment=List of users' >> /home/$MY_USERNAME/Desktop/Users.desktop
925 921
     echo 'Exec=bash /home/$MY_USERNAME/showusers' >> /home/$MY_USERNAME/Desktop/Users.desktop
926
-    echo 'Icon=/usr/share/$PROJECT_NAME/avatars/otheruser.png' >> /home/$MY_USERNAME/Desktop/Users.desktop
922
+    echo 'Icon=/usr/share/$PROJECT_NAME/avatars/icon_users.png' >> /home/$MY_USERNAME/Desktop/Users.desktop
927 923
     echo 'StartupNotify=false' >> /home/$MY_USERNAME/Desktop/Users.desktop
928 924
     chmod +x /home/$MY_USERNAME/Desktop/Users.desktop
929 925
     chown $MY_USERNAME:$MY_USERNAME /home/$MY_USERNAME/Desktop/Users.desktop
@@ -934,7 +930,7 @@ if [ \$no_of_users -gt 0 ]; then
934 930
         echo 'Type=Application' >> /home/$MY_USERNAME/Desktop/cryptpad.desktop
935 931
         echo 'Comment=Realtime collaborative editing of documents' >> /home/$MY_USERNAME/Desktop/cryptpad.desktop
936 932
         echo "Exec=$BROWSER http://\${HOSTNAME}.local" >> /home/$MY_USERNAME/Desktop/cryptpad.desktop
937
-        echo "Icon=/etc/cryptpad/icon_cryptpad.png" >> /home/$MY_USERNAME/Desktop/cryptpad.desktop
933
+        echo "Icon=/usr/share/$PROJECT_NAME/avatars/icon_cryptpad.png" >> /home/$MY_USERNAME/Desktop/cryptpad.desktop
938 934
         echo 'Terminal=false' >> /home/$MY_USERNAME/Desktop/cryptpad.desktop
939 935
         echo 'Categories=Application;' >> /home/$MY_USERNAME/Desktop/cryptpad.desktop
940 936
         chmod +x /home/$MY_USERNAME/Desktop/cryptpad.desktop
@@ -954,7 +950,7 @@ if [ \$no_of_users -gt 0 ]; then
954 950
         echo 'Type=Application' >> /home/$MY_USERNAME/Desktop/social.desktop
955 951
         echo 'Comment=A decentralized messaging and sharing app built on top of Secure Scuttlebutt (SSB)' >> /home/$MY_USERNAME/Desktop/social.desktop
956 952
         echo 'Exec=bash /usr/bin/start_patchwork' >> /home/$MY_USERNAME/Desktop/social.desktop
957
-        echo "Icon=/etc/patchwork/icon_patchwork.png" >> /home/$MY_USERNAME/Desktop/social.desktop
953
+        echo "Icon=/usr/share/$PROJECT_NAME/avatars/icon_social.png" >> /home/$MY_USERNAME/Desktop/social.desktop
958 954
         echo 'Terminal=false' >> /home/$MY_USERNAME/Desktop/social.desktop
959 955
         echo 'Categories=Application;' >> /home/$MY_USERNAME/Desktop/social.desktop
960 956
         chmod +x /home/$MY_USERNAME/Desktop/social.desktop
@@ -988,7 +984,7 @@ if [ \$no_of_users -gt 0 ]; then
988 984
         echo 'Name=Connect Meshes' >> /home/$MY_USERNAME/Desktop/vpn.desktop
989 985
         echo 'Comment=Connect to another mesh network via the internet' >> /home/$MY_USERNAME/Desktop/vpn.desktop
990 986
         echo 'Exec=mate-terminal -e /usr/local/bin/${PROJECT_NAME}-mesh-connect' >> /home/$MY_USERNAME/Desktop/vpn.desktop
991
-        echo 'Icon=/usr/share/${PROJECT_NAME}/avatars/connect.jpg' >> /home/$MY_USERNAME/Desktop/vpn.desktop
987
+        echo 'Icon=/usr/share/$PROJECT_NAME/avatars/icon_connect.png' >> /home/$MY_USERNAME/Desktop/vpn.desktop
992 988
         echo 'StartupNotify=false' >> /home/$MY_USERNAME/Desktop/vpn.desktop
993 989
         chmod +x /home/$MY_USERNAME/Desktop/vpn.desktop
994 990
         chown $MY_USERNAME:$MY_USERNAME /home/$MY_USERNAME/Desktop/vpn.desktop
@@ -1000,7 +996,7 @@ if [ \$no_of_users -gt 0 ]; then
1000 996
         echo "Name=Visit a site" >> /home/$MY_USERNAME/Desktop/sites.desktop
1001 997
         echo 'Comment=Visit a site' >> /home/$MY_USERNAME/Desktop/sites.desktop
1002 998
         echo 'Exec=mate-terminal -e /usr/local/bin/${PROJECT_NAME}-mesh-visit-site' >> /home/$MY_USERNAME/Desktop/sites.desktop
1003
-        echo 'Icon=/usr/share/${PROJECT_NAME}/avatars/ipfs.jpg' >> /home/$MY_USERNAME/Desktop/sites.desktop
999
+        echo 'Icon=/usr/share/$PROJECT_NAME/avatars/icon_sites.png' >> /home/$MY_USERNAME/Desktop/sites.desktop
1004 1000
         echo 'StartupNotify=false' >> /home/$MY_USERNAME/Desktop/sites.desktop
1005 1001
         chmod +x /home/$MY_USERNAME/Desktop/sites.desktop
1006 1002
         chown $MY_USERNAME:$MY_USERNAME /home/$MY_USERNAME/Desktop/sites.desktop
@@ -1010,7 +1006,7 @@ if [ \$no_of_users -gt 0 ]; then
1010 1006
         echo "Name=Blog" >> /home/$MY_USERNAME/Desktop/blog.desktop
1011 1007
         echo 'Comment=View or create blog entries' >> /home/$MY_USERNAME/Desktop/blog.desktop
1012 1008
         echo 'Exec=mate-terminal -e /usr/local/bin/${PROJECT_NAME}-mesh-blog' >> /home/$MY_USERNAME/Desktop/blog.desktop
1013
-        echo 'Icon=/usr/share/${PROJECT_NAME}/avatars/blog.png' >> /home/$MY_USERNAME/Desktop/blog.desktop
1009
+        echo 'Icon=/usr/share/$PROJECT_NAME/avatars/icon_blog.png' >> /home/$MY_USERNAME/Desktop/blog.desktop
1014 1010
         echo 'StartupNotify=false' >> /home/$MY_USERNAME/Desktop/blog.desktop
1015 1011
         chmod +x /home/$MY_USERNAME/Desktop/blog.desktop
1016 1012
         chown $MY_USERNAME:$MY_USERNAME /home/$MY_USERNAME/Desktop/blog.desktop
@@ -1032,7 +1028,7 @@ if [ \$no_of_users -gt 0 ]; then
1032 1028
         echo 'Type=Application' >> /home/$MY_USERNAME/Desktop/tox.desktop
1033 1029
         echo 'Comment=Chat, Voice and Video' >> /home/$MY_USERNAME/Desktop/tox.desktop
1034 1030
         echo 'Exec=bash /home/$MY_USERNAME/runtox' >> /home/$MY_USERNAME/Desktop/tox.desktop
1035
-        echo "Icon=/usr/share/$PROJECT_NAME/avatars/chat.png" >> /home/$MY_USERNAME/Desktop/tox.desktop
1031
+        echo "Icon=/usr/share/$PROJECT_NAME/avatars/icon_chat.png" >> /home/$MY_USERNAME/Desktop/tox.desktop
1036 1032
         echo 'StartupNotify=true' >> /home/$MY_USERNAME/Desktop/tox.desktop
1037 1033
         chmod +x /home/$MY_USERNAME/Desktop/tox.desktop
1038 1034
         chown $MY_USERNAME:$MY_USERNAME /home/$MY_USERNAME/Desktop/tox.desktop
@@ -1048,7 +1044,7 @@ if [ \$no_of_users -gt 0 ]; then
1048 1044
             echo 'Type=Application' >> /home/$MY_USERNAME/Desktop/invite.desktop
1049 1045
             echo 'Comment=Create an invite for Patchwork or Ferment' >> /home/$MY_USERNAME/Desktop/invite.desktop
1050 1046
             echo 'Exec=mate-terminal -e freedombone-mesh-invite' >> /home/$MY_USERNAME/Desktop/invite.desktop
1051
-            echo 'Icon=/usr/share/freedombone/avatars/invite.png' >> /home/$MY_USERNAME/Desktop/invite.desktop
1047
+            echo 'Icon=/usr/share/$PROJECT_NAME/avatars/icon_invite.png' >> /home/$MY_USERNAME/Desktop/invite.desktop
1052 1048
             echo 'Terminal=false' >> /home/$MY_USERNAME/Desktop/invite.desktop
1053 1049
             echo 'Categories=Application;' >> /home/$MY_USERNAME/Desktop/invite.desktop
1054 1050
             chmod +x /home/$MY_USERNAME/Desktop/invite.desktop

+ 6
- 6
src/freedombone-image-mesh Ver arquivo

@@ -282,7 +282,7 @@ function show_desktop_icons {
282 282
     echo 'Type=Application' >> /home/$MY_USERNAME/Desktop/help.desktop
283 283
     echo 'Comment=Show help' >> /home/$MY_USERNAME/Desktop/help.desktop
284 284
     echo "Exec=bash -c /home/$MY_USERNAME/.showhelp" >> /home/$MY_USERNAME/Desktop/help.desktop
285
-    echo 'Icon=/usr/share/freedombone/avatars/help.png' >> /home/$MY_USERNAME/Desktop/help.desktop
285
+    echo "Icon=/usr/share/${PROJECT_NAME}/avatars/icon_help.png" >> /home/$MY_USERNAME/Desktop/help.desktop
286 286
     echo 'Terminal=false' >> /home/$MY_USERNAME/Desktop/help.desktop
287 287
     echo 'Categories=Application;' >> /home/$MY_USERNAME/Desktop/help.desktop
288 288
 
@@ -292,7 +292,7 @@ function show_desktop_icons {
292 292
     echo 'Type=Application' >> /home/$MY_USERNAME/Desktop/wifi.desktop
293 293
     echo 'Comment=Check wifi status' >> /home/$MY_USERNAME/Desktop/wifi.desktop
294 294
     echo 'Exec=mate-terminal -e "sudo batman monitor"' >> /home/$MY_USERNAME/Desktop/wifi.desktop
295
-    echo 'Icon=/usr/share/freedombone/avatars/wifi.png' >> /home/$MY_USERNAME/Desktop/wifi.desktop
295
+    echo "Icon=/usr/share/${PROJECT_NAME}/avatars/icon_wifi.png" >> /home/$MY_USERNAME/Desktop/wifi.desktop
296 296
     echo 'Terminal=false' >> /home/$MY_USERNAME/Desktop/wifi.desktop
297 297
     echo 'Categories=Application;' >> /home/$MY_USERNAME/Desktop/wifi.desktop
298 298
 
@@ -302,7 +302,7 @@ function show_desktop_icons {
302 302
     echo 'Type=Application' >> /home/$MY_USERNAME/Desktop/restart.desktop
303 303
     echo 'Comment=Restart batman' >> /home/$MY_USERNAME/Desktop/restart.desktop
304 304
     echo 'Exec=mate-terminal -e "sudo batman restart 2> /dev/null"' >> /home/$MY_USERNAME/Desktop/restart.desktop
305
-    echo 'Icon=/usr/share/freedombone/avatars/restart.png' >> /home/$MY_USERNAME/Desktop/restart.desktop
305
+    echo "Icon=/usr/share/${PROJECT_NAME}/avatars/icon_restart_network.png" >> /home/$MY_USERNAME/Desktop/restart.desktop
306 306
     echo 'Terminal=false' >> /home/$MY_USERNAME/Desktop/restart.desktop
307 307
     echo 'Categories=Application;' >> /home/$MY_USERNAME/Desktop/restart.desktop
308 308
 
@@ -311,8 +311,8 @@ function show_desktop_icons {
311 311
     echo 'Name=New Identity' >> /home/$MY_USERNAME/Desktop/new_identity.desktop
312 312
     echo 'Type=Application' >> /home/$MY_USERNAME/Desktop/new_identity.desktop
313 313
     echo 'Comment=Create a new identity' >> /home/$MY_USERNAME/Desktop/new_identity.desktop
314
-    echo 'Exec=mate-terminal -e freedombone-mesh-reset' >> /home/$MY_USERNAME/Desktop/new_identity.desktop
315
-    echo 'Icon=/usr/share/freedombone/avatars/newidentity.png' >> /home/$MY_USERNAME/Desktop/new_identity.desktop
314
+    echo "Exec=mate-terminal -e ${PROJECT_NAME}-mesh-reset" >> /home/$MY_USERNAME/Desktop/new_identity.desktop
315
+    echo "Icon=/usr/share/${PROJECT_NAME}/avatars/icon_new_identity.png" >> /home/$MY_USERNAME/Desktop/new_identity.desktop
316 316
     echo 'Terminal=false' >> /home/$MY_USERNAME/Desktop/new_identity.desktop
317 317
     echo 'Categories=Application;' >> /home/$MY_USERNAME/Desktop/new_identity.desktop
318 318
 
@@ -321,7 +321,7 @@ function show_desktop_icons {
321 321
     echo 'Type=Application' >> /home/$MY_USERNAME/Desktop/social.desktop
322 322
     echo 'Comment=A decentralized messaging and sharing app built on top of Secure Scuttlebutt (SSB)' >> /home/$MY_USERNAME/Desktop/social.desktop
323 323
     echo 'Exec=bash /usr/bin/start_patchwork' >> /home/$MY_USERNAME/Desktop/social.desktop
324
-    echo "Icon=/etc/patchwork/icon_patchwork.png" >> /home/$MY_USERNAME/Desktop/social.desktop
324
+    echo "Icon=/usr/share/${PROJECT_NAME}/avatars/icon_social.png" >> /home/$MY_USERNAME/Desktop/social.desktop
325 325
     echo 'Terminal=false' >> /home/$MY_USERNAME/Desktop/social.desktop
326 326
     echo 'Categories=Application;' >> /home/$MY_USERNAME/Desktop/social.desktop
327 327
 

+ 1
- 1
src/meshavahi Ver arquivo

@@ -147,7 +147,7 @@ function detect_new_tox_users {
147 147
     # Produce notifications if new users appear
148 148
     if [ -f $PREV_TOX_USERS_FILE ]; then
149 149
         while IFS='' read -r line || [[ -n "$line" ]]; do
150
-            if [[ $line != "Failed*" && $line != "data "* && $line != "Anon "* && $line != "anon "* ]]; then
150
+            if [[ $line != "Failed*" && $line != "data "* && $line != "Anon "* && $line != "anon "* && $line != "anonymous "* && $line != "Anonymous "* ]]; then
151 151
                 if ! grep -q "$line" $PREV_TOX_USERS_FILE; then
152 152
                     # get the nick of the user
153 153
                     toxidstr=$(echo "$line" | awk -F ' ' '{print $(NF)}')

+ 10
- 646
website/EN/mesh.html Ver arquivo

@@ -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-10-25 Wed 20:24 -->
6
+<!-- 2017-10-27 Fri 13:10 -->
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>
@@ -246,680 +246,44 @@ for the JavaScript code in this tag.
246 246
 
247 247
 <center><h1>Mesh Network</h1></center>
248 248
 
249
-<div class="org-center">
250
-
251
-<div class="figure">
252
-<p><img src="images/mesh_screenshot.jpg" alt="mesh_screenshot.jpg" />
253
-</p>
254
-</div>
255
-</div>
256
-
257
-<table border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides">
258
-
259
-
260
-<colgroup>
261
-<col  class="org-left" />
262
-
263
-<col  class="org-left" />
264
-
265
-<col  class="org-left" />
266
-
267
-<col  class="org-left" />
268
-
269
-<col  class="org-left" />
270
-
271
-<col  class="org-left" />
272
-
273
-<col  class="org-left" />
274
-</colgroup>
275
-<tbody>
276
-<tr>
277
-<td class="org-left"><a href="#orga5044ee">What the system can do</a></td>
278
-<td class="org-left">-</td>
279
-<td class="org-left"><a href="#orge35044f">Disk Images</a></td>
280
-<td class="org-left">-</td>
281
-<td class="org-left"><a href="#org042ab96">Building Disk Images</a></td>
282
-<td class="org-left">-</td>
283
-<td class="org-left"><a href="#org90e6351">How to use it</a></td>
284
-</tr>
285
-</tbody>
286
-</table>
287
-
288
-<blockquote>
289
-<p>
290
-"<i>I see mesh networks naturally evolving to become the dominant form of network over the next few decades, because it’s the most practical solution to a number of problems that will have to be solved in order to build the VR web as well as to connect the entire world to the internet. Centralized networks are only possible in highly developed countries with existing infrastructures like power and telephone grids, as well as roads. You can’t build a tower where you don’t have either power or access. For vast areas of the world, mesh networks will be the only feasible solution.</i>" &#x2013; Valkyrie Ice
291
-</p>
292
-</blockquote>
293
-
294 249
 <p>
295 250
 The Freedombone Mesh is a wireless solution for autonomous or internet connected communication that can be rapidly deployed in temporary, emergency or post-disaster situations where internet access is unavailable or compromised.
296 251
 </p>
297 252
 
298
-<p>
299
-Mesh networks are useful as a quick way to make a fully decentralised communications system which is not connected to or reliant upon the internet. Think festivals, hacker conferences, onboard ships at sea, disaster/war zones, small businesses who don't want the overhead of server maintenance, protests, remote areas of the world, temporary "digital blackouts", scientific expeditions and off-world space colonies.
300
-</p>
301
-
302
-<p>
303
-If an internet connection is available then it can make use of that, but otherwise it can still work regardless of whether the internet exists. So it's not dependent upon ISPs and additional infrastructure other than USB drives isn't required.
304
-</p>
305
-
306
-<p>
307
-Systems only need to be within wifi range of each other for the mesh to be created, so it can be an very convenient way to create a local communications network.
308
-</p>
309
-
310
-<p>
311
-The Freedombone mesh roughly follows MondoNet's ten social specifications:
312
-</p>
313
-
314
-<ul class="org-ul">
315
-<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>
316
-<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>
317
-<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>
318
-<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>
319
-<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>
320
-<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>
321
-<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>
322
-<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>
323
-<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>
324
-<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>
325
-</ul>
326
-
327
-<div id="outline-container-orga5044ee" class="outline-2">
328
-<h2 id="orga5044ee">What the system can do</h2>
329
-<div class="outline-text-2" id="text-orga5044ee">
330 253
 <ul class="org-ul">
331
-<li>Discovery of other users on the network</li>
332
-<li>Text based chat, one-to-one and in groups</li>
333
-<li>Voice chat (VoIP) and video calls</li>
334
-<li>Private and public sharing of files</li>
335
-<li>Blogging</li>
336
-<li>Collaborative editing of documents and presentations</li>
337
-<li>Creating and broadcasting audio media/podcasts</li>
338
-<li>Social network stream. Follow/unfollow other peers</li>
339
-<li>No network administration required</li>
340
-<li>No servers</li>
341
-<li>Internet connection is optional</li>
342
-<li>Works from bootable USB drives or microSD drives</li>
343
-<li>Data is mesh routed between systems</li>
344
-<li>Private communications is end-to-end secured and forward secret</li>
345
-<li>Publicly shared data is <i>content addressable</i></li>
254
+<li><a href="./mesh_philosophic.html">Philosophic</a></li>
255
+<li><a href="./mesh_capabilities.html">Capabilities</a></li>
256
+<li><a href="./mesh_images.html">Disk images and how to build them</a></li>
257
+<li><a href="./mesh_custom.html">Customisation</a></li>
258
+<li><a href="./mesh_usage.html">How to use it</a></li>
346 259
 </ul>
347 260
 
348
-<p>
349
-This system should be quite scalable. Both qTox and IPFS are based upon distributed hash tables (DHT) so that each peer does not need to store the full index of data for the entire network. Gossiping between SSB peers may be slower, but the <a href="https://en.wikipedia.org/wiki/Small-world_network">small world effect</a> will presumably still make for quite efficient delivery in a large network. Caching or pinning of IPFS data and its content addressability means that if a file or blog becomes popular then performance should improve as the number of downloads increases, which is the opposite of the client/server paradigm.
350
-</p>
351
-</div>
352
-</div>
353
-
354
-<div id="outline-container-orge35044f" class="outline-2">
355
-<h2 id="orge35044f">Disk Images</h2>
356
-<div class="outline-text-2" id="text-orge35044f">
357
-</div>
358
-<div id="outline-container-org1e0493b" class="outline-3">
359
-<h3 id="org1e0493b">Writing many images quickly</h3>
360
-<div class="outline-text-3" id="text-org1e0493b">
361
-<p>
362
-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>.
363
-</p>
364
-
365
-<p>
366
-For example on Arch/Parabola:
367
-</p>
368
-
369
-<div class="org-src-container">
370
-<pre class="src src-bash">sudo pacman -S gnome-multi-writer
371
-</pre>
372
-</div>
373
-
374
-<p>
375
-Or on Debian based systems:
376
-</p>
377
-
378
-<div class="org-src-container">
379
-<pre class="src src-bash">sudo apt-get install gnome-multi-writer
380
-</pre>
381
-</div>
382
-
383
-<p>
384
-The MultiWriter tool is also available within mesh client images, so that you can use mesh systems to create more copies of the same system.
385
-</p>
386
-</div>
387
-</div>
388
-<div id="outline-container-orgb14f6b2" class="outline-3">
389
-<h3 id="orgb14f6b2">Client images</h3>
390
-<div class="outline-text-3" id="text-orgb14f6b2">
391
-<div class="org-center">
392
-
393
-<div class="figure">
394
-<p><img src="images/mesh_netbook.jpg" alt="mesh_netbook.jpg" />
395
-</p>
396
-</div>
397
-</div>
398
-
399
-<p>
400
-"Client" isn't exactly the right term, but it's a mesh peer with a user interface. These images can be copied to a USB drive, then you can plug it into a laptop/netbook/desktop machine and boot from it. You will probably also need an Atheros USB wifi dongle (the black protruding object on the left side of the netbook in the picture above), because most built-in wifi usually requires proprietary firmware. In the commands below substitute /dev/sdX with the USB drive device, excluding any trailing numbers (eg. /dev/sdb). The USB drive you're copying to will need to be at least 8GB in size.
401
-</p>
402
-
403
-<div class="org-src-container">
404
-<pre class="src src-bash">sudo apt-get install xz-utils wget
405
-wget https://freedombone.net/downloads/current/freedombone-meshclient-i386.img.xz
406
-wget https://freedombone.net/downloads/current/freedombone-meshclient-i386.img.xz.sig
407
-gpg --verify freedombone-meshclient-i386.img.xz.sig
408
-sha256sum freedombone-meshclient-i386.img.xz
409
-995dd64538f46f6abf83ba258cca6cb82a72399cb9a099caeafc1de947ef795c
410
-unxz freedombone-meshclient-i386.img.xz
411
-sudo dd <span class="org-variable-name">if</span>=/dev/zero <span class="org-variable-name">of</span>=/dev/sdX <span class="org-variable-name">bs</span>=1M <span class="org-variable-name">count</span>=8
412
-sudo dd <span class="org-variable-name">bs</span>=1M <span class="org-variable-name">if</span>=freedombone-meshclient-i386.img <span class="org-variable-name">of</span>=/dev/sdX <span class="org-variable-name">conv</span>=fdatasync
413
-</pre>
414
-</div>
415
-
416
-<p>
417
-To get a number of systems onto the mesh repeat the <i>dd</i> command to create however many bootable USB drives you need.
418
-</p>
419
-
420
-<p>
421
-If you're in an emergency and don't have Atheros wifi dongles then there is also an "insecure" image which contains some proprietary wifi drivers which may work with a wider range of laptops. Proprietary drivers <b>are not recommended</b> because they're unsupportable and may be exploitable or contain malicious antifeatures which fundamentally compromise the security of the network. However, the trade-off between security/maintainability and simply having the ability to communicate at all may be a valid one in some situations.
422
-</p>
423
-
424
-<div class="org-src-container">
425
-<pre class="src src-bash">sudo apt-get install xz-utils wget
426
-wget https://freedombone.net/downloads/current/freedombone-meshclient-insecure-i386.img.xz
427
-wget https://freedombone.net/downloads/current/freedombone-meshclient-insecure-i386.img.xz.sig
428
-gpg --verify freedombone-meshclient-insecure-i386.img.xz.sig
429
-sha256sum freedombone-meshclient-insecure-i386.img.xz
430
-b06e6ff5e56577025e6b994fe0bb28f02da7d2905ac32a2f38d7d074ffe801fc
431
-unxz freedombone-meshclient-insecure-i386.img.xz
432
-sudo dd <span class="org-variable-name">if</span>=/dev/zero <span class="org-variable-name">of</span>=/dev/sdX <span class="org-variable-name">bs</span>=1M <span class="org-variable-name">count</span>=8
433
-sudo dd <span class="org-variable-name">bs</span>=1M <span class="org-variable-name">if</span>=freedombone-meshclient-insecure-i386.img <span class="org-variable-name">of</span>=/dev/sdX <span class="org-variable-name">conv</span>=fdatasync
434
-</pre>
435
-</div>
436
-</div>
437
-</div>
438
-
439
-<div id="outline-container-orgab76248" class="outline-3">
440
-<h3 id="orgab76248">Router images</h3>
441
-<div class="outline-text-3" id="text-orgab76248">
442
-<p>
443
-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.
444
-</p>
445
-</div>
446
-<div id="outline-container-org0b3b781" class="outline-4">
447
-<h4 id="org0b3b781">Beaglebone Black</h4>
448
-<div class="outline-text-4" id="text-org0b3b781">
449
-<div class="org-center">
450
-
451
-<div class="figure">
452
-<p><img src="images/mesh_router.jpg" alt="mesh_router.jpg" />
453
-</p>
454
-</div>
455
-</div>
456
-
457
-<p>
458
-The above picture shows a Beaglebone Black with the image copied onto a microSD card (there's no need to do anything with the internal EMMC). A USB Atheros wifi adaptor with a large antenna is attached and in this case power is from the mains, although it could be from a battery or solar power system capable of supplying 5 volts and maybe 1A (depending upon how active the router is).
459
-</p>
460
-
461
-<div class="org-src-container">
462
-<pre class="src src-bash">sudo apt-get install xz-utils wget
463
-wget https://freedombone.net/downloads/current/freedombone-mesh_beaglebone-armhf.img.xz
464
-wget https://freedombone.net/downloads/current/freedombone-mesh_beaglebone-armhf.img.xz.sig
465
-gpg --verify freedombone-mesh_beaglebone-armhf.img.xz.sig
466
-sha256sum freedombone-mesh_beaglebone-armhf.img.xz
467
-45f131995e2f77188e7ddaf2b42ca3d8d48d821d37c7a31a21e2e6dcceaf510d
468
-unxz freedombone-mesh_beaglebone-armhf.img.xz
469
-sudo dd <span class="org-variable-name">bs</span>=1M <span class="org-variable-name">if</span>=freedombone-mesh_beaglebone-armhf.img <span class="org-variable-name">of</span>=/dev/sdX <span class="org-variable-name">conv</span>=fdatasync
470
-</pre>
471
-</div>
472
-
473
-<p>
474
-If you have a few Beaglebone Blacks to use as routers then repeat the <i>dd</i> command to create however many microSD cards you need.
475
-</p>
476
-
477
-<p>
478
-There is still a software freedom issue with the Beaglebone Black, but it doesn't prevent you from running a fully free system on the board. The TI AM335X SOC has a PowerVR SGX530 GPU which will only run with a proprietary blob, but this would only be an issue for systems with a monitor or LCD screen attached running a desktop environment which also needs GPU acceleration. For "headless" systems such as servers or mesh routers this isn't a problem.
479
-</p>
480
-</div>
481
-</div>
482
-</div>
483
-</div>
484
-
485
-<div id="outline-container-org042ab96" class="outline-2">
486
-<h2 id="org042ab96">Building Disk Images</h2>
487
-<div class="outline-text-2" id="text-org042ab96">
488
-<p>
489
-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.
490
-</p>
491
-
492
-<p>
493
-First you will need to create an image. On a Debian based system (tested on Debian Stretch):
494
-</p>
495
-
496
-<div class="org-src-container">
497
-<pre class="src src-bash">sudo apt-get -y install git wget build-essential
498
-wget https://freedombone.net/downloads/current/freedombone.tar.gz
499
-wget https://freedombone.net/downloads/current/freedombone.tar.gz.sig
500
-gpg --verify freedombone.tar.gz.sig
501
-sha256sum freedombone.tar.gz
502
-fd0b3fe1527de893f4ece7ffe95fdf0c41e635a3f82d22a51b707c1aee541e88
503
-tar -xzvf freedombone.tar.gz
504
-<span class="org-builtin">cd</span> freedombone
505
-git checkout stretch
506
-sudo make install
507
-freedombone-image --setup debian
508
-freedombone-image -t i386 -v meshclient
509
-</pre>
510
-</div>
511
-
512
-<p>
513
-If you don't have Atheros or free software compatible wifi adapter then you can include proprietary wifi drivers which will work with most laptops. This is <b>NOT RECOMMENDED</b> because proprietary drivers are unsupportable and may contain either malware or be exploitable in a way which can't be fixed. However, if you're in an emergency and don't have any Atheros or free software wifi USB dongles then you can use the following command to make the image:
514
-</p>
515
-
516
-<div class="org-src-container">
517
-<pre class="src src-bash">freedombone-image -t i386 -v meshclient --insecure yes
518
-</pre>
519
-</div>
520
-
521
-<p>
522
-This takes a while. Maybe an hour or so, depending on the speed of your system and the internets. The good news though is that once created you can use the resulting image any number of times, and you don't need to trust some pre-built image.
523
-</p>
524
-
525
-<p>
526
-List what drives are on your system with:
527
-</p>
528
-
529
-<div class="org-src-container">
530
-<pre class="src src-bash">ls /dev/sd*
531
-</pre>
532
-</div>
533
-
534
-<p>
535
-Now plug in the USB thumb drive, and do the same again. Notice which drive letter gets added.
536
-</p>
537
-
538
-<p>
539
-You can now copy the image to the USB thumb drive, replacing <b>sdX</b> with the identifier of the USB thumb drive. Don't include any numbers (so for example use <b>sdc</b> instead of <b>sdc1</b>).
540
-</p>
541
-
542
-<div class="org-src-container">
543
-<pre class="src src-bash">sudo dd <span class="org-variable-name">if</span>=/dev/zero <span class="org-variable-name">of</span>=/dev/sdX <span class="org-variable-name">bs</span>=1M <span class="org-variable-name">count</span>=8
544
-sudo dd <span class="org-variable-name">bs</span>=1M <span class="org-variable-name">if</span>=myimagefile.img <span class="org-variable-name">of</span>=/dev/sdX <span class="org-variable-name">conv</span>=fdatasync
545
-</pre>
546
-</div>
547
-
548
-<p>
549
-And wait. Again it will take a while to copy over. When that's done plug it into the laptop or netbook which you want to use on the mesh, power on and set the BIOS to boot from the USB stick.
550
-</p>
551
-
552
-<p>
553
-On first boot you'll be asked to set a username, and then you can open the chat client and select the <b>users</b> icon to show the Tox IDs for other users on the mesh. When folks join they will be announced.
554
-</p>
555
-
556
-<p>
557
-Rinse, repeat, for any number of laptops that you want to get onto the mesh or to build out coverage within an area. There are no servers. Just peer-to-peer communications routed through the network which are end-to-end secure after a friend request is accepted. By default the chat client doesn't log anything.
558
-</p>
559
-
560
-<p>
561
-You can also use single board computers (SBCs) such as the BeagleBone Black to make mesh routers which can be bolted to walls or the sides of buildings and consume minimal electrical power, so could be solar or battery powered for short term events such as festivals. To do that use the following command to make the image:
562
-</p>
563
-
564
-<div class="org-src-container">
565
-<pre class="src src-bash">freedombone-image -t beaglebone -v mesh
566
-</pre>
567
-</div>
568
-
569
-<p>
570
-The resulting image can be copied to a microSD card, inserted into a Beaglebone Black and booted. Don't forget to plug in an Atheros USB wifi dongle.
571
-</p>
572
-</div>
573
-</div>
574
-
575
-<div id="outline-container-org320b796" class="outline-2">
576
-<h2 id="org320b796">Customisation</h2>
577
-<div class="outline-text-2" id="text-org320b796">
578
-<p>
579
-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.
580
-</p>
581
-
582
-<p>
583
-If you need particular <i>dconf</i> commands to alter desktop appearance or behavior then see the function <i>mesh_client_startup_applications</i> within <b>src/freedombone-image-customise</b>.
584
-</p>
585
-</div>
586
-</div>
587
-<div id="outline-container-org90e6351" class="outline-2">
588
-<h2 id="org90e6351">How to use it</h2>
589
-<div class="outline-text-2" id="text-org90e6351">
590
-<p>
591
-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.
592
-</p>
593
-
594
-<p>
595
-After a minute or two if you are within wifi range and there is at least one other user on the network then you should see additional icons appear on the desktop, such as <i>Other Users</i> and <i>Chat</i>.
596
-</p>
597
-</div>
598
-
599
-<div id="outline-container-orgaf18aab" class="outline-3">
600
-<h3 id="orgaf18aab">Boot trouble</h3>
601
-<div class="outline-text-3" id="text-orgaf18aab">
602
-<p>
603
-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.
604
-</p>
605
-
606
-<p>
607
-After the system has booted successfully the problem should resolve itself on subsequent reboots.
608
-</p>
609
-</div>
610
-</div>
611
-<div id="outline-container-org17b251b" class="outline-3">
612
-<h3 id="org17b251b">Set the Date</h3>
613
-<div class="outline-text-3" id="text-org17b251b">
614
-<p>
615
-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.
616
-</p>
617
-
618
-<p>
619
-<b>Right click on the date</b> in the top right corner of the screen. Select <b>preferences</b>, then click the <b>Time Settings</b> button. You can then select the date from the calendar and set the time, then click the <b>Set System Time</b> button. Enter the default password, which is <i>freedombone</i>.
620
-</p>
621
-</div>
622
-</div>
623
-<div id="outline-container-org271731e" class="outline-3">
624
-<h3 id="org271731e">Check network status</h3>
625
-<div class="outline-text-3" id="text-org271731e">
626
-<p>
627
-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.
628
-</p>
629
-
630
-<p>
631
-Select the wifi icon on the desktop and enter the password '<i>freedombone</i>'. The network configuration will go into a monitoring mode and in the bottom right side of the window you will be able to see signal strength and other parameters. This can help you to locate systems or adjust antennas to get the best wifi performance.
632
-</p>
633
-
634
-
635
-<div class="org-center">
636
-
637
-<div class="figure">
638
-<p><img src="images/mesh_signal.jpg" alt="mesh_signal.jpg" />
639
-</p>
640
-</div>
641
-</div>
642
-
643
-<p>
644
-When you are finished close the window and then select the <i>Network Restart</i> desktop icon, which will restart the B.A.T.M.A.N. network. You can also use the restart icon if you are within range of the mesh network but the <i>Chat</i> and <i>Other Users</i> icons do not automatically appear after a few minutes.
645
-</p>
646
-</div>
647
-</div>
648
-<div id="outline-container-org91c530e" class="outline-3">
649
-<h3 id="org91c530e">Connecting to the internet</h3>
650
-<div class="outline-text-3" id="text-org91c530e">
651
-<p>
652
-If you need to be able to access the internet from the mesh then connect one of the peers to an internet router using an ethernet cable, then reboot it. Other peers in the mesh, including any attached mobile devices, will then be able to access the internet using the ethernet attached peer as a gateway. <a href="https://en.wikipedia.org/wiki/Freifunk">Freifunk</a> works in a similar way.
653
-</p>
654
-
655
-<p>
656
-After connecting one peer to the internet you may need to reboot other peers in order to update their network configurations.
657
-</p>
658
-
659
-<p>
660
-If for legal reasons you need to connect to the internet via a VPN then openvpn is preinstalled and you can run the command:
661
-</p>
662
-
663
-<div class="org-src-container">
664
-<pre class="src src-bash">sudo openvpn myclient.ovpn
665
-</pre>
666
-</div>
667
-
668
-<p>
669
-Where <i>myclient.ovpn</i> comes from your VPN provider and with the password "<i>freedombone</i>".
670
-</p>
671
-</div>
672
-</div>
673
-<div id="outline-container-orgad68675" class="outline-3">
674
-<h3 id="orgad68675">Connecting two meshes over the internet via a VPN tunnel</h3>
675
-<div class="outline-text-3" id="text-orgad68675">
676
-<p>
677
-Maybe the internet exists, but you don't care about getting any content from it and just want to use it as a way to connect mesh networks from different geographical locations together.
678
-</p>
679
-
680
-<p>
681
-In your home directory on a system connected via ethernet to an internet router you'll find a file called <b>vpn.tar.gz</b>. If you want another mesh to be able to connect to yours then send them this file and get them to uncompress it into their home directory also on an internet gateway machine. If they have an external IP address or domain name for your router then they will be able to VPN connect using the <b>Connect Meshes</b> icon. They should also forward port 653 from their internet router to the mesh gateway machine.
682
-</p>
683
-
684
-<div class="org-center">
685
-
686
-<div class="figure">
687
-<p><img src="images/mesh_connect.jpg" alt="mesh_connect.jpg" />
688
-</p>
689
-</div>
690
-</div>
691
-
692
-<p>
693
-You should create a new <b>vpn.tar.gz</b> file for every other mesh which wants to be able to connect to yours. If you are prompted for a password it is 'freedombone'.
694
-</p>
695
-
696
-<p>
697
-From a deep packet inspection point of view the traffic going over the internet between mesh gateways will just look like any other TLS connection to a server.
698
-</p>
699
-</div>
700
-</div>
701
-
702
-<div id="outline-container-org538360a" class="outline-3">
703
-<h3 id="org538360a">Mobile devices (phones, etc)</h3>
704
-<div class="outline-text-3" id="text-org538360a">
705
-<p>
706
-To allow mobile devices to connect to the mesh you will need a second wifi adapter connected to your laptop/netbook/SBC. Plug in a second wifi adapter then reboot the system. The second adaptor will then create a wifi hotspot which mobile devices can connect to. The hotspot name also contains its local IP address (eg. "<i>mesh-192.168.1.83</i>").
707
-</p>
708
-
709
-<p>
710
-On a typical Android device go to <b>Settings</b> then <b>Security</b> and ensure that <b>Unknown sources</b> is enabled. Also within <b>Wifi</b> from the <b>Settings</b> screen select the mesh hotspot. The password is "<i>freedombone</i>". Open a non-Tor browser and navigate to the IP address showing in the hotspot name. You can then download and install mesh apps.
711
-</p>
712
-
713
-<div class="org-center">
714
-
715
-<div class="figure">
716
-<p><img src="images/mesh_mobileapps.jpg" alt="mesh_mobileapps.jpg" />
717
-</p>
718
-</div>
719
-</div>
720
-
721
-<p>
722
-On some android devices you may need to move the downloaded APK file from the <b>Downloads</b> directory to your <b>home</b> directory before you can install it.
723
-</p>
724
-</div>
725
-</div>
726
-<div id="outline-container-orgef6e799" class="outline-3">
727
-<h3 id="orgef6e799">Chat System</h3>
728
-<div class="outline-text-3" id="text-orgef6e799">
729
-<p>
730
-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.
731
-</p>
732
-
733
-<div class="org-center">
734
-
735
-<div class="figure">
736
-<p><img src="images/mesh_paste_tox_id.jpg" alt="mesh_paste_tox_id.jpg" />
737
-</p>
738
-</div>
739
-</div>
740
-
741
-<p>
742
-The other user can then accept or decline your friend request.
743
-</p>
744
-
745
-<div class="org-center">
746
-
747
-<div class="figure">
748
-<p><img src="images/mesh_friend_request.jpg" alt="mesh_friend_request.jpg" />
749
-</p>
750
-</div>
751
-</div>
752
-
753
-<p>
754
-You can also select an avatar by selecting the grey head and shoulders image.
755
-</p>
756
-
757
-<div class="org-center">
758
-
759
-<div class="figure">
760
-<p><img src="images/mesh_choose_avatar.jpg" alt="mesh_choose_avatar.jpg" />
761
-</p>
762
-</div>
763
-</div>
764
-
765
-<p>
766
-And by selecting the user from the list on the left hand side the chat can begin.
767
-</p>
768
-
769
-<div class="org-center">
770
-
771
-<div class="figure">
772
-<p><img src="images/mesh_text_chat.jpg" alt="mesh_text_chat.jpg" />
773
-</p>
774
-</div>
775
-</div>
776
-
777
-<p>
778
-One important point is that by default the microphone is turned off. When doing voice chat you can select the microphone volume with the drop down slider in the top right corner of the screen.
779
-</p>
780
-
781
-<p>
782
-At present video doesn't work reliably, but text and voice chat do work well.
783
-</p>
784
-</div>
785
-</div>
786
-
787
-<div id="outline-container-org9a11098" class="outline-3">
788
-<h3 id="org9a11098">Collaborative document editing</h3>
789
-<div class="outline-text-3" id="text-org9a11098">
790
-<p>
791
-The mesh system includes the ability to collaboratively edit various sorts of documents using CryptPad. CryptPad is an almost peer-to-peer system in that it is designed for a client/server environment but that the server aspect of it is very minimal and limited to orchestrating the connected clients. With CryptPad installed on each mesh peer it effectively enables peer-to-peer collaborative editing. Documents are ephemeral and forgotten unless they're exported or copy-pasted to permanent storage.
792
-</p>
793
-
794
-<div class="org-center">
795
-
796
-<div class="figure">
797
-<p><img src="images/mesh_cryptpad1.jpg" alt="mesh_cryptpad1.jpg" />
798
-</p>
799
-</div>
800
-</div>
801
-
802
-<p>
803
-To create a document click on the CryptPad icon. Depending upon the specifications of your system it may take a few seconds to load, so don't be too disturned if the browser contents look blank for a while. Select <span class="underline">Rich Text Pad</span> and give yourself a username.
804
-</p>
805
-
806 261
 <div class="org-center">
807 262
 
808 263
 <div class="figure">
809
-<p><img src="images/mesh_cryptpad2.jpg" alt="mesh_cryptpad2.jpg" />
264
+<p><img src="images/mesh_architecture1.jpg" alt="mesh_architecture1.jpg" />
810 265
 </p>
811 266
 </div>
812 267
 </div>
813 268
 
814 269
 <p>
815
-If you have the chat system running you can then copy and paste the URL for your pad into the chat, and the other user can then open the link and edit the document with you. You can repeat that for however many other users you wish to be able to edit.
816
-</p>
817
-</div>
818
-</div>
819
-
820
-<div id="outline-container-org05473b7" class="outline-3">
821
-<h3 id="org05473b7">Social Network</h3>
822
-<div class="outline-text-3" id="text-org05473b7">
823
-<p>
824
-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.
825
-</p>
826
-
827
-<p>
828
-Double click on the "Social" icon to open the app, then add your nickname and optionally a description. If you want to choose an avatar image some can be found within the directory <b>/usr/share/freedombone/avatars</b>. On older systems or systems without a hardware random number generator, Patchwork sometimes takes a long time (a few minutes) to open for the first time after clicking the icon. This is most likely due to the initial generation of encryption keys, so be patient.
829
-</p>
830
-
831
-<div class="org-center">
832
-
833
-<div class="figure">
834
-<p><img src="images/patchwork_setup.jpg" alt="patchwork_setup.jpg" />
835
-</p>
836
-</div>
837
-</div>
838
-
839
-<p>
840
-Other Patchwork users on the mesh will appear automatically under the <b>local</b> list and you can select and follow them if you wish. It's also possible to select the dark theme from <b>settings</b> on the drop down menu if you prefer.
841
-</p>
842
-
843
-<div class="org-center">
844
-
845
-<div class="figure">
846
-<p><img src="images/patchwork_public.jpg" alt="patchwork_public.jpg" />
847
-</p>
848
-</div>
849
-</div>
850
-
851
-<p>
852
-The Secure Scuttlebutt protocol which Patchwork is based upon is intended to be robust to intermittent network connectivity, so you can write posts when out of range and they will sync once you are back in the network.
853
-</p>
854
-</div>
855
-</div>
856
-
857
-<div id="outline-container-orgc7f141c" class="outline-3">
858
-<h3 id="orgc7f141c">Sharing Files</h3>
859
-<div class="outline-text-3" id="text-orgc7f141c">
860
-<p>
861
-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.
862
-</p>
863
-
864
-<div class="org-center">
865
-
866
-<div class="figure">
867
-<p><img src="images/mesh_share_files.jpg" alt="mesh_share_files.jpg" />
868
-</p>
869
-</div>
870
-</div>
871
-</div>
872
-</div>
873
-
874
-<div id="outline-container-orgc6faf49" class="outline-3">
875
-<h3 id="orgc6faf49">Blogging</h3>
876
-<div class="outline-text-3" id="text-orgc6faf49">
877
-<p>
878
-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.
879
-</p>
880
-
881
-<div class="org-center">
882
-
883
-<div class="figure">
884
-<p><img src="images/mesh_new_blog.jpg" alt="mesh_new_blog.jpg" />
270
+Mesh networks are useful as a quick way to make a fully decentralised communications system which is not connected to or reliant upon the internet. Think festivals, hacker conferences, onboard ships at sea, disaster/war zones, small businesses who don't want the overhead of server maintenance, protests, remote areas of the world, temporary "digital blackouts", scientific expeditions and off-world space colonies.
885 271
 </p>
886
-</div>
887
-</div>
888 272
 
889 273
 <p>
890
-To finish your blog entry just select <i>Save</i> and then close the editor. On older hardware it may take a while to publish the results, and this depends upon the amount of computation needed by IPFS to create file hashes. If you make no changes to the default text then the new blog entry will not be saved.
891
-</p>
892
-
893
-<div class="org-center">
894
-
895
-<div class="figure">
896
-<p><img src="images/mesh_new_blog2.jpg" alt="mesh_new_blog2.jpg" />
897
-</p>
898
-</div>
899
-</div>
900
-
901
-<div class="org-center">
902
-
903
-<div class="figure">
904
-<p><img src="images/mesh_view_blog.jpg" alt="mesh_view_blog.jpg" />
274
+If an internet connection is available then it can make use of that, but otherwise it can still work regardless of whether the internet exists. So it's not dependent upon ISPs and additional infrastructure other than USB drives isn't required.
905 275
 </p>
906
-</div>
907
-</div>
908 276
 
909 277
 <p>
910
-You can also visit other blogs, edit or delete your previous entry and also change your blog theme.
278
+Systems only need to be within wifi range of each other for the mesh to be created, so it can be an very convenient way to create a local communications network.
911 279
 </p>
912 280
 
913
-
914 281
 <div class="org-center">
915 282
 <p>
916 283
 This site can also be accessed via a Tor browser at <a href="http://pazyv7nkllp76hqr.onion">http://pazyv7nkllp76hqr.onion</a>
917 284
 </p>
918 285
 </div>
919 286
 </div>
920
-</div>
921
-</div>
922
-</div>
923 287
 <div id="postamble" class="status">
924 288
 
925 289
 <style type="text/css">

+ 300
- 0
website/EN/mesh_capabilities.html Ver arquivo

@@ -0,0 +1,300 @@
1
+<?xml version="1.0" encoding="utf-8"?>
2
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
3
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
4
+<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
5
+<head>
6
+<!-- 2017-10-27 Fri 11:40 -->
7
+<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
8
+<meta name="viewport" content="width=device-width, initial-scale=1" />
9
+<title>&lrm;</title>
10
+<meta name="generator" content="Org mode" />
11
+<meta name="author" content="Bob Mottram" />
12
+<meta name="description" content="Turn the Beaglebone Black into a personal communications server"
13
+ />
14
+<meta name="keywords" content="freedombox, debian, beaglebone, red matrix, email, web server, home server, internet, censorship, surveillance, social network, irc, jabber" />
15
+<style type="text/css">
16
+ <!--/*--><![CDATA[/*><!--*/
17
+  .title  { text-align: center;
18
+             margin-bottom: .2em; }
19
+  .subtitle { text-align: center;
20
+              font-size: medium;
21
+              font-weight: bold;
22
+              margin-top:0; }
23
+  .todo   { font-family: monospace; color: red; }
24
+  .done   { font-family: monospace; color: green; }
25
+  .priority { font-family: monospace; color: orange; }
26
+  .tag    { background-color: #eee; font-family: monospace;
27
+            padding: 2px; font-size: 80%; font-weight: normal; }
28
+  .timestamp { color: #bebebe; }
29
+  .timestamp-kwd { color: #5f9ea0; }
30
+  .org-right  { margin-left: auto; margin-right: 0px;  text-align: right; }
31
+  .org-left   { margin-left: 0px;  margin-right: auto; text-align: left; }
32
+  .org-center { margin-left: auto; margin-right: auto; text-align: center; }
33
+  .underline { text-decoration: underline; }
34
+  #postamble p, #preamble p { font-size: 90%; margin: .2em; }
35
+  p.verse { margin-left: 3%; }
36
+  pre {
37
+    border: 1px solid #ccc;
38
+    box-shadow: 3px 3px 3px #eee;
39
+    padding: 8pt;
40
+    font-family: monospace;
41
+    overflow: auto;
42
+    margin: 1.2em;
43
+  }
44
+  pre.src {
45
+    position: relative;
46
+    overflow: visible;
47
+    padding-top: 1.2em;
48
+  }
49
+  pre.src:before {
50
+    display: none;
51
+    position: absolute;
52
+    background-color: white;
53
+    top: -10px;
54
+    right: 10px;
55
+    padding: 3px;
56
+    border: 1px solid black;
57
+  }
58
+  pre.src:hover:before { display: inline;}
59
+  /* Languages per Org manual */
60
+  pre.src-asymptote:before { content: 'Asymptote'; }
61
+  pre.src-awk:before { content: 'Awk'; }
62
+  pre.src-C:before { content: 'C'; }
63
+  /* pre.src-C++ doesn't work in CSS */
64
+  pre.src-clojure:before { content: 'Clojure'; }
65
+  pre.src-css:before { content: 'CSS'; }
66
+  pre.src-D:before { content: 'D'; }
67
+  pre.src-ditaa:before { content: 'ditaa'; }
68
+  pre.src-dot:before { content: 'Graphviz'; }
69
+  pre.src-calc:before { content: 'Emacs Calc'; }
70
+  pre.src-emacs-lisp:before { content: 'Emacs Lisp'; }
71
+  pre.src-fortran:before { content: 'Fortran'; }
72
+  pre.src-gnuplot:before { content: 'gnuplot'; }
73
+  pre.src-haskell:before { content: 'Haskell'; }
74
+  pre.src-hledger:before { content: 'hledger'; }
75
+  pre.src-java:before { content: 'Java'; }
76
+  pre.src-js:before { content: 'Javascript'; }
77
+  pre.src-latex:before { content: 'LaTeX'; }
78
+  pre.src-ledger:before { content: 'Ledger'; }
79
+  pre.src-lisp:before { content: 'Lisp'; }
80
+  pre.src-lilypond:before { content: 'Lilypond'; }
81
+  pre.src-lua:before { content: 'Lua'; }
82
+  pre.src-matlab:before { content: 'MATLAB'; }
83
+  pre.src-mscgen:before { content: 'Mscgen'; }
84
+  pre.src-ocaml:before { content: 'Objective Caml'; }
85
+  pre.src-octave:before { content: 'Octave'; }
86
+  pre.src-org:before { content: 'Org mode'; }
87
+  pre.src-oz:before { content: 'OZ'; }
88
+  pre.src-plantuml:before { content: 'Plantuml'; }
89
+  pre.src-processing:before { content: 'Processing.js'; }
90
+  pre.src-python:before { content: 'Python'; }
91
+  pre.src-R:before { content: 'R'; }
92
+  pre.src-ruby:before { content: 'Ruby'; }
93
+  pre.src-sass:before { content: 'Sass'; }
94
+  pre.src-scheme:before { content: 'Scheme'; }
95
+  pre.src-screen:before { content: 'Gnu Screen'; }
96
+  pre.src-sed:before { content: 'Sed'; }
97
+  pre.src-sh:before { content: 'shell'; }
98
+  pre.src-sql:before { content: 'SQL'; }
99
+  pre.src-sqlite:before { content: 'SQLite'; }
100
+  /* additional languages in org.el's org-babel-load-languages alist */
101
+  pre.src-forth:before { content: 'Forth'; }
102
+  pre.src-io:before { content: 'IO'; }
103
+  pre.src-J:before { content: 'J'; }
104
+  pre.src-makefile:before { content: 'Makefile'; }
105
+  pre.src-maxima:before { content: 'Maxima'; }
106
+  pre.src-perl:before { content: 'Perl'; }
107
+  pre.src-picolisp:before { content: 'Pico Lisp'; }
108
+  pre.src-scala:before { content: 'Scala'; }
109
+  pre.src-shell:before { content: 'Shell Script'; }
110
+  pre.src-ebnf2ps:before { content: 'ebfn2ps'; }
111
+  /* additional language identifiers per "defun org-babel-execute"
112
+       in ob-*.el */
113
+  pre.src-cpp:before  { content: 'C++'; }
114
+  pre.src-abc:before  { content: 'ABC'; }
115
+  pre.src-coq:before  { content: 'Coq'; }
116
+  pre.src-groovy:before  { content: 'Groovy'; }
117
+  /* additional language identifiers from org-babel-shell-names in
118
+     ob-shell.el: ob-shell is the only babel language using a lambda to put
119
+     the execution function name together. */
120
+  pre.src-bash:before  { content: 'bash'; }
121
+  pre.src-csh:before  { content: 'csh'; }
122
+  pre.src-ash:before  { content: 'ash'; }
123
+  pre.src-dash:before  { content: 'dash'; }
124
+  pre.src-ksh:before  { content: 'ksh'; }
125
+  pre.src-mksh:before  { content: 'mksh'; }
126
+  pre.src-posh:before  { content: 'posh'; }
127
+  /* Additional Emacs modes also supported by the LaTeX listings package */
128
+  pre.src-ada:before { content: 'Ada'; }
129
+  pre.src-asm:before { content: 'Assembler'; }
130
+  pre.src-caml:before { content: 'Caml'; }
131
+  pre.src-delphi:before { content: 'Delphi'; }
132
+  pre.src-html:before { content: 'HTML'; }
133
+  pre.src-idl:before { content: 'IDL'; }
134
+  pre.src-mercury:before { content: 'Mercury'; }
135
+  pre.src-metapost:before { content: 'MetaPost'; }
136
+  pre.src-modula-2:before { content: 'Modula-2'; }
137
+  pre.src-pascal:before { content: 'Pascal'; }
138
+  pre.src-ps:before { content: 'PostScript'; }
139
+  pre.src-prolog:before { content: 'Prolog'; }
140
+  pre.src-simula:before { content: 'Simula'; }
141
+  pre.src-tcl:before { content: 'tcl'; }
142
+  pre.src-tex:before { content: 'TeX'; }
143
+  pre.src-plain-tex:before { content: 'Plain TeX'; }
144
+  pre.src-verilog:before { content: 'Verilog'; }
145
+  pre.src-vhdl:before { content: 'VHDL'; }
146
+  pre.src-xml:before { content: 'XML'; }
147
+  pre.src-nxml:before { content: 'XML'; }
148
+  /* add a generic configuration mode; LaTeX export needs an additional
149
+     (add-to-list 'org-latex-listings-langs '(conf " ")) in .emacs */
150
+  pre.src-conf:before { content: 'Configuration File'; }
151
+
152
+  table { border-collapse:collapse; }
153
+  caption.t-above { caption-side: top; }
154
+  caption.t-bottom { caption-side: bottom; }
155
+  td, th { vertical-align:top;  }
156
+  th.org-right  { text-align: center;  }
157
+  th.org-left   { text-align: center;   }
158
+  th.org-center { text-align: center; }
159
+  td.org-right  { text-align: right;  }
160
+  td.org-left   { text-align: left;   }
161
+  td.org-center { text-align: center; }
162
+  dt { font-weight: bold; }
163
+  .footpara { display: inline; }
164
+  .footdef  { margin-bottom: 1em; }
165
+  .figure { padding: 1em; }
166
+  .figure p { text-align: center; }
167
+  .inlinetask {
168
+    padding: 10px;
169
+    border: 2px solid gray;
170
+    margin: 10px;
171
+    background: #ffffcc;
172
+  }
173
+  #org-div-home-and-up
174
+   { text-align: right; font-size: 70%; white-space: nowrap; }
175
+  textarea { overflow-x: auto; }
176
+  .linenr { font-size: smaller }
177
+  .code-highlighted { background-color: #ffff00; }
178
+  .org-info-js_info-navigation { border-style: none; }
179
+  #org-info-js_console-label
180
+    { font-size: 10px; font-weight: bold; white-space: nowrap; }
181
+  .org-info-js_search-highlight
182
+    { background-color: #ffff00; color: #000000; font-weight: bold; }
183
+  .org-svg { width: 90%; }
184
+  /*]]>*/-->
185
+</style>
186
+<link rel="stylesheet" type="text/css" href="freedombone.css" />
187
+<script type="text/javascript">
188
+/*
189
+@licstart  The following is the entire license notice for the
190
+JavaScript code in this tag.
191
+
192
+Copyright (C) 2012-2017 Free Software Foundation, Inc.
193
+
194
+The JavaScript code in this tag is free software: you can
195
+redistribute it and/or modify it under the terms of the GNU
196
+General Public License (GNU GPL) as published by the Free Software
197
+Foundation, either version 3 of the License, or (at your option)
198
+any later version.  The code is distributed WITHOUT ANY WARRANTY;
199
+without even the implied warranty of MERCHANTABILITY or FITNESS
200
+FOR A PARTICULAR PURPOSE.  See the GNU GPL for more details.
201
+
202
+As additional permission under GNU GPL version 3 section 7, you
203
+may distribute non-source (e.g., minimized or compacted) forms of
204
+that code without the copy of the GNU GPL normally required by
205
+section 4, provided you include this license notice and a URL
206
+through which recipients can access the Corresponding Source.
207
+
208
+
209
+@licend  The above is the entire license notice
210
+for the JavaScript code in this tag.
211
+*/
212
+<!--/*--><![CDATA[/*><!--*/
213
+ function CodeHighlightOn(elem, id)
214
+ {
215
+   var target = document.getElementById(id);
216
+   if(null != target) {
217
+     elem.cacheClassElem = elem.className;
218
+     elem.cacheClassTarget = target.className;
219
+     target.className = "code-highlighted";
220
+     elem.className   = "code-highlighted";
221
+   }
222
+ }
223
+ function CodeHighlightOff(elem, id)
224
+ {
225
+   var target = document.getElementById(id);
226
+   if(elem.cacheClassElem)
227
+     elem.className = elem.cacheClassElem;
228
+   if(elem.cacheClassTarget)
229
+     target.className = elem.cacheClassTarget;
230
+ }
231
+/*]]>*///-->
232
+</script>
233
+</head>
234
+<body>
235
+<div id="preamble" class="status">
236
+<a name="top" id="top"></a>
237
+</div>
238
+<div id="content">
239
+<div class="org-center">
240
+
241
+<div class="figure">
242
+<p><img src="images/logo.png" alt="logo.png" />
243
+</p>
244
+</div>
245
+</div>
246
+
247
+<center><h1>Mesh Network: Capabilities</h1></center>
248
+
249
+<p>
250
+The mesh system has the following capabilities:
251
+</p>
252
+
253
+<ul class="org-ul">
254
+<li>Discovery of other users on the network</li>
255
+<li>Text based chat, one-to-one and in groups</li>
256
+<li>Voice chat (VoIP) and video calls</li>
257
+<li>Private and public sharing of files</li>
258
+<li>Blogging</li>
259
+<li>Collaborative editing of documents and presentations</li>
260
+<li>Creating and broadcasting audio media/podcasts</li>
261
+<li>Social network stream. Follow/unfollow other peers</li>
262
+<li>No network administration required</li>
263
+<li>No servers</li>
264
+<li>Internet connection is optional</li>
265
+<li>Works from bootable USB drives or microSD drives</li>
266
+<li>Data is mesh routed between systems</li>
267
+<li>Private communications is end-to-end secured and forward secret</li>
268
+<li>Publicly shared data is <i>content addressable</i></li>
269
+</ul>
270
+
271
+<p>
272
+This system should be quite scalable. Both qTox and IPFS are based upon distributed hash tables (DHT) so that each peer does not need to store the full index of data for the entire network. Gossiping between SSB peers may be slower, but the <a href="https://en.wikipedia.org/wiki/Small-world_network">small world effect</a> will presumably still make for quite efficient delivery in a large network. Caching or pinning of IPFS data and its content addressability means that if a file or blog becomes popular then performance should improve as the number of downloads increases, which is the opposite of the client/server paradigm.
273
+</p>
274
+</div>
275
+<div id="postamble" class="status">
276
+
277
+<style type="text/css">
278
+.back-to-top {
279
+    position: fixed;
280
+    bottom: 2em;
281
+    right: 0px;
282
+    text-decoration: none;
283
+    color: #000000;
284
+    background-color: rgba(235, 235, 235, 0.80);
285
+    font-size: 12px;
286
+    padding: 1em;
287
+    display: none;
288
+}
289
+
290
+.back-to-top:hover {
291
+    background-color: rgba(135, 135, 135, 0.50);
292
+}
293
+</style>
294
+
295
+<div class="back-to-top">
296
+<a href="#top">Back to top</a> | <a href="mailto:bob@freedombone.net">E-mail me</a>
297
+</div>
298
+</div>
299
+</body>
300
+</html>

+ 282
- 0
website/EN/mesh_custom.html Ver arquivo

@@ -0,0 +1,282 @@
1
+<?xml version="1.0" encoding="utf-8"?>
2
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
3
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
4
+<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
5
+<head>
6
+<!-- 2017-10-27 Fri 11:41 -->
7
+<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
8
+<meta name="viewport" content="width=device-width, initial-scale=1" />
9
+<title>&lrm;</title>
10
+<meta name="generator" content="Org mode" />
11
+<meta name="author" content="Bob Mottram" />
12
+<meta name="description" content="Turn the Beaglebone Black into a personal communications server"
13
+ />
14
+<meta name="keywords" content="freedombox, debian, beaglebone, red matrix, email, web server, home server, internet, censorship, surveillance, social network, irc, jabber" />
15
+<style type="text/css">
16
+ <!--/*--><![CDATA[/*><!--*/
17
+  .title  { text-align: center;
18
+             margin-bottom: .2em; }
19
+  .subtitle { text-align: center;
20
+              font-size: medium;
21
+              font-weight: bold;
22
+              margin-top:0; }
23
+  .todo   { font-family: monospace; color: red; }
24
+  .done   { font-family: monospace; color: green; }
25
+  .priority { font-family: monospace; color: orange; }
26
+  .tag    { background-color: #eee; font-family: monospace;
27
+            padding: 2px; font-size: 80%; font-weight: normal; }
28
+  .timestamp { color: #bebebe; }
29
+  .timestamp-kwd { color: #5f9ea0; }
30
+  .org-right  { margin-left: auto; margin-right: 0px;  text-align: right; }
31
+  .org-left   { margin-left: 0px;  margin-right: auto; text-align: left; }
32
+  .org-center { margin-left: auto; margin-right: auto; text-align: center; }
33
+  .underline { text-decoration: underline; }
34
+  #postamble p, #preamble p { font-size: 90%; margin: .2em; }
35
+  p.verse { margin-left: 3%; }
36
+  pre {
37
+    border: 1px solid #ccc;
38
+    box-shadow: 3px 3px 3px #eee;
39
+    padding: 8pt;
40
+    font-family: monospace;
41
+    overflow: auto;
42
+    margin: 1.2em;
43
+  }
44
+  pre.src {
45
+    position: relative;
46
+    overflow: visible;
47
+    padding-top: 1.2em;
48
+  }
49
+  pre.src:before {
50
+    display: none;
51
+    position: absolute;
52
+    background-color: white;
53
+    top: -10px;
54
+    right: 10px;
55
+    padding: 3px;
56
+    border: 1px solid black;
57
+  }
58
+  pre.src:hover:before { display: inline;}
59
+  /* Languages per Org manual */
60
+  pre.src-asymptote:before { content: 'Asymptote'; }
61
+  pre.src-awk:before { content: 'Awk'; }
62
+  pre.src-C:before { content: 'C'; }
63
+  /* pre.src-C++ doesn't work in CSS */
64
+  pre.src-clojure:before { content: 'Clojure'; }
65
+  pre.src-css:before { content: 'CSS'; }
66
+  pre.src-D:before { content: 'D'; }
67
+  pre.src-ditaa:before { content: 'ditaa'; }
68
+  pre.src-dot:before { content: 'Graphviz'; }
69
+  pre.src-calc:before { content: 'Emacs Calc'; }
70
+  pre.src-emacs-lisp:before { content: 'Emacs Lisp'; }
71
+  pre.src-fortran:before { content: 'Fortran'; }
72
+  pre.src-gnuplot:before { content: 'gnuplot'; }
73
+  pre.src-haskell:before { content: 'Haskell'; }
74
+  pre.src-hledger:before { content: 'hledger'; }
75
+  pre.src-java:before { content: 'Java'; }
76
+  pre.src-js:before { content: 'Javascript'; }
77
+  pre.src-latex:before { content: 'LaTeX'; }
78
+  pre.src-ledger:before { content: 'Ledger'; }
79
+  pre.src-lisp:before { content: 'Lisp'; }
80
+  pre.src-lilypond:before { content: 'Lilypond'; }
81
+  pre.src-lua:before { content: 'Lua'; }
82
+  pre.src-matlab:before { content: 'MATLAB'; }
83
+  pre.src-mscgen:before { content: 'Mscgen'; }
84
+  pre.src-ocaml:before { content: 'Objective Caml'; }
85
+  pre.src-octave:before { content: 'Octave'; }
86
+  pre.src-org:before { content: 'Org mode'; }
87
+  pre.src-oz:before { content: 'OZ'; }
88
+  pre.src-plantuml:before { content: 'Plantuml'; }
89
+  pre.src-processing:before { content: 'Processing.js'; }
90
+  pre.src-python:before { content: 'Python'; }
91
+  pre.src-R:before { content: 'R'; }
92
+  pre.src-ruby:before { content: 'Ruby'; }
93
+  pre.src-sass:before { content: 'Sass'; }
94
+  pre.src-scheme:before { content: 'Scheme'; }
95
+  pre.src-screen:before { content: 'Gnu Screen'; }
96
+  pre.src-sed:before { content: 'Sed'; }
97
+  pre.src-sh:before { content: 'shell'; }
98
+  pre.src-sql:before { content: 'SQL'; }
99
+  pre.src-sqlite:before { content: 'SQLite'; }
100
+  /* additional languages in org.el's org-babel-load-languages alist */
101
+  pre.src-forth:before { content: 'Forth'; }
102
+  pre.src-io:before { content: 'IO'; }
103
+  pre.src-J:before { content: 'J'; }
104
+  pre.src-makefile:before { content: 'Makefile'; }
105
+  pre.src-maxima:before { content: 'Maxima'; }
106
+  pre.src-perl:before { content: 'Perl'; }
107
+  pre.src-picolisp:before { content: 'Pico Lisp'; }
108
+  pre.src-scala:before { content: 'Scala'; }
109
+  pre.src-shell:before { content: 'Shell Script'; }
110
+  pre.src-ebnf2ps:before { content: 'ebfn2ps'; }
111
+  /* additional language identifiers per "defun org-babel-execute"
112
+       in ob-*.el */
113
+  pre.src-cpp:before  { content: 'C++'; }
114
+  pre.src-abc:before  { content: 'ABC'; }
115
+  pre.src-coq:before  { content: 'Coq'; }
116
+  pre.src-groovy:before  { content: 'Groovy'; }
117
+  /* additional language identifiers from org-babel-shell-names in
118
+     ob-shell.el: ob-shell is the only babel language using a lambda to put
119
+     the execution function name together. */
120
+  pre.src-bash:before  { content: 'bash'; }
121
+  pre.src-csh:before  { content: 'csh'; }
122
+  pre.src-ash:before  { content: 'ash'; }
123
+  pre.src-dash:before  { content: 'dash'; }
124
+  pre.src-ksh:before  { content: 'ksh'; }
125
+  pre.src-mksh:before  { content: 'mksh'; }
126
+  pre.src-posh:before  { content: 'posh'; }
127
+  /* Additional Emacs modes also supported by the LaTeX listings package */
128
+  pre.src-ada:before { content: 'Ada'; }
129
+  pre.src-asm:before { content: 'Assembler'; }
130
+  pre.src-caml:before { content: 'Caml'; }
131
+  pre.src-delphi:before { content: 'Delphi'; }
132
+  pre.src-html:before { content: 'HTML'; }
133
+  pre.src-idl:before { content: 'IDL'; }
134
+  pre.src-mercury:before { content: 'Mercury'; }
135
+  pre.src-metapost:before { content: 'MetaPost'; }
136
+  pre.src-modula-2:before { content: 'Modula-2'; }
137
+  pre.src-pascal:before { content: 'Pascal'; }
138
+  pre.src-ps:before { content: 'PostScript'; }
139
+  pre.src-prolog:before { content: 'Prolog'; }
140
+  pre.src-simula:before { content: 'Simula'; }
141
+  pre.src-tcl:before { content: 'tcl'; }
142
+  pre.src-tex:before { content: 'TeX'; }
143
+  pre.src-plain-tex:before { content: 'Plain TeX'; }
144
+  pre.src-verilog:before { content: 'Verilog'; }
145
+  pre.src-vhdl:before { content: 'VHDL'; }
146
+  pre.src-xml:before { content: 'XML'; }
147
+  pre.src-nxml:before { content: 'XML'; }
148
+  /* add a generic configuration mode; LaTeX export needs an additional
149
+     (add-to-list 'org-latex-listings-langs '(conf " ")) in .emacs */
150
+  pre.src-conf:before { content: 'Configuration File'; }
151
+
152
+  table { border-collapse:collapse; }
153
+  caption.t-above { caption-side: top; }
154
+  caption.t-bottom { caption-side: bottom; }
155
+  td, th { vertical-align:top;  }
156
+  th.org-right  { text-align: center;  }
157
+  th.org-left   { text-align: center;   }
158
+  th.org-center { text-align: center; }
159
+  td.org-right  { text-align: right;  }
160
+  td.org-left   { text-align: left;   }
161
+  td.org-center { text-align: center; }
162
+  dt { font-weight: bold; }
163
+  .footpara { display: inline; }
164
+  .footdef  { margin-bottom: 1em; }
165
+  .figure { padding: 1em; }
166
+  .figure p { text-align: center; }
167
+  .inlinetask {
168
+    padding: 10px;
169
+    border: 2px solid gray;
170
+    margin: 10px;
171
+    background: #ffffcc;
172
+  }
173
+  #org-div-home-and-up
174
+   { text-align: right; font-size: 70%; white-space: nowrap; }
175
+  textarea { overflow-x: auto; }
176
+  .linenr { font-size: smaller }
177
+  .code-highlighted { background-color: #ffff00; }
178
+  .org-info-js_info-navigation { border-style: none; }
179
+  #org-info-js_console-label
180
+    { font-size: 10px; font-weight: bold; white-space: nowrap; }
181
+  .org-info-js_search-highlight
182
+    { background-color: #ffff00; color: #000000; font-weight: bold; }
183
+  .org-svg { width: 90%; }
184
+  /*]]>*/-->
185
+</style>
186
+<link rel="stylesheet" type="text/css" href="freedombone.css" />
187
+<script type="text/javascript">
188
+/*
189
+@licstart  The following is the entire license notice for the
190
+JavaScript code in this tag.
191
+
192
+Copyright (C) 2012-2017 Free Software Foundation, Inc.
193
+
194
+The JavaScript code in this tag is free software: you can
195
+redistribute it and/or modify it under the terms of the GNU
196
+General Public License (GNU GPL) as published by the Free Software
197
+Foundation, either version 3 of the License, or (at your option)
198
+any later version.  The code is distributed WITHOUT ANY WARRANTY;
199
+without even the implied warranty of MERCHANTABILITY or FITNESS
200
+FOR A PARTICULAR PURPOSE.  See the GNU GPL for more details.
201
+
202
+As additional permission under GNU GPL version 3 section 7, you
203
+may distribute non-source (e.g., minimized or compacted) forms of
204
+that code without the copy of the GNU GPL normally required by
205
+section 4, provided you include this license notice and a URL
206
+through which recipients can access the Corresponding Source.
207
+
208
+
209
+@licend  The above is the entire license notice
210
+for the JavaScript code in this tag.
211
+*/
212
+<!--/*--><![CDATA[/*><!--*/
213
+ function CodeHighlightOn(elem, id)
214
+ {
215
+   var target = document.getElementById(id);
216
+   if(null != target) {
217
+     elem.cacheClassElem = elem.className;
218
+     elem.cacheClassTarget = target.className;
219
+     target.className = "code-highlighted";
220
+     elem.className   = "code-highlighted";
221
+   }
222
+ }
223
+ function CodeHighlightOff(elem, id)
224
+ {
225
+   var target = document.getElementById(id);
226
+   if(elem.cacheClassElem)
227
+     elem.className = elem.cacheClassElem;
228
+   if(elem.cacheClassTarget)
229
+     target.className = elem.cacheClassTarget;
230
+ }
231
+/*]]>*///-->
232
+</script>
233
+</head>
234
+<body>
235
+<div id="preamble" class="status">
236
+<a name="top" id="top"></a>
237
+</div>
238
+<div id="content">
239
+<div class="org-center">
240
+
241
+<div class="figure">
242
+<p><img src="images/logo.png" alt="logo.png" />
243
+</p>
244
+</div>
245
+</div>
246
+
247
+<center><h1>Mesh Network: Customisation</h1></center>
248
+
249
+<p>
250
+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.
251
+</p>
252
+
253
+<p>
254
+If you need particular <i>dconf</i> commands to alter desktop appearance or behavior then see the function <i>mesh_client_startup_applications</i> within <b>src/freedombone-image-customise</b>.
255
+</p>
256
+</div>
257
+<div id="postamble" class="status">
258
+
259
+<style type="text/css">
260
+.back-to-top {
261
+    position: fixed;
262
+    bottom: 2em;
263
+    right: 0px;
264
+    text-decoration: none;
265
+    color: #000000;
266
+    background-color: rgba(235, 235, 235, 0.80);
267
+    font-size: 12px;
268
+    padding: 1em;
269
+    display: none;
270
+}
271
+
272
+.back-to-top:hover {
273
+    background-color: rgba(135, 135, 135, 0.50);
274
+}
275
+</style>
276
+
277
+<div class="back-to-top">
278
+<a href="#top">Back to top</a> | <a href="mailto:bob@freedombone.net">E-mail me</a>
279
+</div>
280
+</div>
281
+</body>
282
+</html>

+ 495
- 0
website/EN/mesh_images.html Ver arquivo

@@ -0,0 +1,495 @@
1
+<?xml version="1.0" encoding="utf-8"?>
2
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
3
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
4
+<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
5
+<head>
6
+<!-- 2017-10-27 Fri 11:40 -->
7
+<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
8
+<meta name="viewport" content="width=device-width, initial-scale=1" />
9
+<title>&lrm;</title>
10
+<meta name="generator" content="Org mode" />
11
+<meta name="author" content="Bob Mottram" />
12
+<meta name="description" content="Turn the Beaglebone Black into a personal communications server"
13
+ />
14
+<meta name="keywords" content="freedombox, debian, beaglebone, red matrix, email, web server, home server, internet, censorship, surveillance, social network, irc, jabber" />
15
+<style type="text/css">
16
+ <!--/*--><![CDATA[/*><!--*/
17
+  .title  { text-align: center;
18
+             margin-bottom: .2em; }
19
+  .subtitle { text-align: center;
20
+              font-size: medium;
21
+              font-weight: bold;
22
+              margin-top:0; }
23
+  .todo   { font-family: monospace; color: red; }
24
+  .done   { font-family: monospace; color: green; }
25
+  .priority { font-family: monospace; color: orange; }
26
+  .tag    { background-color: #eee; font-family: monospace;
27
+            padding: 2px; font-size: 80%; font-weight: normal; }
28
+  .timestamp { color: #bebebe; }
29
+  .timestamp-kwd { color: #5f9ea0; }
30
+  .org-right  { margin-left: auto; margin-right: 0px;  text-align: right; }
31
+  .org-left   { margin-left: 0px;  margin-right: auto; text-align: left; }
32
+  .org-center { margin-left: auto; margin-right: auto; text-align: center; }
33
+  .underline { text-decoration: underline; }
34
+  #postamble p, #preamble p { font-size: 90%; margin: .2em; }
35
+  p.verse { margin-left: 3%; }
36
+  pre {
37
+    border: 1px solid #ccc;
38
+    box-shadow: 3px 3px 3px #eee;
39
+    padding: 8pt;
40
+    font-family: monospace;
41
+    overflow: auto;
42
+    margin: 1.2em;
43
+  }
44
+  pre.src {
45
+    position: relative;
46
+    overflow: visible;
47
+    padding-top: 1.2em;
48
+  }
49
+  pre.src:before {
50
+    display: none;
51
+    position: absolute;
52
+    background-color: white;
53
+    top: -10px;
54
+    right: 10px;
55
+    padding: 3px;
56
+    border: 1px solid black;
57
+  }
58
+  pre.src:hover:before { display: inline;}
59
+  /* Languages per Org manual */
60
+  pre.src-asymptote:before { content: 'Asymptote'; }
61
+  pre.src-awk:before { content: 'Awk'; }
62
+  pre.src-C:before { content: 'C'; }
63
+  /* pre.src-C++ doesn't work in CSS */
64
+  pre.src-clojure:before { content: 'Clojure'; }
65
+  pre.src-css:before { content: 'CSS'; }
66
+  pre.src-D:before { content: 'D'; }
67
+  pre.src-ditaa:before { content: 'ditaa'; }
68
+  pre.src-dot:before { content: 'Graphviz'; }
69
+  pre.src-calc:before { content: 'Emacs Calc'; }
70
+  pre.src-emacs-lisp:before { content: 'Emacs Lisp'; }
71
+  pre.src-fortran:before { content: 'Fortran'; }
72
+  pre.src-gnuplot:before { content: 'gnuplot'; }
73
+  pre.src-haskell:before { content: 'Haskell'; }
74
+  pre.src-hledger:before { content: 'hledger'; }
75
+  pre.src-java:before { content: 'Java'; }
76
+  pre.src-js:before { content: 'Javascript'; }
77
+  pre.src-latex:before { content: 'LaTeX'; }
78
+  pre.src-ledger:before { content: 'Ledger'; }
79
+  pre.src-lisp:before { content: 'Lisp'; }
80
+  pre.src-lilypond:before { content: 'Lilypond'; }
81
+  pre.src-lua:before { content: 'Lua'; }
82
+  pre.src-matlab:before { content: 'MATLAB'; }
83
+  pre.src-mscgen:before { content: 'Mscgen'; }
84
+  pre.src-ocaml:before { content: 'Objective Caml'; }
85
+  pre.src-octave:before { content: 'Octave'; }
86
+  pre.src-org:before { content: 'Org mode'; }
87
+  pre.src-oz:before { content: 'OZ'; }
88
+  pre.src-plantuml:before { content: 'Plantuml'; }
89
+  pre.src-processing:before { content: 'Processing.js'; }
90
+  pre.src-python:before { content: 'Python'; }
91
+  pre.src-R:before { content: 'R'; }
92
+  pre.src-ruby:before { content: 'Ruby'; }
93
+  pre.src-sass:before { content: 'Sass'; }
94
+  pre.src-scheme:before { content: 'Scheme'; }
95
+  pre.src-screen:before { content: 'Gnu Screen'; }
96
+  pre.src-sed:before { content: 'Sed'; }
97
+  pre.src-sh:before { content: 'shell'; }
98
+  pre.src-sql:before { content: 'SQL'; }
99
+  pre.src-sqlite:before { content: 'SQLite'; }
100
+  /* additional languages in org.el's org-babel-load-languages alist */
101
+  pre.src-forth:before { content: 'Forth'; }
102
+  pre.src-io:before { content: 'IO'; }
103
+  pre.src-J:before { content: 'J'; }
104
+  pre.src-makefile:before { content: 'Makefile'; }
105
+  pre.src-maxima:before { content: 'Maxima'; }
106
+  pre.src-perl:before { content: 'Perl'; }
107
+  pre.src-picolisp:before { content: 'Pico Lisp'; }
108
+  pre.src-scala:before { content: 'Scala'; }
109
+  pre.src-shell:before { content: 'Shell Script'; }
110
+  pre.src-ebnf2ps:before { content: 'ebfn2ps'; }
111
+  /* additional language identifiers per "defun org-babel-execute"
112
+       in ob-*.el */
113
+  pre.src-cpp:before  { content: 'C++'; }
114
+  pre.src-abc:before  { content: 'ABC'; }
115
+  pre.src-coq:before  { content: 'Coq'; }
116
+  pre.src-groovy:before  { content: 'Groovy'; }
117
+  /* additional language identifiers from org-babel-shell-names in
118
+     ob-shell.el: ob-shell is the only babel language using a lambda to put
119
+     the execution function name together. */
120
+  pre.src-bash:before  { content: 'bash'; }
121
+  pre.src-csh:before  { content: 'csh'; }
122
+  pre.src-ash:before  { content: 'ash'; }
123
+  pre.src-dash:before  { content: 'dash'; }
124
+  pre.src-ksh:before  { content: 'ksh'; }
125
+  pre.src-mksh:before  { content: 'mksh'; }
126
+  pre.src-posh:before  { content: 'posh'; }
127
+  /* Additional Emacs modes also supported by the LaTeX listings package */
128
+  pre.src-ada:before { content: 'Ada'; }
129
+  pre.src-asm:before { content: 'Assembler'; }
130
+  pre.src-caml:before { content: 'Caml'; }
131
+  pre.src-delphi:before { content: 'Delphi'; }
132
+  pre.src-html:before { content: 'HTML'; }
133
+  pre.src-idl:before { content: 'IDL'; }
134
+  pre.src-mercury:before { content: 'Mercury'; }
135
+  pre.src-metapost:before { content: 'MetaPost'; }
136
+  pre.src-modula-2:before { content: 'Modula-2'; }
137
+  pre.src-pascal:before { content: 'Pascal'; }
138
+  pre.src-ps:before { content: 'PostScript'; }
139
+  pre.src-prolog:before { content: 'Prolog'; }
140
+  pre.src-simula:before { content: 'Simula'; }
141
+  pre.src-tcl:before { content: 'tcl'; }
142
+  pre.src-tex:before { content: 'TeX'; }
143
+  pre.src-plain-tex:before { content: 'Plain TeX'; }
144
+  pre.src-verilog:before { content: 'Verilog'; }
145
+  pre.src-vhdl:before { content: 'VHDL'; }
146
+  pre.src-xml:before { content: 'XML'; }
147
+  pre.src-nxml:before { content: 'XML'; }
148
+  /* add a generic configuration mode; LaTeX export needs an additional
149
+     (add-to-list 'org-latex-listings-langs '(conf " ")) in .emacs */
150
+  pre.src-conf:before { content: 'Configuration File'; }
151
+
152
+  table { border-collapse:collapse; }
153
+  caption.t-above { caption-side: top; }
154
+  caption.t-bottom { caption-side: bottom; }
155
+  td, th { vertical-align:top;  }
156
+  th.org-right  { text-align: center;  }
157
+  th.org-left   { text-align: center;   }
158
+  th.org-center { text-align: center; }
159
+  td.org-right  { text-align: right;  }
160
+  td.org-left   { text-align: left;   }
161
+  td.org-center { text-align: center; }
162
+  dt { font-weight: bold; }
163
+  .footpara { display: inline; }
164
+  .footdef  { margin-bottom: 1em; }
165
+  .figure { padding: 1em; }
166
+  .figure p { text-align: center; }
167
+  .inlinetask {
168
+    padding: 10px;
169
+    border: 2px solid gray;
170
+    margin: 10px;
171
+    background: #ffffcc;
172
+  }
173
+  #org-div-home-and-up
174
+   { text-align: right; font-size: 70%; white-space: nowrap; }
175
+  textarea { overflow-x: auto; }
176
+  .linenr { font-size: smaller }
177
+  .code-highlighted { background-color: #ffff00; }
178
+  .org-info-js_info-navigation { border-style: none; }
179
+  #org-info-js_console-label
180
+    { font-size: 10px; font-weight: bold; white-space: nowrap; }
181
+  .org-info-js_search-highlight
182
+    { background-color: #ffff00; color: #000000; font-weight: bold; }
183
+  .org-svg { width: 90%; }
184
+  /*]]>*/-->
185
+</style>
186
+<link rel="stylesheet" type="text/css" href="freedombone.css" />
187
+<script type="text/javascript">
188
+/*
189
+@licstart  The following is the entire license notice for the
190
+JavaScript code in this tag.
191
+
192
+Copyright (C) 2012-2017 Free Software Foundation, Inc.
193
+
194
+The JavaScript code in this tag is free software: you can
195
+redistribute it and/or modify it under the terms of the GNU
196
+General Public License (GNU GPL) as published by the Free Software
197
+Foundation, either version 3 of the License, or (at your option)
198
+any later version.  The code is distributed WITHOUT ANY WARRANTY;
199
+without even the implied warranty of MERCHANTABILITY or FITNESS
200
+FOR A PARTICULAR PURPOSE.  See the GNU GPL for more details.
201
+
202
+As additional permission under GNU GPL version 3 section 7, you
203
+may distribute non-source (e.g., minimized or compacted) forms of
204
+that code without the copy of the GNU GPL normally required by
205
+section 4, provided you include this license notice and a URL
206
+through which recipients can access the Corresponding Source.
207
+
208
+
209
+@licend  The above is the entire license notice
210
+for the JavaScript code in this tag.
211
+*/
212
+<!--/*--><![CDATA[/*><!--*/
213
+ function CodeHighlightOn(elem, id)
214
+ {
215
+   var target = document.getElementById(id);
216
+   if(null != target) {
217
+     elem.cacheClassElem = elem.className;
218
+     elem.cacheClassTarget = target.className;
219
+     target.className = "code-highlighted";
220
+     elem.className   = "code-highlighted";
221
+   }
222
+ }
223
+ function CodeHighlightOff(elem, id)
224
+ {
225
+   var target = document.getElementById(id);
226
+   if(elem.cacheClassElem)
227
+     elem.className = elem.cacheClassElem;
228
+   if(elem.cacheClassTarget)
229
+     target.className = elem.cacheClassTarget;
230
+ }
231
+/*]]>*///-->
232
+</script>
233
+</head>
234
+<body>
235
+<div id="preamble" class="status">
236
+<a name="top" id="top"></a>
237
+</div>
238
+<div id="content">
239
+<div class="org-center">
240
+
241
+<div class="figure">
242
+<p><img src="images/logo.png" alt="logo.png" />
243
+</p>
244
+</div>
245
+</div>
246
+
247
+<center><h1>Mesh Network: Images</h1></center>
248
+
249
+<div id="outline-container-orgc7e2a0b" class="outline-2">
250
+<h2 id="orgc7e2a0b">Pre-built Disk Images</h2>
251
+<div class="outline-text-2" id="text-orgc7e2a0b">
252
+</div>
253
+<div id="outline-container-orgea5a9c8" class="outline-3">
254
+<h3 id="orgea5a9c8">Writing many images quickly</h3>
255
+<div class="outline-text-3" id="text-orgea5a9c8">
256
+<p>
257
+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>.
258
+</p>
259
+
260
+<p>
261
+For example on Arch/Parabola:
262
+</p>
263
+
264
+<div class="org-src-container">
265
+<pre class="src src-bash">sudo pacman -S gnome-multi-writer
266
+</pre>
267
+</div>
268
+
269
+<p>
270
+Or on Debian based systems:
271
+</p>
272
+
273
+<div class="org-src-container">
274
+<pre class="src src-bash">sudo apt-get install gnome-multi-writer
275
+</pre>
276
+</div>
277
+
278
+<p>
279
+The MultiWriter tool is also available within mesh client images, so that you can use mesh systems to create more copies of the same system.
280
+</p>
281
+</div>
282
+</div>
283
+<div id="outline-container-org67e59e6" class="outline-3">
284
+<h3 id="org67e59e6">Client images</h3>
285
+<div class="outline-text-3" id="text-org67e59e6">
286
+<div class="org-center">
287
+
288
+<div class="figure">
289
+<p><img src="images/mesh_netbook.jpg" alt="mesh_netbook.jpg" />
290
+</p>
291
+</div>
292
+</div>
293
+
294
+<p>
295
+"Client" isn't exactly the right term, but it's a mesh peer with a user interface. These images can be copied to a USB drive, then you can plug it into a laptop/netbook/desktop machine and boot from it. You will probably also need an Atheros USB wifi dongle (the black protruding object on the left side of the netbook in the picture above), because most built-in wifi usually requires proprietary firmware. In the commands below substitute /dev/sdX with the USB drive device, excluding any trailing numbers (eg. /dev/sdb). The USB drive you're copying to will need to be at least 8GB in size.
296
+</p>
297
+
298
+<div class="org-src-container">
299
+<pre class="src src-bash">sudo apt-get install xz-utils wget
300
+wget https://freedombone.net/downloads/current/freedombone-meshclient-i386.img.xz
301
+wget https://freedombone.net/downloads/current/freedombone-meshclient-i386.img.xz.sig
302
+gpg --verify freedombone-meshclient-i386.img.xz.sig
303
+sha256sum freedombone-meshclient-i386.img.xz
304
+61e474afae14774d7aa479b6727fd5e77bdc1854e547b3c5b630bf10542a9581
305
+unxz freedombone-meshclient-i386.img.xz
306
+sudo dd <span class="org-variable-name">if</span>=/dev/zero <span class="org-variable-name">of</span>=/dev/sdX <span class="org-variable-name">bs</span>=1M <span class="org-variable-name">count</span>=8
307
+sudo dd <span class="org-variable-name">bs</span>=1M <span class="org-variable-name">if</span>=freedombone-meshclient-i386.img <span class="org-variable-name">of</span>=/dev/sdX <span class="org-variable-name">conv</span>=fdatasync
308
+</pre>
309
+</div>
310
+
311
+<p>
312
+To get a number of systems onto the mesh repeat the <i>dd</i> command to create however many bootable USB drives you need.
313
+</p>
314
+
315
+<p>
316
+If you're in an emergency and don't have Atheros wifi dongles then there is also an "insecure" image which contains some proprietary wifi drivers which may work with a wider range of laptops. Proprietary drivers <b>are not recommended</b> because they're unsupportable and may be exploitable or contain malicious antifeatures which fundamentally compromise the security of the network. However, the trade-off between security/maintainability and simply having the ability to communicate at all may be a valid one in some situations.
317
+</p>
318
+
319
+<div class="org-src-container">
320
+<pre class="src src-bash">sudo apt-get install xz-utils wget
321
+wget https://freedombone.net/downloads/current/freedombone-meshclient-insecure-i386.img.xz
322
+wget https://freedombone.net/downloads/current/freedombone-meshclient-insecure-i386.img.xz.sig
323
+gpg --verify freedombone-meshclient-insecure-i386.img.xz.sig
324
+sha256sum freedombone-meshclient-insecure-i386.img.xz
325
+fec843303d7d280859f75f7a8edccd70512915a34d4cc0787b5de7d8fbde5c81
326
+unxz freedombone-meshclient-insecure-i386.img.xz
327
+sudo dd <span class="org-variable-name">if</span>=/dev/zero <span class="org-variable-name">of</span>=/dev/sdX <span class="org-variable-name">bs</span>=1M <span class="org-variable-name">count</span>=8
328
+sudo dd <span class="org-variable-name">bs</span>=1M <span class="org-variable-name">if</span>=freedombone-meshclient-insecure-i386.img <span class="org-variable-name">of</span>=/dev/sdX <span class="org-variable-name">conv</span>=fdatasync
329
+</pre>
330
+</div>
331
+</div>
332
+</div>
333
+
334
+<div id="outline-container-orgbc42549" class="outline-3">
335
+<h3 id="orgbc42549">Router images</h3>
336
+<div class="outline-text-3" id="text-orgbc42549">
337
+<p>
338
+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.
339
+</p>
340
+</div>
341
+<div id="outline-container-org3b057bd" class="outline-4">
342
+<h4 id="org3b057bd">Beaglebone Black</h4>
343
+<div class="outline-text-4" id="text-org3b057bd">
344
+<div class="org-center">
345
+
346
+<div class="figure">
347
+<p><img src="images/mesh_router.jpg" alt="mesh_router.jpg" />
348
+</p>
349
+</div>
350
+</div>
351
+
352
+<p>
353
+The above picture shows a Beaglebone Black with the image copied onto a microSD card (there's no need to do anything with the internal EMMC). A USB Atheros wifi adaptor with a large antenna is attached and in this case power is from the mains, although it could be from a battery or solar power system capable of supplying 5 volts and maybe 1A (depending upon how active the router is).
354
+</p>
355
+
356
+<div class="org-src-container">
357
+<pre class="src src-bash">sudo apt-get install xz-utils wget
358
+wget https://freedombone.net/downloads/current/freedombone-mesh_beaglebone-armhf.img.xz
359
+wget https://freedombone.net/downloads/current/freedombone-mesh_beaglebone-armhf.img.xz.sig
360
+gpg --verify freedombone-mesh_beaglebone-armhf.img.xz.sig
361
+sha256sum freedombone-mesh_beaglebone-armhf.img.xz
362
+45f131995e2f77188e7ddaf2b42ca3d8d48d821d37c7a31a21e2e6dcceaf510d
363
+unxz freedombone-mesh_beaglebone-armhf.img.xz
364
+sudo dd <span class="org-variable-name">bs</span>=1M <span class="org-variable-name">if</span>=freedombone-mesh_beaglebone-armhf.img <span class="org-variable-name">of</span>=/dev/sdX <span class="org-variable-name">conv</span>=fdatasync
365
+</pre>
366
+</div>
367
+
368
+<p>
369
+If you have a few Beaglebone Blacks to use as routers then repeat the <i>dd</i> command to create however many microSD cards you need.
370
+</p>
371
+
372
+<p>
373
+There is still a software freedom issue with the Beaglebone Black, but it doesn't prevent you from running a fully free system on the board. The TI AM335X SOC has a PowerVR SGX530 GPU which will only run with a proprietary blob, but this would only be an issue for systems with a monitor or LCD screen attached running a desktop environment which also needs GPU acceleration. For "headless" systems such as servers or mesh routers this isn't a problem.
374
+</p>
375
+</div>
376
+</div>
377
+</div>
378
+</div>
379
+
380
+<div id="outline-container-orgeb576f8" class="outline-2">
381
+<h2 id="orgeb576f8">Building Disk Images</h2>
382
+<div class="outline-text-2" id="text-orgeb576f8">
383
+<p>
384
+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.
385
+</p>
386
+
387
+<p>
388
+First you will need to create an image. On a Debian based system (tested on Debian Stretch):
389
+</p>
390
+
391
+<div class="org-src-container">
392
+<pre class="src src-bash">sudo apt-get -y install git wget build-essential
393
+wget https://freedombone.net/downloads/current/freedombone.tar.gz
394
+wget https://freedombone.net/downloads/current/freedombone.tar.gz.sig
395
+gpg --verify freedombone.tar.gz.sig
396
+sha256sum freedombone.tar.gz
397
+e2715e27b142a21fa257eab15778ddc96f86fda70f8d91d47c4c9aa19f22e272
398
+tar -xzvf freedombone.tar.gz
399
+<span class="org-builtin">cd</span> freedombone
400
+git checkout stretch
401
+sudo make install
402
+freedombone-image --setup debian
403
+freedombone-image -t i386 -v meshclient
404
+</pre>
405
+</div>
406
+
407
+<p>
408
+If you don't have Atheros or free software compatible wifi adapter then you can include proprietary wifi drivers which will work with most laptops. This is <b>NOT RECOMMENDED</b> because proprietary drivers are unsupportable and may contain either malware or be exploitable in a way which can't be fixed. However, if you're in an emergency and don't have any Atheros or free software wifi USB dongles then you can use the following command to make the image:
409
+</p>
410
+
411
+<div class="org-src-container">
412
+<pre class="src src-bash">freedombone-image -t i386 -v meshclient --insecure yes
413
+</pre>
414
+</div>
415
+
416
+<p>
417
+This takes a while. Maybe an hour or so, depending on the speed of your system and the internets. The good news though is that once created you can use the resulting image any number of times, and you don't need to trust some pre-built image.
418
+</p>
419
+
420
+<p>
421
+List what drives are on your system with:
422
+</p>
423
+
424
+<div class="org-src-container">
425
+<pre class="src src-bash">ls /dev/sd*
426
+</pre>
427
+</div>
428
+
429
+<p>
430
+Now plug in the USB thumb drive, and do the same again. Notice which drive letter gets added.
431
+</p>
432
+
433
+<p>
434
+You can now copy the image to the USB thumb drive, replacing <b>sdX</b> with the identifier of the USB thumb drive. Don't include any numbers (so for example use <b>sdc</b> instead of <b>sdc1</b>).
435
+</p>
436
+
437
+<div class="org-src-container">
438
+<pre class="src src-bash">sudo dd <span class="org-variable-name">if</span>=/dev/zero <span class="org-variable-name">of</span>=/dev/sdX <span class="org-variable-name">bs</span>=1M <span class="org-variable-name">count</span>=8
439
+sudo dd <span class="org-variable-name">bs</span>=1M <span class="org-variable-name">if</span>=myimagefile.img <span class="org-variable-name">of</span>=/dev/sdX <span class="org-variable-name">conv</span>=fdatasync
440
+</pre>
441
+</div>
442
+
443
+<p>
444
+And wait. Again it will take a while to copy over. When that's done plug it into the laptop or netbook which you want to use on the mesh, power on and set the BIOS to boot from the USB stick.
445
+</p>
446
+
447
+<p>
448
+On first boot you'll be asked to set a username, and then you can open the chat client and select the <b>users</b> icon to show the Tox IDs for other users on the mesh. When folks join they will be announced.
449
+</p>
450
+
451
+<p>
452
+Rinse, repeat, for any number of laptops that you want to get onto the mesh or to build out coverage within an area. There are no servers. Just peer-to-peer communications routed through the network which are end-to-end secure after a friend request is accepted. By default the chat client doesn't log anything.
453
+</p>
454
+
455
+<p>
456
+You can also use single board computers (SBCs) such as the BeagleBone Black to make mesh routers which can be bolted to walls or the sides of buildings and consume minimal electrical power, so could be solar or battery powered for short term events such as festivals. To do that use the following command to make the image:
457
+</p>
458
+
459
+<div class="org-src-container">
460
+<pre class="src src-bash">freedombone-image -t beaglebone -v mesh
461
+</pre>
462
+</div>
463
+
464
+<p>
465
+The resulting image can be copied to a microSD card, inserted into a Beaglebone Black and booted. Don't forget to plug in an Atheros USB wifi dongle.
466
+</p>
467
+</div>
468
+</div>
469
+</div>
470
+<div id="postamble" class="status">
471
+
472
+<style type="text/css">
473
+.back-to-top {
474
+    position: fixed;
475
+    bottom: 2em;
476
+    right: 0px;
477
+    text-decoration: none;
478
+    color: #000000;
479
+    background-color: rgba(235, 235, 235, 0.80);
480
+    font-size: 12px;
481
+    padding: 1em;
482
+    display: none;
483
+}
484
+
485
+.back-to-top:hover {
486
+    background-color: rgba(135, 135, 135, 0.50);
487
+}
488
+</style>
489
+
490
+<div class="back-to-top">
491
+<a href="#top">Back to top</a> | <a href="mailto:bob@freedombone.net">E-mail me</a>
492
+</div>
493
+</div>
494
+</body>
495
+</html>

+ 374
- 0
website/EN/mesh_philosophic.html Ver arquivo

@@ -0,0 +1,374 @@
1
+<?xml version="1.0" encoding="utf-8"?>
2
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
3
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
4
+<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
5
+<head>
6
+<!-- 2017-10-27 Fri 11:48 -->
7
+<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
8
+<meta name="viewport" content="width=device-width, initial-scale=1" />
9
+<title>&lrm;</title>
10
+<meta name="generator" content="Org mode" />
11
+<meta name="author" content="Bob Mottram" />
12
+<meta name="description" content="Turn any laptop or a Beaglebone Black into an off-the-grid mesh peer"
13
+ />
14
+<meta name="keywords" content="freedombox, debian, beaglebone, mesh" />
15
+<style type="text/css">
16
+ <!--/*--><![CDATA[/*><!--*/
17
+  .title  { text-align: center;
18
+             margin-bottom: .2em; }
19
+  .subtitle { text-align: center;
20
+              font-size: medium;
21
+              font-weight: bold;
22
+              margin-top:0; }
23
+  .todo   { font-family: monospace; color: red; }
24
+  .done   { font-family: monospace; color: green; }
25
+  .priority { font-family: monospace; color: orange; }
26
+  .tag    { background-color: #eee; font-family: monospace;
27
+            padding: 2px; font-size: 80%; font-weight: normal; }
28
+  .timestamp { color: #bebebe; }
29
+  .timestamp-kwd { color: #5f9ea0; }
30
+  .org-right  { margin-left: auto; margin-right: 0px;  text-align: right; }
31
+  .org-left   { margin-left: 0px;  margin-right: auto; text-align: left; }
32
+  .org-center { margin-left: auto; margin-right: auto; text-align: center; }
33
+  .underline { text-decoration: underline; }
34
+  #postamble p, #preamble p { font-size: 90%; margin: .2em; }
35
+  p.verse { margin-left: 3%; }
36
+  pre {
37
+    border: 1px solid #ccc;
38
+    box-shadow: 3px 3px 3px #eee;
39
+    padding: 8pt;
40
+    font-family: monospace;
41
+    overflow: auto;
42
+    margin: 1.2em;
43
+  }
44
+  pre.src {
45
+    position: relative;
46
+    overflow: visible;
47
+    padding-top: 1.2em;
48
+  }
49
+  pre.src:before {
50
+    display: none;
51
+    position: absolute;
52
+    background-color: white;
53
+    top: -10px;
54
+    right: 10px;
55
+    padding: 3px;
56
+    border: 1px solid black;
57
+  }
58
+  pre.src:hover:before { display: inline;}
59
+  /* Languages per Org manual */
60
+  pre.src-asymptote:before { content: 'Asymptote'; }
61
+  pre.src-awk:before { content: 'Awk'; }
62
+  pre.src-C:before { content: 'C'; }
63
+  /* pre.src-C++ doesn't work in CSS */
64
+  pre.src-clojure:before { content: 'Clojure'; }
65
+  pre.src-css:before { content: 'CSS'; }
66
+  pre.src-D:before { content: 'D'; }
67
+  pre.src-ditaa:before { content: 'ditaa'; }
68
+  pre.src-dot:before { content: 'Graphviz'; }
69
+  pre.src-calc:before { content: 'Emacs Calc'; }
70
+  pre.src-emacs-lisp:before { content: 'Emacs Lisp'; }
71
+  pre.src-fortran:before { content: 'Fortran'; }
72
+  pre.src-gnuplot:before { content: 'gnuplot'; }
73
+  pre.src-haskell:before { content: 'Haskell'; }
74
+  pre.src-hledger:before { content: 'hledger'; }
75
+  pre.src-java:before { content: 'Java'; }
76
+  pre.src-js:before { content: 'Javascript'; }
77
+  pre.src-latex:before { content: 'LaTeX'; }
78
+  pre.src-ledger:before { content: 'Ledger'; }
79
+  pre.src-lisp:before { content: 'Lisp'; }
80
+  pre.src-lilypond:before { content: 'Lilypond'; }
81
+  pre.src-lua:before { content: 'Lua'; }
82
+  pre.src-matlab:before { content: 'MATLAB'; }
83
+  pre.src-mscgen:before { content: 'Mscgen'; }
84
+  pre.src-ocaml:before { content: 'Objective Caml'; }
85
+  pre.src-octave:before { content: 'Octave'; }
86
+  pre.src-org:before { content: 'Org mode'; }
87
+  pre.src-oz:before { content: 'OZ'; }
88
+  pre.src-plantuml:before { content: 'Plantuml'; }
89
+  pre.src-processing:before { content: 'Processing.js'; }
90
+  pre.src-python:before { content: 'Python'; }
91
+  pre.src-R:before { content: 'R'; }
92
+  pre.src-ruby:before { content: 'Ruby'; }
93
+  pre.src-sass:before { content: 'Sass'; }
94
+  pre.src-scheme:before { content: 'Scheme'; }
95
+  pre.src-screen:before { content: 'Gnu Screen'; }
96
+  pre.src-sed:before { content: 'Sed'; }
97
+  pre.src-sh:before { content: 'shell'; }
98
+  pre.src-sql:before { content: 'SQL'; }
99
+  pre.src-sqlite:before { content: 'SQLite'; }
100
+  /* additional languages in org.el's org-babel-load-languages alist */
101
+  pre.src-forth:before { content: 'Forth'; }
102
+  pre.src-io:before { content: 'IO'; }
103
+  pre.src-J:before { content: 'J'; }
104
+  pre.src-makefile:before { content: 'Makefile'; }
105
+  pre.src-maxima:before { content: 'Maxima'; }
106
+  pre.src-perl:before { content: 'Perl'; }
107
+  pre.src-picolisp:before { content: 'Pico Lisp'; }
108
+  pre.src-scala:before { content: 'Scala'; }
109
+  pre.src-shell:before { content: 'Shell Script'; }
110
+  pre.src-ebnf2ps:before { content: 'ebfn2ps'; }
111
+  /* additional language identifiers per "defun org-babel-execute"
112
+       in ob-*.el */
113
+  pre.src-cpp:before  { content: 'C++'; }
114
+  pre.src-abc:before  { content: 'ABC'; }
115
+  pre.src-coq:before  { content: 'Coq'; }
116
+  pre.src-groovy:before  { content: 'Groovy'; }
117
+  /* additional language identifiers from org-babel-shell-names in
118
+     ob-shell.el: ob-shell is the only babel language using a lambda to put
119
+     the execution function name together. */
120
+  pre.src-bash:before  { content: 'bash'; }
121
+  pre.src-csh:before  { content: 'csh'; }
122
+  pre.src-ash:before  { content: 'ash'; }
123
+  pre.src-dash:before  { content: 'dash'; }
124
+  pre.src-ksh:before  { content: 'ksh'; }
125
+  pre.src-mksh:before  { content: 'mksh'; }
126
+  pre.src-posh:before  { content: 'posh'; }
127
+  /* Additional Emacs modes also supported by the LaTeX listings package */
128
+  pre.src-ada:before { content: 'Ada'; }
129
+  pre.src-asm:before { content: 'Assembler'; }
130
+  pre.src-caml:before { content: 'Caml'; }
131
+  pre.src-delphi:before { content: 'Delphi'; }
132
+  pre.src-html:before { content: 'HTML'; }
133
+  pre.src-idl:before { content: 'IDL'; }
134
+  pre.src-mercury:before { content: 'Mercury'; }
135
+  pre.src-metapost:before { content: 'MetaPost'; }
136
+  pre.src-modula-2:before { content: 'Modula-2'; }
137
+  pre.src-pascal:before { content: 'Pascal'; }
138
+  pre.src-ps:before { content: 'PostScript'; }
139
+  pre.src-prolog:before { content: 'Prolog'; }
140
+  pre.src-simula:before { content: 'Simula'; }
141
+  pre.src-tcl:before { content: 'tcl'; }
142
+  pre.src-tex:before { content: 'TeX'; }
143
+  pre.src-plain-tex:before { content: 'Plain TeX'; }
144
+  pre.src-verilog:before { content: 'Verilog'; }
145
+  pre.src-vhdl:before { content: 'VHDL'; }
146
+  pre.src-xml:before { content: 'XML'; }
147
+  pre.src-nxml:before { content: 'XML'; }
148
+  /* add a generic configuration mode; LaTeX export needs an additional
149
+     (add-to-list 'org-latex-listings-langs '(conf " ")) in .emacs */
150
+  pre.src-conf:before { content: 'Configuration File'; }
151
+
152
+  table { border-collapse:collapse; }
153
+  caption.t-above { caption-side: top; }
154
+  caption.t-bottom { caption-side: bottom; }
155
+  td, th { vertical-align:top;  }
156
+  th.org-right  { text-align: center;  }
157
+  th.org-left   { text-align: center;   }
158
+  th.org-center { text-align: center; }
159
+  td.org-right  { text-align: right;  }
160
+  td.org-left   { text-align: left;   }
161
+  td.org-center { text-align: center; }
162
+  dt { font-weight: bold; }
163
+  .footpara { display: inline; }
164
+  .footdef  { margin-bottom: 1em; }
165
+  .figure { padding: 1em; }
166
+  .figure p { text-align: center; }
167
+  .inlinetask {
168
+    padding: 10px;
169
+    border: 2px solid gray;
170
+    margin: 10px;
171
+    background: #ffffcc;
172
+  }
173
+  #org-div-home-and-up
174
+   { text-align: right; font-size: 70%; white-space: nowrap; }
175
+  textarea { overflow-x: auto; }
176
+  .linenr { font-size: smaller }
177
+  .code-highlighted { background-color: #ffff00; }
178
+  .org-info-js_info-navigation { border-style: none; }
179
+  #org-info-js_console-label
180
+    { font-size: 10px; font-weight: bold; white-space: nowrap; }
181
+  .org-info-js_search-highlight
182
+    { background-color: #ffff00; color: #000000; font-weight: bold; }
183
+  .org-svg { width: 90%; }
184
+  /*]]>*/-->
185
+</style>
186
+<link rel="stylesheet" type="text/css" href="freedombone.css" />
187
+<script type="text/javascript">
188
+/*
189
+@licstart  The following is the entire license notice for the
190
+JavaScript code in this tag.
191
+
192
+Copyright (C) 2012-2017 Free Software Foundation, Inc.
193
+
194
+The JavaScript code in this tag is free software: you can
195
+redistribute it and/or modify it under the terms of the GNU
196
+General Public License (GNU GPL) as published by the Free Software
197
+Foundation, either version 3 of the License, or (at your option)
198
+any later version.  The code is distributed WITHOUT ANY WARRANTY;
199
+without even the implied warranty of MERCHANTABILITY or FITNESS
200
+FOR A PARTICULAR PURPOSE.  See the GNU GPL for more details.
201
+
202
+As additional permission under GNU GPL version 3 section 7, you
203
+may distribute non-source (e.g., minimized or compacted) forms of
204
+that code without the copy of the GNU GPL normally required by
205
+section 4, provided you include this license notice and a URL
206
+through which recipients can access the Corresponding Source.
207
+
208
+
209
+@licend  The above is the entire license notice
210
+for the JavaScript code in this tag.
211
+*/
212
+<!--/*--><![CDATA[/*><!--*/
213
+ function CodeHighlightOn(elem, id)
214
+ {
215
+   var target = document.getElementById(id);
216
+   if(null != target) {
217
+     elem.cacheClassElem = elem.className;
218
+     elem.cacheClassTarget = target.className;
219
+     target.className = "code-highlighted";
220
+     elem.className   = "code-highlighted";
221
+   }
222
+ }
223
+ function CodeHighlightOff(elem, id)
224
+ {
225
+   var target = document.getElementById(id);
226
+   if(elem.cacheClassElem)
227
+     elem.className = elem.cacheClassElem;
228
+   if(elem.cacheClassTarget)
229
+     target.className = elem.cacheClassTarget;
230
+ }
231
+/*]]>*///-->
232
+</script>
233
+</head>
234
+<body>
235
+<div id="preamble" class="status">
236
+<a name="top" id="top"></a>
237
+</div>
238
+<div id="content">
239
+<div class="org-center">
240
+
241
+<div class="figure">
242
+<p><img src="images/logo.png" alt="logo.png" />
243
+</p>
244
+</div>
245
+</div>
246
+
247
+<center><h1>Mesh Network: Philosophic</h1></center>
248
+
249
+<blockquote>
250
+<p>
251
+"<i>I see mesh networks naturally evolving to become the dominant form of network over the next few decades, because it’s the most practical solution to a number of problems that will have to be solved in order to build the VR web as well as to connect the entire world to the internet. Centralized networks are only possible in highly developed countries with existing infrastructures like power and telephone grids, as well as roads. You can’t build a tower where you don’t have either power or access. For vast areas of the world, mesh networks will be the only feasible solution.</i>" &#x2013; Valkyrie Ice
252
+</p>
253
+</blockquote>
254
+
255
+<p>
256
+The Freedombone mesh roughly follows MondoNet's ten social specifications:
257
+</p>
258
+
259
+<div id="outline-container-orgd854595" class="outline-2">
260
+<h2 id="orgd854595">Decentralized</h2>
261
+<div class="outline-text-2" id="text-orgd854595">
262
+<p>
263
+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.
264
+</p>
265
+</div>
266
+</div>
267
+
268
+<div id="outline-container-org5c46858" class="outline-2">
269
+<h2 id="org5c46858">Universally Accessible</h2>
270
+<div class="outline-text-2" id="text-org5c46858">
271
+<p>
272
+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.
273
+</p>
274
+</div>
275
+</div>
276
+
277
+<div id="outline-container-org6776743" class="outline-2">
278
+<h2 id="org6776743">Censor-proof</h2>
279
+<div class="outline-text-2" id="text-org6776743">
280
+<p>
281
+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.
282
+</p>
283
+</div>
284
+</div>
285
+
286
+<div id="outline-container-org0bcdf27" class="outline-2">
287
+<h2 id="org0bcdf27">Surveillance-proof</h2>
288
+<div class="outline-text-2" id="text-org0bcdf27">
289
+<p>
290
+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.
291
+</p>
292
+</div>
293
+</div>
294
+
295
+<div id="outline-container-org0ed66ba" class="outline-2">
296
+<h2 id="org0ed66ba">Secure</h2>
297
+<div class="outline-text-2" id="text-org0ed66ba">
298
+<p>
299
+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.
300
+</p>
301
+</div>
302
+</div>
303
+
304
+<div id="outline-container-org8db594f" class="outline-2">
305
+<h2 id="org8db594f">Scalable</h2>
306
+<div class="outline-text-2" id="text-org8db594f">
307
+<p>
308
+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.
309
+</p>
310
+</div>
311
+</div>
312
+
313
+<div id="outline-container-org0c195ed" class="outline-2">
314
+<h2 id="org0c195ed">Permanent</h2>
315
+<div class="outline-text-2" id="text-org0c195ed">
316
+<p>
317
+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.
318
+</p>
319
+</div>
320
+</div>
321
+
322
+<div id="outline-container-org92fc811" class="outline-2">
323
+<h2 id="org92fc811">Fast (enough)</h2>
324
+<div class="outline-text-2" id="text-org92fc811">
325
+<p>
326
+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.
327
+</p>
328
+</div>
329
+</div>
330
+
331
+<div id="outline-container-orgf2a1737" class="outline-2">
332
+<h2 id="orgf2a1737">Independent</h2>
333
+<div class="outline-text-2" id="text-orgf2a1737">
334
+<p>
335
+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.
336
+</p>
337
+</div>
338
+</div>
339
+
340
+<div id="outline-container-org00e52cf" class="outline-2">
341
+<h2 id="org00e52cf">Evolvable</h2>
342
+<div class="outline-text-2" id="text-org00e52cf">
343
+<p>
344
+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.
345
+</p>
346
+</div>
347
+</div>
348
+</div>
349
+<div id="postamble" class="status">
350
+
351
+<style type="text/css">
352
+.back-to-top {
353
+    position: fixed;
354
+    bottom: 2em;
355
+    right: 0px;
356
+    text-decoration: none;
357
+    color: #000000;
358
+    background-color: rgba(235, 235, 235, 0.80);
359
+    font-size: 12px;
360
+    padding: 1em;
361
+    display: none;
362
+}
363
+
364
+.back-to-top:hover {
365
+    background-color: rgba(135, 135, 135, 0.50);
366
+}
367
+</style>
368
+
369
+<div class="back-to-top">
370
+<a href="#top">Back to top</a> | <a href="mailto:bob@freedombone.net">E-mail me</a>
371
+</div>
372
+</div>
373
+</body>
374
+</html>

+ 636
- 0
website/EN/mesh_usage.html Ver arquivo

@@ -0,0 +1,636 @@
1
+<?xml version="1.0" encoding="utf-8"?>
2
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
3
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
4
+<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
5
+<head>
6
+<!-- 2017-10-27 Fri 14:28 -->
7
+<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
8
+<meta name="viewport" content="width=device-width, initial-scale=1" />
9
+<title>&lrm;</title>
10
+<meta name="generator" content="Org mode" />
11
+<meta name="author" content="Bob Mottram" />
12
+<meta name="description" content="Turn the Beaglebone Black into a personal communications server"
13
+ />
14
+<meta name="keywords" content="freedombox, debian, beaglebone, red matrix, email, web server, home server, internet, censorship, surveillance, social network, irc, jabber" />
15
+<style type="text/css">
16
+ <!--/*--><![CDATA[/*><!--*/
17
+  .title  { text-align: center;
18
+             margin-bottom: .2em; }
19
+  .subtitle { text-align: center;
20
+              font-size: medium;
21
+              font-weight: bold;
22
+              margin-top:0; }
23
+  .todo   { font-family: monospace; color: red; }
24
+  .done   { font-family: monospace; color: green; }
25
+  .priority { font-family: monospace; color: orange; }
26
+  .tag    { background-color: #eee; font-family: monospace;
27
+            padding: 2px; font-size: 80%; font-weight: normal; }
28
+  .timestamp { color: #bebebe; }
29
+  .timestamp-kwd { color: #5f9ea0; }
30
+  .org-right  { margin-left: auto; margin-right: 0px;  text-align: right; }
31
+  .org-left   { margin-left: 0px;  margin-right: auto; text-align: left; }
32
+  .org-center { margin-left: auto; margin-right: auto; text-align: center; }
33
+  .underline { text-decoration: underline; }
34
+  #postamble p, #preamble p { font-size: 90%; margin: .2em; }
35
+  p.verse { margin-left: 3%; }
36
+  pre {
37
+    border: 1px solid #ccc;
38
+    box-shadow: 3px 3px 3px #eee;
39
+    padding: 8pt;
40
+    font-family: monospace;
41
+    overflow: auto;
42
+    margin: 1.2em;
43
+  }
44
+  pre.src {
45
+    position: relative;
46
+    overflow: visible;
47
+    padding-top: 1.2em;
48
+  }
49
+  pre.src:before {
50
+    display: none;
51
+    position: absolute;
52
+    background-color: white;
53
+    top: -10px;
54
+    right: 10px;
55
+    padding: 3px;
56
+    border: 1px solid black;
57
+  }
58
+  pre.src:hover:before { display: inline;}
59
+  /* Languages per Org manual */
60
+  pre.src-asymptote:before { content: 'Asymptote'; }
61
+  pre.src-awk:before { content: 'Awk'; }
62
+  pre.src-C:before { content: 'C'; }
63
+  /* pre.src-C++ doesn't work in CSS */
64
+  pre.src-clojure:before { content: 'Clojure'; }
65
+  pre.src-css:before { content: 'CSS'; }
66
+  pre.src-D:before { content: 'D'; }
67
+  pre.src-ditaa:before { content: 'ditaa'; }
68
+  pre.src-dot:before { content: 'Graphviz'; }
69
+  pre.src-calc:before { content: 'Emacs Calc'; }
70
+  pre.src-emacs-lisp:before { content: 'Emacs Lisp'; }
71
+  pre.src-fortran:before { content: 'Fortran'; }
72
+  pre.src-gnuplot:before { content: 'gnuplot'; }
73
+  pre.src-haskell:before { content: 'Haskell'; }
74
+  pre.src-hledger:before { content: 'hledger'; }
75
+  pre.src-java:before { content: 'Java'; }
76
+  pre.src-js:before { content: 'Javascript'; }
77
+  pre.src-latex:before { content: 'LaTeX'; }
78
+  pre.src-ledger:before { content: 'Ledger'; }
79
+  pre.src-lisp:before { content: 'Lisp'; }
80
+  pre.src-lilypond:before { content: 'Lilypond'; }
81
+  pre.src-lua:before { content: 'Lua'; }
82
+  pre.src-matlab:before { content: 'MATLAB'; }
83
+  pre.src-mscgen:before { content: 'Mscgen'; }
84
+  pre.src-ocaml:before { content: 'Objective Caml'; }
85
+  pre.src-octave:before { content: 'Octave'; }
86
+  pre.src-org:before { content: 'Org mode'; }
87
+  pre.src-oz:before { content: 'OZ'; }
88
+  pre.src-plantuml:before { content: 'Plantuml'; }
89
+  pre.src-processing:before { content: 'Processing.js'; }
90
+  pre.src-python:before { content: 'Python'; }
91
+  pre.src-R:before { content: 'R'; }
92
+  pre.src-ruby:before { content: 'Ruby'; }
93
+  pre.src-sass:before { content: 'Sass'; }
94
+  pre.src-scheme:before { content: 'Scheme'; }
95
+  pre.src-screen:before { content: 'Gnu Screen'; }
96
+  pre.src-sed:before { content: 'Sed'; }
97
+  pre.src-sh:before { content: 'shell'; }
98
+  pre.src-sql:before { content: 'SQL'; }
99
+  pre.src-sqlite:before { content: 'SQLite'; }
100
+  /* additional languages in org.el's org-babel-load-languages alist */
101
+  pre.src-forth:before { content: 'Forth'; }
102
+  pre.src-io:before { content: 'IO'; }
103
+  pre.src-J:before { content: 'J'; }
104
+  pre.src-makefile:before { content: 'Makefile'; }
105
+  pre.src-maxima:before { content: 'Maxima'; }
106
+  pre.src-perl:before { content: 'Perl'; }
107
+  pre.src-picolisp:before { content: 'Pico Lisp'; }
108
+  pre.src-scala:before { content: 'Scala'; }
109
+  pre.src-shell:before { content: 'Shell Script'; }
110
+  pre.src-ebnf2ps:before { content: 'ebfn2ps'; }
111
+  /* additional language identifiers per "defun org-babel-execute"
112
+       in ob-*.el */
113
+  pre.src-cpp:before  { content: 'C++'; }
114
+  pre.src-abc:before  { content: 'ABC'; }
115
+  pre.src-coq:before  { content: 'Coq'; }
116
+  pre.src-groovy:before  { content: 'Groovy'; }
117
+  /* additional language identifiers from org-babel-shell-names in
118
+     ob-shell.el: ob-shell is the only babel language using a lambda to put
119
+     the execution function name together. */
120
+  pre.src-bash:before  { content: 'bash'; }
121
+  pre.src-csh:before  { content: 'csh'; }
122
+  pre.src-ash:before  { content: 'ash'; }
123
+  pre.src-dash:before  { content: 'dash'; }
124
+  pre.src-ksh:before  { content: 'ksh'; }
125
+  pre.src-mksh:before  { content: 'mksh'; }
126
+  pre.src-posh:before  { content: 'posh'; }
127
+  /* Additional Emacs modes also supported by the LaTeX listings package */
128
+  pre.src-ada:before { content: 'Ada'; }
129
+  pre.src-asm:before { content: 'Assembler'; }
130
+  pre.src-caml:before { content: 'Caml'; }
131
+  pre.src-delphi:before { content: 'Delphi'; }
132
+  pre.src-html:before { content: 'HTML'; }
133
+  pre.src-idl:before { content: 'IDL'; }
134
+  pre.src-mercury:before { content: 'Mercury'; }
135
+  pre.src-metapost:before { content: 'MetaPost'; }
136
+  pre.src-modula-2:before { content: 'Modula-2'; }
137
+  pre.src-pascal:before { content: 'Pascal'; }
138
+  pre.src-ps:before { content: 'PostScript'; }
139
+  pre.src-prolog:before { content: 'Prolog'; }
140
+  pre.src-simula:before { content: 'Simula'; }
141
+  pre.src-tcl:before { content: 'tcl'; }
142
+  pre.src-tex:before { content: 'TeX'; }
143
+  pre.src-plain-tex:before { content: 'Plain TeX'; }
144
+  pre.src-verilog:before { content: 'Verilog'; }
145
+  pre.src-vhdl:before { content: 'VHDL'; }
146
+  pre.src-xml:before { content: 'XML'; }
147
+  pre.src-nxml:before { content: 'XML'; }
148
+  /* add a generic configuration mode; LaTeX export needs an additional
149
+     (add-to-list 'org-latex-listings-langs '(conf " ")) in .emacs */
150
+  pre.src-conf:before { content: 'Configuration File'; }
151
+
152
+  table { border-collapse:collapse; }
153
+  caption.t-above { caption-side: top; }
154
+  caption.t-bottom { caption-side: bottom; }
155
+  td, th { vertical-align:top;  }
156
+  th.org-right  { text-align: center;  }
157
+  th.org-left   { text-align: center;   }
158
+  th.org-center { text-align: center; }
159
+  td.org-right  { text-align: right;  }
160
+  td.org-left   { text-align: left;   }
161
+  td.org-center { text-align: center; }
162
+  dt { font-weight: bold; }
163
+  .footpara { display: inline; }
164
+  .footdef  { margin-bottom: 1em; }
165
+  .figure { padding: 1em; }
166
+  .figure p { text-align: center; }
167
+  .inlinetask {
168
+    padding: 10px;
169
+    border: 2px solid gray;
170
+    margin: 10px;
171
+    background: #ffffcc;
172
+  }
173
+  #org-div-home-and-up
174
+   { text-align: right; font-size: 70%; white-space: nowrap; }
175
+  textarea { overflow-x: auto; }
176
+  .linenr { font-size: smaller }
177
+  .code-highlighted { background-color: #ffff00; }
178
+  .org-info-js_info-navigation { border-style: none; }
179
+  #org-info-js_console-label
180
+    { font-size: 10px; font-weight: bold; white-space: nowrap; }
181
+  .org-info-js_search-highlight
182
+    { background-color: #ffff00; color: #000000; font-weight: bold; }
183
+  .org-svg { width: 90%; }
184
+  /*]]>*/-->
185
+</style>
186
+<link rel="stylesheet" type="text/css" href="freedombone.css" />
187
+<script type="text/javascript">
188
+/*
189
+@licstart  The following is the entire license notice for the
190
+JavaScript code in this tag.
191
+
192
+Copyright (C) 2012-2017 Free Software Foundation, Inc.
193
+
194
+The JavaScript code in this tag is free software: you can
195
+redistribute it and/or modify it under the terms of the GNU
196
+General Public License (GNU GPL) as published by the Free Software
197
+Foundation, either version 3 of the License, or (at your option)
198
+any later version.  The code is distributed WITHOUT ANY WARRANTY;
199
+without even the implied warranty of MERCHANTABILITY or FITNESS
200
+FOR A PARTICULAR PURPOSE.  See the GNU GPL for more details.
201
+
202
+As additional permission under GNU GPL version 3 section 7, you
203
+may distribute non-source (e.g., minimized or compacted) forms of
204
+that code without the copy of the GNU GPL normally required by
205
+section 4, provided you include this license notice and a URL
206
+through which recipients can access the Corresponding Source.
207
+
208
+
209
+@licend  The above is the entire license notice
210
+for the JavaScript code in this tag.
211
+*/
212
+<!--/*--><![CDATA[/*><!--*/
213
+ function CodeHighlightOn(elem, id)
214
+ {
215
+   var target = document.getElementById(id);
216
+   if(null != target) {
217
+     elem.cacheClassElem = elem.className;
218
+     elem.cacheClassTarget = target.className;
219
+     target.className = "code-highlighted";
220
+     elem.className   = "code-highlighted";
221
+   }
222
+ }
223
+ function CodeHighlightOff(elem, id)
224
+ {
225
+   var target = document.getElementById(id);
226
+   if(elem.cacheClassElem)
227
+     elem.className = elem.cacheClassElem;
228
+   if(elem.cacheClassTarget)
229
+     target.className = elem.cacheClassTarget;
230
+ }
231
+/*]]>*///-->
232
+</script>
233
+</head>
234
+<body>
235
+<div id="preamble" class="status">
236
+<a name="top" id="top"></a>
237
+</div>
238
+<div id="content">
239
+<div class="org-center">
240
+
241
+<div class="figure">
242
+<p><img src="images/logo.png" alt="logo.png" />
243
+</p>
244
+</div>
245
+</div>
246
+
247
+<center><h1>Mesh Network: How to use it</h1></center>
248
+
249
+<ul class="org-ul">
250
+<li><a href="#org6a43d4d">Boot trouble</a></li>
251
+<li><a href="#org03f4d8a">Set the Date</a></li>
252
+<li><a href="#org55f29f9">Check network status</a></li>
253
+<li><a href="#org802070f">Connecting to the internet</a></li>
254
+<li><a href="#orgd9dffae">Connecting two meshes over the internet via a VPN tunnel</a></li>
255
+<li><a href="#org62a60b3">Mobile devices (phones, etc)</a></li>
256
+<li><a href="#org216d212">Chat System</a></li>
257
+<li><a href="#orgfe4d63b">Collaborative document editing</a></li>
258
+<li><a href="#org76f234d">Social Network</a></li>
259
+<li><a href="#org6154f04">Sharing Files</a></li>
260
+<li><a href="#orga4dae6b">Blogging</a></li>
261
+</ul>
262
+
263
+<p>
264
+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.
265
+</p>
266
+
267
+<p>
268
+After a minute or two if you are within wifi range and there is at least one other user on the network then you should see additional icons appear on the desktop, such as <i>Other Users</i> and <i>Chat</i>.
269
+</p>
270
+
271
+<div id="outline-container-org6a43d4d" class="outline-2">
272
+<h2 id="org6a43d4d">Boot trouble</h2>
273
+<div class="outline-text-2" id="text-org6a43d4d">
274
+<p>
275
+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.
276
+</p>
277
+
278
+<p>
279
+After the system has booted successfully the problem should resolve itself on subsequent reboots.
280
+</p>
281
+</div>
282
+</div>
283
+<div id="outline-container-org03f4d8a" class="outline-2">
284
+<h2 id="org03f4d8a">Set the Date</h2>
285
+<div class="outline-text-2" id="text-org03f4d8a">
286
+<p>
287
+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.
288
+</p>
289
+
290
+<p>
291
+<b>Right click on the date</b> in the top right corner of the screen. Select <b>preferences</b>, then click the <b>Time Settings</b> button. You can then select the date from the calendar and set the time, then click the <b>Set System Time</b> button. Enter the default password, which is <i>freedombone</i>.
292
+</p>
293
+</div>
294
+</div>
295
+<div id="outline-container-org55f29f9" class="outline-2">
296
+<h2 id="org55f29f9">Check network status</h2>
297
+<div class="outline-text-2" id="text-org55f29f9">
298
+<p>
299
+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.
300
+</p>
301
+
302
+<p>
303
+Select the wifi icon on the desktop and enter the password '<i>freedombone</i>'. The network configuration will go into a monitoring mode and in the bottom right side of the window you will be able to see signal strength and other parameters. This can help you to locate systems or adjust antennas to get the best wifi performance.
304
+</p>
305
+
306
+
307
+<div class="org-center">
308
+
309
+<div class="figure">
310
+<p><img src="images/mesh_signal.jpg" alt="mesh_signal.jpg" />
311
+</p>
312
+</div>
313
+</div>
314
+
315
+<p>
316
+When you are finished close the window and then select the <i>Network Restart</i> desktop icon, which will restart the B.A.T.M.A.N. network. You can also use the restart icon if you are within range of the mesh network but the <i>Chat</i> and <i>Other Users</i> icons do not automatically appear after a few minutes.
317
+</p>
318
+</div>
319
+</div>
320
+<div id="outline-container-org802070f" class="outline-2">
321
+<h2 id="org802070f">Connecting to the internet</h2>
322
+<div class="outline-text-2" id="text-org802070f">
323
+<div class="org-center">
324
+
325
+<div class="figure">
326
+<p><img src="images/mesh_architecture2.jpg" alt="mesh_architecture2.jpg" />
327
+</p>
328
+</div>
329
+</div>
330
+
331
+<p>
332
+If you need to be able to access the internet from the mesh then connect one of the peers to an internet router using an ethernet cable (shown as yellow above), then reboot it. Other peers in the mesh, including any attached mobile devices, will then be able to access the internet using the ethernet attached peer as a gateway. <a href="https://en.wikipedia.org/wiki/Freifunk">Freifunk</a> works in a similar way.
333
+</p>
334
+
335
+<p>
336
+After connecting one peer to the internet you may need to reboot other peers in order to update their network configurations.
337
+</p>
338
+
339
+<p>
340
+If for legal reasons you need to connect to the internet via a VPN then openvpn is preinstalled and you can run the command:
341
+</p>
342
+
343
+<div class="org-src-container">
344
+<pre class="src src-bash">sudo openvpn myclient.ovpn
345
+</pre>
346
+</div>
347
+
348
+<p>
349
+Where <i>myclient.ovpn</i> comes from your VPN provider and with the password "<i>freedombone</i>".
350
+</p>
351
+</div>
352
+</div>
353
+<div id="outline-container-orgd9dffae" class="outline-2">
354
+<h2 id="orgd9dffae">Connecting two meshes over the internet via a VPN tunnel</h2>
355
+<div class="outline-text-2" id="text-orgd9dffae">
356
+<div class="org-center">
357
+
358
+<div class="figure">
359
+<p><img src="images/mesh_architecture_vpn.jpg" alt="mesh_architecture_vpn.jpg" />
360
+</p>
361
+</div>
362
+</div>
363
+
364
+<p>
365
+Maybe the internet exists, but you don't care about getting any content from it and just want to use it as a way to connect mesh networks from different geographical locations together.
366
+</p>
367
+
368
+<p>
369
+In your home directory on a system connected via ethernet to an internet router you'll find a file called <b>vpn.tar.gz</b>. If you want another mesh to be able to connect to yours then send them this file and get them to uncompress it into their home directory also on an internet gateway machine. If they have an external IP address or domain name for your router then they will be able to VPN connect using the <b>Connect Meshes</b> icon. They should also forward port 653 from their internet router to the mesh gateway machine.
370
+</p>
371
+
372
+<div class="org-center">
373
+
374
+<div class="figure">
375
+<p><img src="images/mesh_connect.jpg" alt="mesh_connect.jpg" />
376
+</p>
377
+</div>
378
+</div>
379
+
380
+<p>
381
+You should create a new <b>vpn.tar.gz</b> file for every other mesh which wants to be able to connect to yours. If you are prompted for a password it is 'freedombone'.
382
+</p>
383
+
384
+<p>
385
+From a deep packet inspection point of view the traffic going over the internet between mesh gateways will just look like any other TLS connection to a server.
386
+</p>
387
+</div>
388
+</div>
389
+
390
+<div id="outline-container-org62a60b3" class="outline-2">
391
+<h2 id="org62a60b3">Mobile devices (phones, etc)</h2>
392
+<div class="outline-text-2" id="text-org62a60b3">
393
+<div class="org-center">
394
+
395
+<div class="figure">
396
+<p><img src="images/mesh_architecture3.jpg" alt="mesh_architecture3.jpg" />
397
+</p>
398
+</div>
399
+</div>
400
+
401
+<p>
402
+To allow mobile devices to connect to the mesh you will need a second wifi adapter connected to your laptop/netbook/SBC. Plug in a second wifi adapter then reboot the system. The second adaptor will then create a wifi hotspot (the connection shown in green above) which mobile devices can connect to. The hotspot name also contains its local IP address (eg. "<i>mesh-192.168.1.83</i>").
403
+</p>
404
+
405
+<p>
406
+On a typical Android device go to <b>Settings</b> then <b>Security</b> and ensure that <b>Unknown sources</b> is enabled. Also within <b>Wifi</b> from the <b>Settings</b> screen select the mesh hotspot. The password is "<i>freedombone</i>". Open a non-Tor browser and navigate to the IP address showing in the hotspot name. You can then download and install mesh apps.
407
+</p>
408
+
409
+<div class="org-center">
410
+
411
+<div class="figure">
412
+<p><img src="images/mesh_mobileapps.jpg" alt="mesh_mobileapps.jpg" />
413
+</p>
414
+</div>
415
+</div>
416
+
417
+<p>
418
+On some android devices you may need to move the downloaded APK file from the <b>Downloads</b> directory to your <b>home</b> directory before you can install it.
419
+</p>
420
+</div>
421
+</div>
422
+<div id="outline-container-org216d212" class="outline-2">
423
+<h2 id="org216d212">Chat System</h2>
424
+<div class="outline-text-2" id="text-org216d212">
425
+<p>
426
+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.
427
+</p>
428
+
429
+<div class="org-center">
430
+
431
+<div class="figure">
432
+<p><img src="images/mesh_paste_tox_id.jpg" alt="mesh_paste_tox_id.jpg" />
433
+</p>
434
+</div>
435
+</div>
436
+
437
+<p>
438
+The other user can then accept or decline your friend request.
439
+</p>
440
+
441
+<div class="org-center">
442
+
443
+<div class="figure">
444
+<p><img src="images/mesh_friend_request.jpg" alt="mesh_friend_request.jpg" />
445
+</p>
446
+</div>
447
+</div>
448
+
449
+<p>
450
+You can also select an avatar by selecting the grey head and shoulders image.
451
+</p>
452
+
453
+<div class="org-center">
454
+
455
+<div class="figure">
456
+<p><img src="images/mesh_choose_avatar.jpg" alt="mesh_choose_avatar.jpg" />
457
+</p>
458
+</div>
459
+</div>
460
+
461
+<p>
462
+And by selecting the user from the list on the left hand side the chat can begin.
463
+</p>
464
+
465
+<div class="org-center">
466
+
467
+<div class="figure">
468
+<p><img src="images/mesh_text_chat.jpg" alt="mesh_text_chat.jpg" />
469
+</p>
470
+</div>
471
+</div>
472
+
473
+<p>
474
+One important point is that by default the microphone is turned off. When doing voice chat you can select the microphone volume with the drop down slider in the top right corner of the screen.
475
+</p>
476
+
477
+<p>
478
+At present video doesn't work reliably, but text and voice chat do work well.
479
+</p>
480
+</div>
481
+</div>
482
+
483
+<div id="outline-container-orgfe4d63b" class="outline-2">
484
+<h2 id="orgfe4d63b">Collaborative document editing</h2>
485
+<div class="outline-text-2" id="text-orgfe4d63b">
486
+<p>
487
+The mesh system includes the ability to collaboratively edit various sorts of documents using CryptPad. CryptPad is an almost peer-to-peer system in that it is designed for a client/server environment but that the server aspect of it is very minimal and limited to orchestrating the connected clients. With CryptPad installed on each mesh peer it effectively enables peer-to-peer collaborative editing. Documents are ephemeral and forgotten unless they're exported or copy-pasted to permanent storage.
488
+</p>
489
+
490
+<div class="org-center">
491
+
492
+<div class="figure">
493
+<p><img src="images/mesh_cryptpad1.jpg" alt="mesh_cryptpad1.jpg" />
494
+</p>
495
+</div>
496
+</div>
497
+
498
+<p>
499
+To create a document click on the CryptPad icon. Depending upon the specifications of your system it may take a few seconds to load, so don't be too disturned if the browser contents look blank for a while. Select <span class="underline">Rich Text Pad</span> and give yourself a username.
500
+</p>
501
+
502
+<div class="org-center">
503
+
504
+<div class="figure">
505
+<p><img src="images/mesh_cryptpad2.jpg" alt="mesh_cryptpad2.jpg" />
506
+</p>
507
+</div>
508
+</div>
509
+
510
+<p>
511
+If you have the chat system running you can then copy and paste the URL for your pad into the chat, and the other user can then open the link and edit the document with you. You can repeat that for however many other users you wish to be able to edit.
512
+</p>
513
+</div>
514
+</div>
515
+
516
+<div id="outline-container-org76f234d" class="outline-2">
517
+<h2 id="org76f234d">Social Network</h2>
518
+<div class="outline-text-2" id="text-org76f234d">
519
+<p>
520
+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.
521
+</p>
522
+
523
+<p>
524
+Double click on the "Social" icon to open the app, then add your nickname and optionally a description. If you want to choose an avatar image some can be found within the directory <b>/usr/share/freedombone/avatars</b>. On older systems or systems without a hardware random number generator, Patchwork sometimes takes a long time (a few minutes) to open for the first time after clicking the icon. This is most likely due to the initial generation of encryption keys, so be patient.
525
+</p>
526
+
527
+<div class="org-center">
528
+
529
+<div class="figure">
530
+<p><img src="images/patchwork_setup.jpg" alt="patchwork_setup.jpg" />
531
+</p>
532
+</div>
533
+</div>
534
+
535
+<p>
536
+Other Patchwork users on the mesh will appear automatically under the <b>local</b> list and you can select and follow them if you wish. It's also possible to select the dark theme from <b>settings</b> on the drop down menu if you prefer.
537
+</p>
538
+
539
+<div class="org-center">
540
+
541
+<div class="figure">
542
+<p><img src="images/patchwork_public.jpg" alt="patchwork_public.jpg" />
543
+</p>
544
+</div>
545
+</div>
546
+
547
+<p>
548
+The Secure Scuttlebutt protocol which Patchwork is based upon is intended to be robust to intermittent network connectivity, so you can write posts when out of range and they will sync once you are back in the network.
549
+</p>
550
+</div>
551
+</div>
552
+
553
+<div id="outline-container-org6154f04" class="outline-2">
554
+<h2 id="org6154f04">Sharing Files</h2>
555
+<div class="outline-text-2" id="text-org6154f04">
556
+<p>
557
+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.
558
+</p>
559
+
560
+<div class="org-center">
561
+
562
+<div class="figure">
563
+<p><img src="images/mesh_share_files.jpg" alt="mesh_share_files.jpg" />
564
+</p>
565
+</div>
566
+</div>
567
+</div>
568
+</div>
569
+
570
+<div id="outline-container-orga4dae6b" class="outline-2">
571
+<h2 id="orga4dae6b">Blogging</h2>
572
+<div class="outline-text-2" id="text-orga4dae6b">
573
+<p>
574
+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.
575
+</p>
576
+
577
+<div class="org-center">
578
+
579
+<div class="figure">
580
+<p><img src="images/mesh_new_blog.jpg" alt="mesh_new_blog.jpg" />
581
+</p>
582
+</div>
583
+</div>
584
+
585
+<p>
586
+To finish your blog entry just select <i>Save</i> and then close the editor. On older hardware it may take a while to publish the results, and this depends upon the amount of computation needed by IPFS to create file hashes. If you make no changes to the default text then the new blog entry will not be saved.
587
+</p>
588
+
589
+<div class="org-center">
590
+
591
+<div class="figure">
592
+<p><img src="images/mesh_new_blog2.jpg" alt="mesh_new_blog2.jpg" />
593
+</p>
594
+</div>
595
+</div>
596
+
597
+<div class="org-center">
598
+
599
+<div class="figure">
600
+<p><img src="images/mesh_view_blog.jpg" alt="mesh_view_blog.jpg" />
601
+</p>
602
+</div>
603
+</div>
604
+
605
+<p>
606
+You can also visit other blogs, edit or delete your previous entry and also change your blog theme.
607
+</p>
608
+</div>
609
+</div>
610
+</div>
611
+<div id="postamble" class="status">
612
+
613
+<style type="text/css">
614
+.back-to-top {
615
+    position: fixed;
616
+    bottom: 2em;
617
+    right: 0px;
618
+    text-decoration: none;
619
+    color: #000000;
620
+    background-color: rgba(235, 235, 235, 0.80);
621
+    font-size: 12px;
622
+    padding: 1em;
623
+    display: none;
624
+}
625
+
626
+.back-to-top:hover {
627
+    background-color: rgba(135, 135, 135, 0.50);
628
+}
629
+</style>
630
+
631
+<div class="back-to-top">
632
+<a href="#top">Back to top</a> | <a href="mailto:bob@freedombone.net">E-mail me</a>
633
+</div>
634
+</div>
635
+</body>
636
+</html>