Update mesh instructions for mobile
This commit is contained in:
Bob Mottram
parent
bbaa8b7088
commit
c56c52da84
|
|
@ -26,9 +26,13 @@
|
|||
"/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
|
||||
#+end_quote
|
||||
|
||||
The Freedombone Mesh is a wireless solution for autonomous communication that can be rapidly deployed in temporary, emergency or post-disaster situations where internet access is unavailable or compromised.
|
||||
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.
|
||||
|
||||
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 business internal office communications, protests, remote areas of the world, temporary "digital blackouts", scientific expeditions and off-world space colonies. The down side is that you can't access any internet content. The upside is that you can securely communicate with anyone on the local mesh. No ISPs. No payments or subscriptions beyond the cost of obtaining the hardware. Systems need to be within wifi range of each other for the mesh to be created. It can be an ultra-convenient way to do purely local communications.
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
The Freedombone mesh roughly follows MondoNet's ten social specifications:
|
||||
|
||||
|
|
@ -47,18 +51,20 @@ The Freedombone mesh roughly follows MondoNet's ten social specifications:
|
|||
|
||||
- Discovery of other users on the network
|
||||
- Text based chat, one-to-one and in groups
|
||||
- Voice chat (VoIP)
|
||||
- Voice chat (VoIP) and video calls
|
||||
- Private and public sharing of files
|
||||
- Blogging
|
||||
- Creating and broadcasting audio media/podcasts
|
||||
- Social network stream. Follow/unfollow other peers
|
||||
- No network administration required
|
||||
- No servers, internet connection or cabling is needed
|
||||
- No servers
|
||||
- Internet connection is optional
|
||||
- Works from bootable USB drives or microSD drives
|
||||
- Data is mesh routed between systems
|
||||
- Private communications is end-to-end secured and forward secret
|
||||
- Publicly shared data is /content addressable/
|
||||
|
||||
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. 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.
|
||||
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.
|
||||
|
||||
* Disk Images
|
||||
** Writing many images quickly
|
||||
|
|
@ -222,7 +228,16 @@ Select the wifi icon on the desktop and enter the password '/freedombone/'. The
|
|||
#+END_CENTER
|
||||
|
||||
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.
|
||||
** Mobile devices (phones, etc)
|
||||
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/").
|
||||
|
||||
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.
|
||||
|
||||
#+BEGIN_CENTER
|
||||
[[file:images/mesh_mobileapps.jpg]]
|
||||
#+END_CENTER
|
||||
|
||||
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.
|
||||
** Chat System
|
||||
|
||||
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.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@
|
|||
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
||||
<head>
|
||||
<!-- 2017-09-23 Sat 21:46 -->
|
||||
<!-- 2017-10-05 Thu 13:04 -->
|
||||
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||||
<title>‎</title>
|
||||
|
|
@ -274,13 +274,13 @@ for the JavaScript code in this tag.
|
|||
</colgroup>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td class="org-left"><a href="#org802af98">What the system can do</a></td>
|
||||
<td class="org-left"><a href="#org31db069">What the system can do</a></td>
|
||||
<td class="org-left">-</td>
|
||||
<td class="org-left"><a href="#org38eda48">Disk Images</a></td>
|
||||
<td class="org-left"><a href="#org591eab6">Disk Images</a></td>
|
||||
<td class="org-left">-</td>
|
||||
<td class="org-left"><a href="#org0c3a295">Building Disk Images</a></td>
|
||||
<td class="org-left"><a href="#orgfd2a746">Building Disk Images</a></td>
|
||||
<td class="org-left">-</td>
|
||||
<td class="org-left"><a href="#org5f6418e">How to use it</a></td>
|
||||
<td class="org-left"><a href="#orgf02b56e">How to use it</a></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
|
@ -292,11 +292,19 @@ for the JavaScript code in this tag.
|
|||
</blockquote>
|
||||
|
||||
<p>
|
||||
The Freedombone Mesh is a wireless solution for autonomous communication that can be rapidly deployed in temporary, emergency or post-disaster situations where internet access is unavailable or compromised.
|
||||
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.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
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 business internal office communications, protests, remote areas of the world, temporary "digital blackouts", scientific expeditions and off-world space colonies. The down side is that you can't access any internet content. The upside is that you can securely communicate with anyone on the local mesh. No ISPs. No payments or subscriptions beyond the cost of obtaining the hardware. Systems need to be within wifi range of each other for the mesh to be created. It can be an ultra-convenient way to do purely local communications.
|
||||
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.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
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.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
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.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
|
|
@ -316,18 +324,20 @@ The Freedombone mesh roughly follows MondoNet's ten social specifications:
|
|||
<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>
|
||||
</ul>
|
||||
|
||||
<div id="outline-container-org802af98" class="outline-2">
|
||||
<h2 id="org802af98">What the system can do</h2>
|
||||
<div class="outline-text-2" id="text-org802af98">
|
||||
<div id="outline-container-org31db069" class="outline-2">
|
||||
<h2 id="org31db069">What the system can do</h2>
|
||||
<div class="outline-text-2" id="text-org31db069">
|
||||
<ul class="org-ul">
|
||||
<li>Discovery of other users on the network</li>
|
||||
<li>Text based chat, one-to-one and in groups</li>
|
||||
<li>Voice chat (VoIP)</li>
|
||||
<li>Voice chat (VoIP) and video calls</li>
|
||||
<li>Private and public sharing of files</li>
|
||||
<li>Blogging</li>
|
||||
<li>Creating and broadcasting audio media/podcasts</li>
|
||||
<li>Social network stream. Follow/unfollow other peers</li>
|
||||
<li>No network administration required</li>
|
||||
<li>No servers, internet connection or cabling is needed</li>
|
||||
<li>No servers</li>
|
||||
<li>Internet connection is optional</li>
|
||||
<li>Works from bootable USB drives or microSD drives</li>
|
||||
<li>Data is mesh routed between systems</li>
|
||||
<li>Private communications is end-to-end secured and forward secret</li>
|
||||
|
|
@ -335,18 +345,18 @@ The Freedombone mesh roughly follows MondoNet's ten social specifications:
|
|||
</ul>
|
||||
|
||||
<p>
|
||||
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. 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.
|
||||
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.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-org38eda48" class="outline-2">
|
||||
<h2 id="org38eda48">Disk Images</h2>
|
||||
<div class="outline-text-2" id="text-org38eda48">
|
||||
<div id="outline-container-org591eab6" class="outline-2">
|
||||
<h2 id="org591eab6">Disk Images</h2>
|
||||
<div class="outline-text-2" id="text-org591eab6">
|
||||
</div>
|
||||
<div id="outline-container-org2291a28" class="outline-3">
|
||||
<h3 id="org2291a28">Writing many images quickly</h3>
|
||||
<div class="outline-text-3" id="text-org2291a28">
|
||||
<div id="outline-container-orgffdec7f" class="outline-3">
|
||||
<h3 id="orgffdec7f">Writing many images quickly</h3>
|
||||
<div class="outline-text-3" id="text-orgffdec7f">
|
||||
<p>
|
||||
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>.
|
||||
</p>
|
||||
|
|
@ -374,9 +384,9 @@ The MultiWriter tool is also available within mesh client images, so that you ca
|
|||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-orgd0546b8" class="outline-3">
|
||||
<h3 id="orgd0546b8">Client images</h3>
|
||||
<div class="outline-text-3" id="text-orgd0546b8">
|
||||
<div id="outline-container-org4e60223" class="outline-3">
|
||||
<h3 id="org4e60223">Client images</h3>
|
||||
<div class="outline-text-3" id="text-org4e60223">
|
||||
<div class="org-center">
|
||||
|
||||
<div class="figure">
|
||||
|
|
@ -425,16 +435,16 @@ sudo dd <span class="org-variable-name">bs</span>=1M <span class="org-variable-n
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-orgefe9dc5" class="outline-3">
|
||||
<h3 id="orgefe9dc5">Router images</h3>
|
||||
<div class="outline-text-3" id="text-orgefe9dc5">
|
||||
<div id="outline-container-org619ed5c" class="outline-3">
|
||||
<h3 id="org619ed5c">Router images</h3>
|
||||
<div class="outline-text-3" id="text-org619ed5c">
|
||||
<p>
|
||||
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.
|
||||
</p>
|
||||
</div>
|
||||
<div id="outline-container-org2f4e6c1" class="outline-4">
|
||||
<h4 id="org2f4e6c1">Beaglebone Black</h4>
|
||||
<div class="outline-text-4" id="text-org2f4e6c1">
|
||||
<div id="outline-container-orga6faa1b" class="outline-4">
|
||||
<h4 id="orga6faa1b">Beaglebone Black</h4>
|
||||
<div class="outline-text-4" id="text-orga6faa1b">
|
||||
<div class="org-center">
|
||||
|
||||
<div class="figure">
|
||||
|
|
@ -471,9 +481,9 @@ There is still a software freedom issue with the Beaglebone Black, but it doesn'
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-org0c3a295" class="outline-2">
|
||||
<h2 id="org0c3a295">Building Disk Images</h2>
|
||||
<div class="outline-text-2" id="text-org0c3a295">
|
||||
<div id="outline-container-orgfd2a746" class="outline-2">
|
||||
<h2 id="orgfd2a746">Building Disk Images</h2>
|
||||
<div class="outline-text-2" id="text-orgfd2a746">
|
||||
<p>
|
||||
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.
|
||||
</p>
|
||||
|
|
@ -561,9 +571,9 @@ The resulting image can be copied to a microSD card, inserted into a Beaglebone
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-orgdbfa9a8" class="outline-2">
|
||||
<h2 id="orgdbfa9a8">Customisation</h2>
|
||||
<div class="outline-text-2" id="text-orgdbfa9a8">
|
||||
<div id="outline-container-org70ededa" class="outline-2">
|
||||
<h2 id="org70ededa">Customisation</h2>
|
||||
<div class="outline-text-2" id="text-org70ededa">
|
||||
<p>
|
||||
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.
|
||||
</p>
|
||||
|
|
@ -573,9 +583,9 @@ If you need particular <i>dconf</i> commands to alter desktop appearance or beha
|
|||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-org5f6418e" class="outline-2">
|
||||
<h2 id="org5f6418e">How to use it</h2>
|
||||
<div class="outline-text-2" id="text-org5f6418e">
|
||||
<div id="outline-container-orgf02b56e" class="outline-2">
|
||||
<h2 id="orgf02b56e">How to use it</h2>
|
||||
<div class="outline-text-2" id="text-orgf02b56e">
|
||||
<p>
|
||||
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.
|
||||
</p>
|
||||
|
|
@ -585,9 +595,9 @@ After a minute or two if you are within wifi range and there is at least one oth
|
|||
</p>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-org6f259f7" class="outline-3">
|
||||
<h3 id="org6f259f7">Boot trouble</h3>
|
||||
<div class="outline-text-3" id="text-org6f259f7">
|
||||
<div id="outline-container-org6725f18" class="outline-3">
|
||||
<h3 id="org6725f18">Boot trouble</h3>
|
||||
<div class="outline-text-3" id="text-org6725f18">
|
||||
<p>
|
||||
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.
|
||||
</p>
|
||||
|
|
@ -597,9 +607,9 @@ After the system has booted successfully the problem should resolve itself on su
|
|||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-org32ab229" class="outline-3">
|
||||
<h3 id="org32ab229">Set the Date</h3>
|
||||
<div class="outline-text-3" id="text-org32ab229">
|
||||
<div id="outline-container-org3e04c3e" class="outline-3">
|
||||
<h3 id="org3e04c3e">Set the Date</h3>
|
||||
<div class="outline-text-3" id="text-org3e04c3e">
|
||||
<p>
|
||||
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.
|
||||
</p>
|
||||
|
|
@ -609,9 +619,9 @@ On the ordinary internet the date and time of your system would be set automatic
|
|||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-org0a0c31f" class="outline-3">
|
||||
<h3 id="org0a0c31f">Check network status</h3>
|
||||
<div class="outline-text-3" id="text-org0a0c31f">
|
||||
<div id="outline-container-org0643cbc" class="outline-3">
|
||||
<h3 id="org0643cbc">Check network status</h3>
|
||||
<div class="outline-text-3" id="text-org0643cbc">
|
||||
<p>
|
||||
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.
|
||||
</p>
|
||||
|
|
@ -634,10 +644,33 @@ When you are finished close the window and then select the <i>Network Restart</i
|
|||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-org4218a50" class="outline-3">
|
||||
<h3 id="org4218a50">Mobile devices (phones, etc)</h3>
|
||||
<div class="outline-text-3" id="text-org4218a50">
|
||||
<p>
|
||||
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>").
|
||||
</p>
|
||||
|
||||
<div id="outline-container-org334d737" class="outline-3">
|
||||
<h3 id="org334d737">Chat System</h3>
|
||||
<div class="outline-text-3" id="text-org334d737">
|
||||
<p>
|
||||
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.
|
||||
</p>
|
||||
|
||||
<div class="org-center">
|
||||
|
||||
<div class="figure">
|
||||
<p><img src="images/mesh_mobileapps.jpg" alt="mesh_mobileapps.jpg" />
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<p>
|
||||
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.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-org83ac204" class="outline-3">
|
||||
<h3 id="org83ac204">Chat System</h3>
|
||||
<div class="outline-text-3" id="text-org83ac204">
|
||||
<p>
|
||||
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.
|
||||
</p>
|
||||
|
|
@ -696,9 +729,9 @@ At present video doesn't work reliably, but text and voice chat do work well.
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-org2195683" class="outline-3">
|
||||
<h3 id="org2195683">Social Network</h3>
|
||||
<div class="outline-text-3" id="text-org2195683">
|
||||
<div id="outline-container-org7cefd77" class="outline-3">
|
||||
<h3 id="org7cefd77">Social Network</h3>
|
||||
<div class="outline-text-3" id="text-org7cefd77">
|
||||
<p>
|
||||
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.
|
||||
</p>
|
||||
|
|
@ -733,9 +766,9 @@ The Secure Scuttlebutt protocol which Patchwork is based upon is intended to be
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-org41de3cc" class="outline-3">
|
||||
<h3 id="org41de3cc">Sharing Files</h3>
|
||||
<div class="outline-text-3" id="text-org41de3cc">
|
||||
<div id="outline-container-org1d48b53" class="outline-3">
|
||||
<h3 id="org1d48b53">Sharing Files</h3>
|
||||
<div class="outline-text-3" id="text-org1d48b53">
|
||||
<p>
|
||||
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.
|
||||
</p>
|
||||
|
|
@ -750,9 +783,9 @@ You can make files publicly available on the network simply by dragging and drop
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-org534896d" class="outline-3">
|
||||
<h3 id="org534896d">Blogging</h3>
|
||||
<div class="outline-text-3" id="text-org534896d">
|
||||
<div id="outline-container-org152b28b" class="outline-3">
|
||||
<h3 id="org152b28b">Blogging</h3>
|
||||
<div class="outline-text-3" id="text-org152b28b">
|
||||
<p>
|
||||
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.
|
||||
</p>
|
||||
|
|
|
|||
Loading…
Reference in New Issue