From bc139e5a7c5271969f3c7f73db42f1e22d053779 Mon Sep 17 00:00:00 2001 From: idk Date: Fri, 27 Nov 2020 16:16:49 -0500 Subject: [PATCH] Replace all references to eepSite with I2P Site --- i2p2www/blog/2004/07/20/status.html | 6 ++-- i2p2www/blog/2004/08/03/status.html | 2 +- i2p2www/blog/2004/08/10/status.html | 2 +- i2p2www/blog/2004/08/24/status.html | 8 +++--- i2p2www/blog/2004/09/14/status.html | 8 +++--- i2p2www/blog/2004/10/05/status.html | 8 +++--- i2p2www/blog/2004/10/19/status.html | 4 +-- i2p2www/blog/2004/10/26/status.html | 2 +- i2p2www/blog/2004/11/02/status.html | 4 +-- i2p2www/blog/2004/11/23/status.html | 2 +- i2p2www/blog/2004/11/30/status.html | 6 ++-- i2p2www/blog/2004/12/21/status.html | 6 ++-- i2p2www/blog/2004/12/28/status.html | 2 +- i2p2www/blog/2005/02/15/status.html | 4 +-- i2p2www/blog/2005/03/01/status.html | 4 +-- i2p2www/blog/2005/04/05/status.html | 2 +- i2p2www/blog/2005/04/19/status.html | 2 +- i2p2www/blog/2005/05/03/status.html | 2 +- i2p2www/blog/2005/08/23/status.html | 2 +- i2p2www/blog/2005/09/06/status.html | 4 +-- i2p2www/blog/2005/11/22/status.html | 2 +- i2p2www/blog/2006/01/03/status.html | 2 +- i2p2www/blog/2006/01/10/status.html | 2 +- i2p2www/blog/2006/08/01/status.html | 6 ++-- i2p2www/blog/2006/10/03/status.html | 2 +- i2p2www/blog/2008/02/10/release-0.6.1.31.html | 2 +- i2p2www/blog/2009/07/31/release-0.7.6.html | 2 +- i2p2www/blog/2010/03/15/release-0.7.12.html | 2 +- i2p2www/blog/2011/03/02/release-0.8.4.html | 2 +- i2p2www/pages/downloads/debian.html | 2 +- i2p2www/pages/downloads/firefox.html | 2 +- i2p2www/pages/downloads/list.html | 2 +- i2p2www/pages/downloads/post-install.html | 2 +- i2p2www/pages/downloads/windows.html | 2 +- i2p2www/pages/site/browser/intro.html | 4 +-- i2p2www/pages/site/docs/api/i2ptunnel.html | 6 ++-- .../site/docs/applications/embedding.html | 2 +- .../pages/site/docs/discussions/naming.html | 2 +- .../pages/site/docs/discussions/netdb.html | 4 +-- i2p2www/pages/site/docs/how/intro.html | 2 +- .../pages/site/docs/how/network-database.html | 2 +- i2p2www/pages/site/docs/how/tech-intro.html | 10 +++---- i2p2www/pages/site/docs/how/threat-model.html | 4 +-- i2p2www/pages/site/docs/naming.html | 4 +-- .../site/docs/tunnels/unidirectional.html | 4 +-- i2p2www/pages/site/faq.html | 28 +++++++++---------- .../get-involved/develop/applications.html | 2 +- .../get-involved/develop/signed-keys.html | 4 +-- .../get-involved/guides/new-translators.html | 2 +- .../site/get-involved/guides/reseed.html | 2 +- i2p2www/pages/site/get-involved/roadmap.html | 6 ++-- .../pages/site/misc/i2ptunnel-migration.html | 6 ++-- .../pages/site/misc/i2ptunnel-services.html | 2 +- i2p2www/pages/site/misc/ticket919.html | 24 ++++++++-------- 54 files changed, 116 insertions(+), 116 deletions(-) diff --git a/i2p2www/blog/2004/07/20/status.html b/i2p2www/blog/2004/07/20/status.html index 995cb3e4..d890baa9 100644 --- a/i2p2www/blog/2004/07/20/status.html +++ b/i2p2www/blog/2004/07/20/status.html @@ -14,8 +14,8 @@ great job of upgrading - we only have two holdouts now (one at 0.3.2.2 and one way back at 0.3.1.4 :). Over the last few days the network has been more reliable than usual - people are staying on irc.duck.i2p for hours at a time, -larger file downloads are succeeding from I2P sites, and -general I2P site reachability is fairly good. Since its +larger file downloads are succeeding from I2P Sites, and +general I2P Site reachability is fairly good. Since its going well and I want to keep you on your toes, I decided to change a few fundamental concepts and we'll have them deployed in a 0.3.3 release in a day or two. @@ -86,7 +86,7 @@ to jump on - news be a simple heading, with an announcements page below? * i2ptunnel_services, i2ptunnel_tuning, i2ptunnel_lan: - We need someone to rewrite the 'how to set up an I2P site' + We need someone to rewrite the 'how to set up an I2P Site' page, as well as include answers to the two most frequently asked I2PTunnel questions (how to access it through a LAN and how to configure its tunnels - answers diff --git a/i2p2www/blog/2004/08/03/status.html b/i2p2www/blog/2004/08/03/status.html index 2de529fe..2f2e4650 100644 --- a/i2p2www/blog/2004/08/03/status.html +++ b/i2p2www/blog/2004/08/03/status.html @@ -15,7 +15,7 @@ hi y'all, lets get this status update out of the way With last week's 0.3.4 release, the new net is performing pretty well - irc connections are lasting for several hours at a time and -I2P site retrieval seems to be pretty reliable. Throughput is +I2P Site retrieval seems to be pretty reliable. Throughput is still generally low, though slightly improved (I used to see a consistent 4-5KBps, now I consistently see a 5-8KBps). oOo has posted up a pair of scripts summarizing the irc activity, diff --git a/i2p2www/blog/2004/08/10/status.html b/i2p2www/blog/2004/08/10/status.html index 3b0d3fd9..1524f5a5 100644 --- a/i2p2www/blog/2004/08/10/status.html +++ b/i2p2www/blog/2004/08/10/status.html @@ -14,7 +14,7 @@ Hey everyone, weekly update time Well, we've pushed out the 0.3.4.1 release the other day, and it has been doing pretty well. Connect times on irc have been consistently for multiple hours, and transfer rates are doing pretty good as well -(I pulled 25KBps from one I2P site the other day using 3 parallel +(I pulled 25KBps from one I2P Site the other day using 3 parallel streams). One really cool feature added in with the 0.3.4.1 release (that I diff --git a/i2p2www/blog/2004/08/24/status.html b/i2p2www/blog/2004/08/24/status.html index 23c9d9d8..ff51c0f2 100644 --- a/i2p2www/blog/2004/08/24/status.html +++ b/i2p2www/blog/2004/08/24/status.html @@ -23,7 +23,7 @@ pretty well since. There have been some problems with some newly introduced tunnel testing and peer selection code, but after some tweaking since the release, its pretty solid. I don't know if the irc server is on the new rev yet, so we generally have to rely on -testing with I2P sites and the http outproxies (squid.i2p and +testing with I2P Sites and the http outproxies (squid.i2p and www1.squid.i2p). Large (>5MB) file transfers in the 0.3.4.3 release are still not reliable enough, but in my testing, the modifications since then have improved things further. @@ -125,12 +125,12 @@ let the new jcpuid code choose the right one). * 2.3) i2paddresshelper oOo has put together a really cool helper to let people browse -I2P sites without updating their hosts.txt. It is committed to CVS +I2P Sites without updating their hosts.txt. It is committed to CVS and will be deployed in the next release, but people may want to consider updating links accordingly (cervantes has updated forum.i2p's [i2p] bbcode to support it with a "Try it [i2p]" link). -Basically you just make a link to the I2P site with whatever name you +Basically you just make a link to the I2P Site with whatever name you want, then tack on a special url parameter specifying the destination: @@ -138,7 +138,7 @@ destination: Behind the scenes, its pretty safe - you can't spoof some other address, and the name is *not* persisted in hosts.txt, but it will -let you see images / etc linked to on I2P sites that you wouldn't be +let you see images / etc linked to on I2P Sites that you wouldn't be able to with the old http://i2p/base64/ trick. If you want to always be able to use "wowthisiscool.i2p" to reach that site, you will still of course have to add the entry to your hosts.txt (until the diff --git a/i2p2www/blog/2004/09/14/status.html b/i2p2www/blog/2004/09/14/status.html index 28cc1085..1e599e6a 100644 --- a/i2p2www/blog/2004/09/14/status.html +++ b/i2p2www/blog/2004/09/14/status.html @@ -107,11 +107,11 @@ about implementing transparent DCC though, so perhaps the IRC side could be used for public chat and DCC for private file transfers or serverless chat. -General I2P site functionality is also important, and what we +General I2P Site functionality is also important, and what we have now is completely unsatisfactory. As DrWoo points out [9], there are significant anonymity risks with the current setup, and even though oOo has made some patches filtering some -headers, there is much more work to be done before I2P sites can +headers, there is much more work to be done before I2P Sites can be considered secure. There are a few different approaches to addressing this, all of which can work, but all of which require work. I do know that duck mentioned he had someone @@ -151,9 +151,9 @@ network load. It doesn't, however, offer the full richness of normal websites, but the 1.8 million active LiveJournal users don't seem to mind. -Beyond that, securing the I2P site architecture would be my +Beyond that, securing the I2P Site architecture would be my next preference, allowing browsers the safety they need and -letting people serve I2P sites 'out of the box'. +letting people serve I2P Sites 'out of the box'. File transfer and distributed data storage are also incredibly powerful, but they don't seem to be as community oriented as diff --git a/i2p2www/blog/2004/10/05/status.html b/i2p2www/blog/2004/10/05/status.html index 91b8d3c7..5a088c91 100644 --- a/i2p2www/blog/2004/10/05/status.html +++ b/i2p2www/blog/2004/10/05/status.html @@ -14,7 +14,7 @@ Hi y'all, its weekly update time After a pretty bumpy 0.4.1 release (and subsequent rapid 0.4.1.1 update), the net seems to be back to normal - 50-something peers -actrive at the moment, and both irc and I2P sites are reachable. Most +actrive at the moment, and both irc and I2P Sites are reachable. Most of the pain was caused by insufficient testing of the new transport outside lab conditions (e.g. sockets breaking at strange times, excessive delays, etc). Next time we need to make changes at that @@ -133,13 +133,13 @@ lib, we'll switch 'em. * 4) Bundled eepserver As was mentioned in the 0.4.1 release notes [3], we've bunded the -software and configuration necessary for running an I2P site out of -the box - you can simply drop a file in the ./I2P site/docroot/ +software and configuration necessary for running an I2P Site out of +the box - you can simply drop a file in the ./I2P Site/docroot/ directory and share the I2P destination found on the router console. A few people called me on my zeal for .war files though - most apps unfortunately need a little more work than simply dropping a file in -the ./I2P site/webapps/ dir. I've put together a brief tutorial [4] +the ./I2P Site/webapps/ dir. I've put together a brief tutorial [4] on running the blojsom [5] blogging engine, and you can see what that looks like on detonate's site [6]. diff --git a/i2p2www/blog/2004/10/19/status.html b/i2p2www/blog/2004/10/19/status.html index e8496418..9de08112 100644 --- a/i2p2www/blog/2004/10/19/status.html +++ b/i2p2www/blog/2004/10/19/status.html @@ -67,11 +67,11 @@ More news when there's more news. * 4) files.i2p -Ok, we've had a lot of new I2P sites lately, which is kickass. I just +Ok, we've had a lot of new I2P Sites lately, which is kickass. I just want to point out this one especially as its got a pretty neat feature for the rest of us. If you haven't been to files.i2p, its basically a google-like search engine, with a cache of the sites it -spiders (so you can both search and browse when the I2P site is +spiders (so you can both search and browse when the I2P Site is offline). v.cool. * 5) ??? diff --git a/i2p2www/blog/2004/10/26/status.html b/i2p2www/blog/2004/10/26/status.html index 2b660639..9a00ea21 100644 --- a/i2p2www/blog/2004/10/26/status.html +++ b/i2p2www/blog/2004/10/26/status.html @@ -12,7 +12,7 @@ Hi y'all, weekly update time * 1) Net status I don't want to jinx it, but for the last week the network has been -pretty much as before - fairly stable for irc, I2P sites loading +pretty much as before - fairly stable for irc, I2P Sites loading reliably, though large files still often require resuming. Basically nothing new to report, beyond the fact that there's nothing new to report. diff --git a/i2p2www/blog/2004/11/02/status.html b/i2p2www/blog/2004/11/02/status.html index b213a29d..a995feed 100644 --- a/i2p2www/blog/2004/11/02/status.html +++ b/i2p2www/blog/2004/11/02/status.html @@ -13,9 +13,9 @@ Hi y'all, time for the weekly update * 1) Net status -Pretty much as before - a steady number of peers, I2P sites fairly +Pretty much as before - a steady number of peers, I2P Sites fairly reachable, and irc for hours on end. You can get a peek at the -reachability of various I2P sites through a few different pages: +reachability of various I2P Sites through a few different pages: - http://gott.i2p/sites.html - http://www.baffled.i2p/links.html - http://thetower.i2p/pings.txt diff --git a/i2p2www/blog/2004/11/23/status.html b/i2p2www/blog/2004/11/23/status.html index 402556c3..320bb92f 100644 --- a/i2p2www/blog/2004/11/23/status.html +++ b/i2p2www/blog/2004/11/23/status.html @@ -78,7 +78,7 @@ old lib - I2PTunnel and SAM streams automatically use it, but from a packet perspective, it is *not* backwards compatible. This leaves us with an interesting dilemma - there is nothing within I2P requiring us to make 0.4.2 into a manditory upgrade, however people -who don't upgrade won't be able to use I2PTunnel - no I2P sites, no +who don't upgrade won't be able to use I2PTunnel - no I2P Sites, no IRC, no outproxy, no email. I don't want to alienate our long time users by forcing them to upgrade, but I also don't want to alienate them by having everything useful break ;) diff --git a/i2p2www/blog/2004/11/30/status.html b/i2p2www/blog/2004/11/30/status.html index c2b8b12f..60530b31 100644 --- a/i2p2www/blog/2004/11/30/status.html +++ b/i2p2www/blog/2004/11/30/status.html @@ -7,7 +7,7 @@ Hi y'all 1) 0.4.2 and 0.4.2.1 2) mail.i2p 3) i2p-bt -4) I2P sites +4) I2P Sites 5) ??? * 1) 0.4.2 and 0.4.2.1 @@ -36,10 +36,10 @@ some trouble with the i2p-bt port. Some of the problems have been identified found and fixed in the streaming lib, but further work is necessary to get it where we need it to be. -* 4) I2P sites +* 4) I2P Sites There has been some discussion over the months on the list, in the -channel, and on the forum about some problems with how I2P sites +channel, and on the forum about some problems with how I2P Sites and the eepproxy work - recently some have mentioned problems with how and what headers are filtered, others have brought up the dangers of poorly configured browsers, and there's also DrWoo's diff --git a/i2p2www/blog/2004/12/21/status.html b/i2p2www/blog/2004/12/21/status.html index 97e897d5..e3fe0f07 100644 --- a/i2p2www/blog/2004/12/21/status.html +++ b/i2p2www/blog/2004/12/21/status.html @@ -7,7 +7,7 @@ Ev'nin folks, time for our status update 1) 0.4.2.4 & 0.4.2.5 2) 0.5 strategy 3) naming -4) I2P site roundup +4) I2P Site roundup 5) ??? 1) 0.4.2.4 & 0.4.2.5 @@ -77,9 +77,9 @@ based manager at http: through the stats at http://orion.i2p/ and http://susi.i2p/susisworld.html -* 4) I2P site roundup +* 4) I2P Site roundup -There have been some notable developments on various I2P sites worth +There have been some notable developments on various I2P Sites worth mentioning: = http://frosk.i2p/ - I2PContent doc updates diff --git a/i2p2www/blog/2004/12/28/status.html b/i2p2www/blog/2004/12/28/status.html index 72d02a00..74d8878f 100644 --- a/i2p2www/blog/2004/12/28/status.html +++ b/i2p2www/blog/2004/12/28/status.html @@ -36,7 +36,7 @@ Nothing substantial to report here yet though. Very brief summary, I know, but most of the work over the last week has been on paper. As mentioned [1] on the list, Connelly is -running an intersection attack against some I2P sites, so once +running an intersection attack against some I2P Sites, so once there's some data to report on, I'm sure he'll give us the scoop. Anyone else have anything to bring up - if so, swing on by the meeting. diff --git a/i2p2www/blog/2005/02/15/status.html b/i2p2www/blog/2005/02/15/status.html index f7182a60..abb666d4 100644 --- a/i2p2www/blog/2005/02/15/status.html +++ b/i2p2www/blog/2005/02/15/status.html @@ -49,11 +49,11 @@ be a BACKWARDS INCOMPATIBLE RELEASE, to give you time to plan for updating, I'll fix a simple deadline of THIS FRIDAY as when 0.5 will be released. -As bla mentioned on irc, I2P site hosts may want to take their site +As bla mentioned on irc, I2P Site hosts may want to take their site down on Thursday or Friday and keep them down until Saturday when many users will have upgraded. This will help reduce the effect of an intersection attack (e.g. if 90% of the network has migrated to -0.5 and you're still on 0.4, if someone reaches your I2P site, they +0.5 and you're still on 0.4, if someone reaches your I2P Site, they know you're one of the 10% of routers left on the network). I could start to get into whats been updated in 0.5, but I'd end up diff --git a/i2p2www/blog/2005/03/01/status.html b/i2p2www/blog/2005/03/01/status.html index eceb4259..2c41b613 100644 --- a/i2p2www/blog/2005/03/01/status.html +++ b/i2p2www/blog/2005/03/01/status.html @@ -62,8 +62,8 @@ smeghead during the meeting? Legion has also created a fork off the i2p-bt rev, merged in some other code, patched up some things, and has a windows binary -available on his I2P site. The announcement [2] seems to suggest -that source may be made available, though its not up on the I2P site +available on his I2P Site. The announcement [2] seems to suggest +that source may be made available, though its not up on the I2P Site at the moment. The i2p devs haven't audited (or even seen) the code to that client, so those who need anonymity may want to get and review a copy of the code first. diff --git a/i2p2www/blog/2005/04/05/status.html b/i2p2www/blog/2005/04/05/status.html index fb144f2c..0644d929 100644 --- a/i2p2www/blog/2005/04/05/status.html +++ b/i2p2www/blog/2005/04/05/status.html @@ -15,7 +15,7 @@ Last week's 0.5.0.5 release has had its ups and downs - the major change to address some attacks in the netDb seems to work as expected, but has exposed some long overlooked bugs in the netDb's operation. This has caused some substantial reliability issues, -especially for I2P sites. The bugs have however been identified and +especially for I2P Sites. The bugs have however been identified and addressed in CVS, and those fixes among a few others will be pushed out as a 0.5.0.6 release within the next day. diff --git a/i2p2www/blog/2005/04/19/status.html b/i2p2www/blog/2005/04/19/status.html index 226c074b..ac2b825f 100644 --- a/i2p2www/blog/2005/04/19/status.html +++ b/i2p2www/blog/2005/04/19/status.html @@ -13,7 +13,7 @@ Hi y'all, its that time of the week again, * 1) Net status Over the nearly two weeks since 0.5.0.6 came out, things have been -mostly positive, though service providers (I2P sites, ircd, etc) have +mostly positive, though service providers (I2P Sites, ircd, etc) have been running into some bugs as of late. While clients are in good shape, over time a server may run into situation where failing tunnels can trigger some excessive throttling code, preventing diff --git a/i2p2www/blog/2005/05/03/status.html b/i2p2www/blog/2005/05/03/status.html index fc4ebdc6..c7620c4f 100644 --- a/i2p2www/blog/2005/05/03/status.html +++ b/i2p2www/blog/2005/05/03/status.html @@ -53,7 +53,7 @@ there's a lot of work to do before its ready for joe sixpack, earlier this evening I was able to fire it up, browse sirup's shared files, grab some data, and use its *cough* "instant" chat interface. -There's lots more info up on sirup's I2P site [2], and help testing +There's lots more info up on sirup's I2P Site [2], and help testing by people already in the i2p community would be great (though please, until sirup blesses it as a public release, and i2p is at least 0.6 if not 1.0, lets keep it within the i2p community). I diff --git a/i2p2www/blog/2005/08/23/status.html b/i2p2www/blog/2005/08/23/status.html index 314ff96e..41ddeafb 100644 --- a/i2p2www/blog/2005/08/23/status.html +++ b/i2p2www/blog/2005/08/23/status.html @@ -69,7 +69,7 @@ Can I hear a "w00t"? As mentioned on the list and in the channel, we've got a new client app for secure and authenticated blogging / content -distribution. With Syndie, the "is your I2P site up" question goes +distribution. With Syndie, the "is your I2P Site up" question goes away, as you can read the content even when the site is down, but Syndie avoids all the ugly issues inherent in content distribution networks by focusing on the frontend. Anyway, its very much a work diff --git a/i2p2www/blog/2005/09/06/status.html b/i2p2www/blog/2005/09/06/status.html index eb2a2a96..f2920407 100644 --- a/i2p2www/blog/2005/09/06/status.html +++ b/i2p2www/blog/2005/09/06/status.html @@ -18,7 +18,7 @@ some room for improvement, but it seems that the new netDb is performing as designed. We've even had the fallback tested out - when the floodfill peers are unreachable, routers fall back on the kademlia netDb, and the other day when that scenario occurred, irc -and I2P site reliability was not substantially diminished. +and I2P Site reliability was not substantially diminished. I did receive a question regarding how the new netDb works, and have posted up the answer [1] on my blog [2]. As always, if anyone has @@ -51,7 +51,7 @@ Susi has whipped up yet another web application for us - susidns [3]. This serves as a simple interface for managing the addressbook app - its entries, subscriptions, etc. Its looking pretty good, so hopefully we'll be able to ship it as one of the default apps soon, -but for now, its a snap to grab from her I2P site, save it to your +but for now, its a snap to grab from her I2P Site, save it to your webapps directory, restart your router, and you're good to go. [3] http://susi.i2p/?page_id=13 diff --git a/i2p2www/blog/2005/11/22/status.html b/i2p2www/blog/2005/11/22/status.html index 52bf7403..7fb34852 100644 --- a/i2p2www/blog/2005/11/22/status.html +++ b/i2p2www/blog/2005/11/22/status.html @@ -33,7 +33,7 @@ peer review for I2P's anonymity [3]. The more I think about it the more I like it, though I think Raccoon23 is probably right in that we want to wait until 0.9/1.0-beta before running these types of contests. We could even do different contests for different -applications on top of I2P - one for I2P sites, one for irc users, +applications on top of I2P - one for I2P Sites, one for irc users, one for I2Phex users, one for anon-BT users, one for Syndie users, etc. This, meshed with the suggestion of trying with both passive 'foxes' and fairly advanced 'foxes' should give us the opportunity diff --git a/i2p2www/blog/2006/01/03/status.html b/i2p2www/blog/2006/01/03/status.html index 351f11d7..4acb0e59 100644 --- a/i2p2www/blog/2006/01/03/status.html +++ b/i2p2www/blog/2006/01/03/status.html @@ -71,7 +71,7 @@ Saying 2005 broke a lot of ground is a bit of an understatement - we've improved I2P numerous ways in the 25 releases last year, grew the network 5-fold, deployed several new client applications (Syndie, I2Phex, I2PSnark, I2PRufus), migrated to postman's and -cervantes' new irc2p IRC network, and saw some useful I2P sites +cervantes' new irc2p IRC network, and saw some useful I2P Sites bloom (such as zzz's stats.i2p, orion's orion.i2p, and tino's proxy and monitoring services, just to name a few). The community has also matured a bit more, in no small part thanks to the support diff --git a/i2p2www/blog/2006/01/10/status.html b/i2p2www/blog/2006/01/10/status.html index bfa0726f..6620ae33 100644 --- a/i2p2www/blog/2006/01/10/status.html +++ b/i2p2www/blog/2006/01/10/status.html @@ -95,7 +95,7 @@ long requested feature - support for persistent HTTP connections, allowing you to send multiple HTTP requests over a single stream, receiving multiple replies in return. I think someone first asked for this two years ago or so, and it could help with some types of -I2P site or outproxying a bunch. I know the work isn't done yet, but +I2P Site or outproxying a bunch. I know the work isn't done yet, but its coming along. Hopefully zzz can give us a status update during the meeting. diff --git a/i2p2www/blog/2006/08/01/status.html b/i2p2www/blog/2006/08/01/status.html index c0feb2df..c0cfc78b 100644 --- a/i2p2www/blog/2006/08/01/status.html +++ b/i2p2www/blog/2006/08/01/status.html @@ -10,7 +10,7 @@ large I2PSnark transfers completing, and with quite sustantial transfer rates achieved on individual routers - I've seen 650KBytes/sec and 17,000 participating tunnels without any fireworks. Routers on the low end of the spectrum seem to be -doing fine too, browsing I2P sites and irc with 2 hop tunnels +doing fine too, browsing I2P Sites and irc with 2 hop tunnels using under 1KByte/sec average. It isn't all roses for everyone though, but we're working through @@ -26,11 +26,11 @@ we are not reverting to TCP-only. * I2P Site reachability -Remember folks that I2P sites are reachable only when the person +Remember folks that I2P Sites are reachable only when the person who is running it has it up - if they're down, there's nothing you can do to reach it ;) Unfortunately, for the past few days, orion.i2p hasn't been reachable, but the net is definitely still -working - perhaps swing by inproxy.tino.i2p or I2P sites.i2p for +working - perhaps swing by inproxy.tino.i2p or I2P Sites.i2p for your network survey needs. Anyway, there's lots more going on, but it'd be a bit premature diff --git a/i2p2www/blog/2006/10/03/status.html b/i2p2www/blog/2006/10/03/status.html index cf38f896..798d2c61 100644 --- a/i2p2www/blog/2006/10/03/status.html +++ b/i2p2www/blog/2006/10/03/status.html @@ -133,7 +133,7 @@ being worked on. First, from irc (and the not-yet-out-there FAQ): <bar> a question i've been pondering is, who is later going to have balls big enough to host syndie production servers/archives? - <bar> aren't those going to be as easy to track down as the I2P sites + <bar> aren't those going to be as easy to track down as the I2P Sites are today? <jrandom> public syndie archives do not have the ability to *read* the content posted to forums, unless the forums publish diff --git a/i2p2www/blog/2008/02/10/release-0.6.1.31.html b/i2p2www/blog/2008/02/10/release-0.6.1.31.html index ed659092..36bdc4c2 100644 --- a/i2p2www/blog/2008/02/10/release-0.6.1.31.html +++ b/i2p2www/blog/2008/02/10/release-0.6.1.31.html @@ -10,7 +10,7 @@ independent of jrandom and *.i2p.net servers. Our new primary mirror is www.i2p2.de, accessible in I2P at www.i2p2.i2p. -Automatic updates will hosted on several I2P sites, +Automatic updates will hosted on several I2P Sites, signed by Complication, for which purpose 0.6.1.31 includes two new release verification keys. diff --git a/i2p2www/blog/2009/07/31/release-0.7.6.html b/i2p2www/blog/2009/07/31/release-0.7.6.html index 381ed417..4f43af35 100644 --- a/i2p2www/blog/2009/07/31/release-0.7.6.html +++ b/i2p2www/blog/2009/07/31/release-0.7.6.html @@ -86,7 +86,7 @@ Proxy Installer, Split Directories, Distro-Friendly Organization diff --git a/i2p2www/blog/2010/03/15/release-0.7.12.html b/i2p2www/blog/2010/03/15/release-0.7.12.html index fd9089c4..46388b58 100644 --- a/i2p2www/blog/2010/03/15/release-0.7.12.html +++ b/i2p2www/blog/2010/03/15/release-0.7.12.html @@ -4,7 +4,7 @@ themes, translations, or standalone programs. Some plugins are already available for testing. We are hopeful this support will enable rapid development of innovative i2p applications.

-The release fixes the blank-page bug when an I2P site is not reachable, +The release fixes the blank-page bug when an I2P Site is not reachable, and also improves handling of clock skews and IP changes. It adds support for a new, smaller tunnel build message, that will be tested in this release and enabled in the next release. diff --git a/i2p2www/blog/2011/03/02/release-0.8.4.html b/i2p2www/blog/2011/03/02/release-0.8.4.html index 7bc983bb..d2076ddc 100644 --- a/i2p2www/blog/2011/03/02/release-0.8.4.html +++ b/i2p2www/blog/2011/03/02/release-0.8.4.html @@ -19,7 +19,7 @@ Please volunteer on IRC #i2p-dev.

* Fix a severe memory leak in router I2CP session management that caused router crashes for people running the Robert bittorrent client -
* Fix a bug from 0.8.2 that filtered cookies in the HTTP Server tunnel, causing authentication problems for some I2P sites +
* Fix a bug from 0.8.2 that filtered cookies in the HTTP Server tunnel, causing authentication problems for some I2P Sites
* Several fixes for rare NPEs

I2PSnark

diff --git a/i2p2www/pages/downloads/debian.html b/i2p2www/pages/downloads/debian.html index 0b635fc5..f9470b4a 100644 --- a/i2p2www/pages/downloads/debian.html +++ b/i2p2www/pages/downloads/debian.html @@ -238,7 +238,7 @@ as the default settings of 96 KB/s down / 40 KB/s up are fairly conservative. {%- endtrans %}

{% trans browserconfig=site_url('about/browser-config') -%} -If you want to reach I2P sites via your browser, have a look on the browser proxy setup page for an easy howto. +If you want to reach I2P Sites via your browser, have a look on the browser proxy setup page for an easy howto. {%- endtrans %}

{% endblock %} diff --git a/i2p2www/pages/downloads/firefox.html b/i2p2www/pages/downloads/firefox.html index 56d22d6a..0757c00b 100644 --- a/i2p2www/pages/downloads/firefox.html +++ b/i2p2www/pages/downloads/firefox.html @@ -4,7 +4,7 @@ {% block content %}

{{ _('I2P Firefox Browser Profile') }}

{% trans -%} -Now that you have joined the I2P network, you will want to see I2P sites and and +Now that you have joined the I2P network, you will want to see I2P Sites and and other content that is hosted on the network. The Firefox browser is pre-configured to allow you to access the content available on the network. It also keeps your I2P search activity separate from your internet search activity. diff --git a/i2p2www/pages/downloads/list.html b/i2p2www/pages/downloads/list.html index f75b506a..6acde8a1 100644 --- a/i2p2www/pages/downloads/list.html +++ b/i2p2www/pages/downloads/list.html @@ -65,7 +65,7 @@ Windows: Java 8 is recommended. Java 9 or higher may not work.

When you download the I2P software bundle, you get everything you need to connect and start participating in the I2P network and community. It even includes basic -applications for every user, like e-mail, bittorrent, and a basic I2P site for +applications for every user, like e-mail, bittorrent, and a basic I2P Site for you to personalize and share.

diff --git a/i2p2www/pages/downloads/post-install.html b/i2p2www/pages/downloads/post-install.html index 884c3521..37f0e806 100644 --- a/i2p2www/pages/downloads/post-install.html +++ b/i2p2www/pages/downloads/post-install.html @@ -32,5 +32,5 @@ as the default settings of 96 KBps down / 40 KBps up are fairly slow. {%- endtrans %}

{% trans browserconfig=site_url('about/browser-config') -%} -If you want to reach I2P sites via your browser, have a look on the browser proxy setup page for an easy howto. +If you want to reach I2P Sites via your browser, have a look on the browser proxy setup page for an easy howto. {%- endtrans %}

diff --git a/i2p2www/pages/downloads/windows.html b/i2p2www/pages/downloads/windows.html index 7c1a78bf..9a5ce674 100644 --- a/i2p2www/pages/downloads/windows.html +++ b/i2p2www/pages/downloads/windows.html @@ -169,7 +169,7 @@ configuration wizard.{%- endtrans %}

{% trans -%}If you want to re-run the welcome wizard after completing it, you can visit the page on{%- endtrans %} your router console.

-

{% trans -%}That's it! You're now ready to use I2P. You can browse I2P sites, download files, host services, +

{% trans -%}That's it! You're now ready to use I2P. You can browse I2P Sites, download files, host services, e-mail and chat anonymously. Visit the router console homepage to get started.{%- endtrans %}

diff --git a/i2p2www/pages/site/browser/intro.html b/i2p2www/pages/site/browser/intro.html index aa59dff7..f624c6f1 100644 --- a/i2p2www/pages/site/browser/intro.html +++ b/i2p2www/pages/site/browser/intro.html @@ -28,11 +28,11 @@

{% trans bname=browser_name(), bsuff=browser_postname() %}{{ bname }} {{ bsuff }} is an easy-to-use bundle -that provides a streamlined way to use I2P applications and to browse I2P sites. +that provides a streamlined way to use I2P applications and to browse I2P Sites. Although it can provide access to the regular internet via an outproxy, it also integrates secure decentralized browsing, file sharing, and e-mail.{% endtrans %}

- +

diff --git a/i2p2www/pages/site/docs/api/i2ptunnel.html b/i2p2www/pages/site/docs/api/i2ptunnel.html index e55e4fb1..37330214 100644 --- a/i2p2www/pages/site/docs/api/i2ptunnel.html +++ b/i2p2www/pages/site/docs/api/i2ptunnel.html @@ -24,8 +24,8 @@ A web interface for I2PTunnel management is avaliable on I2P Webserver - A tunnel pointed to a Jetty webserver run on localhost:7658 for convenient and quick hosting on I2P.
The document root is:{% endtrans %} -
Unix - $HOME/.i2p/I2P site/docroot -
Windows - %LOCALAPPDATA%\I2P\I2P site\docroot, which expands to: C:\Users\**username**\AppData\Local\I2P\I2P site\docroot +
Unix - $HOME/.i2p/I2P Site/docroot +
Windows - %LOCALAPPDATA%\I2P\I2P Site\docroot, which expands to: C:\Users\**username**\AppData\Local\I2P\I2P Site\docroot

{% trans %}Client tunnels{% endtrans %}

@@ -177,7 +177,7 @@ Accept-encoding: x-i2p-gzip, replies with Content-encoding: x-i2p-gzip in such a

{% trans -%} Functions as both a I2PTunnel HTTP Server, and a I2PTunnel HTTP client with no outproxying capabilities. An example application would be a web application that does client-type -requests, or loopback-testing an I2P site as a diagnostic tool. +requests, or loopback-testing an I2P Site as a diagnostic tool. {%- endtrans %}

IRC Server

diff --git a/i2p2www/pages/site/docs/applications/embedding.html b/i2p2www/pages/site/docs/applications/embedding.html index 869b6676..aa667e2b 100644 --- a/i2p2www/pages/site/docs/applications/embedding.html +++ b/i2p2www/pages/site/docs/applications/embedding.html @@ -309,7 +309,7 @@ It could cause great harm both to our network and our reputation.

{% trans %}Join Us{% endtrans %}

{% trans -%} -This may be obvious, but join the community. Run I2P 24/7. Start an I2P site about your project. +This may be obvious, but join the community. Run I2P 24/7. Start an I2P Site about your project. Hang out in IRC #i2p-dev. Post on the forums. Spread the word. We can help get you users, testers, translators, or even coders. {%- endtrans %}

diff --git a/i2p2www/pages/site/docs/discussions/naming.html b/i2p2www/pages/site/docs/discussions/naming.html index adcd2a1a..990ae24e 100644 --- a/i2p2www/pages/site/docs/discussions/naming.html +++ b/i2p2www/pages/site/docs/discussions/naming.html @@ -196,7 +196,7 @@ the issues of conflicts and hijacking, however.

{% trans -%} Awkward, not real-time: It's a patchwork of hosts.txt providers, key-add web form providers, jump service providers, -I2P site status reporters. +I2P Site status reporters. Jump servers and subscriptions are a pain, it should just work like DNS. {%- endtrans %}

{% trans -%} diff --git a/i2p2www/pages/site/docs/discussions/netdb.html b/i2p2www/pages/site/docs/discussions/netdb.html index 646cfba1..64345e4b 100644 --- a/i2p2www/pages/site/docs/discussions/netdb.html +++ b/i2p2www/pages/site/docs/discussions/netdb.html @@ -161,7 +161,7 @@ the netDb. I2P's netDb is very different from traditional load bearing DHTs - it only carries network metadata, not any actual payload, which is why even a netDb using a floodfill algorithm will be able to sustain an arbitrary amount of -I2P site/IRC/bt/mail/syndie/etc data. We can even do some optimizations as I2P +I2P Site/IRC/bt/mail/syndie/etc data. We can even do some optimizations as I2P grows to distribute that load a bit further (perhaps passing bloom filters between the netDb participants to see what they need to share), but it seems we can get by with a much simpler solution for now. @@ -299,7 +299,7 @@ The code now avoids peers that are shitlisted, failing, or not heard from in half an hour, if possible.

-One benefit is faster first contact to an I2P site (i.e. when you had to fetch +One benefit is faster first contact to an I2P Site (i.e. when you had to fetch the leaseset first). The lookup timeout is 10s, so if you don't start out by asking a peer that is down, you can save 10s. diff --git a/i2p2www/pages/site/docs/how/intro.html b/i2p2www/pages/site/docs/how/intro.html index 27a21aac..aabaf0a2 100644 --- a/i2p2www/pages/site/docs/how/intro.html +++ b/i2p2www/pages/site/docs/how/intro.html @@ -25,7 +25,7 @@ even taken over to attempt more malicious attacks.

{% trans i2ptunnel=site_url('docs/api/i2ptunnel') -%} The network itself is message oriented - it is essentially a secure and anonymous IP layer, where messages are addressed to cryptographic keys (Destinations) and can be significantly larger than IP -packets. Some example uses of the network include "I2P sites" (webservers hosting normal web +packets. Some example uses of the network include "I2P Sites" (webservers hosting normal web applications within I2P), a BitTorrent client ("I2PSnark"), or a distributed data store. With the help of the I2PTunnel application, we are able to stream traditional TCP/IP applications over I2P, such as SSH, IRC, a squid proxy, and even streaming audio. Most people diff --git a/i2p2www/pages/site/docs/how/network-database.html b/i2p2www/pages/site/docs/how/network-database.html index 649eda07..581c355d 100644 --- a/i2p2www/pages/site/docs/how/network-database.html +++ b/i2p2www/pages/site/docs/how/network-database.html @@ -836,7 +836,7 @@ by creating a small number (8-15) of floodfill routers clustered closely in the and distribute the RouterInfos for these routers widely. Then, all lookups and stores for a key in that keyspace would be directed to one of the attacker's routers. -If successful, this could be an effective DOS attack on a particular I2P site, for example. +If successful, this could be an effective DOS attack on a particular I2P Site, for example. {%- endtrans %}

{% trans -%} diff --git a/i2p2www/pages/site/docs/how/tech-intro.html b/i2p2www/pages/site/docs/how/tech-intro.html index f1ae9cd2..2fcf7cde 100644 --- a/i2p2www/pages/site/docs/how/tech-intro.html +++ b/i2p2www/pages/site/docs/how/tech-intro.html @@ -100,7 +100,7 @@ usually a secret. What is hidden is information on what the user is doing, if anything at all, as well as what router a particular destination is connected to. End users will typically have several local destinations on their router - for instance, one proxying in to IRC servers, another supporting the user's -anonymous webserver ("I2P site"), another for an I2Phex instance, another for +anonymous webserver ("I2P Site"), another for an I2Phex instance, another for torrents, etc. {%- endtrans %}

@@ -904,7 +904,7 @@ system. It lets you create information, share it with others, and read posts from those you're interested in, all while taking into consideration your needs for security and anonymity. Rather than building its own content distribution network, Syndie is designed to run on top of existing networks, syndicating -content through I2P sites, Tor hidden services, Freenet freesites, normal websites, +content through I2P Sites, Tor hidden services, Freenet freesites, normal websites, usenet newsgroups, email lists, RSS feeds, etc. Data published with Syndie is done so as to offer pseudonymous authentication to anyone reading or archiving it. @@ -945,7 +945,7 @@ be sufficient for some users.

{% trans -%} I2PTunnel enables most of the applications in use. An "httpserver" pointing -at a webserver lets anyone run their own anonymous website (or "I2P site") +at a webserver lets anyone run their own anonymous website (or "I2P Site") - a webserver is bundled with I2P for this purpose, but any webserver can be used. Anyone may run a "client" pointing at one of the anonymously hosted IRC servers, each of which are running a "server" pointing at their local @@ -963,7 +963,7 @@ proxies to access the "server" instances pointing at an NNTP server.

{% trans -%} i2p-bt is a port of the mainline python BitTorrent client to run both the tracker and peer communication over I2P. Tracker requests are forwarded through -the eepproxy to I2P sites specified in the torrent file while tracker responses +the eepproxy to I2P Sites specified in the torrent file while tracker responses refer to peers by their destination explicitly, allowing i2p-bt to open up a streaming lib connection to query them for blocks. @@ -1041,7 +1041,7 @@ SMTP and POP3 servers - both the outproxies and inproxies communicate with the mail.i2p SMTP and POP3 servers through I2P itself, so compromising those non-anonymous locations does not give access to the mail accounts or activity patterns of the user. At the moment the developers work on a decentralized -mailsystem, called "v2mail". More information can be found on the I2P site +mailsystem, called "v2mail". More information can be found on the I2P Site {{ postman }}. {%- endtrans %}

diff --git a/i2p2www/pages/site/docs/how/threat-model.html b/i2p2www/pages/site/docs/how/threat-model.html index d3984b6d..aa894e5b 100644 --- a/i2p2www/pages/site/docs/how/threat-model.html +++ b/i2p2www/pages/site/docs/how/threat-model.html @@ -231,7 +231,7 @@ However, the attack is still possible, for example by an observer at a large ISP or an Internet exchange point. Those who want to defend against it would want to take appropriate countermeasures, such as -setting low bandwidth limits, and using unpublished or encrypted leasesets for I2P sites. +setting low bandwidth limits, and using unpublished or encrypted leasesets for I2P Sites. Other countermeasures, such as nontrivial delays and restricted routes, are not currently implemented. {%- endtrans %}

@@ -323,7 +323,7 @@ Limits on the number of tunnels routed through a single peer Prevention of peers from the same /16 IP range from being members of a single tunnel {%- endtrans %}
  • {% trans -%} -For I2P sites or other hosted services, we support +For I2P Sites or other hosted services, we support simultaneous hosting on multiple routers, or multihoming {%- endtrans %}
    • diff --git a/i2p2www/pages/site/docs/naming.html b/i2p2www/pages/site/docs/naming.html index 9347bb42..a1b8df31 100644 --- a/i2p2www/pages/site/docs/naming.html +++ b/i2p2www/pages/site/docs/naming.html @@ -165,7 +165,7 @@ For more information see the alter

    {% trans -%} The HTTP proxy does a lookup via the router for all hostnames ending in '.i2p'. Otherwise, it forwards the request to a configured HTTP outproxy. -Thus, in practice, all HTTP (I2P site) hostnames must end in the pseudo-Top Level Domain '.i2p'. +Thus, in practice, all HTTP (I2P Site) hostnames must end in the pseudo-Top Level Domain '.i2p'. {%- endtrans %}

    {% trans i2ptld='https://datatracker.ietf.org/doc/draft-grothoff-iesg-special-use-p2p-names/', @@ -337,7 +337,7 @@ See the specification for details.

    {% trans %}Outgoing Subscriptions{% endtrans %}

    {% trans -%} Addressbook will publish the merged hosts.txt to a location -(traditionally hosts.txt in the local I2P site's home directory) to be accessed by others +(traditionally hosts.txt in the local I2P Site's home directory) to be accessed by others for their subscriptions. This step is optional and is disabled by default. {%- endtrans %}

    diff --git a/i2p2www/pages/site/docs/tunnels/unidirectional.html b/i2p2www/pages/site/docs/tunnels/unidirectional.html index ac252b65..9096bdea 100644 --- a/i2p2www/pages/site/docs/tunnels/unidirectional.html +++ b/i2p2www/pages/site/docs/tunnels/unidirectional.html @@ -82,7 +82,7 @@ The paper's main point is that deanonymizations on unidirectional tunnels take a longer time, which is an advantage, but that an attacker can be more certain in the unidirectional case. Therefore, the paper claims it isn't an advantage at all, but a disadvantage, at least -with long-living I2P sites. +with long-living I2P Sites. {%- endtrans %}

    {% trans -%} @@ -97,7 +97,7 @@ This conclusion is based on an arbitrary certainty vs. time weighting (tradeoff) that may not be applicable in all cases. For example, somebody could make a list of possible IPs then issue subpoenas to each. Or the attacker could DDoS each in turn and via a simple -intersection attack see if the I2P site goes down or is slowed down. So close +intersection attack see if the I2P Site goes down or is slowed down. So close may be good enough, or time may be more important. {%- endtrans %}

    diff --git a/i2p2www/pages/site/faq.html b/i2p2www/pages/site/faq.html index 1f9e1a2a..41a27759 100644 --- a/i2p2www/pages/site/faq.html +++ b/i2p2www/pages/site/faq.html @@ -7,20 +7,20 @@
  • {% trans %}What systems will I2P run on?{% endtrans %}
  • {% trans %}Is installing Java required to use I2P?{% endtrans %}
    • -
  • {% trans %}Whats an "I2P site" and how do I configure my browser so I can use them?{% endtrans %}
    • +
  • {% trans %}Whats an "I2P Site" and how do I configure my browser so I can use them?{% endtrans %}
  • {% trans %}What do the Active x/y numbers mean in the router console?{% endtrans %}
  • {% trans %}My router has very few active peers, is this OK?{% endtrans %}
  • {% trans %}I am opposed to certain types of content. How do I keep from distributing, storing, or accessing them?{% endtrans %}
  • {% trans %}Is it possible to block I2P?{% endtrans %}
  • {% trans %}In wrapper.log I see an error stating Protocol family unavailable when I2P is loading{% endtrans %}
    • -
  • {% trans %}Most of the I2P sites within I2P are down?{% endtrans %}
    • +
  • {% trans %}Most of the I2P Sites within I2P are down?{% endtrans %}
  • {% trans %}Why is I2P listening for connections on port 32000?{% endtrans %}

  • {{ _('Configuration') }}

  • {% trans %}How do I configure my browser?{% endtrans %}
  • {% trans %}How do I connect to IRC within I2P?{% endtrans %}
    • -
  • {% trans %}How do I set up my own I2P site?{% endtrans %}
    • +
  • {% trans %}How do I set up my own I2P Site?{% endtrans %}
  • {% trans %}If I host a website at I2P at home, containing only HTML and CSS, is it dangerous?{% endtrans %}
  • {% trans %}How Does I2P find ".i2p" websites?{% endtrans %}
  • {% trans %}How do I add to the AddressBook?{% endtrans %}
    • @@ -97,11 +97,11 @@ While the main I2P client implementation requires Java, there are several alternative clients which don't require Java. {%- endtrans %}

    -

    +

    {% trans %}What is an "I2P Site?"{% endtrans %}

    {% trans -%} -Formerly called an eepSite, an I2P site is a website that is hosted anonymously, a hidden service which is accessible through your web browser. +Formerly called an eepSite, an I2P Site is a website that is hosted anonymously, a hidden service which is accessible through your web browser. It can be accessed by setting your web browser's HTTP proxy to use the I2P web proxy (typically it listens on localhost port 4444), and browsing to the site. {%- endtrans %}

    @@ -186,13 +186,13 @@ click Shutdown, wait 11 minutes, then start I2P. {%- endtrans %}

    -{% trans %}Most of the I2P sites within I2P are down?{% endtrans %} +{% trans %}Most of the I2P Sites within I2P are down?{% endtrans %}

    {% trans eepstatus='http://'+i2pconv('identiguy.i2p') -%} -If you consider every I2P site that has ever been created, yes, most of them are down. -People and I2P sites come and go. -A good way to get started in I2P is check out a list of I2P sites that are currently up. -{{ eepstatus }} tracks active I2P sites. +If you consider every I2P Site that has ever been created, yes, most of them are down. +People and I2P Sites come and go. +A good way to get started in I2P is check out a list of I2P Sites that are currently up. +{{ eepstatus }} tracks active I2P Sites. {%- endtrans %}

    @@ -232,8 +232,8 @@ Weechat users can use the following command to add a new network: -

    -{% trans %}How do I set up my own I2P site?{% endtrans %} +

    +{% trans %}How do I set up my own I2P Site?{% endtrans %}

    {% trans -%} Click on the Website link at the top of your router console for instructions. @@ -251,7 +251,7 @@ yourself from a real threat will take real consideration in any case.{% endtrans

    The I2P Addressbook application maps human-readable names to long-term destinations, associated with services, making it more like a hosts file or a contact list than a network database or a DNS service. It's also local-first there is no recognized global namespace, you decide what any given .i2p domain maps to in the end. The middle-ground is something called a "Jump Service" which provides a human-readable name by redirecting you to a page where you will be asked "Do you give the I2P router permission to call $SITE_CRYPTO_KEY the name $SITE_NAME.i2p" or something to that effect. Once it's in your addressbook, you can generate your own jump URL's to help share the site with others.

    {% trans %}How do I add addresses to the Addressbook? {% endtrans %}

    -

    {% trans %}You cannot add an address without knowing at least the base32 or base64 of the site you want to visit. The "hostname" which is human-readable is only an alias for the cryptographic address, which corresponds to the base32 or base64. Without the cryptographic address, there is no way to access an I2P site, this is by design. Distributing the address to people who do not know it yet is usually the responsibility of the Jump service provider. Visiting an I2P site which is unknown will trigger the use of a Jump service. stats.i2p is the most reliable Jump service.{% endtrans %}

    +

    {% trans %}You cannot add an address without knowing at least the base32 or base64 of the site you want to visit. The "hostname" which is human-readable is only an alias for the cryptographic address, which corresponds to the base32 or base64. Without the cryptographic address, there is no way to access an I2P Site, this is by design. Distributing the address to people who do not know it yet is usually the responsibility of the Jump service provider. Visiting an I2P Site which is unknown will trigger the use of a Jump service. stats.i2p is the most reliable Jump service.{% endtrans %}

    {% trans %}If you're hosting a site via i2ptunnel, then it won't have a registration with a jump service yet. To give it a URL locally, then visit the configuration page and click the button that says "Add to Local Addressbook." Then go to http://127.0.0.1:7657/dns to look up the addresshelper URL and share it.{% endtrans %}

    @@ -440,7 +440,7 @@ These are described in detail below. 7658 - Your I2P site + Your I2P Site {% trans -%}May be disabled in the clients.config file. diff --git a/i2p2www/pages/site/get-involved/develop/applications.html b/i2p2www/pages/site/get-involved/develop/applications.html index f23447ac..d130cd65 100644 --- a/i2p2www/pages/site/get-involved/develop/applications.html +++ b/i2p2www/pages/site/get-involved/develop/applications.html @@ -207,7 +207,7 @@ to and from I2P. At this point in time it lacks UDP support, but UDP support is planned in the near future. BOB also contains several tools, such as destination key generation, and verification that an address conforms to I2P specifications. Up to date info and applications that use BOB can be -found at this I2P site. +found at this I2P Site. {%- endtrans %}

    diff --git a/i2p2www/pages/site/get-involved/develop/signed-keys.html b/i2p2www/pages/site/get-involved/develop/signed-keys.html index 68a751ec..fe5fddbd 100644 --- a/i2p2www/pages/site/get-involved/develop/signed-keys.html +++ b/i2p2www/pages/site/get-involved/develop/signed-keys.html @@ -15,7 +15,7 @@ signature for his key.

    {{ _('Monotone keys for zzz') }}

    {% trans -%} -Tip: To find zzz's GPG key, on his I2P site locate the key `0xA76E0BED`, with +Tip: To find zzz's GPG key, on his I2P Site locate the key `0xA76E0BED`, with the name `zzz@mail.i2p` and the fingerprint `4456 EBBE C805 63FE 57E6 B310 4155 76BA A76E 0BED`. {%- endtrans %}

    @@ -79,7 +79,7 @@ the name `zzz@mail.i2p` and the fingerprint `4456 EBBE C805 63FE 57E6 B310 4155

    {{ _('Monotone keys for Complication') }}

    {% trans -%} -Tip: To find Complication's GPG key, on his I2P site locate the key +Tip: To find Complication's GPG key, on his I2P Site locate the key `0x79FCCE33`, with the name `complication@mail.i2p` and the fingerprint `73CF 2862 87A7 E7D2 19FF DB66 FA1D FC6B 79FC CE33`. {%- endtrans %}

    diff --git a/i2p2www/pages/site/get-involved/guides/new-translators.html b/i2p2www/pages/site/get-involved/guides/new-translators.html index d27e16a2..0e8baf44 100644 --- a/i2p2www/pages/site/get-involved/guides/new-translators.html +++ b/i2p2www/pages/site/get-involved/guides/new-translators.html @@ -120,7 +120,7 @@ There are about 15 files in the i2p.i2p branch that needs translation:
  • apps/routerconsole/jsp/help_xx.jsp
  • - installer/resources/I2P site.help/help/index_xx.html
    • + installer/resources/I2P Site.help/help/index_xx.html
  • apps/i2ptunnel/locale/messages_xx.po
  • diff --git a/i2p2www/pages/site/get-involved/guides/reseed.html b/i2p2www/pages/site/get-involved/guides/reseed.html index c34d9b0d..9c7a4a9e 100644 --- a/i2p2www/pages/site/get-involved/guides/reseed.html +++ b/i2p2www/pages/site/get-involved/guides/reseed.html @@ -191,7 +191,7 @@ Optional:

    This How-to is tested with Ubuntu/Debian as well as FreeBSD. -The web server has to be public reachable from all over the world, an I2P site inside I2P can be setup in addition. +The web server has to be public reachable from all over the world, an I2P Site inside I2P can be setup in addition. Also frequent or infrequent attempts to scrape all your reseed files, and of course attacks on your server. The web server doesn't need to listen at default SSL/TLS port 443 - any other port can be used for obfuscation.

    diff --git a/i2p2www/pages/site/get-involved/roadmap.html b/i2p2www/pages/site/get-involved/roadmap.html index b6dc8d47..a98deae5 100644 --- a/i2p2www/pages/site/get-involved/roadmap.html +++ b/i2p2www/pages/site/get-involved/roadmap.html @@ -178,7 +178,7 @@ Update onboarding information in router console readme
  • Operators guides for reseed services
  • -Revise CSS on the default I2P site to resemble console Light theme +Revise CSS on the default I2P Site to resemble console Light theme
  • Windows Installer "Install as Windows Service" bugfixes and improvements.
  • @@ -448,7 +448,7 @@ IPv6 address selection improvements
  • Better tunnel peer selection for hidden and IPv6-only modes
  • -Prep for HTTPS console and I2P site by default +Prep for HTTPS console and I2P Site by default
  • Prep for splitting up Debian package
  • @@ -467,7 +467,7 @@ Tomcat 8.5.30
  • Susimail folders, background sending
  • -Improved support for SSL console and I2P site +Improved support for SSL console and I2P Site
  • Bug fixes, translation updates, geoip updates
  • diff --git a/i2p2www/pages/site/misc/i2ptunnel-migration.html b/i2p2www/pages/site/misc/i2ptunnel-migration.html index 6ad4795e..97a10ea2 100644 --- a/i2p2www/pages/site/misc/i2ptunnel-migration.html +++ b/i2p2www/pages/site/misc/i2ptunnel-migration.html @@ -6,7 +6,7 @@

    {% trans -%} After upgrading to the new architecture, you'll have to do a little work to get your old I2PTunnel-driven servers running. -Lets walk through a simple example. For an I2P site with the +Lets walk through a simple example. For an I2P Site with the old clientApp configuration, you had: {%- endtrans %}

    @@ -18,8 +18,8 @@ old clientApp configuration, you had:
 
  • {% trans url='http://localhost:7657/i2ptunnel/' %}Jump to {{ url }}{% endtrans %}
    • 
 
  • {% trans %}Click on Add new: [Server tunnel] "GO"{% endtrans %}
    • 
 
    • 
- 
    • {% trans %}For the name: "I2P site"{% endtrans %}
      • 
- 
    • {% trans %}For the description: "My I2P site, isn't it pretty?"{% endtrans %}
      • 
+ 
    • {% trans %}For the name: "I2P Site"{% endtrans %}
      • 
+ 
    • {% trans %}For the description: "My I2P Site, isn't it pretty?"{% endtrans %}
      • 
  For the target host:{% endtrans %} localhost
  
    • {% trans %}For the target port:{% endtrans %} 80
      • 
  
    • {% trans -%}
diff --git a/i2p2www/pages/site/misc/i2ptunnel-services.html b/i2p2www/pages/site/misc/i2ptunnel-services.html
index a153e054..d4a6b593 100644
--- a/i2p2www/pages/site/misc/i2ptunnel-services.html
+++ b/i2p2www/pages/site/misc/i2ptunnel-services.html
@@ -2,7 +2,7 @@
 {% block title %}{% trans %}I2PTunnel services{% endtrans %}{% endblock %}
 {% block content %}
 
      {% trans -%}
-Below is quick copy of aum's I2P site deployment guide.
+Below is quick copy of aum's I2P Site deployment guide.
 {%- endtrans %}
      
 
 {% trans %}1. - Deploy a local server{%- endtrans %}
diff --git a/i2p2www/pages/site/misc/ticket919.html b/i2p2www/pages/site/misc/ticket919.html
index f7d095dd..a868fae4 100644
--- a/i2p2www/pages/site/misc/ticket919.html
+++ b/i2p2www/pages/site/misc/ticket919.html
@@ -11,17 +11,17 @@ with version 0.9.5. Other operating systems are not affected.
 
 
      Background
      
 
      A change was introduced during the 0.9.5 cycle to allow I2P's configuration files to be edited with the standard
-   Windows text editor, Notepad.  This change had the unfortunate side-effect of causing our I2P site migration code to
-   fail to run on Windows systems, leading to I2P sites being served from the installation directory. Consequently:
+   Windows text editor, Notepad.  This change had the unfortunate side-effect of causing our I2P Site migration code to
+   fail to run on Windows systems, leading to I2P Sites being served from the installation directory. Consequently:
 
      
 
        
-   
      • depending upon how I2P is started, the I2P site may not be accessible; and
        • 
-   
      • confusion ensues—all documentation states that I2P sites are served from the profile path; and
        • 
+   
      • depending upon how I2P is started, the I2P Site may not be accessible; and
        • 
+   
      • confusion ensues—all documentation states that I2P Sites are served from the profile path; and
        • 
    
      • the update to Jetty 7, included in the 0.9.6 release, will fail.
        • 
 
      
-
      While no action is required for users that are not hosting an I2P site (or are not using the included Jetty to host an I2P site), it is
-recommended to follow this procedure to avoid issues in case you decide to run a Jetty-hosted I2P site in the future. If you are running an
-I2P site it is important to follow this procedure prior to upgrading to 0.9.6.
+
      While no action is required for users that are not hosting an I2P Site (or are not using the included Jetty to host an I2P Site), it is
+recommended to follow this procedure to avoid issues in case you decide to run a Jetty-hosted I2P Site in the future. If you are running an
+I2P Site it is important to follow this procedure prior to upgrading to 0.9.6.
 
      
 
 
      
@@ -46,20 +46,20 @@ I2P site it is important to follow this procedure prior to upgrading to 0.9.6.
        You should see something like the following:
        
        
-       If the path at number 1 in the image above is set to I2P site/jetty.xml, the path needs to be updated.
+       If the path at number 1 in the image above is set to I2P Site/jetty.xml, the path needs to be updated.
    
      • 
-   
    • Click the Edit button next to I2P webserver (I2P site). The page will reload to allow the path to be edited as shown below:
+   
    • Click the Edit button next to I2P webserver (I2P Site). The page will reload to allow the path to be edited as shown below:
        
        
-       Insert the full path to your I2P configuration directory before the text "I2P site/jetty.xml" as shown above,
+       Insert the full path to your I2P configuration directory before the text "I2P Site/jetty.xml" as shown above,
        then click Click the Save Client Configuration button.
    
      • 
-   
    •  If you're hosting an I2P site, move its contents to its proper home at %APPDATA%\I2P\I2P site\docroot.
+   
    •  If you're hosting an I2P Site, move its contents to its proper home at %APPDATA%\I2P\I2P Site\docroot.
    
      • 
    
    • At this point you should restart your I2P router.
      • 
 
 
-
      After following the steps outlined above, your I2P site will be served from %APPDATA%\I2P\I2P site\docroot
+
      After following the steps outlined above, your I2P Site will be served from %APPDATA%\I2P\I2P Site\docroot
    and should be accessible at http://127.0.0.1:7658.
 
      
 {% endblock %}