Changes between Version 8 and Version 9 of glossary


Ignore:
Timestamp:
Jul 30, 2010 2:59:07 PM (9 years ago)
Author:
darrob
Comment:

some more sorting

Legend:

Unmodified
Added
Removed
Modified
  • glossary

    v8 v9  
    2222====== singular ======
    2323 Addressbook:: <reply> The I2P addressbook manages .i2p addresses, similar to your OS's hosts file. See http://www.i2p2.i2p/faq.html#subscriptions.
    24  Eepget on Windows:: <reply> Look here for instructions to use eepget on Windows: http://zzz.i2p/topics/105. There is also a bat script for the lazy: http://qgv64klyy4tgk4ranaznet5sjgi7ccsrawtjx3j5tvekvvfl67aa.b32.i2p/handystuff/eepget_url.bat.
    25  Exit node:: a Tor relay that relays traffic to the open web. In I2P they are called <outproxies>. As a participant on I2P you are never an exit node/outproxy yourself.
    26  Floodfill:: a special kind of router that does most of the searching for information on the I2P distributed database. You could call it an "ultrapeer" or a "tracker" but people have been using "floodfill" because that refers to exactly what it does.
    27  GarliCat:: <reply> GarliCat creates a transparent IP layer on top of I2P. It transmits any kind of IP-based data transparently through the I2P network. See http://www.cypherpunk.at/onioncat/wiki/GarliCat and http://echelon.i2p/garlicat/.
    28  Irc2P:: the official I2P-internal <IRC network>. You are currently connected to it. See http://hq.postman.i2p/?page_id=25. Related: <IRC servers>, <IRC tunnel>, <SOCKS5 IRC proxy>.
    29  Jetty:: the webserver that is bundled with I2P. It is used to serve I2P's router console and also your <eepsite> by default. It supports HTML and CGI. If you need more features it's easy to setup <Apache> to work with I2P.
    30  OnionCat:: <reply> OnionCat creates a transparent IP layer on top of <Tor>'s <hidden services>. It transmits any kind of IP-based data transparently through the Tor network on a location hidden basis. See http://www.cypherpunk.at/onioncat/.
    31  Reseed:: automatic in I2P. See <manual reseed>.
    32  Router Console:: the place to configure your I2P router. It also links to interesting eepsites and tells you how to configure your browser and IRC client. You find it under http://localhost:7657. Also see <remote router> if applicable.
    33  Seedless Server:: <reply>Seedless Server is a webapplication that allows you to participate in the <seedless> cloud.
    34  Seedless:: a distributed service directory that is used for trackerless torrents, hidden eepsites and more. See http://sponge.i2p/files/seedless/
    35  UPnP:: <reply> I2P supports UPnP (Universal Plug and Play) and UDP hole punching with "SSU introductions" to relay traffic. This is useful if you can't open/forward the necessary ports manually. See http://localhost:7657/config.jsp#help.
    36  Updating:: <reply> By default your router will check for updates periodically and inform you in the <router console>. After the update is transferred all you have to do is restart the router (give it 11 minutes). For options see http://localhost:7657/configupdate.jsp.
     24 bandwidth:: Your bandwidth is configured on http://localhost:7657/config.jsp . All rates in I2P are specified in bytes per second. Divide your connection rate in bits per second by 8 to get bytes per second.
    3725 block list:: the manually-configured list of banned peers
    3826 bob:: a Basic Open Bridge API to the I2P router. see http://bob.i2p/ for more info.
    3927 bulk:: an i2ptunnel connection type and is the default. You generally do not need to change this.
     28 e2ee:: end to end encryption
    4029 eepannouncer:: <reply>EepAnnouncer is a webapplication that announces your <eepsite> to the <seedless> cloud.
     30 Eepget on Windows:: <reply> Look here for instructions to use eepget on Windows: http://zzz.i2p/topics/105. There is also a bat script for the lazy: http://qgv64klyy4tgk4ranaznet5sjgi7ccsrawtjx3j5tvekvvfl67aa.b32.i2p/handystuff/eepget_url.bat.
    4131 eepget:: a command line HTTP client similar to wget, found in your I2P installation directory. It fetches web pages and files through the I2P HTTP proxy. If you use Windows see <eepget on Windows>. For an alternative ask me about <wget>.
    4232 eeproxy:: <reply>I2P provides a resident http proxy server to access .i2p domains, and optionally http sites on the outernet (via false.i2p). Default: 127.0.0.1:4444
     33 Exit node:: a Tor relay that relays traffic to the open web. In I2P they are called <outproxies>. As a participant on I2P you are never an exit node/outproxy yourself.
     34 firewalled:: <reply>Firewalled means your UDP port appears to be firewalled. As the firewall detection methods are not 100% reliable, this may occasionally be displayed in error. See http://127.0.0.1:7657/config.jsp#help and <ports>
     35 Floodfill:: a special kind of router that does most of the searching for information on the I2P distributed database. You could call it an "ultrapeer" or a "tracker" but people have been using "floodfill" because that refers to exactly what it does.
    4336 garlic routing:: layered encryption of messages, passing through routers selected by the original sender; a technique employed by the i2p router, see http://www.i2p2.i2p/how_garlicrouting
    4437 i2cp:: http://www.i2p2.i2p/i2cp
     
    4740 identity:: Your router identity is shown at http://localhost:7657/netdb.jsp?r=. It is the 44-character string after "our info" and represents a 256-bit SHA-256 hash of your router's public keys. You do not normally need to change it, but see http://zzz.i2p/topics/21 if you really want to.
    4841 interactive:: an i2ptunnel connection type and is not the default. It may be better than bulk for IRC, but this option really doesn't do much and might be removed someday.
     42 Irc2P:: the official I2P-internal <IRC network>. You are currently connected to it. See http://hq.postman.i2p/?page_id=25. Related: <IRC servers>, <IRC tunnel>, <SOCKS5 IRC proxy>.
     43 Itoopie:: the official I2P Mascot.
     44 Jetty:: the webserver that is bundled with I2P. It is used to serve I2P's router console and also your <eepsite> by default. It supports HTML and CGI. If you need more features it's easy to setup <Apache> to work with I2P.
    4945 manual reseed:: only recomended when you have absolutely no communication from anyone at all. Otherwise i2p seeds itself. See http://www.i2p2.de/faq.html#manual_reseed for more info
    5046 message delay:: How long an outbound message waits in the queue. This should generally be a few hundred milliseconds or less.  see also http://localhost:7657/help.jsp
     
    5248 outer net:: a term for the open Internet as opposed to closed (inner) darknets like I2P.
    5349 peer ban list:: automatically updated, but may also contain manual entries called the block list
     50 rejecting tunnels:: when the router is refusing to route traffic for others, for example when it has just started up.
     51 Reseed:: automatic in I2P. See <manual reseed>.
     52 Router Console:: the place to configure your I2P router. It also links to interesting eepsites and tells you how to configure your browser and IRC client. You find it under http://localhost:7657. Also see <remote router> if applicable.
     53 Seedless Server:: <reply>Seedless Server is a webapplication that allows you to participate in the <seedless> cloud.
     54 Seedless:: a distributed service directory that is used for trackerless torrents, hidden eepsites and more. See http://sponge.i2p/files/seedless/
    5455 share:: Your share bandwidth is configured on http://localhost:7657/config.jsp . It is the maximum percentage of your bandwidth limits that is used to route traffic for others. The remainder is reserved for your own traffic. See also <bandwidth>
    5556 streaming lib:: described at http://www.i2p2.i2p/streaming
    5657 tunnel timeout:: fixed at 10 minutes (unlike Tor where a circuit is long-lived). It used to be configurable but it isn't any more. All peers assume a timeout of 10 minutes.
    5758 tunnel:: <reply>A tunnel in I2P refers to the connection between 2 endpoints. Ask me about <creating tunnels>
     59 Updating:: <reply> By default your router will check for updates periodically and inform you in the <router console>. After the update is transferred all you have to do is restart the router (give it 11 minutes). For options see http://localhost:7657/configupdate.jsp.
     60 UPnP:: <reply> I2P supports UPnP (Universal Plug and Play) and UDP hole punching with "SSU introductions" to relay traffic. This is useful if you can't open/forward the necessary ports manually. See http://localhost:7657/config.jsp#help.
    5861 zzzot:: an open tracker plugin. It sets up a tunnel automatically. The statistics page is at http://127.0.0.1:7662/tracker/index.jsp . There is no admin interface.
    5962
    6063====== plural ======
     64 b32 addresses:: shorter addresses to eepsites (shorter than b64) that don't have to be registered anywhere. You can find the b32 address of your eepsite by clicking on the preview button in your eepsite tunnel entry here: http://localhost:7657/i2ptunnel/index.jsp
    6165 Deepsites:: distributed eepsites hosted on the Tahoe-LAFS distributed data storage.
    6266 Eepsites:: anonymously hosted websites in I2P, sometimes accessible from the outernet through an <inproxy>. Ask me about <browsing eepsites>, <hosting eepsites> and <backing up eepsites>. Related: <Deepsites>, <links>.
     
    6569 Outproxies:: servers that allow you to access the Internet anonymously through I2P. They are the equivalent to Tor's exit nodes, however in I2P there are only a few that are run by volunteers. We usually recommend Tor for anonymous web access.
    6670 Plugins:: a way to easily support additional software for I2P. This is quite new but several useful plugins exist already. See http://stats.i2p/i2p/plugins/.
    67  b32 addresses:: shorter addresses to eepsites (shorter than b64) that don't have to be registered anywhere. You can find the b32 address of your eepsite by clicking on the preview button in your eepsite tunnel entry here: http://localhost:7657/i2ptunnel/index.jsp
    6871 ports:: <reply> You'll need to make sure that your router is reachable from the outside. The following link will help you set up your ports correctly: http://localhost:7657/config.jsp#chelp
    6972
    7073=== I2P related ===
    7174===== singular =====
    72  #i2p-help:: a channel meant to help users learn the basics of using i2p from other users and by asking me questions.
     75 addressbook update:: The interval for updating the addressbook from the subscriptions is 12 hours by default. Change the subscription list to force an update immediately.
    7376 Anonymity on I2P:: <reply> Anonymity is not a boolean - we are not trying to make something "perfectly anonymous", but instead are working at making attacks more and more expensive to mount. I2P is a low latency mix network, and there are limits to the anonymity offered by such a system, but the applications on top of I2P, such as Syndie, I2P mail, and I2PSnark extend it to offer both additional functionality and protection.
    7477 Anonymity:: a broad subject. Most importantly it's not a boolean. You may want to ask me about the <disclaimer> or <staying safe>.
     
    7881 Creating tunnels:: <reply> To setup a new I2P tunnel go to: http://localhost:7657/i2ptunnel/index.jsp
    7982 Disclaimer:: <reply> I2P is still a work in progress. It should not be relied upon for "guaranteed" anonymity at this time, due to the relatively small size of the network and the lack of extensive academic review. It is not immune to to attacks from those with unlimited resources, and may never be, due to the inherent limitations of low-latency mix networks.
     83 Eepsite backup:: <reply> To backup your eepsite it should be enough to save your eepsite directory (probably in ~/.i2p). The most important file to backup is your private key (eepsite/eepPriv.dat).
    8084 Eepsite Unreachable:: <reply> The eepsite unreachable error means that the eepsite is either offline, there is network congestion, or that your router is not yet well-integrated with peers. In any case you should retry. You can check if an eepsite is online at http://perv.i2p/.
    81  Eepsite backup:: <reply> To backup your eepsite it should be enough to save your eepsite directory (probably in ~/.i2p). The most important file to backup is your private key (eepsite/eepPriv.dat).
    8285 Eepsite uptime:: <reply> The uptime of <eepsites> can vary if the owner's router is not running 24/7. <Deepsites> might be a solution to this particular problem.
     86 eMule:: a file-sharing client not compatible with I2P. You're probably looking for iMule.
    8387 Exit node sniffing:: a potential problem when routing unencrypted traffic through Tor or I2P to the web, because a malicious exit node/outproxy can easily sniff that traffic. This problem does not exist inside I2P or when using Tor's Hidden Services.
    8488 File-sharing:: <reply> There are several file-sharing solutions for I2P: <BitTorrent>, <iMule>, <I2Phex>, your own <eepsite> and at some point in the future also <Tahoe-LAFS>. BitTorrent is the most popular one.
    8589 Forum project:: something <dream> is working on. That's unfortunately all I know.
    8690 Forum:: <reply> Forum may refer to <forum.i2p> (http://forum.i2p/) or to dream's <Forum> project>. Forum.i2p is a donated service, please respect the operator.
     91 fox:: a link between irc servers outside and irc2p servers inside i2p.  The nick of the person is shown after <fox>
     92 GarliCat:: <reply> GarliCat creates a transparent IP layer on top of I2P. It transmits any kind of IP-based data transparently through the I2P network. See http://www.cypherpunk.at/onioncat/wiki/GarliCat and http://echelon.i2p/garlicat/.
     93 gnutella:: <reply>I2Phex is the I2P port of Phex. It offers you file sharing using the gnutella protocol in I2P.
     94 guitone:: a nice GUI frontend for monotone
    8795 Hosting eepsites:: <reply> If you want to run your own, fully anonymous eepsite follow the instructions on your <router console> (http://127.0.0.1:7658). This will make use of I2P's <Jetty> webserver. You may also use <Apache>.
     96 how eepsite:: <reply>to view eepsites, your browser (or system) proxy for http needs to have the same settings as "eepproxy" under the local destinations link in your console. Usually this is 127.0.0.1 port 4444
     97 howtoirc:: <reply> Dear visitors, you can connect to the anonymous I2P IRC servers directly by adding a server with the address 127.0.0.1 and port 6668 (no proxy) in your client.
    8898 I2P Rufus:: a now unmaintained <BitTorrent client>. Look into <Robert> instead.
    8999 I2P Status:: a <Twitter>-like microblogging service on I2P: http://status.h2ik.i2p/. There is also http://annontwitter.i2p/.
     100 I2P-Bote:: an I2P-internal, anonymous and secure (end-to-end encrypted) serverless e-mail system. For more information visit: http://i2pbote.i2p
    90101 I2P-BT:: <reply> I2P-BT was the first working <BitTorrent> client for I2P. See http://i2p-bt.postman.i2p/. You should also look into the other <BitTorrent clients> available.
    91  I2P-Bote:: an I2P-internal, anonymous and secure (end-to-end encrypted) serverless e-mail system. For more information visit: http://i2pbote.i2p
    92102 I2P-Messenger:: an I2P-internal, anonymous and secure (end-to-end encrypted) serverless instant messenger with support for file transfers. See http://echelon.i2p/qti2pmessenger.
    93103 I2P:: <reply> I2P (Invisible Internet Project) is a darknet implementation built atop java, with full support for streaming, anonymous <BitTorrent>, <webserving>, <mail> and more. See http://www.i2project.net/ or http://www.i2p2.i2p/.
     104 i2phex browser:: I2Phex is a standalone application, it is not accessible from a browser.
     105 I2Phex:: a Gnutella client for use within the I2P network. There is a I2Phex forum here: http://forum.i2p/viewforum.php?f=25. You can download it here: http://echelon.i2p/.
     106 i2ping:: like ping over i2p
    94107 I2PSnark:: the built-in BitTorrent client. It has links to the most common I2P trackers and even explains how to add torrents (http://localhost:7657/i2psnark/). There are also alternative <BitTorrent clients> though.
    95108 I2PSnarkXL:: an extension of the router-builtin I2PSnark BitTorrent client. It adds a nice GUI and some performance enhancements. See http://i2psnarkxl.i2p/. Also ask me about the other <BitTorrent clients>.
    96  I2Phex:: a Gnutella client for use within the I2P network. There is a I2Phex forum here: http://forum.i2p/viewforum.php?f=25. You can download it here: http://echelon.i2p/.
    97109 IM:: <reply> For I2P-internal instant messaging there is <I2P-Messenger>, furthermore we have the I2P-internal IRC network <Irc2P>.
     110 iMule:: an open-source aMule clone for I2P-internal use. It offers filesharing via an I2P-kad network and can be downloaded from http://echelon.i2p or http://www.imule.i2p. And there's a section in the forum: http://forum.i2p/viewforum.php?f=30.
    98111 IRC servers:: <reply> I know of the following I2P IRC servers: irc.postman.i2p/irc.freshcoffee.i2p (here, <Irc2P>), irc.welterde.i2p and irc.telecomix.i2p. You cannot connect to regular internet IRC servers. See <IRC tunnel> and <SOCKS5 IRC poxy> for help on how to connect.
    99  Itoopie:: the official I2P Mascot.
     112 jrandom:: the founder of i2p, who vanished in November 2007
    100113 Mail.i2p:: an I2P mail service. Your you@mail.i2p account also works on the internet as you@i2pmail.org. You can use it to communicate with I2P and non-I2P users. See http://hq.postman.i2p/?page_id=4. Also ask me about <MUAs> and <I2P-Bote>.
    101114 Mail:: <reply> There are two very different email systems on I2P. Ask me about <mail.i2p> and <I2P-Bote>.
    102  NNTP:: the Network News Transfer Protocol which is used for transporting Usenet news articles (netnews) between news servers and for reading and posting articles. Ask me about <news servers> and <newsreaders>.
    103  Netfilter:: a framework that provides hook handling within the Linux kernel for intercepting and manipulating network packets. See http://www.netfilter.org/.
    104  Network accessible router:: <reply> To make your router accessible by all computers on your network subsitute '127.0.0.1' for the IP address of the server in line 'clientApp.0.args=7657 127.0.0.1 ./webapps/' in file ~/.i2p/clients.config. Be aware that traffic to the router console will be unencrypted. You should use <SSH tunnels> instead.
    105  News server:: <reply> There is a news server (<NNTP>) operated by welterde at nntp.welterde.i2p. To access it you need to create a new <tunnel> to point to that address and then set your <newsreader> to connect to localhost and the port you chose. Also see <newsreaders>.
    106  POP3:: a protocol used to retrieve email from a remote server. For <mail.i2p> see http://hq.postman.i2p/?page_id=11. POP3 support is also planned for <I2P-Bote>.
    107  PyBit:: a <BitTorrent client> for I2P. I haven't learned much about it yet. All I know is that you can get it from http://echelon.i2p/.
    108  Remote router:: <reply> If you run the I2P router on another computer the best way to access it is using <SSH tunnels>. Alternatively you can set the router to accept connections from the network (see <network accessible router>).
    109  Robert:: a bittorrent client for the I2P network, with support for trackerless torrents. For more information visit: http://bob.i2p
    110  SOCKS5 IRC proxy:: <reply> With a SOCKS5 IRC proxy tunnel you'll be able to connect to several IRC servers without having to setup a seperate tunnel for each one. Here are the instructions: http://zzz.i2p/topics/690
    111  SSH tunnel settings:: <reply> To tunnel I2P through SSH create the necessary tunnels by either running 'ssh -L7657:127.0.0.1:7657 -L4444:127.0.0.1:4444 $USER@$SERVER' or setting the LocalForwards in your ~/.ssh/config accordingly.
    112  Shutdown:: <reply> The reason a shutdown/restart of your router takes 11 minutes is that tunnel leases last 10 minutes. Your router waits 11 minutes to make sure that all participating tunnels are finished.
    113  Smigmacy:: <reply> Smigacy (which stands for Send Messages through I2pmail with Greater privACY) is an anonymity filter for SMTP, primarily intended to be used with Postman’s I2PMail service. See http://hq.postman.i2p/?page_id=35.
    114  Syndie:: an open source system for operating distributed forums, offering a secure and consistent interface to various anonymous and non-anonymous content networks. More at http://syndie.i2p2.de/ and http://forum.i2p/viewforum.php?f=29.
    115  Tahoe-LAFS:: the first cloud storage system with provider-independent security. Find out more at http://duck.i2p/tahoe-lafs/ and join #tahoe-lafs.
    116  Techintro:: <reply> For an introduction to how I2P works see http://www.i2p2.i2p/techintro.html.
    117  Telecomix:: a group of internet activists that is also active on I2P. See http://telecomix.org/ and http://telecomix.i2p/.
    118  Tor overview:: https://www.torproject.org/overview.html.en
    119  Tor:: an anonymous network very similar to I2P, but unlike I2P it focuses on anonymous access to the open web. We consider the two as being complimentary. See http://www.i2p2.de/techintro.html#similar.tor & https://www.torproject.org/
    120  Torbutton:: a recommended Firefox extensions that despite its name is very useful on I2P. It takes care of many different browser settings to prevent privacy attacks. See https://www.torproject.org/torbutton/.
    121  Trac:: an open source, web-based project management and bug-tracking tool. I2P's trac is located here: http://trac.i2p2.i2p/
    122  Transmission:: a BitTorrent client. There is also a port of it that works for I2P-internal torrents. See http://echelon.i2p for more details.
    123  Video tutorial:: <reply> There is a video tutorial on how to install I2P by Telecomix: http://www.youtube.com/watch?v=QeRN2G9VW5E.
    124  addressbook update:: The interval for updating the addressbook from the subscriptions is 12 hours by default. Change the subscription list to force an update immediately.
    125  bandwidth:: Your bandwidth is configured on http://localhost:7657/config.jsp . All rates in I2P are specified in bytes per second. Divide your connection rate in bits per second by 8 to get bytes per second.
    126  e2ee:: end to end encryption
    127  eMule:: a file-sharing client not compatible with I2P. You're probably looking for iMule.
    128  firewalled:: <reply>Firewalled means your UDP port appears to be firewalled. As the firewall detection methods are not 100% reliable, this may occasionally be displayed in error. See http://127.0.0.1:7657/config.jsp#help and <ports>
    129  fox:: a link between irc servers outside and irc2p servers inside i2p.  The nick of the person is shown after <fox>
    130  gnutella:: <reply>I2Phex is the I2P port of Phex. It offers you file sharing using the gnutella protocol in I2P.
    131  guitone:: a nice GUI frontend for monotone
    132  how eepsite:: <reply>to view eepsites, your browser (or system) proxy for http needs to have the same settings as "eepproxy" under the local destinations link in your console. Usually this is 127.0.0.1 port 4444
    133  howtoirc:: <reply> Dear visitors, you can connect to the anonymous I2P IRC servers directly by adding a server with the address 127.0.0.1 and port 6668 (no proxy) in your client.
    134  i2phex browser:: I2Phex is a standalone application, it is not accessible from a browser.
    135  i2ping:: like ping over i2p
    136  iMule:: an open-source aMule clone for I2P-internal use. It offers filesharing via an I2P-kad network and can be downloaded from http://echelon.i2p or http://www.imule.i2p. And there's a section in the forum: http://forum.i2p/viewforum.php?f=30.
    137  jrandom:: the founder of i2p, who vanished in November 2007
    138115 monotone help:: http://www.i2p2.i2p/newdevelopers
    139116 monotone:: the distributed version control system (DVCS) used to propagate and store development work on I2P. See http://monotone.ca also see http://www.i2p2.i2p/newdevelopers
     
    141118 mtn co:: monotone checkout, you only need to do this once for each branch
    142119 mtn help:: an easy way to get inline help about misc monotone commands. see also <monotone>
     120 Netfilter:: a framework that provides hook handling within the Linux kernel for intercepting and manipulating network packets. See http://www.netfilter.org/.
     121 Network accessible router:: <reply> To make your router accessible by all computers on your network subsitute '127.0.0.1' for the IP address of the server in line 'clientApp.0.args=7657 127.0.0.1 ./webapps/' in file ~/.i2p/clients.config. Be aware that traffic to the router console will be unencrypted. You should use <SSH tunnels> instead.
     122 News server:: <reply> There is a news server (<NNTP>) operated by welterde at nntp.welterde.i2p. To access it you need to create a new <tunnel> to point to that address and then set your <newsreader> to connect to localhost and the port you chose. Also see <newsreaders>.
     123 NNTP:: the Network News Transfer Protocol which is used for transporting Usenet news articles (netnews) between news servers and for reading and posting articles. Ask me about <news servers> and <newsreaders>.
     124 OnionCat:: <reply> OnionCat creates a transparent IP layer on top of <Tor>'s <hidden services>. It transmits any kind of IP-based data transparently through the Tor network on a location hidden basis. See http://www.cypherpunk.at/onioncat/.
    143125 pastebin:: a place where you can share snippets of text that are too long for IRC (e.g. error messages). The I2P internal, anonymous pastbin is at http://paste.i2p2.i2p/.
    144  rejecting tunnels:: when the router is refusing to route traffic for others, for example when it has just started up.
     126 POP3:: a protocol used to retrieve email from a remote server. For <mail.i2p> see http://hq.postman.i2p/?page_id=11. POP3 support is also planned for <I2P-Bote>.
     127 PyBit:: a <BitTorrent client> for I2P. I haven't learned much about it yet. All I know is that you can get it from http://echelon.i2p/.
     128 Remote router:: <reply> If you run the I2P router on another computer the best way to access it is using <SSH tunnels>. Alternatively you can set the router to accept connections from the network (see <network accessible router>).
     129 Robert:: a bittorrent client for the I2P network, with support for trackerless torrents. For more information visit: http://bob.i2p
     130 Shutdown:: <reply> The reason a shutdown/restart of your router takes 11 minutes is that tunnel leases last 10 minutes. Your router waits 11 minutes to make sure that all participating tunnels are finished.
     131 Smigmacy:: <reply> Smigacy (which stands for Send Messages through I2pmail with Greater privACY) is an anonymity filter for SMTP, primarily intended to be used with Postman’s I2PMail service. See http://hq.postman.i2p/?page_id=35.
     132 SOCKS5 IRC proxy:: <reply> With a SOCKS5 IRC proxy tunnel you'll be able to connect to several IRC servers without having to setup a seperate tunnel for each one. Here are the instructions: http://zzz.i2p/topics/690
     133 SSH tunnel settings:: <reply> To tunnel I2P through SSH create the necessary tunnels by either running 'ssh -L7657:127.0.0.1:7657 -L4444:127.0.0.1:4444 $USER@$SERVER' or setting the LocalForwards in your ~/.ssh/config accordingly.
    145134 stats.i2p:: <reply>http://stats.i2p provides near-realtime stats on the network and other misc services, run by zzz.
    146135 susimail:: <reply>Susimail is the resident webmail client that interfaces with postman's mail services. http://127.0.0.1:7657/susimail
     136 Syndie:: an open source system for operating distributed forums, offering a secure and consistent interface to various anonymous and non-anonymous content networks. More at http://syndie.i2p2.de/ and http://forum.i2p/viewforum.php?f=29.
     137 Tahoe-LAFS:: the first cloud storage system with provider-independent security. Find out more at http://duck.i2p/tahoe-lafs/ and join #tahoe-lafs.
     138 Techintro:: <reply> For an introduction to how I2P works see http://www.i2p2.i2p/techintro.html.
     139 Telecomix:: a group of internet activists that is also active on I2P. See http://telecomix.org/ and http://telecomix.i2p/.
    147140 thepiratebay:: an eepsite that is hard to find, has bad stuff on it, and may not be up anymore. Not recommended. Instead ask me about <BitTorrent trackers>.
     141 Tor overview:: https://www.torproject.org/overview.html.en
     142 Tor:: an anonymous network very similar to I2P, but unlike I2P it focuses on anonymous access to the open web. We consider the two as being complimentary. See http://www.i2p2.de/techintro.html#similar.tor & https://www.torproject.org/
     143 Torbutton:: a recommended Firefox extensions that despite its name is very useful on I2P. It takes care of many different browser settings to prevent privacy attacks. See https://www.torproject.org/torbutton/.
     144 Trac:: an open source, web-based project management and bug-tracking tool. I2P's trac is located here: http://trac.i2p2.i2p/
    148145 tracker:: <reply>A tracker is a public site dedicated to offering bittorrent downloads.
     146 Transmission:: a BitTorrent client. There is also a port of it that works for I2P-internal torrents. See http://echelon.i2p for more details.
     147 Video tutorial:: <reply> There is a video tutorial on how to install I2P by Telecomix: http://www.youtube.com/watch?v=QeRN2G9VW5E.
    149148 vulpine:: a link between irc servers outside and irc2p servers inside i2p. The nick of the person is shown after <vulpine>
    150149 wiki:: <reply> see http://ugha.i2p
     
    172171 ELinks:: a free text-based console web browser for Unix-like operating systems. To use it with I2P you need to set the http proxy variable: 'http_proxy=127.0.0.1:4444 elinks'. You could create a bash alias for convenience.
    173172 Encryption:: the process of transforming information (referred to as plaintext) using an algorithm (called cipher) to make it unreadable to anyone except those possessing special knowledge, usually referred to as a key. http://en.wikipedia.org/wiki/Encryption
    174  FLIP:: <reply> FLIP (Freenet Lightweight IRC Program) is an application to provide chat over Freenet using the IRC protocol. See http://new-wiki.freenetproject.org/FLIP.
    175173 Fetchmail:: a MRA. Personally I think <getmail> is a better choice, but I may be convinced otherwise. See http://www.fetchmail.info/.
    176174 Firefox:: a recommended web browser for I2P. Ask me about <Firefox extensions> and <browser profiles>.
     175 FLIP:: <reply> FLIP (Freenet Lightweight IRC Program) is an application to provide chat over Freenet using the IRC protocol. See http://new-wiki.freenetproject.org/FLIP.
    177176 FoxyProxy I2P rule:: <reply> To correctly route all I2P traffic using <FoxyProxy> add the following regular expression rule: {{{^http://[^/]*\.i2p/.*}}}
    178177 FoxyProxy:: an addon that lets you configure several different proxies in Firefox to access I2P and the web at the same time. See http://zephyr.i2p/foxyproxy.html and <FoxyProxy I2P rule>. Alternatives are <browser profiles> and <Privoxy>.
    179  FreeTalk:: supposed to be a spam-resistant system for discussion forums on Freenet. See http://new-wiki.freenetproject.org/Freetalk.
    180178 Freenet proxy:: <reply> There is a Freenet proxy at http://fproxy.tino.i2p/.
    181179 Freenet:: a decentralized, distributed data store. All applications etc. are built on top of the data store which is extremely limiting. See http://freenetproject.org/. For a distributed datastore on I2P see <Tahoe-LAFS>.
     180 FreeTalk:: supposed to be a spam-resistant system for discussion forums on Freenet. See http://new-wiki.freenetproject.org/Freetalk.
    182181 Frost:: an external application for Freenet that provides usenet-like messaging and a searchable file-sharing system. See http://new-wiki.freenetproject.org/Frost.
     182 Getmail:: a MRA that is very easy to setup to work with <mail.i2p>. Simply point it to localhost port 7660 and set it to SimplePOP3Retriever (non-SSL). See http://pyropus.ca/software/getmail/. An alternative is <Fetchmail>.
    183183 GNUnet:: an anoymous P2P network that's build around the purpose of file-sharing. http://gnunet.org/
    184  Getmail:: a MRA that is very easy to setup to work with <mail.i2p>. Simply point it to localhost port 7660 and set it to SimplePOP3Retriever (non-SSL). See http://pyropus.ca/software/getmail/. An alternative is <Fetchmail>.
    185  MRA:: <reply> A mail retrieval agent (MRA) is an application that retrieves e-mail from a remote mail server, for example <mail.i2p>. I know about <getmail> and <fetchmail>.
     184 iptables:: a user space application program that allows a system administrator to configure the tables provided by the Linux kernel firewall and the chains and rules it stores. See http://www.netfilter.org/.
    186185 Microblogging:: a form of blogging (like on Twitter). There is an I2P microblogging service called I2P Status at http://status.h2ik.i2p.
    187186 Mixminion:: an anonymous remailer: http://en.wikipedia.org/wiki/Mixminion. For I2P mail systems ask me about <mail>.
     187 MRA:: <reply> A mail retrieval agent (MRA) is an application that retrieves e-mail from a remote mail server, for example <mail.i2p>. I know about <getmail> and <fetchmail>.
    188188 Multiproxy Switch:: a Firefox extension for proxy management, it can be used to quickly switch proxy settings; with a visual indication... covers more settings than the on/off of torbutton... and is not conditional like foxyproxy,so it works better feeding a conditional proxy. More details of it's robustness and info leaks are needed...
    189189 Mutt:: a mail client (MUA) that works with <mail.i2p>. Research the header related options to make sure you're not giving away personal information though. Use <getmail> and mutt's native SMTP support. See http://www.mutt.org/ and compare it with other MUAs here: http://hq.postman.i2p/?page_id=9.
     
    196196 RefControl:: a Firefox extension that allows you to forge the HTTP Referer and thereby hide from which site you have been redirected. See https://addons.mozilla.org/en-US/firefox/addon/953/ and http://www.stardrifter.org/refcontrol/.
    197197 RequestPolicy:: a highly recommended Firefox extension that allows you to control which cross-site requests you want to allow. See https://addons.mozilla.org/en-US/firefox/addon/9727/ and http://www.requestpolicy.com/.
    198  SMTP:: a protocol used to transfer email. For <mail.i2p> see http://hq.postman.i2p/?page_id=10. STMP support is also planned for <I2P-Bote>.
    199198 Search engine:: <reply> http://eepsites.i2p/ is an I2P internal search engine.
    200199 Sendmail:: an MTA. Sorry, that's all I can tell you right now.
     200 slrn:: an open source text-based news client. Once you created the tunnel for an I2P <news server> run 'slrn --nntp -h localhost -p $port' to connect. Before actually using it you should configure a .slrnrc for I2P. Ask me about <slrnrc>.
     201 slrnrc:: <reply> A standard .slrnrc will work. However, make sure you configure your desired nickname and 'set generate_message_id 0' to keep your hostname secret. Also fake your hostname (set hostname) and set your mail.i2p address as the replyto address.
     202 SMTP:: a protocol used to transfer email. For <mail.i2p> see http://hq.postman.i2p/?page_id=10. STMP support is also planned for <I2P-Bote>.
    201203 Squid:: possibly the most common caching proxy server. It is rather complex and most users might be better off using Polipo. See http://www.squid-cache.org/.
    202204 Staying safe:: <reply> Staying safe on anonymous networks requires discipline regarding the information you give away as well as a secure and trustworthy computer system.
    203  TLS:: <reply> Transport Layer Security (TLS) and its predecessor, Secure Socket Layer (SSL), are cryptographic protocols that provide security for communications over networks such as the Internet. Since I2P encrypts connections by default TLS is not needed for internal services.
    204205 Thaw:: a filesharing utility and upload/download manager. It is used as a graphical interface for Freenet filesharing. See http://new-wiki.freenetproject.org/Thaw.
    205206 Thunderbird:: a MUA that can be used with <mail.i2p>. Be sure to read the following page though: http://hq.postman.i2p/?page_id=9.
     207 TLS:: <reply> Transport Layer Security (TLS) and its predecessor, Secure Socket Layer (SSL), are cryptographic protocols that provide security for communications over networks such as the Internet. Since I2P encrypts connections by default TLS is not needed for internal services.
    206208 Twitter:: a micro-blogging platform. There are 2 similar services on I2P. See http://status.h2ik.i2p/ and http://annontwitter.i2p/. Also, zzz is on twitter at http://twitter.com/i2p/.
    207209 VPN:: <reply> VPNs (virtual private networks) are a very useful tool. For the purpose of staying anonymous those commercial VPN providers that are being hyped everywhere are useless though. Be careful.
    208  iptables:: a user space application program that allows a system administrator to configure the tables provided by the Linux kernel firewall and the chains and rules it stores. See http://www.netfilter.org/.
    209  slrn:: an open source text-based news client. Once you created the tunnel for an I2P <news server> run 'slrn --nntp -h localhost -p $port' to connect. Before actually using it you should configure a .slrnrc for I2P. Ask me about <slrnrc>.
    210  slrnrc:: <reply> A standard .slrnrc will work. However, make sure you configure your desired nickname and 'set generate_message_id 0' to keep your hostname secret. Also fake your hostname (set hostname) and set your mail.i2p address as the replyto address.
    211210 wget:: a utility for downloading network data. It reads the http_proxy environment variable. Set it to localhost:4444 to be able to retrieve files from I2P. Also see <eepget>.
    212211