idk/I2P_in_Private_Browsing_Mode_for_Firefox
1
0
Fork 0
Code Issues 17 Pull Requests Packages Projects Releases Wiki Activity

update page

Browse Source
This commit is contained in:
idk
2019-12-24 13:28:25 -05:00
parent 64c5c05b82
commit 185467937c
2 changed files with 19 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
Makefile
View File

@@ -60,7 +60,18 @@ amo-readme:
sed 's|</h2>|</strong>|g' | \
sed 's|<h3>|<strong>|g' | \
sed 's|</h3>|</strong>|g' | \
grep -v '<img' > index.html
grep -v '<img' > amo-index.html
index:
markdown README.md | \
sed 's|<p>||g' | \
sed 's|</p>||g' | \
sed 's|<h1>|<strong>|g' | \
sed 's|</h1>|</strong>|g' | \
sed 's|<h2>|<strong>|g' | \
sed 's|</h2>|</strong>|g' | \
sed 's|<h3>|<strong>|g' | \
sed 's|</h3>|</strong>|g' > index.html
xpi:
#wget -O ../i2ppb@eyedeekay.github.io.xpi \

7
index.html
View File

@@ -38,10 +38,12 @@ to the I2P container. Isolate the router console from other local
applications by automatically intercepting requests to the router console to
another container.
<ul>
<li><img src="i2psetproxy.js.png" alt="Visiting i2p-projekt.i2p" title="" /></li>
</ul></li>
<li>[done] <strong>Indicate</strong> the I2P browser is in use visually. Find an
acceptable way to indicate it on Android.
<ul>
<li><img src="susimail.png" alt="Visiting webmail" title="" /></li>
</ul></li>
<li>[done] <strong>Set</strong> the http proxy to use the local I2P proxy automatically.
Provide specific configuration for other types of I2P proxies(SOCKS,
@@ -51,6 +53,7 @@ them with the proxy enforced.</li>
<li>[done] <strong>Change</strong> the color of the browser window to indicate that I2P is in
use
<ul>
<li><img src="i2ptunnel.png" alt="Visiting i2ptunnel" title="" /></li>
</ul></li>
<li>[ready/broken/wip] <strong>Provide</strong> help in a variety of languages.</li>
<li>[wip] <strong>Monitor</strong> the health and readiness of the I2P router it is
@@ -64,12 +67,14 @@ confined to it's own container tab. (2) Use a custom protocol handler to
place each i2p application/plugin under it's own origin, shortening router
console URL's and placing applications under their own origin.
<ul>
<li><img src="routerconsole.png" alt="Visiting routerconsole" title="" /></li>
</ul></li>
<li>[wip] <strong>Handle Torrents</strong> by talking to i2psnark-rpc plugin and then
adding them directly into the Firefox downloads drop-downs, menus, etc. If I
can. Right now instead of talking to snark-rpc, it uses a web-based protocl
handler that simply auto-fills the torrent into i2psnark.
<ul>
<li><img src="i2psnark.png" alt="Visiting i2psnark" title="" /></li>
</ul></li>
<li>[barely started] <strong>Isolate</strong> traffic by contextual identity to it's own HTTP
Proxy tunnel, each reflecting it's own pseudonymous identity within I2P. The
@@ -88,10 +93,12 @@ tunnel-close timeout and key-reuse until specifically invoked.</li>
<li>I2P Blogging: Use this for posting content to the web interface of your
blog or to other similar websites that you create content on.</li>
</ul></li>
<li><img src="clearweb.png" alt="Visiting clearweb" title="" /></li>
</ul>
<strong>Video</strong>
<img src="i2psetproxy.js.gif" alt="Video of the plugin in action" title="" />
<strong>Documents</strong>