page title depends on content, great for google etc.
(duck)
This commit is contained in:
duck
@@ -1,4 +1,5 @@
|
||||
<?php
|
||||
include('menu.php');
|
||||
|
||||
define(PAGE_DIR,'pages/');
|
||||
define(PAGE_EXT,'.html');
|
||||
@@ -15,6 +16,8 @@ if(isset($_REQUEST['page'])) {
|
||||
$page = 'home';
|
||||
}
|
||||
|
||||
$pagetitle = getpagetitle($page);
|
||||
|
||||
if(is_readable(PAGE_DIR.$page.PAGE_EXT)) {
|
||||
include(PAGE_DIR.'header'.PAGE_EXT);
|
||||
include(PAGE_DIR.$page.PAGE_EXT);
|
||||
|
||||
41
menu.php
Normal file
41
menu.php
Normal file
@@ -0,0 +1,41 @@
|
||||
<?php
|
||||
// TODO: improve this, like include the navigation hierarchy into it
|
||||
|
||||
// dictionary for looking up the page title, if there is no match
|
||||
// the first character of the page is capitalized
|
||||
$pagetitles = array('home' => 'News',
|
||||
'about' => 'About I2P',
|
||||
'getinvolved' => 'Get involved',
|
||||
'halloffame' => 'Hall of Fame',
|
||||
'myi2p' => 'MyI2P',
|
||||
'minwww' => 'MinWWW',
|
||||
'i2ptunnel' => 'I2PTunnel',
|
||||
'i2ptunnel_services' => 'Setting up services',
|
||||
'i2ptunnel_tuning' => 'Tuning',
|
||||
'i2ptunnel_lan' => 'LAN setup',
|
||||
'jvm' => 'JVM',
|
||||
'api' => 'API',
|
||||
'sam' => 'SAM',
|
||||
'i2cp' => 'I2CP',
|
||||
'how' => 'How does it work?',
|
||||
'how_intro' => 'Intro',
|
||||
'how_threatmodel' => 'Threat model',
|
||||
'how_tunnelrouting' => 'Tunnel routing',
|
||||
'how_garlicrouting' => 'Garlic routing',
|
||||
'how_networkdatabase' => 'Network database',
|
||||
'how_peerselection' => 'Peer selection',
|
||||
'how_cryptography' => 'Cryptography',
|
||||
'how_elgamalaes' => 'ElGamal/AES+SessionTag',
|
||||
'how_networkcomparisons' => 'Network comparisons',
|
||||
'faq' => 'FAQ',
|
||||
'cvs' => 'CVS');
|
||||
|
||||
function getpagetitle($page) {
|
||||
global $pagetitles;
|
||||
if (isset($pagetitles[$page])) {
|
||||
return $pagetitles[$page];
|
||||
}
|
||||
$title = str_replace ('_', ' ', $page);
|
||||
return ucfirst($title);
|
||||
}
|
||||
?>
|
||||
@@ -1,4 +1,3 @@
|
||||
<h1>API</h1>
|
||||
<ul>
|
||||
<li><a href="sam">SAM[ ]</a></li>
|
||||
<li><a href="ministreaming">ministreaming[ ]</a></li>
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
<h1>Applications</h1>
|
||||
<p>here's some content that might help someone who wants to put together an application developer's guide for I2P - I dont have time to polish this up before I leave, but thought it might be of use to someone. Feel free to tear this up, edit like mad, or just read it :)</p>
|
||||
|
||||
<h1>Application development guide</h1>
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
<h1>Bounties</h1>
|
||||
<p>While we always gratefully accept any contributions of code,
|
||||
documentation, and the like, there are other ways to help I2P move
|
||||
forward. As with any open source project, our goals would be achieved more
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
<h1>CVS</h1>
|
||||
<p>This is just a reminder for me so I don't have to memorize the commands to
|
||||
download i2p cvs:</p>
|
||||
|
||||
|
||||
@@ -1,5 +1,3 @@
|
||||
<h1>Donate</h1>
|
||||
|
||||
<p>Thank you for your interest in contributing to I2P! The details of how you
|
||||
can make your contribution are provided below:</p>
|
||||
|
||||
|
||||
@@ -1,5 +1,3 @@
|
||||
<h1>Download</h1>
|
||||
|
||||
<h3>New installs</h3>
|
||||
<ul>
|
||||
<li><a href="http://dev.i2p.net/i2p/i2p_0_3_2.1.tar.gz">http://dev.i2p.net/i2p/i2p_0_3_2.1.tar.gz</a>
|
||||
|
||||
@@ -1,5 +1,3 @@
|
||||
<h1>FAQ</h1>
|
||||
|
||||
<h3>What is I2P?</h3>
|
||||
<p>
|
||||
I2P is a generic anonymous and secure peer to peer communication layer. It is
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
<h1>Get involved</h1>
|
||||
<p>To get involved, please feel free to join us on the #i2p IRC channel (on
|
||||
irc.freenode.net, or within I2P on irc.duck.i2p or irc.baffled.i2p). In
|
||||
addition, we have a <a href="http://dev.i2p.net/pipermail/i2p/">mailing list</a>
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
<h1>Hall of Fame</h1>
|
||||
<p>Big thanks go to the following people who have donated to bounties or the general fund!</p>
|
||||
|
||||
<p>
|
||||
|
||||
@@ -5,7 +5,7 @@ echo "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n";
|
||||
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" >
|
||||
<head>
|
||||
<title>I2P</title>
|
||||
<title>I2P - <?=$pagetitle?></title>
|
||||
<link rel="stylesheet" href="styles/default.css" type="text/css" />
|
||||
<link rel="shortcut icon" href="favicon.ico" />
|
||||
</head>
|
||||
@@ -17,7 +17,7 @@ echo "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n";
|
||||
<div class="logo">
|
||||
<a href="home"><img src="images/i2plogo.png" alt="I2P Logo" width="178" height="35" /></a>
|
||||
</div>
|
||||
<h1>I2P</h1>
|
||||
<h1>I2P - <?=$pagetitle?></h1>
|
||||
|
||||
<div class="menu">
|
||||
<?php include(PAGE_DIR.'menu'.PAGE_EXT); ?>
|
||||
|
||||
@@ -1,3 +1,9 @@
|
||||
<h1>Welcome on I2P.net</h1>
|
||||
<h3>Welcome on I2P.net</h3>
|
||||
|
||||
<p>A distributed anonymous and secure communication network.</p>
|
||||
|
||||
<p><b>Latest version:</b><br />
|
||||
2004-07-11 - 0.3.2.1 -
|
||||
<a href="http://dev.i2p.net/pipermail/i2p/2004-July/000327.html">Announcement</a>
|
||||
- <a href="download">Download</a>
|
||||
</p>
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
<h1>How does it work?</h1>
|
||||
<ul>
|
||||
<li><a href="how_intro">Intro</a></li>
|
||||
<li><a href="how_threatmodel">Threat model</a></li>
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
<h1>ElGamal / AES+SessionTag</h1>
|
||||
<p>
|
||||
Within I2P, various messages are encrypted, but we don't want anyone to know
|
||||
to whom or from whom it is bound, so we can't just toss a "to" or "from" address.
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
<h1>Intro</h1>
|
||||
<p>I2P is an effort to build, deploy, and maintain a network to support secure and anonymous
|
||||
communication. People using I2P are in control of the tradeoffs between anonymity, reliability,
|
||||
bandwidth usage, and latency. There is no central point in the network on which pressure can be
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
<h1>Network comparisons</h1>
|
||||
<p>
|
||||
There are a great many other applications and projects working on anonymous
|
||||
communication and I2P has been inspired by much of their efforts. This is not
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
<h1>Threatmodel</h1>
|
||||
<p>
|
||||
There are a great many other applications and projects working on anonymous
|
||||
communication and I2P has been inspired by much of their efforts. This is not
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
<h1>I2PTunnel</h1>
|
||||
<ul>
|
||||
<li><a href="i2ptunnel_services">Setting up services[ ]</a></li>
|
||||
<li><a href="i2ptunnel_tuning">Tuning[ ]</a></li>
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
<h1>jbigi</h1>
|
||||
<p>Using JNI (Java Native Interface), a bit of C code (thanks ugha!), a little
|
||||
manual work and a piece of chewinggum it is possible to make the public key
|
||||
cryptography quite a bit faster.</p>
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
<h1>Licenses</h1>
|
||||
<p>As required by our threat model (among other reasons), the
|
||||
software developed to support the anonymous communication
|
||||
network we call I2P must be freely available, open source,
|
||||
|
||||
@@ -1,5 +1,3 @@
|
||||
<h1>Links</h1>
|
||||
|
||||
<ul>
|
||||
<li><a href="http://freehaven.net/anonbib/topic.html">Freehaven's Anonymity Bibliography</a></li>
|
||||
<li><a href="http://www.ovmj.org/GNUnet/links.php3">GNUNet's related projects</a></li>
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
<h1>Meeting 90</h1>
|
||||
<h3> Tuesday, May 18, 2004 14:00:00 PDT</h3>
|
||||
|
||||
<pre>
|
||||
|
||||
@@ -1,5 +1,3 @@
|
||||
<h1>Meeting 92</h1>
|
||||
|
||||
<pre>
|
||||
[22:59] <duck> Tue Jun 1 21:00:00 UTC 2004
|
||||
[23:00] <duck> hi folks!
|
||||
|
||||
@@ -1,5 +1,3 @@
|
||||
<h1>Meeting 93</h1>
|
||||
|
||||
<pre>
|
||||
21:02:08 <duck> Tue Jun 8 21:02:08 UTC 2004
|
||||
21:02:21 <duck> meeting time
|
||||
|
||||
@@ -1,5 +1,3 @@
|
||||
<h1>Meeting 95</h1>
|
||||
|
||||
<pre>
|
||||
14:00 < jrandom> 0) hi
|
||||
14:00 < jrandom> 1) status update
|
||||
|
||||
@@ -1,5 +1,3 @@
|
||||
<h1>Meetings</h1>
|
||||
|
||||
<p>The meetings are held every Tuesday at 9PM GMT on IRC.</p>
|
||||
|
||||
<h3>Logs of past meetings</h3>
|
||||
|
||||
@@ -43,8 +43,8 @@
|
||||
* <a href="how_cryptography">Cryptography[ ]</a><br />
|
||||
> <a href="how_elgamalaes">ElGamal/AES+SessionTag</a><br />
|
||||
* <a href="how_networkcomparisons">Network comparisons</a><br />
|
||||
<br />
|
||||
-->
|
||||
<br />
|
||||
<b><a href="faq">FAQ</a></b><br />
|
||||
<br />
|
||||
<b><a href="development">Development[ ]</a></b><br />
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
<h1>MinWWW</h1>
|
||||
<p>Here's an outline and rationale for a minimal WWW proxy app for use over
|
||||
I2P.</p>
|
||||
<p>HTTP operation over I2P using I2PTunnel. When the base SocketLibrary
|
||||
|
||||
@@ -1,4 +1,3 @@
|
||||
<h1>Performance</h1>
|
||||
<p>Probably one of the most frequent things people ask is "how fast is I2P?",
|
||||
and no one seems to like the answer - "it depends". After trying out I2P, the
|
||||
next thing they ask is "will it get faster?", and the answer to that is a most
|
||||
|
||||
@@ -1,5 +1,3 @@
|
||||
<h1>Roadmap</h1>
|
||||
|
||||
<h2>0.3.2 (May)</h2>
|
||||
<ul>
|
||||
<li>Fixed the netDb for more reliability</li>
|
||||
|
||||
@@ -1,5 +1,3 @@
|
||||
<h1>I2P Team</h1>
|
||||
|
||||
<p>We are a small group of people spread around several continents, working to
|
||||
advance different aspects of the project and discussing the design of the
|
||||
network.</p>
|
||||
|
||||
Reference in New Issue
Block a user