Make it so that older blog posts mentioning eepsites reference I2P sites now but leave original verbiage in place

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 eepsites(I2P Sites), and
+general eepsite(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 eepsite(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

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
+eepsite(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,

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 eepsite(I2P Site) the other day using 3 parallel
 streams).
 
 One really cool feature added in with the 0.3.4.1 release (that I

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 eepsites(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
+eepsites(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 eepsite(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 eepsites(I2P Sites) that you wouldn't be
 able to with the old <a  rel="nofollow" href="http://i2p/base64/">http://i2p/base64/</a> trick.  If you want to always
 be able to use &quot;wowthisiscool.i2p&quot; to reach that site, you will
 still of course have to add the entry to your hosts.txt (until the

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 eepsite(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 eepsites(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 eepsite(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 eepsites(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

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 eepsites(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,7 +133,7 @@ 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
+software and configuration necessary for running an eepsite(I2P Site) out of
 the box - you can simply drop a file in the ./eepsite/docroot/
 directory and share the I2P destination found on the router console.
 

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 eepsites(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 eepsite(I2P Site) is
 offline).  v.cool.
 
 * 5) ???

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, eepsites(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.

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, eepsites(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 eepsites(I2P Sites) through a few different pages:
  - <a  rel="nofollow" href="http://gott.i2p/sites.html">http://gott.i2p/sites.html</a>
  - <a  rel="nofollow" href="http://www.baffled.i2p/links.html">http://www.baffled.i2p/links.html</a>
  - <a  rel="nofollow" href="http://thetower.i2p/pings.txt">http://thetower.i2p/pings.txt</a>

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 eepsites(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 ;)

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) eepsites(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) eepsites(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 eepsites(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

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) eepsite(I2P Site) roundup
 5) ???
 
 1) 0.4.2.4 & 0.4.2.5
@@ -77,9 +77,9 @@ based manager at <a  rel="nofollow" href="http://susi.i2p/susidns/manager">http:
 through the stats at <a  rel="nofollow" href="http://orion.i2p/">http://orion.i2p/</a> and
 <a  rel="nofollow" href="http://susi.i2p/susisworld.html">http://susi.i2p/susisworld.html</a>
 
-* 4) I2P Site roundup
+* 4) eepsite(I2P Site) roundup
 
-There have been some notable developments on various I2P Sites worth
+There have been some notable developments on various eepsites(I2P Sites) worth
 mentioning:
 
 = <a  rel="nofollow" href="http://frosk.i2p/">http://frosk.i2p/</a> - I2PContent doc updates

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 eepsites(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.

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, eepsite(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 eepsite(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

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 eepsite(I2P Site).  The announcement [2] seems to suggest
+that source may be made available, though its not up on the eepsite(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.

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 eepsites(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.
 

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 (eepsites(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

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 eepsite(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

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 eepsite(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

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 eepsite(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 eepsite(I2P Site), save it to your
 webapps directory, restart your router, and you're good to go.
 
 [3] <a  rel="nofollow" href="http://susi.i2p/?page_id=13">http://susi.i2p/?page_id=13</a>

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 eepsites(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

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 eepsites(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

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
+eepsite(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.
 

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 eepsites(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
@@ -24,13 +24,13 @@ clearing up the initial bumps and bruises.  To answer a frequent
 question, in the long run, both NTCP and SSU will be in operation -
 we are not reverting to TCP-only.
 
-* I2P Site reachability
+* eepsite(I2P Site) reachability
 
-Remember folks that I2P Sites are reachable only when the person
+Remember folks that eepsites(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 eepsites(I2P Sites).i2p for
 your network survey needs.
 
 Anyway, there's lots more going on, but it'd be a bit premature

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 eepsites(I2P Sites)
        are today?
  <jrandom> public syndie archives do not have the ability to
        *read* the content posted to forums, unless the forums publish

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 eepsites(I2P Sites),
 signed by Complication, for which purpose 0.6.1.31
 includes two new release verification keys.
 

i2p2www/blog/2009/07/31/release-0.7.6.html

@@ -86,7 +86,7 @@ Proxy
 Installer, Split Directories, Distro-Friendly Organization
 
 <ul>
-<li>For new installs, code and data will be split into different directories. Data (router files, config files, i2psnark files, I2P Site files, etc.) will be in ~/.i2p on linux and %APPDATA%\I2P on Windows. The code directory can be read-only to the user (although the user will not be able to update in that case). On linux, the shell scripts i2prouter, runplain.sh, and eepget can be moved to a directory such as /usr/bin. All assumptions that files are in the current working directory are removed. Don't launch the router anymore in the install scripts on linux.
+<li>For new installs, code and data will be split into different directories. Data (router files, config files, i2psnark files, eepsite(I2P Site) files, etc.) will be in ~/.i2p on linux and %APPDATA%\I2P on Windows. The code directory can be read-only to the user (although the user will not be able to update in that case). On linux, the shell scripts i2prouter, runplain.sh, and eepget can be moved to a directory such as /usr/bin. All assumptions that files are in the current working directory are removed. Don't launch the router anymore in the install scripts on linux.
 <li>For existing installs, about the only visible change will be a few temporary files now in the Java temporary directory (e.g. /var/tmp on linux) instead of $I2P.
 </ul>
 

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.
 </p><p>
-The release fixes the blank-page bug when an I2P Site is not reachable,
+The release fixes the blank-page bug when an eepsite(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.

i2p2www/blog/2011/03/02/release-0.8.4.html

@@ -19,7 +19,7 @@ Please volunteer on IRC #i2p-dev.
 </p>
 
 <p>* Fix a severe memory leak in router I2CP session management that caused router crashes for people running the Robert bittorrent client
-<br />* Fix a bug from 0.8.2 that filtered cookies in the HTTP Server tunnel, causing authentication problems for some I2P Sites
+<br />* Fix a bug from 0.8.2 that filtered cookies in the HTTP Server tunnel, causing authentication problems for some eepsites(I2P Sites)
 <br />* Several fixes for rare NPEs</p>
 
 <p><strong>I2PSnark</strong></p>