[GNUnet-SVN] [gnunet-texinfo] branch master updated: user.texi: Remove trailing whitespaces.

[gnunet]

This is an automated email from the git hooks/post-receive script.

ng0 pushed a commit to branch master
in repository gnunet-texinfo.

The following commit(s) were added to refs/heads/master by this push:
     new 079d03d  user.texi: Remove trailing whitespaces.
079d03d is described below

commit 079d03dfea28ac89fa3dfd419bf1b79c7cb154eb
Author: ng0 <address@hidden>
AuthorDate: Fri Feb 17 16:58:06 2017 +0000

    user.texi: Remove trailing whitespaces.
---
 user.texi | 73 +++++++++++++++++++++++++++------------------------------------
 1 file changed, 31 insertions(+), 42 deletions(-)

diff --git a/user.texi b/user.texi
index c9d5431..da3e704 100644
--- a/user.texi
+++ b/user.texi
@@ -123,7 +123,7 @@ of which should be "significantly" above zero (at least if 
your peer has been
 running for a few seconds). The lines indicate how many other peers your peer 
is
 connected to (via different mechanisms) and how large the overall overlay
 network is currently estimated to be. The x-axis represents time (in seconds
-since the start of @code{gnunet-gtk}). 
+since the start of @code{gnunet-gtk}).
 
 You can click on "Traffic" to see information about the amount of bandwidth 
your
 peer has consumed, and on "Storage" to check the amount of storage available 
and
@@ -142,10 +142,6 @@ country of origin (if determined) and address information. 
If hardly any peers
 are listed and/or if there are very few peers with a green light for
 connectivity, there is likely a problem with your network configuration.
 
-
address@hidden @columnfractions 0.333333333333333 0.333333333333333 
0.333333333333333
address@hidden multitable
-
 @node First steps: File-sharing
 @chapter First steps: File-sharing
 @c %**end of header
@@ -162,7 +158,7 @@ for testing, we need to begin by publishing a file.
 @c %**end of header
 
 To publish a file, select "File Sharing" in the menu bar just below the
-"Statistics" icon, and then select "Publish" from the menu. 
+"Statistics" icon, and then select "Publish" from the menu.
 
 Afterwards, the following publishing dialog will appear:
 
@@ -224,7 +220,7 @@ on what other users may have shared and how your peer is 
connected.
 You can now select one of the search results. Once you do this, additional
 information about the result should be displayed on the right. If available, a
 preview image should appear on the top right. Meta data describing the file 
will
-be listed at the bottom right. 
+be listed at the bottom right.
 
 Once a file is selected, at the bottom of the search result list a little area
 for downloading appears.
@@ -249,13 +245,10 @@ downloads are not aborted but moved to a special "*" tab.
 
 You can remove completed downloads from the "*" tab by clicking the cleanup
 button next to the "*". You can also abort downloads by right clicking on the
-respective download and selecting "Abort download" from the menu. 
+respective download and selecting "Abort download" from the menu.
 
 That's it, you now know the basics for file-sharing with GNUnet!
 
address@hidden @columnfractions 0.0833333333333333 0.0833333333333333 
0.0833333333333333 0.0833333333333333 0.0833333333333333 0.0833333333333333 
0.0833333333333333 0.0833333333333333 0.0833333333333333 0.0833333333333333 
0.0833333333333333 0.0833333333333333
address@hidden multitable
-
 @node First steps: Using the GNU Name System
 @chapter First steps: Using the GNU Name System
 @c %**end of header
@@ -271,7 +264,7 @@ it. Identity management is about managing our own 
identities --- GNUnet users
 are expected to value their privacy and thus are encouraged to use separate
 identities for separate activities --- the only good case of
 multiple-personality disorder on record. By default, each user should have run
address@hidden during installation. This script creates four
address@hidden during installation. This script creates four
 identities, which should show up in the identity management tab:@
 
 For this tutorial, we will pretty much only be concerned with the "master-zone"
@@ -413,7 +406,7 @@ Select SOCKS v5 and then push "OK".@
 You must also go to About:config and change the
 @code{browser.fixup.alternate.enabled} option to @code{false}, otherwise the
 browser will autoblunder an address like @address@hidden://www.gnu/, www.gnu}}
-to @address@hidden://www.gnu.com/, www.gnu.com}}. 
+to @address@hidden://www.gnu.com/, www.gnu.com}}.
 
 After configuring your browser, you might want to first confirm that it
 continues to work as before. (The proxy is still experimental and if you
@@ -471,9 +464,6 @@ to use GNS to have a private conversation with your friend. 
Finally, help us
 with the next GNUnet release for even more applications using this new
 public key infrastructure.
 
address@hidden @columnfractions 0.166666666666667 0.166666666666667 
0.166666666666667 0.166666666666667 0.166666666666667 0.166666666666667
address@hidden multitable
-
 @node First steps: Using GNUnet Conversation
 @chapter First steps: Using GNUnet Conversation
 @c %**end of header
@@ -518,7 +508,7 @@ choice. Run:@
 }@
 to start the command-line tool. You will see a message saying that your phone 
is
 now "active on line 0". You can connect multiple phones on different lines at
-the same peer. For the first phone, the line zero is of course a fine choice. 
+the same peer. For the first phone, the line zero is of course a fine choice.
 
 Next, you should type in "/help" for a list of available commands. We will
 explain the important ones during this tutorial. First, you will need to type 
in
@@ -530,7 +520,7 @@ something like this:@
 }@
 Here, the "0" is your phone line, and what follows after the hyphen is your
 peer's identity. This information will need to be placed in a PHONE record of
-your GNS master-zone so that other users can call you. 
+your GNS master-zone so that other users can call you.
 
 Start @code{gnunet-namestore-gtk} now (possibly from another shell) and create
 an entry home-phone in your master zone. For the record type, select PHONE. You
@@ -538,7 +528,7 @@ should then see the PHONE dialog:@
 
 Note: Do not choose the expiry time to be 'Never'. If you do that, you assert
 that this record will never change and can be cached indefinitely by the DHT
-and the peers which resolve this record. A reasonable period is 1 year. 
+and the peers which resolve this record. A reasonable period is 1 year.
 
 Enter your peer identity under Peer and leave the line at zero. Select the 
first
 option to make the record public. If you entered your peer identity 
incorrectly,
@@ -562,7 +552,7 @@ a call using:@
 It may take some time for GNUnet to resolve the name and to establish a link. 
If
 your buddy has your public key in his master zone, he should see an incoming
 call with your name. If your public key is not in his master zone, he will just
-see the public key as the caller ID. 
+see the public key as the caller ID.
 
 Your buddy then can answer the call using the "/accept" command. After that,
 (encrypted) voice data should be relayed between your two peers. Either of you
@@ -594,13 +584,13 @@ If you have not done this, you should also configure your 
Name System Service
 switch to use GNS. In your @code{/etc/nsswitch.conf} you should fine a line 
like
 this:
 @example
-hosts:          files mdns4_minimal [NOTFOUND=return] dns mdns4
+hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4
 @end example
 
 The exact details may differ a bit, which is fine. Add the text
 @code{gns [NOTFOUND=return]} after @code{files}:
 @example
-hosts:          files gns [NOTFOUND=return] mdns4_minimal [NOTFOUND=return] 
dns mdns4
+hosts: files gns [NOTFOUND=return] mdns4_minimal [NOTFOUND=return] dns mdns4
 @end example
 
 
@@ -842,7 +832,7 @@ level zero, the selection is simply random.
 The command @code{gnunet-publish} can be used to add content to the network.
 The basic format of the command is
 @example
-$ gnunet-publish [-n] [-k KEYWORDS]* [-m TYPE:VALUE] FILENAME 
+$ gnunet-publish [-n] [-k KEYWORDS]* [-m TYPE:VALUE] FILENAME
 @end example
 
 @node Important command-line options
@@ -859,7 +849,7 @@ to libextractor. You can obtain this list by running 
@code{extract -L}.
 Use quotes around the entire meta-data argument if the value contains spaces.
 The meta-data is displayed to other users when they select which files to
 download. The meta-data and the keywords are optional and maybe inferred using
-GNU libextractor. 
address@hidden libextractor}.
 
 gnunet-publish has a few additional options to handle namespaces and
 directories.
@@ -885,26 +875,26 @@ way, there is no need for an additional encrypted copy of 
the file to stay
 anywhere on the drive. This is different from other systems, such as Freenet,
 where each file that is put online must be in Freenet's database in encrypted
 format, doubling the space requirements if the user wants to preseve a directly
-accessible copy in plaintext. 
+accessible copy in plaintext.
 
 Thus indexing should be used for all files where the user will keep using this
 file (at the location given to gnunet-publish) and does not want to retrieve it
 back from GNUnet each time. If you want to remove a file that you have indexed
-from the local peer, use the tool @code{gnunet-unindex} to un-index the file. 
+from the local peer, use the tool @code{gnunet-unindex} to un-index the file.
 
 The option @code{-n} may be used if the user fears that the file might be found
 on his drive (assuming the computer comes under the control of an adversary).
 When used with the @code{-n} flag, the user has a much better chance of denying
 knowledge of the existence of the file, even if it is still (encrypted) on the
 drive and the adversary is able to crack the encryption (e.g. by guessing the
-keyword. 
+keyword.
 
 @node File-sharing: Searching
 @chapter File-sharing: Searching
 @c %**end of header
 
 The command @code{gnunet-search} can be used to search for content on GNUnet.
-The format is: 
+The format is:
 @example
 $ gnunet-search [-t TIMEOUT] KEYWORD
 @end example
@@ -912,10 +902,10 @@ $ gnunet-search [-t TIMEOUT] KEYWORD
 The -t option specifies that the query should timeout after approximately
 TIMEOUT seconds. A value of zero is interpreted as @emph{no timeout}, which is
 also the default. In this case, gnunet-search will never terminate (unless you
-press CTRL-C). 
+press CTRL-C).
 
 If multiple words are passed as keywords, they will all be considered optional.
-Prefix keywords with a "+" to make them mandatory. 
+Prefix keywords with a "+" to make them mandatory.
 
 Note that searching using
 @example
@@ -928,15 +918,14 @@ $ gnunet-search "Das Kapital"
 @end example
 
 as the first will match files shared under the keywords "Das" or "Kapital"
-whereas the second will match files shared under the keyword "Das Kapital". 
+whereas the second will match files shared under the keyword "Das Kapital".
 
-Search results are printed by gnunet-search like this: 
+Search results are printed by gnunet-search like this:
 @example
 $ gnunet-download -o "COPYING" --- gnunet://fs/chk/N8...C92.17992
 => The GNU Public License <= (mimetype: text/plain)
 @end example
 
-
 The first line is the command you would have to enter to download the file.
 The argument passed to @code{-o} is the suggested filename (you may change it 
to
 whatever you like).
@@ -945,7 +934,7 @@ searching the file, a checksum (in hexadecimal) finally the 
size of the file in
 bytes.
 The second line contains the description of the file; here this is
 "The GNU Public License" and the mime-type (see the options for gnunet-publish
-on how to specify these). 
+on how to specify these).
 
 @node File-sharing: Downloading
 @chapter File-sharing: Downloading
@@ -963,7 +952,7 @@ result. Existing files are overwritten. If the existing 
file contains blocks
 that are identical to the desired download, those blocks will not be downloaded
 again (automatic resume).
 
-If you want to download the GPL from the previous example, you do the 
following: 
+If you want to download the GPL from the previous example, you do the 
following:
 @example
 $ gnunet-download -o "COPYING" --- gnunet://fs/chk/N8...92.17992
 @end example
@@ -973,11 +962,11 @@ re-issuing @code{gnunet-download} with the same filename. 
In that case, GNUnet
 will @strong{not} download blocks again that are already present.
 
 GNUnet's file-encoding mechanism will ensure file integrity, even if the
-existing file was not downloaded from GNUnet in the first place. 
+existing file was not downloaded from GNUnet in the first place.
 
 You may want to use the @code{-V} switch (must be added before the @code{--}) 
to
 turn on verbose reporting. In this case, @code{gnunet-download} will print the
-current number of bytes downloaded whenever new data was received. 
+current number of bytes downloaded whenever new data was received.
 
 @node File-sharing: Directories
 @chapter File-sharing: Directories
@@ -991,7 +980,7 @@ meta data.
 The URIs contain all the information required by @code{gnunet-download} to
 retrieve the file. The meta data typically includes the mime-type, description,
 a filename and other meta information, and possibly even the full original file
-(if it was small). 
+(if it was small).
 
 @node File-sharing: Namespace Management
 @chapter File-sharing: Namespace Management
@@ -1049,7 +1038,7 @@ to the NICKNAME to get a unique identifier.
 An item of particular interest in the namespace advertisement is the ROOT.
 The ROOT is the identifier of a designated entry in the namespace. The idea is
 that the ROOT can be used to advertise an entry point to the content of the
-namespace. 
+namespace.
 
 @node File-Sharing URIs
 @c %**end of header
@@ -1222,7 +1211,7 @@ card containing this information as a QR code).
 Assuming Bob has an A record for his website under the name of www in his zone,
 you can then access Bob's website under www.bob.gnu --- as well as any (public)
 GNS record that Bob has in his zone by replacing www with the respective name 
of
-the record in Bob's zone. 
+the record in Bob's zone.
 
 Furthermore, if Bob has himself a (public) delegation to Carol's zone under
 "carol", you can access Carol's records under NAME.carol.bob.gnu (where NAME is
@@ -1305,7 +1294,7 @@ webpages. Zone relative names end in ".+" which indicates 
that the name needs to
 be resolved relative to the current authoritative zone. The extended processing
 of those names will expand the ".+" with the correct delegation chain to the
 authoritative zone (replacing ".+" with the name of the location where the name
-was encountered) and hence generate a valid @code{.gnu} name. 
+was encountered) and hence generate a valid @code{.gnu} name.
 
 GNS currently supports the following record types:
 
@@ -1610,7 +1599,7 @@ For applications that do not use DNS, you can also 
manually create such a
 mapping using the gnunet-vpn command-line tool. Here, you specfiy the desired
 address family of the result (i.e. "-4"), and the intended target IP on the
 Internet ("-i 131.159.74.67") and "gnunet-vpn" will tell you which IP address 
in
-the range of your VPN tunnel was mapped. 
+the range of your VPN tunnel was mapped.
 
 gnunet-vpn can also be used to access "internal" services offered by GNUnet
 nodes. So if you happen to know a peer and a service offered by that peer, you

-- 
To stop receiving notification emails like this one, please contact
address@hidden