From ee3285e83009c69d4680196d1f535120361bb884 Mon Sep 17 00:00:00 2001 From: idk Date: Thu, 16 Sep 2021 18:54:33 -0400 Subject: [PATCH 1/9] Fix formatting and consistency issues --- i2p2www/pages/downloads/firefox.html | 6 +++--- i2p2www/pages/downloads/list.html | 6 +++--- i2p2www/pages/downloads/nsis.html | 11 +++++------ 3 files changed, 11 insertions(+), 12 deletions(-) diff --git a/i2p2www/pages/downloads/firefox.html b/i2p2www/pages/downloads/firefox.html index 981099a3..5dc366ca 100644 --- a/i2p2www/pages/downloads/firefox.html +++ b/i2p2www/pages/downloads/firefox.html @@ -3,7 +3,7 @@ {% block title %}Firefox Profile{% endblock %} {% block content %} -

{{ _('I2P Easy Install Bundle(Beta)') }}

+

{{ _('I2P Easy Install Bundle (Beta) for Windows') }}

{% trans nsis="/nsis" -%} The I2P Firefox Browser Profile has been expanded into the new I2P Easy Install Bundle, which is in Beta. If you already have an I2P Router installed, it is @@ -12,7 +12,7 @@ I2P Settings will be left untouched. If you do not have an I2P router installed, then you do not need to install I2P. This package will install I2P at the same time it installs the browser profile. This page has been kept to document the motivations and design of the included Firefox profile. To learn more about the -new bundle, visit The Easy-Install Bundle Page. +new bundle, visit The Easy Install Bundle Page. {%- endtrans %}

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

{% trans -%} @@ -107,7 +107,7 @@ I2P routers are designed to have long uptimes, and so unlike Tor Browser, the lifetime of your I2P Router is not tied to the lifetime of your I2P browsing session. The browser profile will manage your history, your browser's local storage and cache, and your browsing context but it will never stop your I2P -router on it's own. You may stop the router using the web interface on the +router on its own. You may stop the router using the web interface on the router console homepage. {%- endtrans %}

diff --git a/i2p2www/pages/downloads/list.html b/i2p2www/pages/downloads/list.html index a2aeab50..20b4448c 100644 --- a/i2p2www/pages/downloads/list.html +++ b/i2p2www/pages/downloads/list.html @@ -101,14 +101,14 @@ I2P connections.

{% trans -%} After installing Java, download the file and double-click to run it. {%- endtrans %}

-

{% trans %}Easy-Install Bundle(Beta){% endtrans %}

+

{% trans %}Easy-Install Bundle (Beta){% endtrans %}

{% trans %}It's now possible to install all I2P components using a single package(No Java Required). To try out the new installer, click here. This bundle can also be used to configure a Firefox Profile. It will not interfere with an existing I2P installation if one exists. {% endtrans %}

- {% trans %}I2P Easy-Install Bundle(Beta){% endtrans %} + {% trans %}I2P Easy Install Bundle (Beta){% endtrans %}

{% trans %}Detailed Install Guide{% endtrans %}

@@ -137,7 +137,7 @@ I2P connections.

the install procedure in your terminal. {%- endtrans %} -

{% trans %}DMG Bundle (BETA){% endtrans %}

+

{% trans %}DMG Bundle (Beta){% endtrans %}

If you do not want to use the installer or do not have a Java Runtime Environment available on your Mac, you can try our latest DMG bundle.
diff --git a/i2p2www/pages/downloads/nsis.html b/i2p2www/pages/downloads/nsis.html index 966b71e9..26e0bf3d 100644 --- a/i2p2www/pages/downloads/nsis.html +++ b/i2p2www/pages/downloads/nsis.html @@ -3,10 +3,10 @@ {% block title %}I2P Easy Install Bundle(Beta){% endblock %} {% block content %} -

{{ _('I2P Easy Install Bundle(Beta)') }}

+

{{ _('I2P Easy Install Bundle (Beta) for Windows') }}

{% trans firefox="/firefox" -%} This is an "All-in-One" installer which includes the complete I2P desktop -software and all of it's dependencies in a single, easy-to-install package. It +software and all of its dependencies in a single, easy-to-install package. It is built on the premise that I2P should be easy, and that we should help our users get their initial configuration in place instead of requiring an elaborate install process. To learn more about the Firefox profile that comes bundled with @@ -14,10 +14,9 @@ this installer, visit The Firefox Profile Page. {%- endtrans %}

{{ _('Is it a Zero-Dependency I2P Browser?') }}

{% trans -%} -Not yet. -{%- endtrans %}{% trans issueurl="https://i2pgit.org/i2p-hackers/i2p.firefox/-/issues/2" -%} For now, this installer still requires +Not yet. {%- endtrans %}{% trans issueurl="https://i2pgit.org/i2p-hackers/i2p.firefox/-/issues/2" -%} For now, this installer still requires Firefox to be installed on the system, it does not bundle a Firefox installer of -it's own. This was a judgement made to protect users of the bundle, we believe +its own. This was a judgement made to protect users of the bundle, we believe that you should obtain your Firefox distribution from a vendor who can provide updates. Please obtain Firefox from Mozilla. If you would like to discuss supporting other browsers, please join the discussion on the @@ -108,7 +107,7 @@ I2P routers are designed to have long uptimes, and so unlike Tor Browser, the lifetime of your I2P Router is not tied to the lifetime of your I2P browsing session. The browser profile will manage your history, your browser's local storage and cache, and your browsing context but it will never stop your I2P -router on it's own. You may stop the router using the web interface on the +router on its own. You may stop the router using the web interface on the router console homepage. {%- endtrans %}

From d8e5d4bb2245e9e41e69b4de8ce37f1329ffbc49 Mon Sep 17 00:00:00 2001 From: idk Date: Thu, 16 Sep 2021 20:03:16 -0400 Subject: [PATCH 2/9] Change URL from nsis to easyinstall --- i2p2www/downloads.py | 4 ++-- i2p2www/legacy.py | 2 +- i2p2www/pages/downloads/{nsis.html => easyinstall.html} | 0 i2p2www/sitemap.py | 2 +- i2p2www/urls.py | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) rename i2p2www/pages/downloads/{nsis.html => easyinstall.html} (100%) diff --git a/i2p2www/downloads.py b/i2p2www/downloads.py index 1996657f..5a049050 100644 --- a/i2p2www/downloads.py +++ b/i2p2www/downloads.py @@ -90,13 +90,13 @@ def downloads_windows(): return render_template('downloads/windows.html') # AIO-Windows-specific page -def downloads_nsis(): +def downloads_easyinstall(): # TODO: read mirror list or list of available files if request.headers.get('X-I2P-Desthash') and not request.headers.get('X-Forwarded-Server'): def_mirror = DEFAULT_I2P_MIRROR else: def_mirror = DEFAULT_MIRROR - return render_template('downloads/nsis.html', def_mirror=def_mirror) + return render_template('downloads/easyinstall.html', def_mirror=def_mirror) # Docker-specific page def downloads_docker(): diff --git a/i2p2www/legacy.py b/i2p2www/legacy.py index 59c1f6cc..b3b2418e 100644 --- a/i2p2www/legacy.py +++ b/i2p2www/legacy.py @@ -20,7 +20,7 @@ LEGACY_FUNCTIONS_MAP={ 'firefox': {'function': 'downloads_firefox', 'params': {}}, 'lab': {'function': 'downloads_lab', 'params': {}}, 'mac': {'function': 'downloads_mac', 'params': {}}, - 'nsis': {'function': 'downloads_nsis', 'params': {}}, + 'easyinstall': {'function': 'downloads_easyinstall', 'params': {}}, 'windows': {'function': 'downloads_windows', 'params': {}}, 'download': {'function': 'downloads_list', 'params': {}}, 'installation': {'function': 'downloads_list', 'params': {}}, diff --git a/i2p2www/pages/downloads/nsis.html b/i2p2www/pages/downloads/easyinstall.html similarity index 100% rename from i2p2www/pages/downloads/nsis.html rename to i2p2www/pages/downloads/easyinstall.html diff --git a/i2p2www/sitemap.py b/i2p2www/sitemap.py index 27066bb9..24588405 100644 --- a/i2p2www/sitemap.py +++ b/i2p2www/sitemap.py @@ -119,7 +119,7 @@ def render_sitemap(): 'path': '/download/mac', }) urls.append({ - 'path': '/download/nsis', + 'path': '/download/easyinstall', }) urls.append({ 'path': '/download/windows', diff --git a/i2p2www/urls.py b/i2p2www/urls.py index 208ced09..84a08ed4 100644 --- a/i2p2www/urls.py +++ b/i2p2www/urls.py @@ -92,7 +92,7 @@ url('//download', 'downloads.downloads_list') url('//download/debian', 'downloads.downloads_debian') url('//download/docker', 'downloads.downloads_docker') url('//download/windows', 'downloads.downloads_windows') -url('//download/nsis', 'downloads.downloads_nsis') +url('//download/easyinstall', 'downloads.downloads_easyinstall') url('//download/firefox', 'downloads.downloads_firefox') url('//download/config', 'downloads.downloads_config') url('//download/lab', 'downloads.downloads_lab') From 345cd69cd194f3c408765c78e033ac0ae70a1e75 Mon Sep 17 00:00:00 2001 From: idk Date: Fri, 17 Sep 2021 00:33:47 -0400 Subject: [PATCH 3/9] Make nsis link point to easyinstall --- i2p2www/legacy.py | 1 + i2p2www/pages/downloads/easyinstall.html | 2 +- i2p2www/urls.py | 1 + 3 files changed, 3 insertions(+), 1 deletion(-) diff --git a/i2p2www/legacy.py b/i2p2www/legacy.py index b3b2418e..f507b451 100644 --- a/i2p2www/legacy.py +++ b/i2p2www/legacy.py @@ -21,6 +21,7 @@ LEGACY_FUNCTIONS_MAP={ 'lab': {'function': 'downloads_lab', 'params': {}}, 'mac': {'function': 'downloads_mac', 'params': {}}, 'easyinstall': {'function': 'downloads_easyinstall', 'params': {}}, + 'nsis': {'function': 'downloads_easyinstall', 'params': {}}, 'windows': {'function': 'downloads_windows', 'params': {}}, 'download': {'function': 'downloads_list', 'params': {}}, 'installation': {'function': 'downloads_list', 'params': {}}, diff --git a/i2p2www/pages/downloads/easyinstall.html b/i2p2www/pages/downloads/easyinstall.html index 26e0bf3d..89ceb0a1 100644 --- a/i2p2www/pages/downloads/easyinstall.html +++ b/i2p2www/pages/downloads/easyinstall.html @@ -1,6 +1,6 @@ {% extends "global/layout.html" %} {%- from "downloads/macros" import package_outer with context -%} -{% block title %}I2P Easy Install Bundle(Beta){% endblock %} +{% block title %}I2P Easy Install Bundle (Beta) for Windows{% endblock %} {% block content %}

{{ _('I2P Easy Install Bundle (Beta) for Windows') }}

diff --git a/i2p2www/urls.py b/i2p2www/urls.py index 84a08ed4..fe0486bc 100644 --- a/i2p2www/urls.py +++ b/i2p2www/urls.py @@ -93,6 +93,7 @@ url('//download/debian', 'downloads.downloads_debian') url('//download/docker', 'downloads.downloads_docker') url('//download/windows', 'downloads.downloads_windows') url('//download/easyinstall', 'downloads.downloads_easyinstall') +url('//download/nsis', 'downloads.downloads_easyinstall') url('//download/firefox', 'downloads.downloads_firefox') url('//download/config', 'downloads.downloads_config') url('//download/lab', 'downloads.downloads_lab') From 32e5a35cccfe374aa3f0cdadfb723f30ad7b9cdd Mon Sep 17 00:00:00 2001 From: idk Date: Sat, 18 Sep 2021 02:15:08 -0400 Subject: [PATCH 4/9] Start BTC news blog post. --- i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst | 28 +++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst diff --git a/i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst b/i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst new file mode 100644 index 00000000..9ccc32f9 --- /dev/null +++ b/i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst @@ -0,0 +1,28 @@ +============================================================= +{% trans -%}Bitcoin Code adds support for I2P!{%- endtrans %} +============================================================= + +.. meta:: + :author: idk + :date: 2021-09-18 + :category: general + :excerpt: {% trans %}A new use case and a signal of growing acceptance{% endtrans %} + +{% trans -%} +An event months in the making, Bitcoin Core has added official support for I2P! +Bitcoin-over-I2P nodes can interact fully with the rest of the Bitcoin nodes, +using the help of nodes that operate within both I2P and the clearnet, making +them first-class participants in the Bitcoin network. This is exciting news, in +part because it highlights some of the things I2P is singularly good at, like +empowering application developers to build I2P connections programmatically and +conveniently. +{%- endtrans %} + +{% trans -%} +How it Works +{%- endtrans %} +------------ + +{% trans -%} +I2P support is automatic, via the SAM API. +{%- endtrans %} \ No newline at end of file From f963add18354a5dd6785c55629181d661550e83c Mon Sep 17 00:00:00 2001 From: idk Date: Mon, 20 Sep 2021 23:28:22 -0400 Subject: [PATCH 5/9] Update glossary to include broad p2p/distributed software terms --- i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst | 16 ++-- i2p2www/pages/site/about/glossary.html | 78 +++++++++++++++++-- 2 files changed, 81 insertions(+), 13 deletions(-) diff --git a/i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst b/i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst index 9ccc32f9..9f19a8f1 100644 --- a/i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst +++ b/i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst @@ -12,10 +12,9 @@ An event months in the making, Bitcoin Core has added official support for I2P! Bitcoin-over-I2P nodes can interact fully with the rest of the Bitcoin nodes, using the help of nodes that operate within both I2P and the clearnet, making -them first-class participants in the Bitcoin network. This is exciting news, in -part because it highlights some of the things I2P is singularly good at, like -empowering application developers to build I2P connections programmatically and -conveniently. +them first-class participants in the Bitcoin network. It's exciting to see +large communities like Bitcoin taking notice of the advantages I2P can bring +to them providing privacy and reachability to people all over the world. {%- endtrans %} {% trans -%} @@ -24,5 +23,10 @@ How it Works ------------ {% trans -%} -I2P support is automatic, via the SAM API. -{%- endtrans %} \ No newline at end of file +I2P support is automatic, via the SAM API. This is also exciting news, because +it highlights some of the things I2P is singularly good at, like empowering +application developers to build I2P connections programmatically and +conveniently. Bitcoin-over-I2P users can use I2P with no manual configuration by +enabling the SAM API. +{%- endtrans %} + diff --git a/i2p2www/pages/site/about/glossary.html b/i2p2www/pages/site/about/glossary.html index 67c6ff26..effa0840 100644 --- a/i2p2www/pages/site/about/glossary.html +++ b/i2p2www/pages/site/about/glossary.html @@ -2,16 +2,80 @@ {% block title %}{{ _('Glossary') }}{% endblock %} {% block content %} {% trans -%} -This page lists often-used terminology when discussing I2P and cryptography. +This table lists often-used terminology when discussing I2P and cryptography. {%- endtrans %}
    -
  • I2P: Invisible Internet Project: a project meant to provide an anonymity layer, so user can communicate anonymously using a range of applications.
    • -
  • Router: The core I2P software, which routes encrypted packets on the I2P network. All routers by default participate in the network, which both helps the network and provides cover traffic for any clients or servers connecting to the I2P network through the router.
    • -
  • RouterIdentity: A collection of information required to communicate directly with a router, such as its IP address and listening port, public signing and encryption keys etc.
    • -
  • Tunnel: An anonymous communication pathway between a client or server and the I2P network. Tunnels are unidirectional, so any one client or server must have at least two Tunnels - one for inbound traffic and one for outbound traffic.
    • -
  • Destination: The cryptographic identity of a tunnel. These are the identities of clients and servers within the I2P network, and are analogous to the IP:port of a computer on the normal internet.
    • -
  • LeaseSet: A collection of information required to communicate with a client or server at a particular Destination, such as the gateways of the inbound Tunnels for that Destination.
    • +
  • {% trans -%}I2P: Invisible Internet Project: a project meant to + provide an anonymity layer, so user can communicate anonymously using a + range of applications.{%- endtrans %}
    • +
  • {% trans -%}Router: The core I2P software, which routes encrypted + packets on the I2P network. All routers by default participate in the + network, which both helps the network and provides cover traffic for any + clients or servers connecting to the I2P network through the + router.{%- endtrans %}
    • +
  • {% trans -%}RouterIdentity: A collection of information required to + communicate directly with a router, such as its IP address and listening + port, public signing and encryption keys etc.{%- endtrans %}
    • +
  • {% trans -%}Tunnel: An anonymous communication pathway between a + client or server and the I2P network. Tunnels are unidirectional, so any + one client or server must have at least two Tunnels - one for inbound + traffic and one for outbound traffic.{%- endtrans %}
    • +
  • {% trans -%}Destination: The cryptographic identity of a tunnel. + These are the identities of clients and servers within the I2P network, + and are analogous to the IP:port of a computer on the normal + internet.{%- endtrans %}
    • +
  • {% trans -%}LeaseSet: A collection of information required to + communicate with a client or server at a particular Destination, such as + the gateways of the inbound Tunnels for that + Destination.{%- endtrans %}
    • +
+
+{% trans -%}This table lists definition of different networks and their components. These +terms and the definitions provided are taken from +Decentralization Off The +Shelf: 7 Maxims by Simply Secure(used with permission).{%- endtrans %} + +
    +
  • {% trans -%}Decentralization: Network architecture that avoids + reliance on a single party. Encompasses peer-to-peer, blockchain, + federated, and distributed technologies that involve many individual + users.{%- endtrans %}
    • +
  • {% trans -%}Peer-to-Peer (p2p): Peers make a portion of their + resources, such as processing power, disk storage or network bandwidth, + directly available to other network participants, without the need for + central coordination by servers or stable hosts. Popularized by + BitTorrent, Napster, and Bitcoin.{%- endtrans %}
    • +
  • {% trans -%}Federated: Federation allows separate deployments of a + service to communicate with each other through a common protocol, for + instance a mail server run by Google federates with a mail server run by + Microsoft when you send an email from @gmail.com to @hotmail.com. + Each deployment may host multiple users.{%- endtrans %}
    • +
  • {% trans -%}Blockchain: A distributed ledger that can record + transactions between multiple parties efficiently and in a verifiable + and permanent way.{%- endtrans %}
    • +
  • {% trans -%}Distributed systems: Academic topic within the + discipline of Computer Science which is concerned with the design of + computer systems that consist of many individual computers connected + over a network. Peer-to-peer networks and blockchains are examples of + distributed systems architectures.{%- endtrans %}
    • +
  • {% trans -%}TCP/UDP: The two foundational transport protocols used + on the Internet. Common protocols used to send data between two + computers.{%- endtrans %}
    • +
  • {% trans -%}DHT: Distributed hash table, used in some projects to + connect peers to each other by storing information in the form of + key-value pairs in a distributed manner.{%- endtrans %}
    • +
  • {% trans -%}IP address: A number of a computer or network which is + unique and thus can be used to address it.{%- endtrans %}
    • +
  • {% trans -%}WebRTC: A protocol standard for establishing connections + in a web browser where data passes directly between + users.{%- endtrans %}
    • +
  • {% trans -%}Hash: A number, usually displayed as a string of letters + and numbers. It can serve as a ‘fingerprint’ uniquely identifying + data.{%- endtrans %}
    • +
  • {% trans -%}UX: User experience, the overall experience of a person + using a product or a service, especially in terms of how easy it is to + use.{%- endtrans %}
{% endblock %} From 0bb7ed6de487da21292b64bac91c61a120f0fbfd Mon Sep 17 00:00:00 2001 From: idk Date: Tue, 21 Sep 2021 18:47:09 -0400 Subject: [PATCH 6/9] Add details to bitcoin post --- i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst | 77 ++++++++++++++++++- i2p2www/pages/downloads/easyinstall.html | 14 ++-- i2p2www/pages/global/nav.html | 1 - 3 files changed, 83 insertions(+), 9 deletions(-) diff --git a/i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst b/i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst index 9f19a8f1..8a404d88 100644 --- a/i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst +++ b/i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst @@ -1,5 +1,5 @@ ============================================================= -{% trans -%}Bitcoin Code adds support for I2P!{%- endtrans %} +{% trans -%}Bitcoin Core adds support for I2P!{%- endtrans %} ============================================================= .. meta:: @@ -27,6 +27,79 @@ I2P support is automatic, via the SAM API. This is also exciting news, because it highlights some of the things I2P is singularly good at, like empowering application developers to build I2P connections programmatically and conveniently. Bitcoin-over-I2P users can use I2P with no manual configuration by -enabling the SAM API. +enabling the SAM API and running Bitcoin with I2P enabled. {%- endtrans %} +{% trans -%} +Configuring your I2P Router +{%- endtrans %} +--------------------------- + +{% trans -%} +In order to set up an I2P Router to provide anonymous connectivity to bitcoin, +the SAM API needs to be enabled. In Java I2P, you should go to `http://127.0.0.1:7657/configclients +`_. and start the SAM Application Bridge +with the "Start" button. You may also want to enable the SAM Application Bridge +by default by checking the "Run at Startup" box and clicking "Save Client +Configuration." +{%- endtrans %} + +{% trans -%} +On i2pd, the SAM API is normally enabled by default, but if it isn't, you should +set:: + + sam.enabled=true + +in your i2pd.conf file. +{%- endtrans %} + +{% trans -%} +Configuring your Bitcoin Node for Anonymity and Connectivity +{%- endtrans %} +------------------------------------------------------------ + +{% trans -%} +Getting Bitcoin itself launched in an anonyous mode still requires editing some +configuration files in the Bitcoin Data Directory, which is %APPDATA%\Bitcoin on +Windows, ~/.bitcoin on Linux, and ~/Library/Application Support/Bitcoin/ on Mac +OSX. It also requires at least version 22.0.0 for I2P support to be present. +After following the following instructions, you should have a private Bitcoin +node which uses I2P for I2P connections, and Tor for .onion and clearnet +connections, so that all your connections are anonymized. For convenience, +Windows users should open their Bitcoin Data Directory by opening the start menu +and searching for "Run." Inside the run prompt, type "%APPDATA%\Bitcoin" and +press enter. +{%- endtrans %} + +{% trans -%} +In that directory create a file called "i2p.conf." On Windows, you should make +sure that you've add quotes around the file when you save it, in order to +prevent Windows from adding a default file extension to the file. The file +should contain the following I2P-Related Bitcoin configuration options:: + + i2psam=127.0.0.1:7656 + i2pacceptincoming=true + onlynet=i2p + +Next, you should create another file called "tor.conf." The file should contain +the following Tor related configuration options:: + + proxy=127.0.0.1:9050 + onion=127.0.0.1:9050 + onlynet=tor + +Finally, you'll need to "Include" these configuration options in your Bitcoin +configuration file, called "bitcoin.conf" in the Data Directory. Add these two +lines to your bitcoin.conf file:: + + includeconf=i2p.conf + includeconf=tor.conf + +Now your Bitcoin node is configured to only use anonymous connections. In order +to enable direct connections to remote nodes, remove the lines beginning in:: + + onlynet= + +You can do this if you do not require your Bitcoin node to be anonymous, and +it helps anonymous users connect to the rest of the Bitcoin network. +{%- endtrans %} \ No newline at end of file diff --git a/i2p2www/pages/downloads/easyinstall.html b/i2p2www/pages/downloads/easyinstall.html index 89ceb0a1..e18c8669 100644 --- a/i2p2www/pages/downloads/easyinstall.html +++ b/i2p2www/pages/downloads/easyinstall.html @@ -14,12 +14,14 @@ this installer, visit The Firefox Profile Page. {%- endtrans %}

{{ _('Is it a Zero-Dependency I2P Browser?') }}

{% trans -%} -Not yet. {%- endtrans %}{% trans issueurl="https://i2pgit.org/i2p-hackers/i2p.firefox/-/issues/2" -%} For now, this installer still requires -Firefox to be installed on the system, it does not bundle a Firefox installer of -its own. This was a judgement made to protect users of the bundle, we believe -that you should obtain your Firefox distribution from a vendor who can provide -updates. Please obtain Firefox from Mozilla. If you would like to discuss -supporting other browsers, please join the discussion on the +Not yet.{%- endtrans %} +{% trans issueurl="https://i2pgit.org/i2p-hackers/i2p.firefox/-/issues/2" -%} +For now, this installer still requires Firefox to be installed on the system, it +does not bundle a Firefox installer of its own. This was a judgement made to +protect users of the bundle, we believe that you should obtain your Firefox +distribution from a vendor who can provide updates. Please obtain Firefox from +Mozilla. If you would like to discuss supporting other browsers, please join the +discussion on the Gitlab Issue. {%- endtrans %}

{{ _('Why should I use it?') }}

diff --git a/i2p2www/pages/global/nav.html b/i2p2www/pages/global/nav.html index bb3f789c..2bea3e70 100644 --- a/i2p2www/pages/global/nav.html +++ b/i2p2www/pages/global/nav.html @@ -51,7 +51,6 @@
  • {{ _('Using an IDE with I2P') }}
  • {{ _('Developer guidelines and coding style') }}
  • {{ _('Git') }}
    • -
  • {{ _('Monotone') }}
  • {{ _('Translate I2P into more Languages') }}
    • From 7e3f95fd2fc26371eb3690d027cc5ff8fdc47484 Mon Sep 17 00:00:00 2001 From: idk Date: Tue, 21 Sep 2021 18:49:57 -0400 Subject: [PATCH 7/9] run aspell on bitcoin post --- i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst b/i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst index 8a404d88..6e385b1b 100644 --- a/i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst +++ b/i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst @@ -59,13 +59,13 @@ Configuring your Bitcoin Node for Anonymity and Connectivity ------------------------------------------------------------ {% trans -%} -Getting Bitcoin itself launched in an anonyous mode still requires editing some +Getting Bitcoin itself launched in an anonymous mode still requires editing some configuration files in the Bitcoin Data Directory, which is %APPDATA%\Bitcoin on Windows, ~/.bitcoin on Linux, and ~/Library/Application Support/Bitcoin/ on Mac OSX. It also requires at least version 22.0.0 for I2P support to be present. After following the following instructions, you should have a private Bitcoin node which uses I2P for I2P connections, and Tor for .onion and clearnet -connections, so that all your connections are anonymized. For convenience, +connections, so that all your connections are anonymous. For convenience, Windows users should open their Bitcoin Data Directory by opening the start menu and searching for "Run." Inside the run prompt, type "%APPDATA%\Bitcoin" and press enter. From 5956da28a2603cbc577aa4c1e38c0789a5b3549f Mon Sep 17 00:00:00 2001 From: idk Date: Tue, 21 Sep 2021 18:50:28 -0400 Subject: [PATCH 8/9] fix capital in bitcoin post --- i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst b/i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst index 6e385b1b..9f77177d 100644 --- a/i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst +++ b/i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst @@ -88,7 +88,7 @@ the following Tor related configuration options:: onion=127.0.0.1:9050 onlynet=tor -Finally, you'll need to "Include" these configuration options in your Bitcoin +Finally, you'll need to "include" these configuration options in your Bitcoin configuration file, called "bitcoin.conf" in the Data Directory. Add these two lines to your bitcoin.conf file:: From 4837bac9a15d301a3d0ea7b106e8fab1c4fea0ed Mon Sep 17 00:00:00 2001 From: idk Date: Tue, 21 Sep 2021 18:54:47 -0400 Subject: [PATCH 9/9] fix capital in bitcoin post --- i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst b/i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst index 9f77177d..88bb3751 100644 --- a/i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst +++ b/i2p2www/blog/2021/09/18/i2p-bitcoin.draft.rst @@ -63,7 +63,10 @@ Getting Bitcoin itself launched in an anonymous mode still requires editing some configuration files in the Bitcoin Data Directory, which is %APPDATA%\Bitcoin on Windows, ~/.bitcoin on Linux, and ~/Library/Application Support/Bitcoin/ on Mac OSX. It also requires at least version 22.0.0 for I2P support to be present. -After following the following instructions, you should have a private Bitcoin +{%- endtrans %} + +{% trans -%} +After following these instructions, you should have a private Bitcoin node which uses I2P for I2P connections, and Tor for .onion and clearnet connections, so that all your connections are anonymous. For convenience, Windows users should open their Bitcoin Data Directory by opening the start menu