diff options
author | ng0 <ng0@infotropique.org> | 2017-10-26 13:47:05 +0000 |
---|---|---|
committer | ng0 <ng0@infotropique.org> | 2017-10-26 13:47:05 +0000 |
commit | b658d1a112ba6e20f7affeea225ef438166defc0 (patch) | |
tree | 05d2a9e2d095c65c640b65a94b3a13d80bf4691d /doc | |
parent | 8a7db950118a53cfa9ed69eab2785fe7f71647c1 (diff) | |
download | gnunet-b658d1a112ba6e20f7affeea225ef438166defc0.tar.gz gnunet-b658d1a112ba6e20f7affeea225ef438166defc0.zip |
doc user: line length
Diffstat (limited to 'doc')
-rw-r--r-- | doc/documentation/chapters/user.texi | 41 |
1 files changed, 23 insertions, 18 deletions
diff --git a/doc/documentation/chapters/user.texi b/doc/documentation/chapters/user.texi index 395524a6d..65b20c9c9 100644 --- a/doc/documentation/chapters/user.texi +++ b/doc/documentation/chapters/user.texi | |||
@@ -65,7 +65,8 @@ following window: | |||
65 | @c @image{images/gnunet-gtk-0-10,5in,, picture of gnunet-gtk application} | 65 | @c @image{images/gnunet-gtk-0-10,5in,, picture of gnunet-gtk application} |
66 | 66 | ||
67 | The five images on top represent the five different graphical applications | 67 | The five images on top represent the five different graphical applications |
68 | that you can use within @command{gnunet-gtk}. They are (from left to right): | 68 | that you can use within @command{gnunet-gtk}. |
69 | They are (from left to right): | ||
69 | 70 | ||
70 | @itemize @bullet | 71 | @itemize @bullet |
71 | @item Statistics | 72 | @item Statistics |
@@ -79,10 +80,12 @@ that you can use within @command{gnunet-gtk}. They are (from left to right): | |||
79 | @subsection Statistics | 80 | @subsection Statistics |
80 | @c %**end of header | 81 | @c %**end of header |
81 | 82 | ||
82 | When @command{gnunet-gtk} is started, the statistics area should be selected | 83 | When @command{gnunet-gtk} is started, the statistics area should be |
83 | at first. If your peer is running correctly, you should see a bunch of | 84 | selected at first. |
85 | If your peer is running correctly, you should see a bunch of | ||
84 | lines, all of which should be "significantly" above zero (at least if your | 86 | lines, all of which should be "significantly" above zero (at least if your |
85 | peer has been running for a few seconds). The lines indicate how many other | 87 | peer has been running for a few seconds). The lines indicate how many |
88 | other | ||
86 | peers your peer is connected to (via different mechanisms) and how large | 89 | peers your peer is connected to (via different mechanisms) and how large |
87 | the overall overlay network is currently estimated to be. The X-axis | 90 | the overall overlay network is currently estimated to be. The X-axis |
88 | represents time (in seconds since the start of @command{gnunet-gtk}). | 91 | represents time (in seconds since the start of @command{gnunet-gtk}). |
@@ -304,10 +307,10 @@ follow the GNUnet setup, you will have 4 egos created by default. | |||
304 | They can be listed by the command @command{gnunet-identity -d} | 307 | They can be listed by the command @command{gnunet-identity -d} |
305 | 308 | ||
306 | @example | 309 | @example |
307 | short-zone - JTDVJC69NHU6GQS4B5721MV8VM7J6G2DVRGJV0ONIT6QH7OI6D50@ | 310 | short-zone - JTDVJC69NHU6GQS4B5721MV8VM7J6G2DVRGJV0ONIT6QH7OI6D50 |
308 | sks-zone - GO0T87F9BPMF8NKD5A54L2AH1T0GRML539TPFSRMCEA98182QD30@ | 311 | sks-zone - GO0T87F9BPMF8NKD5A54L2AH1T0GRML539TPFSRMCEA98182QD30 |
309 | master-zone - LOC36VTJD3IRULMM6C20TGE6D3SVEAJOHI9KRI5KAQVQ87UJGPJG@ | 312 | master-zone - LOC36VTJD3IRULMM6C20TGE6D3SVEAJOHI9KRI5KAQVQ87UJGPJG |
310 | private-zone - 6IGJIU0Q1FO3RJT57UJRS5DLGLH5IHRB9K2L3DO4P4GVKKJ0TN4G@ | 313 | private-zone - 6IGJIU0Q1FO3RJT57UJRS5DLGLH5IHRB9K2L3DO4P4GVKKJ0TN4G |
311 | @end example | 314 | @end example |
312 | 315 | ||
313 | @noindent | 316 | @noindent |
@@ -725,8 +728,8 @@ a link. If your buddy has your public key in their master zone, they | |||
725 | should see an incoming call with your name. If your public key is not | 728 | should see an incoming call with your name. If your public key is not |
726 | in their master zone, they will just see the public key as the caller ID. | 729 | in their master zone, they will just see the public key as the caller ID. |
727 | 730 | ||
728 | Your buddy then can answer the call using the "/accept" command. After that, | 731 | Your buddy then can answer the call using the "/accept" command. After |
729 | (encrypted) voice data should be relayed between your two peers. | 732 | that, (encrypted) voice data should be relayed between your two peers. |
730 | Either of you can end the call using @command{/cancel}. You can exit | 733 | Either of you can end the call using @command{/cancel}. You can exit |
731 | @code{gnunet-converation} using @command{/quit}. | 734 | @code{gnunet-converation} using @command{/quit}. |
732 | 735 | ||
@@ -793,16 +796,17 @@ to install the NSS plugins in the proper location. | |||
793 | @subsection Exit configuration | 796 | @subsection Exit configuration |
794 | @c %**end of header | 797 | @c %**end of header |
795 | 798 | ||
796 | Stop your peer (as user @code{gnunet}, run @command{gnunet-arm -e}) and run | 799 | Stop your peer (as user @code{gnunet}, run @command{gnunet-arm -e}) and |
797 | @command{gnunet-setup}. In @command{gnunet-setup}, make sure to activate the | 800 | run @command{gnunet-setup}. In @command{gnunet-setup}, make sure to |
798 | @strong{EXIT} and @strong{GNS} services in the General tab. Then select | 801 | activate the @strong{EXIT} and @strong{GNS} services in the General tab. |
799 | the Exit tab. Most of the defaults should be fine (but you should check | 802 | Then select the Exit tab. Most of the defaults should be fine (but |
800 | against the screenshot that they have not been modified). In the | 803 | you should check against the screenshot that they have not been modified). |
801 | bottom area, enter @code{bcd} under Identifier and change the | 804 | In the bottom area, enter @code{bcd} under Identifier and change the |
802 | Destination to @code{169.254.86.1:8888} (if your server runs on a port | 805 | Destination to @code{169.254.86.1:8888} (if your server runs on a port |
803 | other than 8888, change the 8888 port accordingly). | 806 | other than 8888, change the 8888 port accordingly). |
804 | 807 | ||
805 | Now exit @command{gnunet-setup} and restart your peer (@command{gnunet-arm -s}). | 808 | Now exit @command{gnunet-setup} and restart your peer |
809 | (@command{gnunet-arm -s}). | ||
806 | 810 | ||
807 | @node GNS configuration | 811 | @node GNS configuration |
808 | @subsection GNS configuration | 812 | @subsection GNS configuration |
@@ -821,7 +825,8 @@ as the @code{gnunet} user. For the Identifier, you need to supply the same | |||
821 | identifier that we used in the Exit setup earlier, so here supply "bcd". | 825 | identifier that we used in the Exit setup earlier, so here supply "bcd". |
822 | If you want others to be able to use the service, you should probably make | 826 | If you want others to be able to use the service, you should probably make |
823 | the record public. For non-public services, you should use a passphrase | 827 | the record public. For non-public services, you should use a passphrase |
824 | instead of the string "bcd". Save the record and exit @command{gnunet-gtk}. | 828 | instead of the string "bcd". Save the record and |
829 | exit @command{gnunet-gtk}. | ||
825 | 830 | ||
826 | @node Accessing the service | 831 | @node Accessing the service |
827 | @subsection Accessing the service | 832 | @subsection Accessing the service |