Update bundle news

Fix blog post URL

.github/workflows/sync.yaml

@@ -0,0 +1,66 @@
+# GitHub Actions workflow file to sync an external repository to this GitHub mirror.
+# This file was automatically generated by go-github-sync.
+#
+# The workflow does the following:
+# - Runs on a scheduled basis (and can also be triggered manually)
+# - Clones the GitHub mirror repository
+# - Fetches changes from the primary external repository
+# - Applies those changes to the mirror repository
+# - Pushes the updated content back to the GitHub mirror
+#
+# Authentication is handled by the GITHUB_TOKEN secret provided by GitHub Actions.
+
+jobs:
+  sync:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Validate Github Actions Environment
+        run: if [ "$GITHUB_ACTIONS" != "true" ]; then echo 'This script must be run in a GitHub Actions environment.'; exit 1; fi
+      - name: Checkout GitHub Mirror
+        uses: actions/checkout@v3
+        with:
+          fetch-depth: 0
+      - name: Configure Git
+        run: |-
+          git config user.name 'GitHub Actions'
+          git config user.email 'actions@github.com'
+      - env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        name: Sync Primary Repository
+        run: |-
+          # Add the primary repository as a remote
+          git remote add primary https://i2pgit.org/I2P_Developers/i2p.newsxml.git
+
+          # Fetch the latest changes from the primary repository
+          git fetch primary
+
+          # Check if the primary branch exists in the primary repository
+          if git ls-remote --heads primary master | grep -q master; then
+            echo "Primary branch master found in primary repository"
+          else
+            echo "Error: Primary branch master not found in primary repository"
+            exit 1
+          fi
+
+          # Check if we're already on the mirror branch
+          if git rev-parse --verify --quiet master; then
+            git checkout master
+          else
+            # Create the mirror branch if it doesn't exist
+            git checkout -b master
+          fi
+
+
+          # Force-apply all changes from primary, overriding any conflicts
+          echo "Performing force sync from primary/master to master"
+          git reset --hard primary/master
+
+
+          # Push changes back to the mirror repository
+          git push origin master
+name: Sync Primary Repository to GitHub Mirror
+"on":
+  push: {}
+  schedule:
+    - cron: 0 * * * *
+  workflow_dispatch: {}

.gitignore

@@ -7,4 +7,8 @@
 build
 logs
 etc/*custom*
-build.old
+build.old
+/certificates
+/blocklist.txt
+news.su3
+news.xml

.tx/config

@@ -2,7 +2,7 @@
 host = https://www.transifex.com
 lang_map = ru_RU: ru, sv_SE: sv, tr_TR: tr, uk_UA: uk, zh_CN: zh
 
-[I2P.newsxml]
+[o:otf:p:I2P:r:newsxml]
 file_filter = data/translations/entries.<lang>.html
 source_file = data/entries.html
 source_lang = en

Dockerfile.signing

@@ -1,4 +1,4 @@
-FROM debian:stable
+FROM debian:oldstable
 ENV PATH=/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
 ENV PYTHONPATH=/opt/newsxml
 ENV LANG en_US.UTF-8  

README

@@ -60,12 +60,12 @@ $ xmllint data/entries.html > /dev/null || echo FAIL
 To push the new entry into translations:
 
 $ tx push -s
-$ tx pull -a
+$ tx pull --use-git-timestamps -a
 
 
 To pull translations:
 
-$ tx pull -a
+$ tx pull --use-git-timestamps -a
 
 
 To build the feeds:
@@ -124,6 +124,11 @@ for routers to verify the signature. If you do not have privileges, ask somebody
 does to generate it and check it in.
 Generation requires I2P 0.9.27-12 or higher.
 
+Before signing, create a symlink to the certificates directory in the
+directory you are signing from, usually this will be the `i2p.newsxml` checkout.
+
+        ln -s $HOME/i2p/certificates
+
 Input file is blocklist.txt. Format:
 One IPv4 or IPv6 address or base 64 router hash per line.
 No host names or netmasks (e.g. /24) are allowed.

app.py

@@ -1,133 +0,0 @@
-#!/usr/bin/env python
-#
-# -*- coding: utf-8 -*-
-#
-import flask
-import logging
-import sys
-import os
-
-app = flask.Flask(__name__)
-
-def hit(x):
-    pass
-try:
-    import stats
-    hit = stats.engine.hit
-except ImportError:
-    stats = None
-
-# this is the root path for news.xml server, must end it /
-# i.e. http://news.psi.i2p/news/
-# defaults to /
-ROOT='/'
-port=9696
-if len(sys.argv) > 1:
-    ROOT=sys.argv[1]
-    if len(sys.argv) > 2:
-        port = int(sys.argv[2])
-
-def has_lang(lang):
-    """
-    :return True if we have news for a language:
-    """
-    logging.info("Checking for language: " + lang)
-    if '.' in lang or '/' in lang:
-        return False
-    return os.path.exists(os.path.join(app.static_folder, 'news_{}.su3'.format(lang)))
-
-def serve_platform_feed(osname, branch):
-    logging.info("Serving: "+ osname + " Branch: " + branch)
-    lang = flask.request.args.get('lang', 'en')
-    lang = lang.split('_')[0]
-    hit(lang)
-    fname = os.path.join(osname, branch, 'news.su3')
-    if has_lang(lang):
-        fname = os.path.join(osname, branch, 'news_{}.su3'.format(lang))
-    return serveFile(os.path.join(app.static_folder, fname))
-
-def serveFile(path):
-    logging.info("Serving file: "+ path)
-    return flask.send_file(path)
-
-@app.route('/')
-def index():
-    """
-    serve news stats page
-    """
-    logging.info("Serving news stats page")
-    return flask.render_template('index.html',root=ROOT)
-
-@app.route('/news.su3')
-def news_su3():
-    """
-    serve news.su3
-    """
-    logging.info("Serving standard newsfeed")
-    return serve_platform_feed("", "")
-
-@app.route('/mac-arm64/stable/news.su3')
-def news_mac_arm_stable_su3():
-    """
-    serve mac-arm64/stable/news.su3
-    """
-    return serve_platform_feed("mac-arm64", "stable")
-
-@app.route('/mac/stable/news.su3')
-def news_mac_stable_su3():
-    """
-    serve mac/stable/news.su3
-    """
-    return serve_platform_feed("mac", "stable")
-
-@app.route('/win/beta/news.su3')
-def news_win_beta_su3():
-    """
-    serve win/beta/news.su3
-    """
-    return serve_platform_feed("win", "beta")
-
-@app.route('/netsize.svg')
-def netsize_svg():
-    """
-    generate and serve network size svg
-    """
-    if stats:
-        args = flask.request.args
-        try:
-            window = int(args['window'])
-            tslice = int(args['tslice'])
-            mult = int(args['mult'])
-            resp = flask.Response(stats.engine.netsize(tslice, window, mult))
-            resp.mimetype = 'image/svg+xml'
-            return resp
-        except Exception as e:
-            print (e)
-            flask.abort(503)
-    # we don't have stats to show, stats module not imported
-    flask.abort(404)
-
-
-@app.route('/requests.svg')
-def requests_svg():
-    """
-    generate and serve requests per interval graph 
-    """
-    args = flask.request.args
-    if stats:
-        try:
-            window = int(args['window'])
-            tslice = int(args['tslice'])
-            mult = int(args['mult'])
-            resp = flask.Response(stats.engine.requests(tslice, window, mult))
-            resp.mimetype = 'image/svg+xml'
-            return resp
-        except Exception as e:
-            print (e)
-            flask.abort(503)
-    flask.abort(404)
-
-if __name__ == '__main__':
-    # run it
-    logging.basicConfig(level=logging.INFO)
-    app.run('127.0.0.1', port)

create_new_entry.sh

@@ -11,14 +11,36 @@
 
 ENTRIES=data/$I2P_OS/$I2P_BRANCH/entries.html
 UUIDGEN="`which uuidgen || which uuid`"
-DATE=$(date +%Y-%m-%dT%H:00:00Z)
+if  [ -z "$DATE" ]; then
+    DATE=$(date +%Y-%m-%dT%H:00:00Z)
+    YEAR=$(date +%Y)
+    MONTH=$(date +%m)
+    DAY=$(date +%d)
+else
+    DATE2=$(echo "$DATE" | sed 's/T.*//')
+    YEAR=$(echo "$DATE2" | cut -d - -f 1)
+    MONTH=$(echo "$DATE2" | cut -d - -f 2)
+    DAY=$(echo "$DATE2" | cut -d - -f 3)
+fi
 if [ -z "$HREF" ]; then
-    HREF="http://i2p-projekt.i2p/en/blog/post/"$(date +%Y)/$(date +%-m)/$(date +%-d)"/CHANGEME_URL_HERE"
+    if [ ! -z "$CHANGEME_URL_HERE" ]; then
+        CHANGEME_URL_HERE=CHANGEME_URL_HERE
+    else
+        CHANGEME_URL_HERE=$(echo "$TITLE" | tr "[:upper:]" "[:lower:]" | sed 's| |_|g')
+    fi
+    HREF="http://i2p-projekt.i2p/en/blog/post/$YEAR/$MONTH/$DAY/$CHANGEME_URL_HERE"
 fi
 TITLE=${TITLE:-TITLE_HERE}
 AUTHOR=${AUTHOR:-AUTHOR_HERE}
+if [ -z "$SUMMARY_HERE" ]; then
+    SUMMARY_HERE="SUMMARY_HERE"
+fi
 
-sed -i "3i <article\n  id=\"urn:uuid:`$UUIDGEN`\"\n  title=\"$TITLE\"\n  href=\"$HREF\"\n  author=\"$AUTHOR\"\n  published=\"$DATE\"\n  updated=\"$DATE\">\n<details>\n<summary>SUMMARY_HERE</summary>\n</details>\n<p>\n\n</p>\n</article>\n\n\n" $ENTRIES
+if [ -z "$CONTENT_HERE" ]; then
+    CONTENT_HERE="<p>\n\n</p>"
+fi
+
+sed -i "3i <article\n  id=\"urn:uuid:`$UUIDGEN`\"\n  title=\"$TITLE\"\n  href=\"$HREF\"\n  author=\"$AUTHOR\"\n  published=\"$DATE\"\n  updated=\"$DATE\">\n<details>\n<summary>$SUMMARY_HERE</summary>\n</details>\n$CONTENT_HERE\n</article>\n\n\n" $ENTRIES
 
 if [ ! -z "$EDITOR" ]; then
     case "$EDITOR" in

data/blocklist.xml

@@ -1,6 +1,125 @@
-  <i2p:blocklist signer="zzz@mail.i2p" sig="6:JKPab5sCZ82UiCkL45Gmr5zEVHGMYtcWVIbo07EVXPZJHATE-ShwCgE8PDqv468tlLhRGw3zWl92-AwkC1rTD5yhs08q7gdRiRkUzLqNASuEeIJZ~6wXoKXwSVGd2YnjWKT40IcbuYVr1JVpr6w9NSDbcv52yWGo7IFXzZNgHzaQ7lFkYSwr4YJyd6xY7uaI3Vq0039WlbKDk6hPLpjuVe4elEPyH7m-ciz~0ir2q~tFhw2aKBBWGr9hzZo~BoXWif5U37T-o-l9nBC4rz3XBCmb0vWdJh9~azJw5KsRLdCk66Riyeueyh86A8UIhT3yvJnUx92MKvDJv1gTLOOTTjer8vqG6K~vLx8IoK1OJ2DpB0I5M9KMlMfvgCcq8H5daCGp9xYPfh8HDiWbwtPGbSprHnNINv8ZdrXT1nuF87MUkyWZqmHb9Qf9FfuWvaVzHSoDNkgbC70Vaj0yTmPLaxEsKE2ffFLdEaRYcTWlJJZsWuO-bAtmN1hmXXEZxu1dM0k-EOEUSj-xvEPG5yleMKhmYUBItqfCJmoewWgCQgtxfz3Q1WdYX9HPYUHjhEPinwykS7F-rUICIT1BMKMZ3Hte-NmsdRvEGnr6OWdQLztoMMmmieS0tc7poHQYSqKRwfZ7FB2dGjhQhl7oGPNoYbGQ-lXqOGr3WwSUE-SU8bg=">
-    <updated>2022-07-13T19:15:49Z</updated>
+  <i2p:blocklist signer="zzz@mail.i2p" sig="6:NUAbQZOcQOlRUAnLxjFsrxNfia6ckgqJ-164bLe7lVI8GfaKT61CjXb22DEFnDXri8buGVAOTs0PN-R-J2i4fRUp5qoW2JfZkRafWc~YAuwyMjoytx6aTKOkjJA-OZYFiLHA0sbodDagUajOsBVpwdF97GtNH2f9FyRy9f9j68jV-cGqPh4VEXbk50jFfL4v~ABhuj2xUbNmdJseKP2bQkC21kd0qMqeNfd0Wxpy9Ij-IODHV0tzd-JqgMntXBshMPWE5ywOfuCIpqMCvjvHIYlKKxOmi0e1Khx5wsJ0BnP-JdXB9xbLh0PUeFpZCDuxweOYPb~kihON85xLttRmcSXQ6wGfXechWzqx8bcWqhs501pUBvakEwPFgkkHG-tMHBfJPfLY~xCHGXOOOT0xNtEDuGyDbc-dA1D38a5O6ImKUW4xZUvv~NbQFG8zKfEIVJ5PHg1Ch2sqNB0NMNOP8DxZw311D-vR~yZndk11W~j8S7WLN7tor4t4FTGnPO1gdoMSW-NXR8wlnrkbEFrt6m-HVKZsf18mL~9T~dqaihWBuWi8mcX9ZfseuXdou-ip~FK4ktXVUNBKOADUseykp2GTgQYhZK~QCjppEILmVcf1LyIULqIFvOUhC6JZUX62xsM8jpCuBw3t2o7CjxzZYqRH55zeDDVrfGMAMR~IjKw=">
+    <updated>2025-05-11T22:04:43Z</updated>
     <i2p:block>93.157.12.248</i2p:block>
+    <i2p:block>185.213.155.252</i2p:block>
+    <i2p:block>223.167.199.60</i2p:block>
+    <i2p:block>2a03:1b20:6:f011:0:0:0:a02e</i2p:block>
     <i2p:block>JbifzqZZqeTXtxK6KDqNUPWaW-phKqeS~tfJT82SIYI=</i2p:block>
     <i2p:block>QPUV1bW6arN2zp3gTBMvOEvgSuKbXUqk2oqHkb~UoSw=</i2p:block>
+    <i2p:block>CyLg6w8lypk1gnAX-CdG8O4NCR86hq8ifge6QKXAoJg=</i2p:block>
+    <i2p:block>DtQsGzkbeR3nilr6ZvywR2O7-f0XaaV~YfHXohqwjgI=</i2p:block>
+    <i2p:block>lam824jtkYq4qTiZHT~TkdHoVTVRwnLghgFheZbgDhU=</i2p:block>
+    <i2p:block>Qqj3p9F0Y~qXAkSz3FYo~e~OfSgaM5qZ2OYUrzOtrgM=</i2p:block>
+    <i2p:block>NUo2wncm49XY8f~dzdxII5fnVopL9oT92KC9JC3IOFY=</i2p:block>
+    <i2p:block>GEpq15rG0XjIvP7oZCW9cmL8Dhb8eLSweTU3hZuT2fE=</i2p:block>
+    <i2p:block>aNBK4IQwYCejjMnD31hapWQvova~u1OINPnHCqceljw=</i2p:block>
+    <i2p:block>6lWUeurYBX4w6lsfPdkAxbFKXoGEXKxofXwlWOC3RQA=</i2p:block>
+    <i2p:block>xKAdoKJUvrSEGS0gREC4lEUawa4IKsVnQU189X~QQhk=</i2p:block>
+    <i2p:block>2EJgHsXnjQo8gHt-jmS-GlhXjqtHnNgWiK~QyQ0Rsh4=</i2p:block>
+    <i2p:block>o-atVIIK0N2Eu6r2Nq42cAVqlK6wJGrXqU0Ps3x0HmY=</i2p:block>
+    <i2p:block>2C-fFbGjOJks1mDYxlQ~~M3Q-tX9Dx~tyAUHPzfct~E=</i2p:block>
+    <i2p:block>Qc5rvLavMYNhzQBQfBgFkZbesEvGW~3nz1ZwllR1MoM=</i2p:block>
+    <i2p:block>0bLUiXtgYCzAy3533C~wjaUxUkH63JGSRlx2huH-6Bo=</i2p:block>
+    <i2p:block>3~ZOYyQFJAJXxuynetnoijOFjliGGmN9kZ5BkiSupy0=</i2p:block>
+    <i2p:block>4V3EsOGTWrIXJDNaGpOLZrnSGWgSxwgZ7Tsxb0txFtE=</i2p:block>
+    <i2p:block>4yr5497JpDG-K7s1unMbvWBPPfds72Qw27DNH9FpcKQ=</i2p:block>
+    <i2p:block>5MAAvwKgnG7hYbi93q0Luro~-AyIjO5xvUbABc2T3IU=</i2p:block>
+    <i2p:block>5SI8wX-KUefASp0KbjuQ2KaCyZboFHcsXsgwaONVqzc=</i2p:block>
+    <i2p:block>6lKXyJfzTrrt2B7R-p24FSMQQHmyPBb1JSp1N49wdrM=</i2p:block>
+    <i2p:block>6yUKWdxJKF0wtxd3Ro0VfkSlLe74gvM2b0IJbzm~mT0=</i2p:block>
+    <i2p:block>7NzcMy-ty6WICyPHbYBuGQlbcMs7dV-5lN2HIZ-PvuY=</i2p:block>
+    <i2p:block>9ELLjPmb9PBMTOeXqMsRmRfLRlctQMELTZFrkDBOiVA=</i2p:block>
+    <i2p:block>AQ2Wq8Guob3CI1jve~W5wErlaaSF-iZz9mhzKsFmWeo=</i2p:block>
+    <i2p:block>BhqgIK5aTiL8UosUjmBMsCl5NtNCFCZTu0wUSFt0Mkg=</i2p:block>
+    <i2p:block>cC8PmCV4AehT0hKPAfp3yP1DYJKFxmWBk8JWSVZT8Oo=</i2p:block>
+    <i2p:block>cfhT8b5PNxSIFhmg-6ZvP78W5eD9jtGBLjM~oIRRqoE=</i2p:block>
+    <i2p:block>fGe1bjAyj-V0kRJmbXbCGp9y0ZVkYDZksdvfBwo2nME=</i2p:block>
+    <i2p:block>G7d8g3yIjMTG1M6ui1zWf-YYYe0K3Pz8dCg~gRHM-KI=</i2p:block>
+    <i2p:block>Giy8ehFNw~RyB5KV5BCMzgMUMxVI2hiWFS3gdWPthCA=</i2p:block>
+    <i2p:block>HPDYhgrDNJK0STyIJM-A3Q~aMU9D63P-7Bw-Qs15Bmk=</i2p:block>
+    <i2p:block>I5rpywP3dJsP1bfKzp-QUsRCNgT2sO7sTqxuH8~AjmQ=</i2p:block>
+    <i2p:block>ioBAP6QWbWpzkUbmpKn2eWe~XlNmFuIsTJxvstMt2hU=</i2p:block>
+    <i2p:block>jizbTEmYpthOrW2louGRyR057W9G4vcOKtvk~lPqvYg=</i2p:block>
+    <i2p:block>JtgxUY6P7VcgJV3HQUzAaUSVInTR20PT8E34xvwkEck=</i2p:block>
+    <i2p:block>kISWAKZmX0n9C~vQ19oTdL9iWdLs1BfDrssNiZunubw=</i2p:block>
+    <i2p:block>krZK4oqwsee2Qsevb9b9n5jGuNrVaTJlt-nE8G8ft5w=</i2p:block>
+    <i2p:block>lj1A58-iv9W4V9r-jrHZISKncWlSYaQCYvQcBvZppEg=</i2p:block>
+    <i2p:block>N9GkaK294wlSRKaUicSimnxDwebUWKggFlrBUpe00KA=</i2p:block>
+    <i2p:block>Oy4ZaiVxxel1XAWW1p23JlekMGEFvWbWuizQMRnG~tc=</i2p:block>
+    <i2p:block>q1rjeEo0hB61qIcER59aEdQWsX8-gpW-K862deAJkp0=</i2p:block>
+    <i2p:block>QYkhWCudqWhty-TvJ-sFd0z5uLYBXHW5t61L-I6ltJU=</i2p:block>
+    <i2p:block>RDX~26d6ugO1C-DEhkEzPQaGHurvfgKL0cXZlqr4C6Y=</i2p:block>
+    <i2p:block>RjBVJtLfMhLgaSNDpv-D4UqybO5GWSgtcJqAqqd6L~Q=</i2p:block>
+    <i2p:block>S7-xKQ1wSqiqmjODZrTWprTD1L0dtiZlwT055DArGFw=</i2p:block>
+    <i2p:block>SdXmd046uxhAvscEM7ogR6HtH2eWBiyo4~XOnj3dr7c=</i2p:block>
+    <i2p:block>Sm6IkscEdA0vBy9Cx~VQcgB2f5e0fvQ2CEu8fkceL1s=</i2p:block>
+    <i2p:block>tFv6N4kwPdOlMXo8VqoOO3UrSsWAg~-5nadozzBm2Tc=</i2p:block>
+    <i2p:block>TJwtpwSS7yANCDPDfbGdx3f4lDQNYcfA-0X75jHbbNU=</i2p:block>
+    <i2p:block>w~1a6nvIBJfFHGur0mPJmjlwjSBOrWGTC-INPEesPJ0=</i2p:block>
+    <i2p:block>wMIJ9Ax~4kW-jkFQLTHfzSSBqaMSy3EKiBH8YUQjAVA=</i2p:block>
+    <i2p:block>wPorvAjMYj6FipnUHruA0dF2K-Xm~GngCY3QDIVlZyU=</i2p:block>
+    <i2p:block>wWP~J-g-e8Fok7NpTURpJJfeNTGB5S7F15QshyRn9n0=</i2p:block>
+    <i2p:block>X52PGfb8TysUDO7pvQIKGeoPcmWx4jwQJjoHLDD7A5Y=</i2p:block>
+    <i2p:block>xirj-SFuNcYapYv7vnkfa2peqqCzuWeKeUB937Odl3s=</i2p:block>
+    <i2p:block>xXvAxpq~FFyNx9bm6XlPVXNQ7vYfGkjC7nj0xWvNjwE=</i2p:block>
+    <i2p:block>YbIKZpPSqdohVjzi8s~N-D0t~bbayKM4hHcBk-fcJvY=</i2p:block>
+    <i2p:block>ynL10zIHBslFPSf1cmAONogYvNm1WrZ9bgE0txHzOr4=</i2p:block>
+    <i2p:block>YSfLfZVPUvvyQtAltBSJ2RHcU~uTiV0x0H4y~QIPczc=</i2p:block>
+    <i2p:block>ZTOVAP9GJYEKu8CjCQBmOigw79oyTVpQQguTDqwv2EU=</i2p:block>
+    <i2p:block>-xH2G0zblY4mRQxeb1WtXAJwyy8hlsrqpY3~fgPBnoU=</i2p:block>
+    <i2p:block>~CrJVoN00MNvEjZIWudnWFzjqDPDsZxKuFq1Y~Sh8fo=</i2p:block>
+    <i2p:block>8ej3XrMgI2IMIwP4X6~h9Nw4vtDV~2yX1nI7u-nOidg=</i2p:block>
+    <i2p:block>o0N6orDrgfMY29G4Z8Q7CRwhSnvw4LuuKhvadrtDsSE=</i2p:block>
+    <i2p:block>tATb9Xe-Tj5QqTm1u1zY1CZlqK0X6Ygn6LjnQBjb55w=</i2p:block>
+    <i2p:block>xnMzPiEhGe2mFuoN8PiB5voV-H2JLk4g5a054mVmFds=</i2p:block>
+    <i2p:block>yb2KWHXrtLdSGG4G53GXjVRilYXFDj7KzsHMLYCNK3o=</i2p:block>
+    <i2p:block>yQN8Qt0K0yi89DrMaMa0LhHpQkxj2X3zS0SATe5QAXI=</i2p:block>
+    <i2p:block>F~UzS1mTN3XYlnOfidMBv5Z4lHI7dsCZ8N5mxpyc-OU=</i2p:block>
+    <i2p:block>6NMfknVMawT~baK0VanEkbXvO2hJCLJ5rreieysRrNE=</i2p:block>
+    <i2p:block>MogB-V71uOsLBu5z9gW5sa3zzUfI5GD43selaYiOy4U=</i2p:block>
+    <i2p:block>~SN8k6Hid107ighTnxRSiwTwwPMjEpPbDEyEY--zD~U=</i2p:block>
+    <i2p:block>ixpaFrLz3C-Fo~6~TOKtQIsHRvmdC~hOFtmJenNz3-Y=</i2p:block>
+    <i2p:block>2l9Eg2BKOmu8hixe~UyElpu~~2RXkhBOM5j8rSqjsKs=</i2p:block>
+    <i2p:block>i1Viub4WK3l-6KbZHifQCY9aGwhU8JG3u5gg5fVJWlM=</i2p:block>
+    <i2p:block>nA-DRzbe33yVHcvITENBWKJ~yVVie6hngoQbB~MoYH0=</i2p:block>
+    <i2p:block>jDFMFtR3wmtuixX0LajCoW1Ko-fSU8sWTtkuqKM9ti8=</i2p:block>
+    <i2p:block>nRTKhTmfXEmpLGe7QmpEPOZr6C3SpX0ke~sgqcX8axA=</i2p:block>
+    <i2p:block>3lgHIOIADdUIoyJjWymzE1Xikx7RojrEBfYT6P7eLzk=</i2p:block>
+    <i2p:block>jhyiaB9Nd2RRVInrmSi0rquBwJaLhhiPemlqj7HGo7k=</i2p:block>
+    <i2p:block>1jhJoqpi5oFB6yvObMwAiiTi7DT8~WTIAd1zh1XSNEM=</i2p:block>
+    <i2p:block>y8q2xWGfKdUzGVkapSZ~wJbqGWJ1vTaPUz0oChBp99M=</i2p:block>
+    <i2p:block>3.225.127.222</i2p:block>
+    <i2p:block>3.234.89.179</i2p:block>
+    <i2p:block>5.250.198.133</i2p:block>
+    <i2p:block>18.210.78.199</i2p:block>
+    <i2p:block>31.155.206.27</i2p:block>
+    <i2p:block>38.242.206.110</i2p:block>
+    <i2p:block>44.210.192.47</i2p:block>
+    <i2p:block>46.53.244.68</i2p:block>
+    <i2p:block>52.60.61.249</i2p:block>
+    <i2p:block>52.70.234.81</i2p:block>
+    <i2p:block>59.56.69.164</i2p:block>
+    <i2p:block>77.165.6.8</i2p:block>
+    <i2p:block>91.138.224.31</i2p:block>
+    <i2p:block>93.235.73.128</i2p:block>
+    <i2p:block>98.15.244.49</i2p:block>
+    <i2p:block>109.197.204.101</i2p:block>
+    <i2p:block>109.197.205.47</i2p:block>
+    <i2p:block>110.137.220.12</i2p:block>
+    <i2p:block>139.59.133.151</i2p:block>
+    <i2p:block>145.239.83.230</i2p:block>
+    <i2p:block>162.55.230.167</i2p:block>
+    <i2p:block>162.218.65.219</i2p:block>
+    <i2p:block>172.6.174.68</i2p:block>
+    <i2p:block>174.27.149.30</i2p:block>
+    <i2p:block>176.88.62.2</i2p:block>
+    <i2p:block>185.209.196.140</i2p:block>
+    <i2p:block>185.209.196.150</i2p:block>
+    <i2p:block>185.209.196.180</i2p:block>
+    <i2p:block>185.65.134.232</i2p:block>
+    <i2p:block>185.65.134.233</i2p:block>
+    <i2p:block>185.65.134.253</i2p:block>
+    <i2p:block>186.166.142.51</i2p:block>
+    <i2p:block>193.32.249.139</i2p:block>
+    <i2p:block>2a03:1b20:6:f011:0:0:0:a07e</i2p:block>
   </i2p:blocklist>

data/entries.html

@@ -1,5 +1,569 @@
 <div>
 <header title="I2P News">News feed, and router updates</header>
+<article
+  id="urn:uuid:f2a6aabd-ee29-4f45-a8dd-7378e907016a"
+  title="2.9.0 Released"
+  href="http://i2p-projekt.i2p/en/blog/post/2025/06/02/2.9.0_released"
+  author="idk"
+  published="2025-06-02T19:00:00Z"
+  updated="2025-06-02T19:00:00Z">
+<details>
+<summary>I2P 2.9.0 Release</summary>
+</details>
+<p>
+I2P 2.9.0 is a maintenance release that includes bug fixes and work on new features.
+</p>
+<p>
+Thread usage has been improved to improve the performance of the i2ptunnel system.
+NTCP2 has been improved to resist probing attacks.
+The notification system has been integrated into more applications to provide better feedback to users from I2PSnark and the other applications.
+Automatic floodfill enrollment has been fixed.
+Users may observe increased resource usage when acting as floodfill.
+If this is not desired, floodfill mode can be disabled on the /config page.
+</p>
+<p>
+A new global map feature is available in the console which shows the locations of routers in your view of the netDb.
+These are the peers that help your router build tunnels and provide services anonymously.
+</p>
+<p>
+Work continues on implementing automatic bandwidth management for tunnels, the Datagram2 protocol, and Post-Quantum cryptography.
+In two releases, at 2.11.0, I2P will require Java 17.
+</p>
+<p>
+As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.
+</p>
+</article>
+
+
+
+<article
+  id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe"
+  title="2.8.2 Released"
+  href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release"
+  author="zzz"
+  published="2025-03-29T12:00:00Z"
+  updated="2025-03-29T12:00:00Z">
+<details>
+<summary>I2P 2.8.2 Release</summary>
+</details>
+<p>
+2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
+The bug primarily affected high-bandwidth routers.
+</p>
+<p>
+As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.
+</p>
+</article>
+
+
+
+<article
+  id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce"
+  title="2.8.1 Released"
+  href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release"
+  author="zzz"
+  published="2025-03-17T14:00:00Z"
+  updated="2025-03-17T14:00:00Z">
+<details>
+<summary>I2P 2.8.1 Release</summary>
+</details>
+<p>
+2.8.1 fixes accesses to local sites that were broken in 2.8.0.
+We have added notification bubbles to several applications in the console to highlight application messages.
+We fixed a tunnel test bug that may have been affecting tunnel reliability.
+The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
+There are several dark theme fixes and improvements.
+</p>
+<p>
+We fixed the installer that previously failed on Java 21 or higher.
+We also fixed installing to directory paths that contain spaces on Linux.
+For those of you that use Docker, we updated outdated Docker container and container libraries.
+</p>
+<p>
+As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.
+</p>
+</article>
+
+
+
+<article
+  id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e"
+  title="Local site access fails in 2.8.0"
+  href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release"
+  author="zzz"
+  published="2025-02-08T16:00:00Z"
+  updated="2025-02-08T16:00:00Z">
+<details>
+<summary>2.8.0 Local Access Bug</summary>
+</details>
+<p>
+In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
+The workaround is using localhost and the server port, usually 7658, to bypass I2P.
+For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
+We apologize for the issue and are working on a fix.
+</p>
+</article>
+
+
+
+<article
+  id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994"
+  title="I2P 2.8.0 Release"
+  href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release"
+  author="idk"
+  published="2025-02-03T13:00:00Z"
+  updated="2025-02-03T13:00:00Z">
+<details>
+<summary>I2P 2.8.0 Release</summary>
+</details>
+<p>
+This release improves I2P by fixing bugs, removing unused code, and improving network stability.
+</p>
+<p>
+We have improved handling of congested routers in the network.
+Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
+We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
+Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.
+</p>
+<p>
+As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.
+</p>
+</article>
+
+
+
+<article
+  id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0"
+  title="I2P 2.7.0 Release"
+  href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release"
+  author="idk"
+  published="2024-10-08T10:00:00Z"
+  updated="2024-10-08T10:00:00Z">
+<details>
+<summary>I2P 2.7.0 Release</summary>
+</details>
+<p>
+This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.
+</p>
+<p>
+Access to information from the console and applications has been improved.
+Issues have been fixed in I2PSnark and SusiMail search.
+The netDB search embedded into the router console now operates in a more intuitive and useful way.
+Minor improvements have been made to diagnostic displays in advanced mode.
+</p>
+<p>
+Bugs have also been fixed to improve compatibility within the network.
+An issue with publishing leaseSets was solved which improves reliability major hidden services.
+I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
+This prevents torrents from being unnecessarily disrupted by these changes.
+We welcomed this contribution from a new contributor.
+A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.
+</p>
+<p>
+As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.
+</p>
+</article>
+
+
+
+<article
+  id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632"
+  title="I2P 2.6.1 Released"
+  href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released"
+  author="idk"
+  published="2024-08-06T13:00:00Z"
+  updated="2024-08-06T13:00:00Z">
+<details>
+<summary>I2P 2.6.1 Release</summary>
+</details>
+<p>
+I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
+This bug caused scrolling to be disabled, rendering some configuration inaccessible.
+</p>
+<p>
+As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.
+</p>
+</article>
+
+
+
+<article
+  id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e"
+  title="I2P 2.6.0 Released"
+  href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released"
+  author="idk"
+  published="2024-07-19T22:00:00Z"
+  updated="2024-07-19T22:00:00Z">
+<details>
+<summary>I2P 2.6.0 Release</summary>
+</details>
+<p>
+This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.
+</p>
+<p>
+Newer routers will be favored when selecting floodfill routers.
+I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
+Legacy transport protocols are being removed, simplifying the code in the UDP transports.
+Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
+Additional tweaks were made to peer selection strategies.
+</p>
+<p>
+I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
+We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
+If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
+Non-exit relays and Tor clients are unaffected by this and do not need to change anything.
+</p>
+<p>
+As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.
+</p>
+</article>
+
+
+
+<article
+  id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf"
+  title="2.5.2 Released"
+  href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release"
+  author="zzz"
+  published="2024-05-15T12:00:00Z"
+  updated="2024-05-15T12:00:00Z">
+<details>
+<summary>2.5.2 with HTTP fix</summary>
+</details>
+<p>
+I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.
+</p>
+<p>
+As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.
+</p>
+</article>
+
+
+
+<article
+  id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a"
+  title="I2P 2.5.1 Released"
+  href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released"
+  author="idk"
+  published="2024-05-06T10:00:00Z"
+  updated="2024-05-06T10:00:00Z">
+<details>
+<summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary>
+</details>
+<p>
+I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
+With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
+This should help the network return to normal operation.
+Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
+Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.
+</p>
+<p>
+As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.
+</p>
+</article>
+
+
+
+<article
+  id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d"
+  title="Stormy Weather"
+  href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather"
+  author="idk"
+  published="2024-04-25T22:00:00Z"
+  updated="2024-04-25T22:00:00Z">
+<details>
+<summary>Network Weather: Stormy. I2P is under attack.</summary>
+</details>
+<p>
+The I2P network is currently under a Denial-of-Service attack.
+This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
+Reachability of I2P sites is badly degraded.
+</p>
+<p>
+If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
+Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.
+</p>
+</article>
+
+
+
+<article
+  id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3"
+  title="New Release I2P 2.5.0"
+  href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0"
+  author="idk"
+  published="2024-04-08T10:00:00Z"
+  updated="2024-04-08T10:00:00Z">
+<details>
+<summary>More Application Improvements, Audit of NetDB Isolation strategy</summary>
+</details>
+<p>
+This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.
+</p>
+<p>
+New features have been added to I2PSnark like the ability to search through torrents.
+Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
+We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
+New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
+Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
+<p>
+During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
+This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
+This investigation uncovered one minor isolation-piercing event which we repaired.
+This issue was discovered and fixed internally by the I2P team.
+</p>
+<p>
+During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
+This should result in improved delivery and availability for these downstream products.
+</p>
+<p>
+As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.
+</p>
+</article>
+
+
+
+<article
+  id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7"
+  title="I2P 2.4.0 Release with Congestion and NetDB Security improvements"
+  href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0"
+  author="idk"
+  published="2023-12-18T20:00:00Z"
+  updated="2023-12-18T20:00:00Z">
+<details>
+<summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary>
+</details>
+<p>
+This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
+It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.
+</p>
+<p>
+The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
+This will help the network limit the effect of tunnel spam.
+It will also help the network heal during and after DDOS attacks.
+</p>
+<p>
+The NetDb changes also help secure individual routers and the applications that use them. 
+Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
+This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.
+</p>
+<p>
+Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.
+</p>
+<p>
+As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.
+</p>
+</article>
+
+
+
+<article
+  id="urn:uuid:"
+  title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API"
+  href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0"
+  author="idk"
+  published="2023-06-25T12:00:00Z"
+  updated="2023-06-25T12:00:00Z">
+<details>
+<summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary>
+</details>
+<p>
+This release contains fixes for CVE-2023-36325.
+CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
+An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
+The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
+The attacker then sends the same message directly to the router.
+The router passes the message to the bloom filter, and is dropped.
+This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
+This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
+Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
+Users of Java I2P are recommended to update immediately to avoid the attack.
+</p>
+<p>
+In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
+This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.
+</p>
+<p>
+This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.
+</p>
+<p>
+This release also contains a tweakable blocklist.
+Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
+Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
+This feature is off-by-default and is only recommended for advanced users at this time.
+</p>
+<p>
+This release also includes an API for plugins to modify with the Desktop GUI(DTG).
+It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.
+</p>
+<p>
+As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.
+</p>
+</article>
+
+<article
+  id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5"
+  title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid"
+  href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1"
+  author="idk"
+  published="2023-04-12T03:00:00Z"
+  updated="2023-04-12T03:00:00Z">
+<details>
+<summary>I2P 2.2.1 - maintenance release for 2.2.0</summary>
+</details>
+<p>
+After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
+This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
+Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
+This issue has also been resolved.
+The docker container is now also compatible with Podman.
+</p>
+<p>
+This release syncs translations with transifex and updates the GeoIP database.
+</p>
+<p>
+As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.
+</p>
+</article>
+
+
+
+<article
+  id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362"
+  title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem"
+  href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0"
+  author="idk"
+  published="2023-03-13T17:00:00Z"
+  updated="2023-03-13T17:00:00Z">
+<details>
+<summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary>
+</details>
+<p>
+We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
+This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
+The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.
+</p>
+<p>
+This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
+This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
+This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
+We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.
+</p>
+<p>
+As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
+zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
+As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
+We thank zzz for providing these services for such a long time.
+</p>
+<p>
+As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.
+</p>
+</article>
+
+
+
+<article
+  id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7"
+  title="DDoS Update"
+  href="http://zzz.i2p/topics/3593"
+  author="zzz"
+  published="2023-02-14T19:00:00Z"
+  updated="2023-02-14T19:00:00Z">
+<details>
+<summary>DDoS Update</summary>
+</details>
+<p>
+We have confirmed that the attacker controls a large number of routers.
+Our investigations and mitigations continue.
+</p><p>
+This is a good time to remind people that even after 20 years, the I2P network is relatively small.
+We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
+However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
+The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.
+</p><p>
+We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
+We ask for your patience as we work to improve I2P.
+</p>
+</article>
+
+
+
+<article
+  id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d"
+  title="About the recent Denial of Service attacks"
+  href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks"
+  author="sadie,idk"
+  published="2023-02-09T23:00:00Z"
+  updated="2023-02-09T23:00:00Z">
+<details>
+<summary>I2P remains intact with impaired performance</summary>
+</details>
+<p>
+  The I2P network is currently being affected by a Denial of Service attack.
+  The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
+  Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
+  Mitigation strategies are being investigated and implemented gradually.
+</p>
+<p>
+  While the attack has degraded performance, the network remains intact and usable.
+  Java I2P routers appear to be handling the issues better than i2pd routers for now.
+  Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.
+</p>
+</article>
+
+
+
+<article
+  id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007"
+  title="2.1.0 Released"
+  href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release"
+  author="zzz"
+  published="2023-01-09T12:00:00Z"
+  updated="2023-01-09T12:00:00Z">
+<details>
+<summary>2.1.0 with numerous SSU2 fixes</summary>
+</details>
+<p>
+We have learned several things since our 2.0.0 release in November.
+As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
+First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
+Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
+Cumulatively, the effects of these bugs have reduced the performance of the network.
+</p><p>
+Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
+possibly triggered by Bitcoin's new I2P transient address feature,
+but made worse by our SSU2 bugs and other congestion control problems.
+We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
+We have improved our algorithms to reduce network load during times of congestion.
+We are also collaborating with i2pd to develop common congestion control strategies.
+</p><p>
+Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
+i2pd released their version 2.45.0 last week and the early results are encouraging.
+New protocols, and distributed networks, are difficult to develop.
+Congestion can arrive with little warning and with little clue of the cause.
+Thank you for your patience as we have diagnosed and hopefully fixed the problems.
+</p><p>
+As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.
+</p>
+</article>
+
+
+
 
 <article
   id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2"

data/mac-arm64/stable/entries.html

@@ -1,6 +1,29 @@
 <div>
     <header title="I2P News">News feed, and router updates</header>
 
+<article
+  id="urn:uuid:59d8a3ea-aa97-4770-965e-c0ab4e61307b"
+  title="OSX Release Status"
+  href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release"
+  author="zzz"
+  published="2023-01-09T13:00:00Z"
+  updated="2023-01-09T13:00:00Z">
+<details>
+<summary>OSX Support Update</summary>
+</details>
+<p>
+Unfortunately we were unable to release a 2.0.0 OSX Easy-Install Bundle in December as promised.
+As the 2.1.0 release was accelerated by six weeks, we will not be releasing 2.0.0.
+We are now focused on the build and release for the 2.1.0 Bundle.
+</p><p>
+We will make an annoucement here in the news feed when it is ready.
+You may check our <a href="http://zzz.i2p/">development forum</a> for the latest status.
+Thanks for your patience.
+</p>
+</article>
+
+
+
 <article
   id="urn:uuid:593f667a-4260-4042-b32d-360f4c4455c9"
   title="2.0.0 OSX Release Delayed"

data/mac/stable/entries.html

@@ -1,6 +1,29 @@
 <div>
     <header title="I2P News">News feed, and router updates</header>
 
+<article
+  id="urn:uuid:59d8a3ea-aa97-4770-965e-c0ab4e61307b"
+  title="OSX Release Status"
+  href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release"
+  author="zzz"
+  published="2023-01-09T13:00:00Z"
+  updated="2023-01-09T13:00:00Z">
+<details>
+<summary>OSX Support Update</summary>
+</details>
+<p>
+Unfortunately we were unable to release a 2.0.0 OSX Easy-Install Bundle in December as promised.
+As the 2.1.0 release was accelerated by six weeks, we will not be releasing 2.0.0.
+We are now focused on the build and release for the 2.1.0 Bundle.
+</p><p>
+We will make an annoucement here in the news feed when it is ready.
+You may check our <a href="http://zzz.i2p/">development forum</a> for the latest status.
+Thanks for your patience.
+</p>
+</article>
+
+
+
 <article
   id="urn:uuid:49bc001e-4b3b-46a4-a255-9efd2104282b"
   title="2.0.0 OSX Release Delayed"

data/releases.json

@@ -1,15 +1,15 @@
 [
   {
-    "date": "2022-11-21",
-    "version": "2.0.0",
+    "date": "2025-03-29",
+    "version": "2.9.0",
     "minVersion": "0.9.9",
     "minJavaVersion": "1.8",
     "updates": {
       "su3": {
-        "torrent": "magnet:?xt=urn:btih:a50f8479a39896f00431d7b500447fe303d2b6b5&dn=i2pupdate-2.0.0.su3&tr=http://tracker2.postman.i2p/announce.php",
+        "torrent": "magnet:?xt=urn:btih:78d9f15e58a405f32be7b6ee50f30aeaa5c98460&dn=i2pupdate-2.9.0.su3&tr=http://tracker2.postman.i2p/announce.php",
         "url": [
-          "http://stats.i2p/i2p/2.0.0/i2pupdate.su3",
-          "http://mgp6yzdxeoqds3wucnbhfrdgpjjyqbiqjdwcfezpul3or7bzm4ga.b32.i2p/releases/2.0.0/i2pupdate.su3"
+          "http://mgp6yzdxeoqds3wucnbhfrdgpjjyqbiqjdwcfezpul3or7bzm4ga.b32.i2p/2.9.0/i2pupdate.su3",
+          "http://stats.i2p/i2p/2.9.0/i2pupdate.su3"
         ]
       }
     }

data/translations/entries.ar.html

@@ -1,5 +1,174 @@
 <div>
-<header title="أخبار I2P">الخلاصة الإخبارية، وتحديثات التوجيه</header><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
+<header title="أخبار I2P">الخلاصة الإخبارية، وتحديثات التوجيه</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
+The bug primarily affected high-bandwidth routers.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
+We have added notification bubbles to several applications in the console to highlight application messages.
+We fixed a tunnel test bug that may have been affecting tunnel reliability.
+The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
+There are several dark theme fixes and improvements.</p>
+<p>We fixed the installer that previously failed on Java 21 or higher.
+We also fixed installing to directory paths that contain spaces on Linux.
+For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
+The workaround is using localhost and the server port, usually 7658, to bypass I2P.
+For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
+We apologize for the issue and are working on a fix.</p>
+</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
+<p>We have improved handling of congested routers in the network.
+Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
+We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
+Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
+<p>Access to information from the console and applications has been improved.
+Issues have been fixed in I2PSnark and SusiMail search.
+The netDB search embedded into the router console now operates in a more intuitive and useful way.
+Minor improvements have been made to diagnostic displays in advanced mode.</p>
+<p>Bugs have also been fixed to improve compatibility within the network.
+An issue with publishing leaseSets was solved which improves reliability major hidden services.
+I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
+This prevents torrents from being unnecessarily disrupted by these changes.
+We welcomed this contribution from a new contributor.
+A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
+This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
+<p>Newer routers will be favored when selecting floodfill routers.
+I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
+Legacy transport protocols are being removed, simplifying the code in the UDP transports.
+Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
+Additional tweaks were made to peer selection strategies.</p>
+<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
+We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
+If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
+Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
+With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
+This should help the network return to normal operation.
+Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
+Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
+This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
+Reachability of I2P sites is badly degraded.</p>
+<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
+Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
+</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
+<p>New features have been added to I2PSnark like the ability to search through torrents.
+Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
+We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
+New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
+Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
+<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
+This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
+This investigation uncovered one minor isolation-piercing event which we repaired.
+This issue was discovered and fixed internally by the I2P team.</p>
+<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
+This should result in improved delivery and availability for these downstream products.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
+It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
+<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
+This will help the network limit the effect of tunnel spam.
+It will also help the network heal during and after DDOS attacks.</p>
+<p>The NetDb changes also help secure individual routers and the applications that use them. 
+Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
+This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
+<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
+CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
+An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
+The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
+The attacker then sends the same message directly to the router.
+The router passes the message to the bloom filter, and is dropped.
+This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
+This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
+Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
+Users of Java I2P are recommended to update immediately to avoid the attack.</p>
+<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
+This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
+<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
+<p>This release also contains a tweakable blocklist.
+Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
+Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
+This feature is off-by-default and is only recommended for advanced users at this time.</p>
+<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
+It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
+This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
+Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
+This issue has also been resolved.
+The docker container is now also compatible with Podman.</p>
+<p>This release syncs translations with transifex and updates the GeoIP database.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
+This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
+The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
+<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
+This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
+This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
+We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
+<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
+zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
+As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
+We thank zzz for providing these services for such a long time.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
+Our investigations and mitigations continue.</p>
+<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
+We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
+However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
+The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
+<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
+We ask for your patience as we work to improve I2P.</p>
+</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
+  The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
+  Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
+  Mitigation strategies are being investigated and implemented gradually.</p>
+<p>While the attack has degraded performance, the network remains intact and usable.
+  Java I2P routers appear to be handling the issues better than i2pd routers for now.
+  Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
+</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
+As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
+First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
+Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
+Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
+<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
+possibly triggered by Bitcoin's new I2P transient address feature,
+but made worse by our SSU2 bugs and other congestion control problems.
+We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
+We have improved our algorithms to reduce network load during times of congestion.
+We are also collaborating with i2pd to develop common congestion control strategies.</p>
+<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
+i2pd released their version 2.45.0 last week and the early results are encouraging.
+New protocols, and distributed networks, are difficult to develop.
+Congestion can arrive with little warning and with little clue of the cause.
+Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
+<p>كالعادة ، نوصي بالتحديث لهذا الإصدار. أفضل طريقة
+للحفاظ على الأمان ومساعدة الشبكة هي بتشغيل أحدث إصدار. </p>
+</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
 <p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
 <p>كالعادة ، نوصي بالتحديث لهذا الإصدار. أفضل طريقة
 للحفاظ على الأمان ومساعدة الشبكة هي بتشغيل أحدث إصدار. </p>

data/translations/entries.ast.html

@@ -1,5 +1,174 @@
 <div>
-<header title="Noticies de I2P">Cahal (feed) de noticies, y anovamientos del router</header><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
+<header title="Noticies de I2P">Cahal (feed) de noticies, y anovamientos del router</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
+The bug primarily affected high-bandwidth routers.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
+We have added notification bubbles to several applications in the console to highlight application messages.
+We fixed a tunnel test bug that may have been affecting tunnel reliability.
+The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
+There are several dark theme fixes and improvements.</p>
+<p>We fixed the installer that previously failed on Java 21 or higher.
+We also fixed installing to directory paths that contain spaces on Linux.
+For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
+The workaround is using localhost and the server port, usually 7658, to bypass I2P.
+For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
+We apologize for the issue and are working on a fix.</p>
+</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
+<p>We have improved handling of congested routers in the network.
+Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
+We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
+Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
+<p>Access to information from the console and applications has been improved.
+Issues have been fixed in I2PSnark and SusiMail search.
+The netDB search embedded into the router console now operates in a more intuitive and useful way.
+Minor improvements have been made to diagnostic displays in advanced mode.</p>
+<p>Bugs have also been fixed to improve compatibility within the network.
+An issue with publishing leaseSets was solved which improves reliability major hidden services.
+I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
+This prevents torrents from being unnecessarily disrupted by these changes.
+We welcomed this contribution from a new contributor.
+A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
+This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
+<p>Newer routers will be favored when selecting floodfill routers.
+I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
+Legacy transport protocols are being removed, simplifying the code in the UDP transports.
+Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
+Additional tweaks were made to peer selection strategies.</p>
+<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
+We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
+If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
+Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
+With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
+This should help the network return to normal operation.
+Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
+Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
+This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
+Reachability of I2P sites is badly degraded.</p>
+<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
+Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
+</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
+<p>New features have been added to I2PSnark like the ability to search through torrents.
+Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
+We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
+New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
+Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
+<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
+This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
+This investigation uncovered one minor isolation-piercing event which we repaired.
+This issue was discovered and fixed internally by the I2P team.</p>
+<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
+This should result in improved delivery and availability for these downstream products.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
+It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
+<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
+This will help the network limit the effect of tunnel spam.
+It will also help the network heal during and after DDOS attacks.</p>
+<p>The NetDb changes also help secure individual routers and the applications that use them. 
+Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
+This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
+<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
+CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
+An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
+The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
+The attacker then sends the same message directly to the router.
+The router passes the message to the bloom filter, and is dropped.
+This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
+This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
+Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
+Users of Java I2P are recommended to update immediately to avoid the attack.</p>
+<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
+This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
+<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
+<p>This release also contains a tweakable blocklist.
+Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
+Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
+This feature is off-by-default and is only recommended for advanced users at this time.</p>
+<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
+It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
+This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
+Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
+This issue has also been resolved.
+The docker container is now also compatible with Podman.</p>
+<p>This release syncs translations with transifex and updates the GeoIP database.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
+This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
+The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
+<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
+This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
+This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
+We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
+<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
+zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
+As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
+We thank zzz for providing these services for such a long time.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
+Our investigations and mitigations continue.</p>
+<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
+We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
+However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
+The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
+<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
+We ask for your patience as we work to improve I2P.</p>
+</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
+  The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
+  Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
+  Mitigation strategies are being investigated and implemented gradually.</p>
+<p>While the attack has degraded performance, the network remains intact and usable.
+  Java I2P routers appear to be handling the issues better than i2pd routers for now.
+  Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
+</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
+As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
+First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
+Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
+Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
+<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
+possibly triggered by Bitcoin's new I2P transient address feature,
+but made worse by our SSU2 bugs and other congestion control problems.
+We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
+We have improved our algorithms to reduce network load during times of congestion.
+We are also collaborating with i2pd to develop common congestion control strategies.</p>
+<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
+i2pd released their version 2.45.0 last week and the early results are encouraging.
+New protocols, and distributed networks, are difficult to develop.
+Congestion can arrive with little warning and with little clue of the cause.
+Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
 <p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
 <p>As usual, we recommend that you update to this release. The best way to
 maintain security and help the network is to run the latest release.</p>
@@ -228,7 +397,7 @@ A plan is in place to be in Tails, Debian and Ubuntu Disco. We still need people
 <p>As usual, we recommend that you update to this release. The best way to
 maintain security and help the network is to run the latest release.</p>
 </article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="Espublizáu 0.9.36" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 con NTCP2 y igua de fallos</summary></details><p>0.9.36 contien un protocolu de tresporte nuevu, más seguru llamáu NTCP2.
-&lt;&lt;&lt;ta desactiváu de mou predetermináu, pero puedes activalu pa pruebes añadiendo en &lt;a href="/configadvanced"&gt;configuración avanzada  <tt>i2np.ntcp2.enable=true</tt> y reaniciado.
+ta desactiváu de mou predetermináu, pero puedes activalu pa pruebes añadiendo en configuración avanzada  i2np.ntcp2.enable=true y reaniciado.
 NTCP2 tará activáu nel siguiente llanzamientu.</p>
 <p>This release also contains several performance improvements and bug fixes.</p>
 <p>As usual, we recommend that you update to this release. The best way to

data/translations/entries.az.html

@@ -1,5 +1,173 @@
 <div>
-<header title="I2P Xəbərlər">Xəbər axını və istiqamətləndiricinin yenilənməsi</header><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
+<header title="I2P Xəbərlər">Xəbər axını və istiqamətləndiricinin yenilənməsi</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
+The bug primarily affected high-bandwidth routers.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
+We have added notification bubbles to several applications in the console to highlight application messages.
+We fixed a tunnel test bug that may have been affecting tunnel reliability.
+The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
+There are several dark theme fixes and improvements.</p>
+<p>We fixed the installer that previously failed on Java 21 or higher.
+We also fixed installing to directory paths that contain spaces on Linux.
+For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
+The workaround is using localhost and the server port, usually 7658, to bypass I2P.
+For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
+We apologize for the issue and are working on a fix.</p>
+</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
+<p>We have improved handling of congested routers in the network.
+Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
+We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
+Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
+<p>Access to information from the console and applications has been improved.
+Issues have been fixed in I2PSnark and SusiMail search.
+The netDB search embedded into the router console now operates in a more intuitive and useful way.
+Minor improvements have been made to diagnostic displays in advanced mode.</p>
+<p>Bugs have also been fixed to improve compatibility within the network.
+An issue with publishing leaseSets was solved which improves reliability major hidden services.
+I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
+This prevents torrents from being unnecessarily disrupted by these changes.
+We welcomed this contribution from a new contributor.
+A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
+This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
+<p>Newer routers will be favored when selecting floodfill routers.
+I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
+Legacy transport protocols are being removed, simplifying the code in the UDP transports.
+Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
+Additional tweaks were made to peer selection strategies.</p>
+<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
+We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
+If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
+Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
+With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
+This should help the network return to normal operation.
+Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
+Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
+This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
+Reachability of I2P sites is badly degraded.</p>
+<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
+Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
+</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
+<p>New features have been added to I2PSnark like the ability to search through torrents.
+Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
+We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
+New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
+Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
+<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
+This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
+This investigation uncovered one minor isolation-piercing event which we repaired.
+This issue was discovered and fixed internally by the I2P team.</p>
+<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
+This should result in improved delivery and availability for these downstream products.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
+It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
+<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
+This will help the network limit the effect of tunnel spam.
+It will also help the network heal during and after DDOS attacks.</p>
+<p>The NetDb changes also help secure individual routers and the applications that use them. 
+Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
+This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
+<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
+CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
+An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
+The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
+The attacker then sends the same message directly to the router.
+The router passes the message to the bloom filter, and is dropped.
+This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
+This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
+Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
+Users of Java I2P are recommended to update immediately to avoid the attack.</p>
+<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
+This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
+<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
+<p>This release also contains a tweakable blocklist.
+Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
+Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
+This feature is off-by-default and is only recommended for advanced users at this time.</p>
+<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
+It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
+This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
+Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
+This issue has also been resolved.
+The docker container is now also compatible with Podman.</p>
+<p>This release syncs translations with transifex and updates the GeoIP database.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
+This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
+The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
+<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
+This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
+This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
+We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
+<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
+zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
+As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
+We thank zzz for providing these services for such a long time.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
+Our investigations and mitigations continue.</p>
+<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
+We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
+However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
+The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
+<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
+We ask for your patience as we work to improve I2P.</p>
+</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
+  The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
+  Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
+  Mitigation strategies are being investigated and implemented gradually.</p>
+<p>While the attack has degraded performance, the network remains intact and usable.
+  Java I2P routers appear to be handling the issues better than i2pd routers for now.
+  Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
+</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
+As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
+First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
+Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
+Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
+<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
+possibly triggered by Bitcoin's new I2P transient address feature,
+but made worse by our SSU2 bugs and other congestion control problems.
+We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
+We have improved our algorithms to reduce network load during times of congestion.
+We are also collaborating with i2pd to develop common congestion control strategies.</p>
+<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
+i2pd released their version 2.45.0 last week and the early results are encouraging.
+New protocols, and distributed networks, are difficult to develop.
+Congestion can arrive with little warning and with little clue of the cause.
+Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
+<p>Hər zamanki kimi bu versiyanı yeniləməyi məsləhət görürük. Təhlükəsizliyi qorumaq və şəbəkəyə kömək etmək üçün  ən yaxşı yol son buraxılışı yükləməkdir.</p>
+</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
 <p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
 <p>Hər zamanki kimi bu versiyanı yeniləməyi məsləhət görürük. Təhlükəsizliyi qorumaq və şəbəkəyə kömək etmək üçün  ən yaxşı yol son buraxılışı yükləməkdir.</p>
 </article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Recent Blog Posts" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>

data/translations/entries.cs.html

@@ -1,5 +1,174 @@
 <div>
-<header title="I2P Novinky">News feed, and router updates</header><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
+<header title="I2P Novinky">News feed, and router updates</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
+The bug primarily affected high-bandwidth routers.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
+We have added notification bubbles to several applications in the console to highlight application messages.
+We fixed a tunnel test bug that may have been affecting tunnel reliability.
+The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
+There are several dark theme fixes and improvements.</p>
+<p>We fixed the installer that previously failed on Java 21 or higher.
+We also fixed installing to directory paths that contain spaces on Linux.
+For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
+The workaround is using localhost and the server port, usually 7658, to bypass I2P.
+For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
+We apologize for the issue and are working on a fix.</p>
+</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
+<p>We have improved handling of congested routers in the network.
+Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
+We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
+Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
+<p>Access to information from the console and applications has been improved.
+Issues have been fixed in I2PSnark and SusiMail search.
+The netDB search embedded into the router console now operates in a more intuitive and useful way.
+Minor improvements have been made to diagnostic displays in advanced mode.</p>
+<p>Bugs have also been fixed to improve compatibility within the network.
+An issue with publishing leaseSets was solved which improves reliability major hidden services.
+I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
+This prevents torrents from being unnecessarily disrupted by these changes.
+We welcomed this contribution from a new contributor.
+A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
+This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
+<p>Newer routers will be favored when selecting floodfill routers.
+I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
+Legacy transport protocols are being removed, simplifying the code in the UDP transports.
+Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
+Additional tweaks were made to peer selection strategies.</p>
+<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
+We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
+If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
+Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
+With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
+This should help the network return to normal operation.
+Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
+Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
+This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
+Reachability of I2P sites is badly degraded.</p>
+<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
+Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
+</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
+<p>New features have been added to I2PSnark like the ability to search through torrents.
+Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
+We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
+New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
+Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
+<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
+This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
+This investigation uncovered one minor isolation-piercing event which we repaired.
+This issue was discovered and fixed internally by the I2P team.</p>
+<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
+This should result in improved delivery and availability for these downstream products.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
+It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
+<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
+This will help the network limit the effect of tunnel spam.
+It will also help the network heal during and after DDOS attacks.</p>
+<p>The NetDb changes also help secure individual routers and the applications that use them. 
+Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
+This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
+<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
+CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
+An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
+The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
+The attacker then sends the same message directly to the router.
+The router passes the message to the bloom filter, and is dropped.
+This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
+This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
+Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
+Users of Java I2P are recommended to update immediately to avoid the attack.</p>
+<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
+This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
+<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
+<p>This release also contains a tweakable blocklist.
+Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
+Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
+This feature is off-by-default and is only recommended for advanced users at this time.</p>
+<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
+It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
+This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
+Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
+This issue has also been resolved.
+The docker container is now also compatible with Podman.</p>
+<p>This release syncs translations with transifex and updates the GeoIP database.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
+This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
+The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
+<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
+This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
+This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
+We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
+<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
+zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
+As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
+We thank zzz for providing these services for such a long time.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
+Our investigations and mitigations continue.</p>
+<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
+We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
+However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
+The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
+<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
+We ask for your patience as we work to improve I2P.</p>
+</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
+  The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
+  Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
+  Mitigation strategies are being investigated and implemented gradually.</p>
+<p>While the attack has degraded performance, the network remains intact and usable.
+  Java I2P routers appear to be handling the issues better than i2pd routers for now.
+  Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
+</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
+As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
+First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
+Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
+Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
+<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
+possibly triggered by Bitcoin's new I2P transient address feature,
+but made worse by our SSU2 bugs and other congestion control problems.
+We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
+We have improved our algorithms to reduce network load during times of congestion.
+We are also collaborating with i2pd to develop common congestion control strategies.</p>
+<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
+i2pd released their version 2.45.0 last week and the early results are encouraging.
+New protocols, and distributed networks, are difficult to develop.
+Congestion can arrive with little warning and with little clue of the cause.
+Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
 <p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
 <p>As usual, we recommend that you update to this release. The best way to
 maintain security and help the network is to run the latest release.</p>
@@ -318,10 +487,10 @@ has been implemented for all pages.</p>
 after I2P 0.9.29 is released in mid-February. However, for safety we recommend that you
 <a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
 upgrade manually if you plan on using I2P or I2P-Bote in the intervening time.</p>
-</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="0.9.28 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>0.9.28 contains bug fixes</summary></details><p>0.9.28 contains fixes for over 25 Trac tickets, and updates for a number of bundled software packages including Jetty.
-There are fixes for the IPv6 peer testing feature introduced last release.
-We continue improvements to detect and block peers that are potentially malicious.
-There are preliminary fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
+</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="0.9.28 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>0.9.28 contains bug fixes</summary></details><p>0.9.28 obsahuje opravy více než 25 Trac problémů a aktualizací vestavěných balíčků software, včetně Jetty.
+Jsou zde opravy funkce testování IPv6 peera, která byla představena v minulém vydání.
+Pokračujeme s vylepšeními rozpoznání a blokování peerů, kteří jsou potenciálně nebezpeční.
+Jsou zde předběžné opravy pro Java 9, avšak ještě nedoporučujeme Java 9 pro obecné použití.</p>
 <p>I2P will be at 33C3, please stop by our table and give us your ideas on how to improve the network.
 We will review our 2017 roadmap and priorities 2017 at the Congress.</p>
 <p>As usual, we recommend that all users update to this release.

data/translations/entries.da.html

@@ -0,0 +1,605 @@
+<div>
+<header title="I2P nyheder">Nyhedsfeed og router-opdateringer</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
+The bug primarily affected high-bandwidth routers.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
+We have added notification bubbles to several applications in the console to highlight application messages.
+We fixed a tunnel test bug that may have been affecting tunnel reliability.
+The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
+There are several dark theme fixes and improvements.</p>
+<p>We fixed the installer that previously failed on Java 21 or higher.
+We also fixed installing to directory paths that contain spaces on Linux.
+For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
+The workaround is using localhost and the server port, usually 7658, to bypass I2P.
+For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
+We apologize for the issue and are working on a fix.</p>
+</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
+<p>We have improved handling of congested routers in the network.
+Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
+We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
+Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
+<p>Access to information from the console and applications has been improved.
+Issues have been fixed in I2PSnark and SusiMail search.
+The netDB search embedded into the router console now operates in a more intuitive and useful way.
+Minor improvements have been made to diagnostic displays in advanced mode.</p>
+<p>Bugs have also been fixed to improve compatibility within the network.
+An issue with publishing leaseSets was solved which improves reliability major hidden services.
+I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
+This prevents torrents from being unnecessarily disrupted by these changes.
+We welcomed this contribution from a new contributor.
+A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
+This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
+<p>Newer routers will be favored when selecting floodfill routers.
+I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
+Legacy transport protocols are being removed, simplifying the code in the UDP transports.
+Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
+Additional tweaks were made to peer selection strategies.</p>
+<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
+We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
+If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
+Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
+With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
+This should help the network return to normal operation.
+Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
+Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
+This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
+Reachability of I2P sites is badly degraded.</p>
+<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
+Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
+</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
+<p>New features have been added to I2PSnark like the ability to search through torrents.
+Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
+We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
+New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
+Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
+<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
+This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
+This investigation uncovered one minor isolation-piercing event which we repaired.
+This issue was discovered and fixed internally by the I2P team.</p>
+<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
+This should result in improved delivery and availability for these downstream products.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
+It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
+<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
+This will help the network limit the effect of tunnel spam.
+It will also help the network heal during and after DDOS attacks.</p>
+<p>The NetDb changes also help secure individual routers and the applications that use them. 
+Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
+This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
+<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
+CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
+An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
+The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
+The attacker then sends the same message directly to the router.
+The router passes the message to the bloom filter, and is dropped.
+This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
+This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
+Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
+Users of Java I2P are recommended to update immediately to avoid the attack.</p>
+<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
+This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
+<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
+<p>This release also contains a tweakable blocklist.
+Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
+Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
+This feature is off-by-default and is only recommended for advanced users at this time.</p>
+<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
+It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
+This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
+Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
+This issue has also been resolved.
+The docker container is now also compatible with Podman.</p>
+<p>This release syncs translations with transifex and updates the GeoIP database.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
+This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
+The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
+<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
+This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
+This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
+We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
+<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
+zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
+As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
+We thank zzz for providing these services for such a long time.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
+Our investigations and mitigations continue.</p>
+<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
+We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
+However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
+The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
+<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
+We ask for your patience as we work to improve I2P.</p>
+</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
+  The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
+  Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
+  Mitigation strategies are being investigated and implemented gradually.</p>
+<p>While the attack has degraded performance, the network remains intact and usable.
+  Java I2P routers appear to be handling the issues better than i2pd routers for now.
+  Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
+</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
+As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
+First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
+Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
+Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
+<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
+possibly triggered by Bitcoin's new I2P transient address feature,
+but made worse by our SSU2 bugs and other congestion control problems.
+We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
+We have improved our algorithms to reduce network load during times of congestion.
+We are also collaborating with i2pd to develop common congestion control strategies.</p>
+<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
+i2pd released their version 2.45.0 last week and the early results are encouraging.
+New protocols, and distributed networks, are difficult to develop.
+Congestion can arrive with little warning and with little clue of the cause.
+Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Frigivet" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
+<p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Recent Blog Posts" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>
+<ul>
+<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Overview of our new SSU2 transport</a></li>
+<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">A warning about I2P coins and other scams</a></li>
+<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">An interview with Konrad from diva.exchange</a></li>
+<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">An interview with Dustin from StormyCloud</a></li>
+</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 frigivet" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 med SSU2 til test</summary></details><p>Vi har de tre seneste måneder arbejdet på vores nye UDP transport protokol SSU2
+med et lille antal frivillige testere.
+Denne release færdiggør implementeringen, inklusiv relay og peer testing.
+Vi aktiverer det pr. default for Androud og ARM platforme, og en mindre andel øvrige, tilfældige routere
+Dette muliggør, at vi kan foretage meget mere testning i de næste tre måneder, færdiggøre forbindelsesmigrationsfeaturen,
+samt rette øvrige tilbageværende problemer.
+Vi planlægger at aktivere det for alle i den næste frigivelse, som er planlagt til november.
+Manuel konfiguration er ikke nødvendig.</p>
+<p>Of course, there's the usual collection of bug fixes in this release as well.
+We also added an automatic deadlock detector that has already found a rare deadlock that is now fixed.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="New Outproxy exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>New Outproxy</summary></details><p>I2P "outproxies" (exit nodes) may be used to access the internet through
+your HTTP proxy tunnel.
+As approved at our <a href="http://i2p-projekt.i2p/en/meetings/314">monthly meeting</a>,
+<b>exit.stormycloud.i2p</b> is now our official, recommended outproxy, replacing the long-dead <b>false.i2p</b>.
+For more information on the StormyCloud <a href="http://stormycloud.i2p/">organization</a>,
+<a href="http://stormycloud.i2p/outproxy.html">outproxy</a>,
+and <a href="http://stormycloud.i2p/tos.html">terms of service</a>,
+see the <a href="http://stormycloud.i2p/">StormyCloud website</a>.</p>
+<p>We suggest you change your <a href="/i2ptunnel/edit?tunnel=0">Hidden Services Manager configuration</a>
+to specify <b>exit.stormycloud.i2p</b>
+in two places: <b>Outproxies</b> and <b>SSL Outproxies</b>.
+After editing, <b>scroll down and click Save</b>.
+See our <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">blog post for a screenshot</a>.
+For Android instructions and screenshots see <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">notbob's blog</a>.</p>
+<p>Router updates will not update your configuration, you must edit it manually.
+Thanks to StormyCloud for their support, and please consider a <a href="http://stormycloud.i2p/donate.html">donation</a>.</p>
+</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 with bug fixes</summary></details><p>This release includes bug fixes in i2psnark,
+the router, I2CP, and UPnP.
+Router fixes address bugs in soft restart, IPv6, SSU peer testing,
+network database stores, and tunnel building.
+Router family handling and Sybil classification have also been
+significantly improved.</p>
+<p>Together with i2pd, we are developing our new UDP transport, SSU2.
+SSU2 will bring substantial performance and security improvements.
+It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
+completing the full cryptography upgrade we started about 9 years ago.
+This release contains a preliminary implementation which is disabled by default.
+If you wish to participate in testing, please look for current information
+on zzz.i2p.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Install essential Java/Jpackage updates" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>The recent Java "Psychic Signatues" vulnerability affects I2P. Current users of
+I2P on Linux, or any users of I2P who are using a non-bundled JVM should update
+their JVM or switch to a version which does not contain the vulnerability, below
+Java 15.</p>
+<p>New I2P Easy-Install bundles have been generated using the latest release of the
+Java Virtual Machine. Further details have been published in the respective
+bundle newsfeeds.</p>
+</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 with reliability and performance improvements</summary></details><p>The 1.7.0 release contains several performance and reliability improvements.</p>
+<p>There are now popup messages in the system tray, for those platforms that support it.
+i2psnark has a new torrent editor.
+The NTCP2 transport now uses much less CPU.</p>
+<p>The long-deprecated BOB interface is removed for new installs.
+It will continue to work in existing installs, except for Debian packages.
+Any remaining users of BOB applications should ask the developers to convert to the SAMv3 protocol.</p>
+<p>We know that since our 1.6.1 release, network reliability has steadily deteriorated.
+We were aware of the problem soon after the release, but it took us almost two months to find the cause.
+We eventually identified it as a bug in i2pd 2.40.0,
+and the fix will be in their 2.41.0 release coming out about the same time as this release.
+Along the way, we've made several changes on the Java I2P side to improve the
+robustness of network database lookups and stores, and avoid poorly-performing peers in tunnel peer selection.
+This should help the network be more robust even in the presence of buggy or malicious routers.
+Additionally, we're starting a joint program to test pre-release i2pd and Java I2P routers
+together in an isolated test network, so we can find more problems before the releases, not after.</p>
+<p>In other news, we continue to make great progress on the design of our new UDP transport "SSU2" (proposal 159)
+and have started implementation.
+SSU2 will bring substantial performance and security improvements.
+It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
+completing a full cryptography upgrade that started about 9 years ago.
+We expect to start joint testing with i2pd soon, and roll it out to the network later this year.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 enables new tunnel build messages</summary></details><p>This release completes the rollout of two major protocol updates developed in 2021.
+The transition to X25519 encryption for routers is accelerated, and we expect almost all routers to be rekeyed by the end of the year.
+Short tunnel build messages are enabled for a significant bandwidth reduction.</p>
+<p>We added a theme selection panel to the new install wizard.
+We've improved SSU performance and fixed an issue with SSU peer test messages.
+The tunnel build Bloom filter was adjusted to reduce memory usage.
+We have enhanced support for non-Java plugins.</p>
+<p>In other news, we are making excellent progress on the design of our new UDP transport SSU2 and expect to start implementation early next year.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 with new tunnel build messages</summary></details><p>Yes, that's right, after 9 years of 0.9.x releases, we are going straight from 0.9.50 to 1.5.0.
+This does not signify a major API change, or a claim that development is now complete.
+It is simply a recognition of almost 20 years of work to provide anonymity and security for our users.</p>
+<p>This release finishes implementation of smaller tunnel build messages to reduce bandwidth.
+We continue the transition of the network's routers to X25519 encryption.
+Of course there are also numerous bug fixes and performance improvements.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="MuWire Desktop Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Muwire Desktop Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire standalone desktop application.
+It does not affect the console plugin, and is not related to the previously-announced plugin issue.
+If you are running the MuWire desktop application you should <a href="http://muwire.i2p/">update to version 0.8.8</a> immediately.</p>
+<p>Details of the issue will be published on <a href="http://muwire.i2p/security.html">muwire.i2p</a>
+on July 15, 2021.</p>
+</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="MuWire Plugin Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Muwire Plugin Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire plugin.
+It does not affect the standalone desktop client.
+If you are running the MuWire plugin you should <a href="/configplugins">update to version 0.8.7-b1</a> immediately.</p>
+<p>See <a href="http://muwire.i2p/security.html">muwire.i2p</a>
+for more information about the vulnerability and updated security recommendations.</p>
+</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 with IPv6 fixes</summary></details><p>0.9.50 continues the transition to ECIES-X25519 for router encryption keys.
+We have enabled DNS over HTTPS for reseeding to protect users from passive DNS snooping.
+There are numerous fixes and improvements for IPv6 addresses, including new UPnP support.</p>
+<p>We have finally fixed some longstanding SusiMail corruption bugs.
+Changes to the bandwidth limiter should improve network tunnel performance.
+There are several improvements in our Docker containers.
+We have improved our defenses for possible malicious and buggy routers in the network.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0.9.49 with SSU fixes and faster crypto</summary></details><p>0.9.49 continues the work to make I2P faster and more secure.
+We have several improvements and fixes for the SSU (UDP) transport that should result in faster speeds.
+This release also starts the migration to new, faster ECIES-X25519 encryption for routers.
+(Destinations have been using this encryption for a few releases now)
+We've been working on the specifications and protocols for new encryption for several years,
+and we are getting close to the end of it! The migration will take several releases to complete.</p>
+<p>For this release, to minimize disruption, only new installs and a very small percentage of existing installs
+(randomly selected at restart) will be using the new encryption.
+If your router does "rekey" to use the new encryption, it may have lower traffic or less reliability than usual for several days after you restart.
+This is normal, because your router has generated a new identity.
+Your performance should recover after a while.</p>
+<p>We have "rekeyed" the network twice before, when changing the default signature type,
+but this is the first time we've changed the default encryption type.
+Hopefully it will all go smoothly, but we're starting slowly to be sure.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 with performance enhancements</summary></details><p>0.9.48 enables our new end-to-end encryption protocol (proposal 144) for most services.
+We have added preliminary support for new tunnel build message encryption (proposal 152).
+There are significant performance improvements throughout the router.</p>
+<p>Packages for Ubuntu Xenial (16.04 LTS) are no longer supported.
+Users on that platform should upgrade so you may continue to receive I2P updates.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 enables new encryption</summary></details><p>0.9.47 enables our new end-to-end encryption protocol (proposal 144) by default for some services.
+The Sybil analysis and blocking tool is now enabled by default.</p>
+<p>Java 8 or higher is now required.
+Debian packages for Wheezy and Stretch, and for Ubuntu Trusty and Precise, are no longer supported.
+Users on those platforms should upgrade so you may continue to receive I2P updates.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="0.9.46 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 with bug fixes</summary></details><p>0.9.46 contains significant performance improvements in the streaming library.
+We have completed development of ECIES encryption (proposal 144) and there is now an option to enable it for testing.</p>
+<p>Windows users only:
+This release fixes a local privilege escalation vulnerability
+which could be exploited by a local user.
+Please apply the update as soon as possible.
+Thanks to Blaze Infosec for responsible disclosure of the issue.</p>
+<p>This is the last release to support Java 7, Debian packages Wheezy and Stretch, and Ubuntu packages Precise and Trusty.
+Users on those platforms must upgrade to receive future I2P updates.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 with bug fixes</summary></details><p>0.9.45 contains important fixes for hidden mode and the bandwidth tester.
+There's an update to the console dark theme.
+We continue work on improving performance and the development of new end-to-end encryption (proposal 144).</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="0.9.44 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 with bug fixes</summary></details><p>0.9.44 contains an important fix for a denial of service issue in hidden services handling of new encryption types.
+All users should update as soon as possible.</p>
+<p>The release includes initial support for new end-to-end encryption (proposal 144).
+Work continues on this project, and it is not yet ready for use.
+There are changes to the console home page, and new embedded HTML5 media players in i2psnark.
+Additional fixes for firewalled IPv6 networks are included.
+Tunnel build fixes should result in faster startup for some users.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="0.9.43 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 with bug fixes</summary></details><p>In the 0.9.43 release, we continue work on stronger security and privacy features and performance improvements.
+Our implementation of the new leaseset specification (LS2) is now complete.
+We are beginning our implementation of stronger and faster end-to-end encryption (proposal 144) for a future release.
+Several IPv6 address detection issues have been fixed, and there of course are several other bug fixes.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="0.9.42 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 with bug fixes</summary></details><p>0.9.42 continues the work to make I2P faster and more reliable.
+It includes several changes to speed up our UDP transport.
+We have split up the configuration files to enable future work for more modular packaging.
+We continue work to implement new proposals for faster and more secure encryption.
+There are, of course, a lot of bug fixes also.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="0.9.41 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.41 with bug fixes</summary></details><p>0.9.41 continues the work to implement new features for proposal 123,
+including per-client authentication for encrypted leasesets.
+The console has an updated I2P logo and several new icons.
+We've updated the Linux installer.</p>
+<p>Startup should be faster on platforms such as Raspberry Pi.
+We've fixed several bugs, including some serious ones affecting low-level network messages.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="0.9.40 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 with new icons</summary></details><p>0.9.40 includes support for the new encrypted leaseset format.
+We disabled the old NTCP 1 transport protocol.
+There's a new SusiDNS import feature, and a new scripted filtering mechanism for incoming connections.</p>
+<p>We've made a lot of improvements to the OSX native installer, and we've updated the IzPack installer as well.
+The work continues on refreshing the console with new icons.
+As usual, we've fixed lots of bugs also!</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 with performance improvements</summary></details><p>0.9.39 includes extensive changes for the new network database types (proposal 123).
+We've bundled the i2pcontrol plugin as a webapp to support development of RPC applications.
+There are numerous performance improvements and bug fixes.</p>
+<p>We've removed the midnight and classic themes to reduce the maintenance burden;
+previous users of those themes will now see the dark or light theme.
+There's also new home page icons, a first step in updating the console.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 with new setup wizard</summary></details><p>0.9.38 includes a new first-install wizard with a bandwidth tester.
+We've added support for the latest GeoIP database format.
+There's a new Firefox profile installer and a new, native Mac OSX installer on our website.
+Work continues on supporting the new "LS2" netdb format.</p>
+<p>This release also contains plenty of bug fixes, including several issues with susimail attachments, and a fix for IPv6-only routers.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="35C3 Trip Report" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P at 35C3</summary></details><p>The I2P team was mostly all in attendance at 35C3 in Leipzig.
+Daily meetings were held to review the past year and cover our development and design goals for 2019.</p>
+<p>The Project Vision and new Roadmap can be <a href="http://i2p-projekt.i2p/en/get-involved/roadmap">reviewed here</a>.</p>
+<p>Work will continue on LS2, the Testnet, and usability improvements to our website and console.
+A plan is in place to be in Tails, Debian and Ubuntu Disco. We still need people to work on Android and I2P_Bote fixes.</p>
+</article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="0.9.37 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37 with NTCP2 enabled</summary></details><p>0.9.37 enables a faster, more secure transport protocol called NTCP2.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="0.9.36 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 with NTCP2 and bug fixes</summary></details><p>0.9.36 contains a new, more secure transport protocol called NTCP2.
+It is disabled by default, but you may enable it for testing by adding the <a href="/configadvanced">advanced configuration</a> <tt>i2np.ntcp2.enable=true</tt> and restarting.
+NTCP2 will be enabled in the next release.</p>
+<p>This release also contains several performance improvements and bug fixes.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 with SusiMail folders and SSL Wizard</summary></details><p>0.9.35 adds support for folders in SusiMail, and a new SSL Wizard for setting up HTTPS on your Hidden Service website.
+We also have the usual collection of bug fixes, especially in SusiMail.</p>
+<p>We're hard at work on several things for 0.9.36, including a new OSX installer and a faster, more secure transport protocol called NTCP2.</p>
+<p>I2P will be at HOPE in New York City, July 20-22. Find us and say hello!</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 with bug fixes</summary></details><p>0.9.34 contains a lot of bug fixes!
+It also has improvements in SusiMail, IPv6 handling, and tunnel peer selection.
+We add support for IGD2 schemas in UPnP.
+There's also preparation for more improvements you will see in future releases.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="0.9.33 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 with bug fixes</summary></details><p>0.9.33 contains a large number of bug fixes, including i2psnark, i2ptunnel, streaming, and SusiMail.
+For those who cannot access the reseed sites directly, we now support several types of proxies for reseeding.
+We now set rate limits by default in the hidden services manager.
+For those that run high-traffic servers, please review and adjust the limits as necessary.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER, Meltdown and Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Security issues found in nearly every system</summary></details><p>A very serious issue has been found in modern CPUs which are found in nearly all sold computers worldwide, including mobiles. Those security issues are named "Kaiser", "Meltdown", and "Spectre".</p>
+<p>The whitepaper for KAISER/KPTI can be found under <a href="https://gruss.cc/files/kaiser.pdf" target="_blank">KAISER.pdf</a>, Meltdown under <a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a>, and SPECTRE under <a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a>. Intels first response is listed under <a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">Intels response</a>.</p>
+<p>It is important for our I2P users to update your system, as long as updates are available. Windows 10 patches are availble from now on, Windows 7 and 8 will follow soon. MacOS patches are already available, to. Lots of Linux systems have a newer Kernel with a included fix available, too. Same applies to Android, which security fix of 2nd Jan 2018 includes a patch for this issues.
+Please update your systems as soon as available and possible.</p>
+</article><article id="urn:uuid:a6fc490b-2877-4cbf-afa8-d6e7d4637440" title="Happy new year! - 34C3" href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>New year and I2P at 34C3</summary></details><p>Happy new year from the I2P team to everyone!</p>
+<p>No less than 7 I2P team members did meet at the 34C3 in Leipzig from 27th til 30th december 2017. Beside the <a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" target="_blank">meetings</a> at our table we did meet lots of friends of I2P all over the place. 
+Results of the meetings are posted on <a href="http://zzz.i2p" target="_blank">zzz.i2p</a> already.</p>
+<p>Also we did hand out lots of stickers and gave information about our project to anyone asking. 
+Our annual I2P dinner was a full success as a thank you to all attendees for ongoing support of I2P.</p>
+</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="0.9.32 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 with console updates</summary></details><p>0.9.32 contains a number of fixes in the router console and associated webapps (addressbook, i2psnark, and susimail).
+We have also changed the way we handle configured hostnames for published router infos, to eliminate some network enumeration attacks via DNS.
+We have added some checks in the console to resist rebinding attacks.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="0.9.31 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>0.9.31 with console updates</summary></details><p>The changes in this release are much more noticeable than usual!
+We have refreshed the router console to make it easier to understand,
+improved accessibility and cross-browser support,
+and generally tidied things up.
+This is the first step in a longer-term plan to make the router console more user-friendly.
+We have also added torrent ratings and comments support to i2psnark.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:2ce9a846-4d7e-11e7-b788-00163e5e6c1b" title="Call for Translators" href="https://www.transifex.com/otf/I2P/announcements/7243/" author="str4d" published="2017-06-10T12:00:00Z" updated="2017-06-10T12:00:00Z"><details><summary>The upcoming 0.9.31 release has more untranslated strings than usual</summary></details><p>In preparation for the 0.9.31 release, which brings with it significant updates
+to the user interface, we have a larger than normal collection of untranslated
+strings that need attention. If you're a translator, we would greatly appreciate
+it if you could set aside a little more time than usual during this release cycle
+in order to bring the translations up to speed. We have pushed the strings early
+to give you three weeks to work on them.</p>
+<p>If you're not currently an I2P translator, now would be a great time to get
+involved! Please see the
+<a href="http://i2p-projekt.i2p/en/get-involved/guides/new-translators" target="_blank">New Translator's Guide</a>
+for information on how to get started.</p>
+</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="0.9.30 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>0.9.30 updates to Jetty 9</summary></details><p>0.9.30 contains an upgrade to Jetty 9 and Tomcat 8.
+The previous versions are no longer supported, and are not available in the upcoming Debian Stretch and Ubuntu Zesty releases.
+The router will migrate the jetty.xml configuration file for each Jetty website to the new Jetty 9 setup.
+This should work for recent, unmodified configurations but may not work for modified or very old setups.
+Verify that your Jetty website works after upgrading, and contact us on IRC if you need assistance.</p>
+<p>Several plugins are not compatible with Jetty 9 and must be updated.
+The following plugins have been updated to work with 0.9.30, and your router should update them after restart:
+i2pbote 0.4.6; zzzot 0.15.0.
+The following plugins (with current versions listed) will not work with 0.9.30.
+Contact the appropriate plugin developer for the status of new versions:
+BwSchedule 0.0.36; i2pcontrol 0.11.</p>
+<p>This release also supports migration of old (2014 and earlier) DSA-SHA1 hidden services to the more-secure EdDSA signature type.
+See <a href="http://zzz.i2p/topics/2271">zzz.i2p</a> for further information, including a guide and FAQ.</p>
+<p>Note: On non-Android ARM platforms such as the Raspberry Pi, the blockfile database will upgrade on restart, which may take several minutes.
+Please be patient.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="0.9.29 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29 contains bug fixes</summary></details><p>0.9.29 contains fixes for numerous Trac tickets, including workarounds for corrupt compressed messages.
+We now support NTP over IPv6.
+We've added preliminary Docker support.
+We now have translated man pages.
+We now pass same-origin Referer headers through the HTTP proxy.
+There are more fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
+<p>As usual, we recommend that all users update to this release.
+The best way to help the network and stay secure is to run the latest release.</p>
+</article><article id="urn:uuid:cb742cac-df38-11e6-aed3-00163e5e6c1b" title="I2P-Bote Security Vulnerability" href="http://bote.i2p/news/0.4.5/" author="str4d" published="2017-01-20T12:00:00Z" updated="2017-01-20T12:00:00Z"><details><summary>I2P-Bote Security Vulnerability</summary></details><p>I2P-Bote 0.4.5 fixes a security vulnerability present in all earlier versions of the
+I2P-Bote plugin. The Android app was not affected.</p>
+<p>When showing emails to the user, most fields were being escaped. However, the filenames
+of attachments were not escaped, and could be used to execute malicious code in a browser
+with JavaScript enabled. These are now escaped, and additionally a Content Security Policy
+has been implemented for all pages.</p>
+<p>All I2P-Bote users will be upgraded automatically the first time they restart their router
+after I2P 0.9.29 is released in mid-February. However, for safety we recommend that you
+<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
+upgrade manually if you plan on using I2P or I2P-Bote in the intervening time.</p>
+</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="0.9.28 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>0.9.28 contains bug fixes</summary></details><p>0.9.28 contains fixes for over 25 Trac tickets, and updates for a number of bundled software packages including Jetty.
+There are fixes for the IPv6 peer testing feature introduced last release.
+We continue improvements to detect and block peers that are potentially malicious.
+There are preliminary fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
+<p>I2P will be at 33C3, please stop by our table and give us your ideas on how to improve the network.
+We will review our 2017 roadmap and priorities 2017 at the Congress.</p>
+<p>As usual, we recommend that all users update to this release.
+The best way to help the network and stay secure is to run the latest release.</p>
+</article><article id="urn:uuid:00015ff6-b556-11e6-adb4-00163e5e6c1a" title="I2P-Bote Security Vulnerability" href="http://bote.i2p/news/0.4.4/" author="str4d" published="2016-11-28T12:00:00Z" updated="2016-11-28T12:00:00Z"><details><summary>I2P-Bote Security Vulnerability</summary></details><p>I2P-Bote 0.4.4 fixes a security vulnerability present in all earlier versions of the
+I2P-Bote plugin. The Android app was not affected.</p>
+<p>A lack of CSRF protection meant that if a user was running I2P-Bote and then loaded a
+malicious site in a browser with JavaScript enabled, the adversary could trigger actions
+in I2P-Bote on behalf of the user, such as sending messages. This might also have enabled
+extraction of private keys for I2P-Bote addresses, however no proof-of-exploit was tested
+for this.</p>
+<p>All I2P-Bote users will be upgraded automatically the first time they restart their router
+after I2P 0.9.28 is released in mid-December. However, for safety we recommend that you
+<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
+upgrade manually if you plan on using I2P or I2P-Bote in the intervening time. You should
+also consider generating new I2P-Bote addresses if you regularly browse sites with
+JavaScript enabled while running I2P-Bote.</p>
+</article><article id="urn:uuid:c1d01ac3-81e7-4acd-bacd-d9178089e8c3" title="0.9.27 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/10/17/0.9.27-Release" author="zzz" published="2016-10-17T12:00:00Z" updated="2016-10-17T12:00:00Z"><details><summary>0.9.27 contains bug fixes</summary></details><p>0.9.27 contains a number of bug fixes.
+The updated GMP library for crypto acceleration, which was bundled in the 0.9.26 release for new installs and Debian builds only, is now included in the in-network update for 0.9.27.
+There are improvements in IPv6 transports, SSU peer testing, and hidden mode.</p>
+<p>We updated a number of plugins during <a href="http://i2p-projekt.i2p/en/blog/post/2016/06/01/I2P-Summer-Dev">I2P Summer</a> and your router will automatically update them after restart.</p>
+<p>As usual, we recommend that all users update to this release.
+The best way to help the network and stay secure is to run the latest release.</p>
+</article><article id="urn:uuid:7e818120-88f8-401a-88fe-8db4ba20ad4d" title="I2P Stack Exchange proposal" href="https://area51.stackexchange.com/proposals/99297/i2p" author="zzz" published="2016-06-07T13:00:00Z" updated="2016-06-07T13:00:00Z"><details><summary>I2P is now a proposed site on Stack Exchange!</summary></details><p>I2P is now a proposed site on Stack Exchange!
+Please <a href="https://area51.stackexchange.com/proposals/99297/i2p">commit to using it</a> so the beta phase can begin.</p>
+</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="0.9.26 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>0.9.26 contains crypto updates, Debian packaging improvements, and bug fixes</summary></details><p>0.9.26 contains a major upgrade to our native crypto library,
+a new addressbook subscription protocol with signatures,
+and major improvements to the Debian/Ubuntu packaging.</p>
+<p>For crypto, we have upgraded to GMP 6.0.0, and added support for newer processors,
+which will speed up crypto operations considerably.
+Also, we are now using constant-time GMP functions to prevent side-channel attacks.
+For caution, the GMP changes are enabled for new installs and Debian/Ubuntu builds only;
+we will include them for in-net updates in the 0.9.27 release.</p>
+<p>For Debian/Ubuntu builds, we have added dependencies on several packages,
+including Jetty 8 and geoip, and removed the equivalent bundled code.</p>
+<p>There's a collection of bug fixes also, including a fix for a timer bug
+that caused instability and performance degradations over time.
+As usual, we recommend that all users update to this release.
+The best way to help the network and stay secure is to run the latest release.</p>
+</article><article id="urn:uuid:c6f7228d-3330-4422-a651-ef9d8ca3484b" title="0.9.25 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/03/22/0.9.25-Release" author="zzz" published="2016-03-22T12:00:00Z" updated="2016-03-22T12:00:00Z"><details><summary>0.9.25 contains SAM 3.3, QR codes, and bug fixes</summary></details><p>0.9.25 contains a major new version of SAM, v3.3, to support sophisticated multiprotocol applications.
+It adds QR codes for sharing hidden service addresses with others,
+and "identicon" images for visually distinguishing addresses.</p>
+<p>We've added a new "router family" configuration page in the console,
+to make it easier to declare that your group of routers is run by a single person.
+There are several changes to increase the capacity of the network and hopefully improve tunnel build success.</p>
+<p>As usual, we recommend that all users update to this release.
+The best way to help the network and stay secure is to run the latest release.</p>
+</article><article id="urn:uuid:8390114d-8e50-45fd-8b4d-3e613bdd034e" title="0.9.24 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/01/27/0.9.24-Release" author="zzz" published="2016-01-27T18:00:00Z" updated="2016-01-27T18:00:00Z"><details><summary>0.9.24 contains several bug fixes and speedups</summary></details><p>0.9.24 contains a new version of SAM (v3.2) and numerous bug fixes and efficiency improvements.
+Note that this release is the first to require Java 7.
+Please update to Java 7 or 8 as soon as possible.
+Your router will not automatically update if you are using Java 6.</p>
+<p>To prevent the problems caused by the ancient commons-logging library, we have removed it.
+This will cause very old I2P-Bote plugins (0.2.10 and below, signed by HungryHobo) to crash if they have IMAP enabled.
+The recommended fix is to replace your old I2P-Bote plugin with the current one signed by str4d.
+For more details, see <a href="http://bote.i2p/news/0.4.3">this post</a>.</p>
+<p>We had a great <a href="http://i2p-projekt.i2p/en/blog/post/2016/01/23/32C3">32C3 Congress</a> and are making good progress on our 2016 project plans.
+Echelon gave a talk on I2P's history and current status, and his slides are <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/ccc/2015/I2P_Still_alive.pdf">here</a> (pdf).
+Str4d attended <a href="http://www.realworldcrypto.com/rwc2016/program">Real World Crypto</a> and gave a talk on our crypto migration, 
+his slides are <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/rwc/2016/rwc2016-str4d-slides.pdf">here</a> (pdf).</p>
+<p>As usual, we recommend that all users update to this release.
+The best way to help the network and stay secure is to run the latest release.</p>
+</article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="0.9.23 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>0.9.23 contains a variety of bug fixes, and some minor improvements in I2PSnark</summary></details><p>Hello I2P! This is the first release signed by me (str4d), after 49 releases
+signed by zzz. This is an important test of our redundancy for all things,
+including people.</p>
+<p><b>Housekeeping</b></p>
+<p>My signing key has been in router updates for over two years (since 0.9.9), so
+if you are on a recent version of I2P this update should be just as easy as
+every other update. However, if you are running an older version than 0.9.9, you
+will first need to manually update to a recent version. Update files for recent
+versions can be downloaded
+<a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/releases/">here</a>,
+and instructions on how to manually update are provided
+<a href="http://i2p-projekt.i2p/en/download#update">here</a>. Once you have manually
+updated, your router will then find and download the 0.9.23 update as usual.</p>
+<p>If you installed I2P via a package manager, you are not affected by the change,
+and can update as usual.</p>
+<p><b>Update details</b></p>
+<p>The migration of RouterInfos to new, stronger Ed25519 signatures is going well,
+with at least half of the network already estimated to have rekeyed. This
+release accelerates the rekeying process. To reduce network churn, your router
+will have a small probability of converting to Ed25519 at each restart. When it
+does rekey, expect to see lower bandwidth usage for a couple of days as it
+reintegrates into the network with its new identity.</p>
+<p>Note that this will be the last release to support Java 6. Please update to
+Java 7 or 8 as soon as possible. We are already working to make I2P compatible
+with the upcoming Java 9, and some of that work is in this release.</p>
+<p>We have also made some minor improvements in I2PSnark, and added a new page in
+the routerconsole for viewing older news items.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="0.9.22 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 with bug fixes and starts Ed25519 migration</summary></details><p>0.9.22 contains fixes for i2psnark getting stuck before completion, and begins the migration of router infos to new, stronger Ed25519 signatures.
+To reduce network churn, your router will have only a small probability of converting to Ed25519 at each restart.
+When it does rekey, expect to see lower bandwidth usage for a couple of days as it reintegrates into the network with its new identity.
+If all goes well, we will accelerate the rekeying process in the next release.</p>
+<p>I2PCon Toronto was a big success!
+All the presentations and videos are listed on the <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">I2PCon page</a>.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="0.9.21 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>0.9.21 released with performance improvements and bug fixes.</summary></details><p>0.9.21 contains several changes to add capacity to the network, increase the efficiency of the floodfills,
+and use bandwidth more effectively.
+We have migrated the shared clients tunnels to ECDSA signatures and added a DSA fallback
+using the new "multisession" capability for those sites that don't support ECDSA.</p>
+<p>The speakers and the schedule of the I2PCon in Toronto 2015 have been announced.
+Have a look on the <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon page</a> for details.
+Reserve your seat on <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:53ba215d-6cf2-489c-8135-10248e06a141" title="I2PCon Toronto speakers and schedule announced" href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon" author="echelon" published="2015-07-19T18:00:00Z" updated="2015-07-22T12:00:00Z"><details><summary>I2PCon Toronto 2015 speakers and schedule announced</summary></details><p>The speakers and the schedule of the I2PCon in Toronto 2015 have been announced.
+Have a look on the <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon page</a> for details.
+Reserve your seat on <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
+</article>
+</div>

data/translations/entries.de.html

@@ -1,5 +1,160 @@
 <div>
-<header title="I2P - Nachrichten">Neuigkeiten und Router-Aktualisierungen</header><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 veröffentlicht" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2-Übertragung aktiviert</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
+<header title="I2P - Nachrichten">Neuigkeiten und Router-Aktualisierungen</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
+The bug primarily affected high-bandwidth routers.</p>
+<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
+</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
+We have added notification bubbles to several applications in the console to highlight application messages.
+We fixed a tunnel test bug that may have been affecting tunnel reliability.
+The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
+There are several dark theme fixes and improvements.</p>
+<p>We fixed the installer that previously failed on Java 21 or higher.
+We also fixed installing to directory paths that contain spaces on Linux.
+For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
+<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
+</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
+The workaround is using localhost and the server port, usually 7658, to bypass I2P.
+For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
+We apologize for the issue and are working on a fix.</p>
+</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
+<p>We have improved handling of congested routers in the network.
+Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
+We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
+Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
+<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
+</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
+<p>Access to information from the console and applications has been improved.
+Issues have been fixed in I2PSnark and SusiMail search.
+The netDB search embedded into the router console now operates in a more intuitive and useful way.
+Minor improvements have been made to diagnostic displays in advanced mode.</p>
+<p>Bugs have also been fixed to improve compatibility within the network.
+An issue with publishing leaseSets was solved which improves reliability major hidden services.
+I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
+This prevents torrents from being unnecessarily disrupted by these changes.
+We welcomed this contribution from a new contributor.
+A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
+<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
+</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
+This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
+<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
+</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
+<p>Newer routers will be favored when selecting floodfill routers.
+I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
+Legacy transport protocols are being removed, simplifying the code in the UDP transports.
+Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
+Additional tweaks were made to peer selection strategies.</p>
+<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
+We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
+If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
+Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
+<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
+</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
+<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
+</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
+With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
+This should help the network return to normal operation.
+Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
+Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
+<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
+</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
+This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
+Reachability of I2P sites is badly degraded.</p>
+<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
+Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
+</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
+<p>New features have been added to I2PSnark like the ability to search through torrents.
+Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
+We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
+New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
+Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
+<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
+This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
+This investigation uncovered one minor isolation-piercing event which we repaired.
+This issue was discovered and fixed internally by the I2P team.</p>
+<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
+This should result in improved delivery and availability for these downstream products.</p>
+<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
+</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
+It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
+<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
+This will help the network limit the effect of tunnel spam.
+It will also help the network heal during and after DDOS attacks.</p>
+<p>The NetDb changes also help secure individual routers and the applications that use them. 
+Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
+This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
+<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
+<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
+</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
+CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
+An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
+The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
+The attacker then sends the same message directly to the router.
+The router passes the message to the bloom filter, and is dropped.
+This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
+This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
+Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
+Users of Java I2P are recommended to update immediately to avoid the attack.</p>
+<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
+This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
+<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
+<p>This release also contains a tweakable blocklist.
+Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
+Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
+This feature is off-by-default and is only recommended for advanced users at this time.</p>
+<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
+It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
+<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
+</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
+This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
+Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
+This issue has also been resolved.
+The docker container is now also compatible with Podman.</p>
+<p>This release syncs translations with transifex and updates the GeoIP database.</p>
+<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
+</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
+This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
+The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
+<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
+This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
+This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
+We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
+<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
+zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
+As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
+We thank zzz for providing these services for such a long time.</p>
+<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
+</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
+Our investigations and mitigations continue.</p>
+<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
+We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
+However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
+The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
+<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
+We ask for your patience as we work to improve I2P.</p>
+</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
+  The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
+  Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
+  Mitigation strategies are being investigated and implemented gradually.</p>
+<p>While the attack has degraded performance, the network remains intact and usable.
+  Java I2P routers appear to be handling the issues better than i2pd routers for now.
+  Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
+</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 veröffentlicht" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 mit zahlreichen SSU2-Korrekturen</summary></details><p>We have learned several things since our 2.0.0 release in November.
+As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
+First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
+Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
+Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
+<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
+possibly triggered by Bitcoin's new I2P transient address feature,
+but made worse by our SSU2 bugs and other congestion control problems.
+We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
+We have improved our algorithms to reduce network load during times of congestion.
+We are also collaborating with i2pd to develop common congestion control strategies.</p>
+<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
+i2pd released their version 2.45.0 last week and the early results are encouraging.
+New protocols, and distributed networks, are difficult to develop.
+Congestion can arrive with little warning and with little clue of the cause.
+Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
+<p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
+</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 veröffentlicht" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2-Übertragung aktiviert</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
 <p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
 <p>Wir empfehlen wie immer, baldmöglichst auf die neue Routerversion zu aktualisieren. Ihrer eigenen Sicherheit und dem Netz ist am besten gedient, wenn Sie stets die neueste stabile Version von I2P verwenden.</p>
 </article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Neueste Blog-Beiträge" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>
@@ -8,7 +163,7 @@
 <li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">A warning about I2P coins and other scams</a></li>
 <li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">An interview with Konrad from diva.exchange</a></li>
 <li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">An interview with Dustin from StormyCloud</a></li>
-</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 veröffentlicht" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 with SSU2 for testing</summary></details><p>We have spent the last three months working on our new UDP transport protocol "SSU2"
+</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 veröffentlicht" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 mit SSU2 zum Testen</summary></details><p>We have spent the last three months working on our new UDP transport protocol "SSU2"
 with a small number of volunteer testers.
 This release completes the implementation, including relay and peer testing.
 We are enabling it by default for Android and ARM platforms, and a small percentage of other routers at random.

data/translations/entries.el.html

@@ -1,5 +1,173 @@
 <div>
-<header title="Νέα I2P">Ροή νέων, και ενημέρωσης δρομολογητών </header><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
+<header title="Νέα I2P">Ροή νέων, και ενημέρωσης δρομολογητών </header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
+The bug primarily affected high-bandwidth routers.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
+We have added notification bubbles to several applications in the console to highlight application messages.
+We fixed a tunnel test bug that may have been affecting tunnel reliability.
+The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
+There are several dark theme fixes and improvements.</p>
+<p>We fixed the installer that previously failed on Java 21 or higher.
+We also fixed installing to directory paths that contain spaces on Linux.
+For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
+The workaround is using localhost and the server port, usually 7658, to bypass I2P.
+For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
+We apologize for the issue and are working on a fix.</p>
+</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
+<p>We have improved handling of congested routers in the network.
+Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
+We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
+Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
+<p>Access to information from the console and applications has been improved.
+Issues have been fixed in I2PSnark and SusiMail search.
+The netDB search embedded into the router console now operates in a more intuitive and useful way.
+Minor improvements have been made to diagnostic displays in advanced mode.</p>
+<p>Bugs have also been fixed to improve compatibility within the network.
+An issue with publishing leaseSets was solved which improves reliability major hidden services.
+I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
+This prevents torrents from being unnecessarily disrupted by these changes.
+We welcomed this contribution from a new contributor.
+A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
+This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
+<p>Newer routers will be favored when selecting floodfill routers.
+I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
+Legacy transport protocols are being removed, simplifying the code in the UDP transports.
+Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
+Additional tweaks were made to peer selection strategies.</p>
+<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
+We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
+If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
+Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
+With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
+This should help the network return to normal operation.
+Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
+Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
+This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
+Reachability of I2P sites is badly degraded.</p>
+<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
+Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
+</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
+<p>New features have been added to I2PSnark like the ability to search through torrents.
+Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
+We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
+New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
+Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
+<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
+This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
+This investigation uncovered one minor isolation-piercing event which we repaired.
+This issue was discovered and fixed internally by the I2P team.</p>
+<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
+This should result in improved delivery and availability for these downstream products.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
+It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
+<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
+This will help the network limit the effect of tunnel spam.
+It will also help the network heal during and after DDOS attacks.</p>
+<p>The NetDb changes also help secure individual routers and the applications that use them. 
+Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
+This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
+<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
+CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
+An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
+The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
+The attacker then sends the same message directly to the router.
+The router passes the message to the bloom filter, and is dropped.
+This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
+This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
+Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
+Users of Java I2P are recommended to update immediately to avoid the attack.</p>
+<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
+This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
+<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
+<p>This release also contains a tweakable blocklist.
+Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
+Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
+This feature is off-by-default and is only recommended for advanced users at this time.</p>
+<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
+It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
+This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
+Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
+This issue has also been resolved.
+The docker container is now also compatible with Podman.</p>
+<p>This release syncs translations with transifex and updates the GeoIP database.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
+This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
+The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
+<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
+This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
+This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
+We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
+<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
+zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
+As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
+We thank zzz for providing these services for such a long time.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
+Our investigations and mitigations continue.</p>
+<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
+We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
+However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
+The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
+<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
+We ask for your patience as we work to improve I2P.</p>
+</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
+  The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
+  Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
+  Mitigation strategies are being investigated and implemented gradually.</p>
+<p>While the attack has degraded performance, the network remains intact and usable.
+  Java I2P routers appear to be handling the issues better than i2pd routers for now.
+  Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
+</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
+As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
+First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
+Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
+Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
+<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
+possibly triggered by Bitcoin's new I2P transient address feature,
+but made worse by our SSU2 bugs and other congestion control problems.
+We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
+We have improved our algorithms to reduce network load during times of congestion.
+We are also collaborating with i2pd to develop common congestion control strategies.</p>
+<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
+i2pd released their version 2.45.0 last week and the early results are encouraging.
+New protocols, and distributed networks, are difficult to develop.
+Congestion can arrive with little warning and with little clue of the cause.
+Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
+<p>Όπως συνήθως, συνιστούμε το να ενημερώνεται σε αυτήν την κυκλοφορία. Ο καλύτερος τρόπος να διατηρήσετε ασφάλεια και να βοηθήσετε το δίκτυο είναι να τρέχετε την τελευταία έκδοση. </p>
+</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
 <p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
 <p>Όπως συνήθως, συνιστούμε το να ενημερώνεται σε αυτήν την κυκλοφορία. Ο καλύτερος τρόπος να διατηρήσετε ασφάλεια και να βοηθήσετε το δίκτυο είναι να τρέχετε την τελευταία έκδοση. </p>
 </article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Recent Blog Posts" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>

data/translations/entries.es.html

@@ -1,14 +1,162 @@
 <div>
-<header title="Noticias de I2P">Suscripción (feed) de noticias, y actualizaciones del router I2P</header><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
-<p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
+<header title="Noticias de I2P">Suscripción (feed) de noticias, y actualizaciones del router I2P</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="Versión 2.8.2 Disponible" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>Versión 2.8.2 Disponible</summary></details><p>La versión 2.8.2 corrige un error que causaba fallos de SHA256 que se introdujo en la versión 2.8.1.
+El error afectaba principalmente a los enrutadores de alto ancho de banda.</p>
+<p>Como es habitual, le recomendamos que actualice a esta versión.
+La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
+</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="Versión 2.8.1 Disponible" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>Lanzamiento de I2P 2.8.1</summary></details><p>La versión 2.8.1 corrige los accesos a sitios locales que se rompieron en 2.8.0.
+Hemos añadido burbujas de notificación a varias aplicaciones en la consola para destacar los mensajes de la aplicación.
+Hemos corregido un error en la prueba del túnel que podría haber estado afectando a la fiabilidad del túnel.
+La libreta de direcciones ahora tiene una nueva pestaña "última" que muestra los nombres de host más recientes añadidos de tus suscripciones.
+Hay varias correcciones y mejoras en el tema oscuro.</p>
+<p>Arreglamos el instalador que antes fallaba en Java 21 o superior.
+También arreglamos la instalación en rutas de directorio que contienen espacios en Linux.
+Para los que usáis Docker, actualizamos el contenedor de Docker y las librerías de contenedor que estaban desactualizadas.</p>
+<p>Como es habitual, le recomendamos que actualice a esta versión.
+La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
+</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="El acceso al sitio local falla en 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Error de acceso local</summary></details><p>En la versión 2.8.0, navegar a un sitio local (ya sea por nombre de host o b32) fallará.
+La solución alternativa es usar localhost y el puerto del servidor, generalmente 7658, para evitar I2P.
+Por ejemplo, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
+Pedimos disculpas por el problema y estamos trabajando en una solución.</p>
+</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="Lanzamiento de I2P 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>Lanzamiento de I2P 2.8.0</summary></details><p>Esta versión mejora I2P al corregir errores, eliminar código no utilizado y mejorar la estabilidad de la red.</p>
+<p>Hemos mejorado el manejo de routers congestionados en la red. 
+Se abordaron problemas en UPnP y la transversalidad NAT para mejorar la conectividad y la notificación de errores. 
+Ahora tenemos una estrategia más agresiva para la eliminación de leasesets del NetDb con el fin de mejorar el rendimiento del router y mitigar la sobrecarga. 
+Se implementaron otros cambios para reducir la observabilidad de eventos como el reinicio o apagado de un router.</p>
+<p>Como es habitual, le recomendamos que actualice a esta versión.
+La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
+</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="Publicada la versión 2.7.0 de I2P" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>Publicada la versión 2.7.0 de I2P</summary></details><p>Esta versión, I2P 2.7.0, continúa nuestro trabajo corrigiendo errores, mejorando el rendimiento y añadiendo funciones.</p>
+<p>Se ha mejorado el acceso a la información desde la consola y las aplicaciones. 
+Se han solucionado problemas en I2PSnark y la búsqueda de SusiMail. 
+La búsqueda de netDB integrada en la consola del router ahora funciona de una manera más intuitiva y útil. 
+Se han realizado pequeñas mejoras en las pantallas de diagnóstico en modo avanzado.</p>
+<p>También se han corregido errores para mejorar la compatibilidad dentro de la red. 
+Se resolvió un problema con la publicación de leaseSets, lo que mejora la fiabilidad de los servicios ocultos principales. 
+I2PSnark ya no cambia el infohash cuando un usuario solo modifica los trackers en un torrent existente. 
+Esto evita que los torrents se vean innecesariamente interrumpidos por estos cambios. 
+Damos la bienvenida a esta contribución de un nuevo colaborador. 
+Se resolvió un conflicto en el manejo de una opción de la biblioteca de streaming para mejorar la compatibilidad con otras implementaciones de I2P.</p>
+<p>Como es habitual, le recomendamos que actualice a esta versión.
+La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
+</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="Publicada la versión 2.6.1 de I2P" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>Publicada la versión 2.6.1 de I2P</summary></details><p>I2P 2.6.1 se lanza para corregir un error en la interfaz de usuario de la aplicación Hidden Services Manager. 
+Este error deshabilitaba el desplazamiento, haciendo que algunas configuraciones fueran inaccesibles.</p>
+<p>Como es habitual, le recomendamos que actualice a esta versión.
+La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
+</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="Publicada la versión 2.6.0 de I2P" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>Publicada la versión 2.6.0 de I2P</summary></details><p>Esta versión, I2P 2.6.0, continúa nuestro trabajo al corregir errores, agregar funciones y mejorar la fiabilidad de la red.</p>
+<p>Se favorecerán los routers más nuevos al seleccionar routers floodfill. 
+I2PSnark recibió funciones que mejoran el rendimiento de PeX (Intercambio de Pares), además de correcciones de errores. 
+Se están eliminando los protocolos de transporte heredados, simplificando el código en los transportes UDP. 
+Los destinos alojados localmente serán accesibles para los clientes locales sin solicitar su LeaseSet, mejorando el rendimiento y la capacidad de prueba. 
+Se realizaron ajustes adicionales en las estrategias de selección de pares.</p>
+<p>I2P ya no permite I2P-sobre-Tor, las conexiones desde direcciones IP de salida de Tor ahora están bloqueadas. 
+Desalentamos esto porque degrada el rendimiento de I2P y consume los recursos de las salidas de Tor sin ningún beneficio. 
+Si eres una persona solidaria que opera tanto una salida de Tor como I2P, te animamos a continuar haciéndolo, utilizando direcciones IP diferentes para cada uno. 
+Los relés no de salida y los clientes de Tor no se ven afectados por esto y no necesitan cambiar nada.</p>
+<p>Como es habitual, le recomendamos que actualice a esta versión.
+La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
+</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="Publicada la versión 2.5.2 de I2P" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 con corrección de HTTP</summary></details><p>Se publica I2P 2.5.2 para corregir un error introducido en 2.5.0 que provocaba el truncamiento de algunos contenidos HTTP.</p>
+<p>Como es habitual, le recomendamos que actualice a esta versión.
+La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
+</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="Publicada la versión 2.5.1 de I2P" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>Lanzamiento de la versión 2.5.1 de I2P para hacer frente a los ataques de denegación de servicio</summary></details><p>"I2P 2.5.1 se ha lanzado para abordar los ataques de Denegación de Servicio que afectan a la red y los servicios de I2P. 
+Con este lanzamiento, deshabilitamos las partes basadas en IP de la herramienta de detección de ataques Sybil, que estaban dirigidas a amplificar el efecto y la duración del ataque. 
+Esto debería ayudar a que la red vuelva a la operación normal. 
+Aquellos de ustedes que han deshabilitado la herramienta de detección de ataques Sybil pueden volver a habilitarla de forma segura. 
+También se han realizado ajustes en otros subsistemas para mejorar la validación de RouterInfo y la selección de pares."</p>
+<p>Como es habitual, le recomendamos que actualice a esta versión.
+La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
+</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Clima tormentoso." href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Clima de la red: Tormentoso. I2P está bajo ataque.</summary></details><p>La red I2P está actualmente bajo un ataque de Denegación de Servicio. 
+Este ataque afecta a I2P e i2pd, pero de diferentes maneras, y está teniendo un efecto grave en la salud de la red. 
+La accesibilidad de los sitios de I2P está gravemente degradada.</p>
+<p>Si estás alojando un servicio dentro de I2P y está alojado en un router Floodfill, deberías considerar alojar el servicio también en un router con Floodfill deshabilitado para mejorar la accesibilidad. 
+Se están discutiendo otras mitigaciones, pero todavía se está trabajando en una solución a largo plazo y compatible con versiones anteriores.</p>
+</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="Nueva versión I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>Más mejoras de aplicaciones, auditoría de la estrategia de aislamiento de NetDB.</summary></details><p>Esta versión, I2P 2.5.0, ofrece más mejoras orientadas al usuario que la versión 2.4.0, que se centró en implementar la estrategia de aislamiento de NetDB.</p>
+<p>Se han añadido nuevas funciones a I2PSnark, como la capacidad de buscar a través de torrents. 
+Se han corregido errores para mejorar la compatibilidad con otros clientes de torrents de I2P, como BiglyBT y qBittorrent. 
+Nos gustaría agradecer a todos los desarrolladores que han trabajado con libtorrent y qBittorrent para habilitar y mejorar su soporte para I2P. 
+También se han añadido nuevas funciones a SusiMail, incluyendo soporte para el formato Markdown en correos electrónicos y la capacidad de arrastrar y soltar archivos adjuntos en correos electrónicos. 
+Los túneles creados con el administrador de Servicios Ocultos ahora soportan "Keepalive", lo que mejora el rendimiento y la compatibilidad con tecnologías web, permitiendo sitios I2P más sofisticados.</p>
+<p>Durante esta versión también realizamos varios ajustes en la NetDB para mejorar su resistencia al spam y la capacidad del router para rechazar mensajes sospechosos. 
+Esto fue parte de un esfuerzo por "auditar" la implementación de las defensas de "aislamiento de Sub-DB" de la versión 2.4.0. 
+Esta investigación descubrió un evento menor que rompía el aislamiento, el cual reparamos. 
+Este problema fue descubierto y solucionado internamente por el equipo de I2P.</p>
+<p>Durante esta versión se realizaron varias mejoras en el proceso de lanzamiento de nuestras distribuciones downstream para Android y Windows. 
+Esto debería resultar en una mejor entrega y disponibilidad de estos productos downstream.</p>
+<p>Como es habitual, le recomendamos que actualice a esta versión.
+La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
+</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="Lanzamiento de I2P 2.4.0 con mejoras en la congestión y la seguridad de NetDB." href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>Lanzamiento de I2P 2.4.0 con mejoras en la congestión y la seguridad de NetDB.</summary></details><p>Esta versión, I2P 2.4.0, continúa nuestro esfuerzo por mejorar la seguridad y estabilidad de la red I2P. 
+Contiene mejoras significativas en la Base de Datos de la Red, una estructura esencial dentro de la red I2P utilizada para descubrir a tus pares.</p>
+<p>Los cambios en la gestión de la congestión mejorarán la estabilidad de la red al dar a los enrutadores la capacidad de aliviar a los pares congestionados evitándolos. 
+Esto ayudará a la red a limitar el efecto del spam de túneles. 
+También ayudará a la red a recuperarse durante y después de los ataques DDOS.</p>
+<p>Los cambios en NetDb también ayudan a proteger los routers individuales y las aplicaciones que los utilizan. 
+Los routers ahora pueden defenderse contra atacantes separando el NetDB en múltiples "Sub-DB's", que usamos para prevenir fugas de información entre las aplicaciones y el router. 
+Esto también mejora la información disponible para los routers Java sobre su actividad en NetDB y simplifica nuestro soporte para aplicaciones multihoming.</p>
+<p>También se incluyen una serie de correcciones de errores y mejoras en las aplicaciones I2PSnark y SusiMail.</p>
+<p>Como es habitual, le recomendamos que actualice a esta versión.
+La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
+</article><article id="urn:uuid:" title="Nuevo lanzamiento I2P 2.3.0 - Correcciones de seguridad, listas de bloqueo ajustables, API DTG." href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Correcciones de seguridad, listas de bloqueo ajustables, API DTG</summary></details><p>Esta versión contiene correcciones para CVE-2023-36325. 
+CVE-2023-36325 es un error de confusión de contexto que ocurrió en el filtro de Bloom. 
+Un atacante elabora un mensaje I2NP que contiene un messageID único y envía ese messageID a un cliente. 
+El mensaje, después de pasar por el filtro de Bloom, no se permite reutilizar en un segundo mensaje. 
+El atacante luego envía el mismo mensaje directamente al enrutador. 
+El enrutador pasa el mensaje al filtro de Bloom y se descarta. 
+Esto filtra la información de que el messageID se ha visto antes, dando al atacante una fuerte razón para creer que el enrutador está alojando al cliente. 
+Esto se ha solucionado separando la funcionalidad del filtro de Bloom en diferentes contextos según si un mensaje provino de un túnel de cliente, un túnel exploratorio o se envió directamente al enrutador. 
+Bajo circunstancias normales, este ataque tarda varios días en realizarse con éxito y puede verse afectado por varios factores, como el reinicio de enrutadores durante la fase de ataque y la sensibilidad a falsos positivos. 
+Se recomienda a los usuarios de Java I2P que actualicen de inmediato para evitar el ataque.</p>
+<p>En el proceso de solucionar este error de confusión de contexto, hemos revisado algunas de nuestras estrategias para programar de manera defensiva contra este tipo de fugas. 
+Esto incluye ajustes en el netDb, los mecanismos de limitación de velocidad y el comportamiento de los routers floodfill.</p>
+<p>Esta versión añade not_bob como un segundo proveedor de hosts predeterminado, y añade <a href="http://notbob.i2p">notbob.i2p</a> y <a href="http://ramble.i2p">ramble.i2p</a> a la página de inicio de la consola.</p>
+<p>Esta versión también contiene una lista de bloqueo ajustable. 
+El bloqueo es semipermanente, cada dirección IP bloqueada normalmente permanece bloqueada hasta que se reinicia el router. 
+Los usuarios que observen un crecimiento explosivo de la lista de bloqueo durante ataques Sybil pueden optar por tiempos de espera más cortos configurando la lista de bloqueo para que las entradas expiren en un intervalo. 
+Esta función está desactivada por defecto y solo se recomienda para usuarios avanzados en este momento.</p>
+<p>Esta versión también incluye una API para que los complementos se modifiquen con la interfaz gráfica de escritorio (DTG). 
+Ahora es posible agregar elementos al menú de la bandeja del sistema, lo que permite un lanzamiento más intuitivo de los complementos que utilizan interfaces de aplicaciones nativas.</p>
+<p>Como es habitual, le recomendamos que actualice a esta versión.
+La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
+</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="Nueva versión 2.2.1, correcciones de empaquetado para Docker, Ubuntu Lunar y Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - versión de mantenimiento para 2.2.0</summary></details><p>Después del lanzamiento de I2P 2.2.0, que se adelantó para acelerar las mitigaciones de los ataques DDOS, nos enteramos de algunos problemas en desarrollo que hicieron necesario construir y lanzar nuevos paquetes.
+Esta versión soluciona un problema en Ubuntu Lunar y Debian Sid por el que no se podía acceder a la consola del router utilizando una versión actualizada del paquete jakarta.
+Los paquetes Docker no leían los argumentos correctamente, lo que resultaba en archivos de configuración inaccesibles.
+Este problema también se ha resuelto.
+
+El contenedor Docker ahora también es compatible con Podman.</p>
+<p>Esta versión sincroniza las traducciones con transifex y actualiza la base de datos GeoIP.</p>
+<p>Como es habitual, le recomendamos que actualice a esta versión.
+La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
+</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="Nueva versión 2.2.0. Mitigación de los ataques DDoS y ajustes del subsistema de streaming." href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigación de ataques DDoS y ajustes del subsistema de streaming</summary></details><p>Hemos decidido adelantar la fecha de lanzamiento de la versión 2.2.0, que tendrá lugar hoy, 13 de marzo de 2023.Esta versión incluye cambios en los componentes NetDB, Floodfill y Peer-Selection que mejoran la capacidad del router para sobrevivir a ataques DDOS.Es probable que los ataques continúen, pero las mejoras en estos sistemas ayudarán a mitigar el riesgo de ataques DDOS al ayudar al router a identificar y quitar prioridad a los routers que parezcan maliciosos.</p>
+<p>Esta versión también añade protección contra repeticiones al subsistema de streaming, lo que impide que un atacante que pueda capturar un paquete cifrado pueda reutilizarlo enviándolo a destinatarios no deseados.Se trata de un cambio compatible con versiones anteriores, por lo que los routers más antiguos podrán seguir utilizando las funciones de streaming de los routers más recientes.Este problema fue descubierto y solucionado internamente por el equipo de desarrollo de I2P y no está relacionado con los ataques DDoS.Nunca hemos encontrado un paquete de streaming reproducido en la naturaleza y no creemos que un ataque de repetición de streaming haya tenido lugar contra la red I2P en este momento.</p>
+<p>Como habréis notado, estas notas de publicación y la propia publicación han sido firmadas por idk, y no por zzz.zzz ha decidido alejarse del proyecto y sus responsabilidades están siendo asumidas por otros miembros del equipo.Por ello, el proyecto está trabajando en la sustitución de la infraestructura de estadísticas de red y en el traslado del foro de desarrollo a i2pforum.i2p.Agradecemos a zzz que haya prestado estos servicios durante tanto tiempo.</p>
+<p>Como es habitual, le recomendamos que actualice a esta versión.
+La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
+</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="Actualización DDoS" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>Actualización DDoS</summary></details><p>Hemos confirmado que el atacante controla un gran número de routers.Nuestras investigaciones y mitigaciones continúan.</p>
+<p>Es un buen momento para recordar que, incluso después de 20 años, la red I2P es relativamente pequeña.No tenemos pruebas de que el atacante esté intentando desanonimizar a ningún usuario en particular o servicio oculto.Sin embargo, si usted tiene un modelo de amenaza de alto riesgo, debería considerar cuidadosamente si I2P le proporciona actualmente la protección que necesita.La mejor solución, a largo plazo, es correr la voz y hacer crecer la red I2P para aumentar la seguridad de nuestros usuarios.</p>
+<p>Proporcionaremos información adicional aquí en el feed de noticias y en <a href="http://zzz.i2p">zzz.i2p</a> según sea necesario.Le pedimos paciencia mientras trabajamos para mejorar I2P.</p>
+</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="Acerca de los recientes ataques de denegación de servicio" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>La I2P permanece intacta con el rendimiento mermado</summary></details><p>La red I2P está siendo afectada por un ataque de denegación de servicio.La función floodfill de la red se ha visto afectada, lo que ha provocado la interrupción de las respuestas y el descenso de los índices de éxito en la construcción de túneles.Los participantes en la red han experimentado dificultades para conectarse a los sitios I2P y utilizar los servicios I2P.Se están investigando y aplicando gradualmente estrategias de mitigación.</p>
+<p>Aunque el ataque ha degradado el rendimiento, la red sigue intacta y utilizable.Los enrutadores Java I2P parecen manejar los problemas mejor que los enrutadores i2pd por ahora.En la próxima semana deberían empezar a aparecer varias mitigaciones en las versiones de desarrollo de los routers Java y C++.</p>
+</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="Publicada la 2.1.0" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 con varias correcciones de SSU2</summary></details><p>Hemos aprendido muchas cosas desde el lanzamiento de la versión 2.0.0 en noviembre. A medida que los routers se han actualizad, la red ha pasado de aproximadamente el 1% a más del 60% a usar el nuevo protocolo de transporte SSU2. Primero, hemos confirmado que el protocolo SSU2 es sólido y seguro. En segundo lugar, sin embargo, hemos encontrado y corregido numerosos errores menores o raramente activados en la implementación del protocolo. Los efectos de estos errores se han acumulado, reducido el rendimiento de la red.</p>
+<p>Además, somos conscientes del aumento del número de túneles y la reducción de la tasa de éxito en la construcción de túneles en la red,
+posiblemente provocados por la nueva función de dirección transitoria I2P de Bitcoin,
+pero empeorados por nuestros errores en SSU2 y otros problemas de control de congestión.
+Estamos trabajando con Bitcoin y otros proyectos que no son de Bitcoin para reducir las demandas de la red I2P.
+Hemos mejorado nuestros algoritmos para reducir la carga de la red durante tiempos de congestión.
+También estamos colaborando con i2pd para desarrollar estrategias comunes de control de la congestión.</p>
+<p>Por lo tanto, hemos acelerado este lanzamiento en unas seis semanas, para hacer llegar las correcciones a todo el mundo.
+i2pd lanzó su versión 2.45.0 la semana pasada y los primeros resultados son alentadores.
+Los nuevos protocolos y las redes distribuidas son difíciles de desarrollar.
+La congestión puede llegar con poca advertencia y con pocas pistas de la causa.
+Gracias por su paciencia, ya que hemos diagnosticado y, con suerte, solucionado los problemas.</p>
 <p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
 de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
-</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Entradas recientes del blog" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>
+</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="Lanzamiento de la versión 2.0.0" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>Transporte SSU2 habilitado</summary></details><p>La versión 2.0.0 de I2P habilita nuestro nuevo transporte UDP SSU2 para todos los usuarios, después de completar funciones menores, pruebas y numerosas correcciones de errores.</p>
+<p>También tenemos correcciones en todas partes, incluso para el instalador, la base de datos de la red, la adición a la libreta de direcciones privada, el iniciador del navegador de Windows y UPnP IPv6.</p>
+<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
+de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
+</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Entradas recientes del blog" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>Algunas publicaciones de blog recientes</summary></details><p>Aquí hay enlaces a varias publicaciones de blog recientes en nuestra web:</p>
 <ul>
-<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Overview of our new SSU2 transport</a></li>
-<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">A warning about I2P coins and other scams</a></li>
-<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">An interview with Konrad from diva.exchange</a></li>
-<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">An interview with Dustin from StormyCloud</a></li>
+<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Descripción general sobre nuestro nuevo transporte SSU2</a></li>
+<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">Advertencia sobre monedas I2P y otras estafas</a></li>
+<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">Una entrevista con Konrad de diva.exchange</a></li>
+<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">Una entrevista con Dustin de StormyCloud1</a></li>
 </ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="Lanzamiento de la versión 1.9.0" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 con SSU2 para pruebas</summary></details><p>Hemos pasado los últimos tres meses trabajando en nuestro nuevo protocolo de transporte UDP "SSU2"
 con un pequeño número de probadores voluntarios.
 Esta versión completa la implementación, incluyendo pruebas de retransmisión y de pares.

data/translations/entries.es_AR.html

@@ -1,14 +1,165 @@
 <div>
-<header title="Noticias de I2P">Suscripción (feed) de noticias, y actualizaciones del router I2P</header><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
-<p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
+<header title="Noticias de I2P">Suscripción (feed) de noticias, y actualizaciones del router I2P</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="Versión 2.8.2 Disponible" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>Versión 2.8.2 Disponible</summary></details><p>La versión 2.8.2 corrige un error que causaba fallos de SHA256 que se introdujo en la versión 2.8.1.
+El error afectaba principalmente a los enrutadores de alto ancho de banda.</p>
+<p>Como es habitual, le recomendamos que actualice a esta versión.
+La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
+</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="Versión 2.8.1 Disponible" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>Lanzamiento de I2P 2.8.1</summary></details><p>La versión 2.8.1 corrige los accesos a sitios locales que se rompieron en 2.8.0.
+Hemos añadido burbujas de notificación a varias aplicaciones en la consola para destacar los mensajes de la aplicación.
+Hemos corregido un error en la prueba del túnel que podría haber estado afectando a la fiabilidad del túnel.
+La libreta de direcciones ahora tiene una nueva pestaña "última" que muestra los nombres de host más recientes añadidos de tus suscripciones.
+Hay varias correcciones y mejoras en el tema oscuro.
+</p>
+<p>Arreglamos el instalador que antes fallaba en Java 21 o superior.
+También arreglamos la instalación en rutas de directorio que contienen espacios en Linux.
+Para los que usáis Docker, actualizamos el contenedor de Docker y las librerías de contenedor que estaban desactualizadas.
+</p>
+<p>Como es habitual, le recomendamos que actualice a esta versión.
+La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
+</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="El acceso al sitio local falla en 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Error de acceso local</summary></details><p>En la versión 2.8.0, navegar a un sitio local (ya sea por nombre de host o b32) fallará.
+La solución alternativa es usar localhost y el puerto del servidor, generalmente 7658, para evitar I2P.
+Por ejemplo, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
+Pedimos disculpas por el problema y estamos trabajando en una solución.
+</p>
+</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="Lanzamiento de I2P 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>Lanzamiento de I2P 2.8.0</summary></details><p>Esta versión mejora I2P al corregir errores, eliminar código no utilizado y mejorar la estabilidad de la red.</p>
+<p>Hemos mejorado el manejo de routers congestionados en la red. 
+Se abordaron problemas en UPnP y la transversalidad NAT para mejorar la conectividad y la notificación de errores. 
+Ahora tenemos una estrategia más agresiva para la eliminación de leasesets del NetDb con el fin de mejorar el rendimiento del router y mitigar la sobrecarga. 
+Se implementaron otros cambios para reducir la observabilidad de eventos como el reinicio o apagado de un router.</p>
+<p>Como es habitual, le recomendamos que actualice a esta versión.
+La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
+</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="Publicada la versión 2.7.0 de I2P" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>Publicada la versión 2.7.0 de I2P</summary></details><p>Esta versión, I2P 2.7.0, continúa nuestro trabajo corrigiendo errores, mejorando el rendimiento y añadiendo funciones.</p>
+<p>Se ha mejorado el acceso a la información desde la consola y las aplicaciones. 
+Se han solucionado problemas en I2PSnark y la búsqueda de SusiMail. 
+La búsqueda de netDB integrada en la consola del router ahora funciona de una manera más intuitiva y útil. 
+Se han realizado pequeñas mejoras en las pantallas de diagnóstico en modo avanzado.</p>
+<p>También se han corregido errores para mejorar la compatibilidad dentro de la red. 
+Se resolvió un problema con la publicación de leaseSets, lo que mejora la fiabilidad de los servicios ocultos principales. 
+I2PSnark ya no cambia el infohash cuando un usuario solo modifica los trackers en un torrent existente. 
+Esto evita que los torrents se vean innecesariamente interrumpidos por estos cambios. 
+Damos la bienvenida a esta contribución de un nuevo colaborador. 
+Se resolvió un conflicto en el manejo de una opción de la biblioteca de streaming para mejorar la compatibilidad con otras implementaciones de I2P.</p>
+<p>Como es habitual, le recomendamos que actualice a esta versión.
+La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
+</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="Publicada la versión 2.6.1 de I2P" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>Publicada la versión 2.6.1 de I2P</summary></details><p>I2P 2.6.1 se lanza para corregir un error en la interfaz de usuario de la aplicación Hidden Services Manager. 
+Este error deshabilitaba el desplazamiento, haciendo que algunas configuraciones fueran inaccesibles.</p>
+<p>Como es habitual, le recomendamos que actualice a esta versión.
+La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
+</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="Publicada la versión 2.6.0 de I2P" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>Publicada la versión 2.6.0 de I2P</summary></details><p>Esta versión, I2P 2.6.0, continúa nuestro trabajo al corregir errores, agregar funciones y mejorar la fiabilidad de la red.</p>
+<p>Se favorecerán los routers más nuevos al seleccionar routers floodfill. 
+I2PSnark recibió funciones que mejoran el rendimiento de PeX (Intercambio de Pares), además de correcciones de errores. 
+Se están eliminando los protocolos de transporte heredados, simplificando el código en los transportes UDP. 
+Los destinos alojados localmente serán accesibles para los clientes locales sin solicitar su LeaseSet, mejorando el rendimiento y la capacidad de prueba. 
+Se realizaron ajustes adicionales en las estrategias de selección de pares.</p>
+<p>I2P ya no permite I2P-sobre-Tor, las conexiones desde direcciones IP de salida de Tor ahora están bloqueadas. 
+Desalentamos esto porque degrada el rendimiento de I2P y consume los recursos de las salidas de Tor sin ningún beneficio. 
+Si eres una persona solidaria que opera tanto una salida de Tor como I2P, te animamos a continuar haciéndolo, utilizando direcciones IP diferentes para cada uno. 
+Los relés no de salida y los clientes de Tor no se ven afectados por esto y no necesitan cambiar nada.</p>
+<p>Como es habitual, le recomendamos que actualice a esta versión.
+La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
+</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="Publicada la versión 2.5.2 de I2P" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 con corrección de HTTP</summary></details><p>Se publica I2P 2.5.2 para corregir un error introducido en 2.5.0 que provocaba el truncamiento de algunos contenidos HTTP.</p>
+<p>Como es habitual, le recomendamos que actualice a esta versión.
+La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
+</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="Publicada la versión 2.5.1 de I2P" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>Lanzamiento de la versión 2.5.1 de I2P para hacer frente a los ataques de denegación de servicio</summary></details><p>"I2P 2.5.1 se ha lanzado para abordar los ataques de Denegación de Servicio que afectan a la red y los servicios de I2P. 
+Con este lanzamiento, deshabilitamos las partes basadas en IP de la herramienta de detección de ataques Sybil, que estaban dirigidas a amplificar el efecto y la duración del ataque. 
+Esto debería ayudar a que la red vuelva a la operación normal. 
+Aquellos de ustedes que han deshabilitado la herramienta de detección de ataques Sybil pueden volver a habilitarla de forma segura. 
+También se han realizado ajustes en otros subsistemas para mejorar la validación de RouterInfo y la selección de pares."</p>
+<p>Como es habitual, le recomendamos que actualice a esta versión.
+La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
+</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Clima tormentoso." href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Clima de la red: Tormentoso. I2P está bajo ataque.</summary></details><p>La red I2P está actualmente bajo un ataque de Denegación de Servicio. 
+Este ataque afecta a I2P e i2pd, pero de diferentes maneras, y está teniendo un efecto grave en la salud de la red. 
+La accesibilidad de los sitios de I2P está gravemente degradada.</p>
+<p>Si estás alojando un servicio dentro de I2P y está alojado en un router Floodfill, deberías considerar alojar el servicio también en un router con Floodfill deshabilitado para mejorar la accesibilidad. 
+Se están discutiendo otras mitigaciones, pero todavía se está trabajando en una solución a largo plazo y compatible con versiones anteriores.</p>
+</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="Nueva versión I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>Más mejoras de aplicaciones, auditoría de la estrategia de aislamiento de NetDB.</summary></details><p>Esta versión, I2P 2.5.0, ofrece más mejoras orientadas al usuario que la versión 2.4.0, que se centró en implementar la estrategia de aislamiento de NetDB.</p>
+<p>Se han añadido nuevas funciones a I2PSnark, como la capacidad de buscar a través de torrents. 
+Se han corregido errores para mejorar la compatibilidad con otros clientes de torrents de I2P, como BiglyBT y qBittorrent. 
+Nos gustaría agradecer a todos los desarrolladores que han trabajado con libtorrent y qBittorrent para habilitar y mejorar su soporte para I2P. 
+También se han añadido nuevas funciones a SusiMail, incluyendo soporte para el formato Markdown en correos electrónicos y la capacidad de arrastrar y soltar archivos adjuntos en correos electrónicos. 
+Los túneles creados con el administrador de Servicios Ocultos ahora soportan "Keepalive", lo que mejora el rendimiento y la compatibilidad con tecnologías web, permitiendo sitios I2P más sofisticados.</p>
+<p>Durante esta versión también realizamos varios ajustes en la NetDB para mejorar su resistencia al spam y la capacidad del router para rechazar mensajes sospechosos. 
+Esto fue parte de un esfuerzo por "auditar" la implementación de las defensas de "aislamiento de Sub-DB" de la versión 2.4.0. 
+Esta investigación descubrió un evento menor que rompía el aislamiento, el cual reparamos. 
+Este problema fue descubierto y solucionado internamente por el equipo de I2P.</p>
+<p>Durante esta versión se realizaron varias mejoras en el proceso de lanzamiento de nuestras distribuciones downstream para Android y Windows. 
+Esto debería resultar en una mejor entrega y disponibilidad de estos productos downstream.</p>
+<p>Como es habitual, le recomendamos que actualice a esta versión.
+La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
+</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="Lanzamiento de I2P 2.4.0 con mejoras en la congestión y la seguridad de NetDB." href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>Lanzamiento de I2P 2.4.0 con mejoras en la congestión y la seguridad de NetDB.</summary></details><p>Esta versión, I2P 2.4.0, continúa nuestro esfuerzo por mejorar la seguridad y estabilidad de la red I2P. 
+Contiene mejoras significativas en la Base de Datos de la Red, una estructura esencial dentro de la red I2P utilizada para descubrir a tus pares.</p>
+<p>Los cambios en la gestión de la congestión mejorarán la estabilidad de la red al dar a los enrutadores la capacidad de aliviar a los pares congestionados evitándolos. 
+Esto ayudará a la red a limitar el efecto del spam de túneles. 
+También ayudará a la red a recuperarse durante y después de los ataques DDOS.</p>
+<p>Los cambios en NetDb también ayudan a proteger los routers individuales y las aplicaciones que los utilizan. 
+Los routers ahora pueden defenderse contra atacantes separando el NetDB en múltiples "Sub-DB's", que usamos para prevenir fugas de información entre las aplicaciones y el router. 
+Esto también mejora la información disponible para los routers Java sobre su actividad en NetDB y simplifica nuestro soporte para aplicaciones multihoming.</p>
+<p>También se incluyen una serie de correcciones de errores y mejoras en las aplicaciones I2PSnark y SusiMail.</p>
+<p>Como es habitual, le recomendamos que actualice a esta versión.
+La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
+</article><article id="urn:uuid:" title="Nuevo lanzamiento I2P 2.3.0 - Correcciones de seguridad, listas de bloqueo ajustables, API DTG." href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Correcciones de seguridad, listas de bloqueo ajustables, API DTG</summary></details><p>Esta versión contiene correcciones para CVE-2023-36325. 
+CVE-2023-36325 es un error de confusión de contexto que ocurrió en el filtro de Bloom. 
+Un atacante elabora un mensaje I2NP que contiene un messageID único y envía ese messageID a un cliente. 
+El mensaje, después de pasar por el filtro de Bloom, no se permite reutilizar en un segundo mensaje. 
+El atacante luego envía el mismo mensaje directamente al enrutador. 
+El enrutador pasa el mensaje al filtro de Bloom y se descarta. 
+Esto filtra la información de que el messageID se ha visto antes, dando al atacante una fuerte razón para creer que el enrutador está alojando al cliente. 
+Esto se ha solucionado separando la funcionalidad del filtro de Bloom en diferentes contextos según si un mensaje provino de un túnel de cliente, un túnel exploratorio o se envió directamente al enrutador. 
+Bajo circunstancias normales, este ataque tarda varios días en realizarse con éxito y puede verse afectado por varios factores, como el reinicio de enrutadores durante la fase de ataque y la sensibilidad a falsos positivos. 
+Se recomienda a los usuarios de Java I2P que actualicen de inmediato para evitar el ataque.</p>
+<p>En el proceso de solucionar este error de confusión de contexto, hemos revisado algunas de nuestras estrategias para programar de manera defensiva contra este tipo de fugas. 
+Esto incluye ajustes en el netDb, los mecanismos de limitación de velocidad y el comportamiento de los routers floodfill.</p>
+<p>Esta versión añade not_bob como un segundo proveedor de hosts predeterminado, y añade <a href="http://notbob.i2p">notbob.i2p</a> y <a href="http://ramble.i2p">ramble.i2p</a> a la página de inicio de la consola.</p>
+<p>Esta versión también contiene una lista de bloqueo ajustable. 
+El bloqueo es semipermanente, cada dirección IP bloqueada normalmente permanece bloqueada hasta que se reinicia el router. 
+Los usuarios que observen un crecimiento explosivo de la lista de bloqueo durante ataques Sybil pueden optar por tiempos de espera más cortos configurando la lista de bloqueo para que las entradas expiren en un intervalo. 
+Esta función está desactivada por defecto y solo se recomienda para usuarios avanzados en este momento.</p>
+<p>Esta versión también incluye una API para que los complementos se modifiquen con la interfaz gráfica de escritorio (DTG). 
+Ahora es posible agregar elementos al menú de la bandeja del sistema, lo que permite un lanzamiento más intuitivo de los complementos que utilizan interfaces de aplicaciones nativas.</p>
+<p>Como es habitual, le recomendamos que actualice a esta versión.
+La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
+</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="Nueva versión 2.2.1, correcciones de empaquetado para Docker, Ubuntu Lunar y Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - versión de mantenimiento para 2.2.0</summary></details><p>Después del lanzamiento de I2P 2.2.0, que se adelantó para acelerar las mitigaciones de los ataques DDOS, nos enteramos de algunos problemas en desarrollo que hicieron necesario construir y lanzar nuevos paquetes.
+Esta versión soluciona un problema en Ubuntu Lunar y Debian Sid por el que no se podía acceder a la consola del router utilizando una versión actualizada del paquete jakarta.
+Los paquetes Docker no leían los argumentos correctamente, lo que resultaba en archivos de configuración inaccesibles.
+Este problema también se ha resuelto.
+
+El contenedor Docker ahora también es compatible con Podman.</p>
+<p>Esta versión sincroniza las traducciones con transifex y actualiza la base de datos GeoIP.</p>
+<p>Como es habitual, le recomendamos que actualice a esta versión.
+La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
+</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="Nueva versión 2.2.0. Mitigación de los ataques DDoS y ajustes del subsistema de streaming." href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigación de ataques DDoS y ajustes del subsistema de streaming</summary></details><p>Hemos decidido adelantar la fecha de lanzamiento de la versión 2.2.0, que tendrá lugar hoy, 13 de marzo de 2023.Esta versión incluye cambios en los componentes NetDB, Floodfill y Peer-Selection que mejoran la capacidad del router para sobrevivir a ataques DDOS.Es probable que los ataques continúen, pero las mejoras en estos sistemas ayudarán a mitigar el riesgo de ataques DDOS al ayudar al router a identificar y quitar prioridad a los routers que parezcan maliciosos.</p>
+<p>Esta versión también añade protección contra repeticiones al subsistema de streaming, lo que impide que un atacante que pueda capturar un paquete cifrado pueda reutilizarlo enviándolo a destinatarios no deseados.Se trata de un cambio compatible con versiones anteriores, por lo que los routers más antiguos podrán seguir utilizando las funciones de streaming de los routers más recientes.Este problema fue descubierto y solucionado internamente por el equipo de desarrollo de I2P y no está relacionado con los ataques DDoS.Nunca hemos encontrado un paquete de streaming reproducido en la naturaleza y no creemos que un ataque de repetición de streaming haya tenido lugar contra la red I2P en este momento.</p>
+<p>Como habréis notado, estas notas de publicación y la propia publicación han sido firmadas por idk, y no por zzz.zzz ha decidido alejarse del proyecto y sus responsabilidades están siendo asumidas por otros miembros del equipo.Por ello, el proyecto está trabajando en la sustitución de la infraestructura de estadísticas de red y en el traslado del foro de desarrollo a i2pforum.i2p.Agradecemos a zzz que haya prestado estos servicios durante tanto tiempo.</p>
+<p>Como es habitual, le recomendamos que actualice a esta versión.
+La mejor manera de mantener la seguridad y ayudar a la red es ejecutar la última versión.</p>
+</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="Actualización DDoS" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>Actualización DDoS</summary></details><p>Hemos confirmado que el atacante controla un gran número de routers.Nuestras investigaciones y mitigaciones continúan.</p>
+<p>Es un buen momento para recordar que, incluso después de 20 años, la red I2P es relativamente pequeña.No tenemos pruebas de que el atacante esté intentando desanonimizar a ningún usuario en particular o servicio oculto.Sin embargo, si usted tiene un modelo de amenaza de alto riesgo, debería considerar cuidadosamente si I2P le proporciona actualmente la protección que necesita.La mejor solución, a largo plazo, es correr la voz y hacer crecer la red I2P para aumentar la seguridad de nuestros usuarios.</p>
+<p>Proporcionaremos información adicional aquí en el feed de noticias y en <a href="http://zzz.i2p">zzz.i2p</a> según sea necesario.Le pedimos paciencia mientras trabajamos para mejorar I2P.</p>
+</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="Acerca de los recientes ataques de denegación de servicio" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>La I2P permanece intacta con el rendimiento mermado</summary></details><p>La red I2P está siendo afectada por un ataque de denegación de servicio.La función floodfill de la red se ha visto afectada, lo que ha provocado la interrupción de las respuestas y el descenso de los índices de éxito en la construcción de túneles.Los participantes en la red han experimentado dificultades para conectarse a los sitios I2P y utilizar los servicios I2P.Se están investigando y aplicando gradualmente estrategias de mitigación.</p>
+<p>Aunque el ataque ha degradado el rendimiento, la red sigue intacta y utilizable.Los enrutadores Java I2P parecen manejar los problemas mejor que los enrutadores i2pd por ahora.En la próxima semana deberían empezar a aparecer varias mitigaciones en las versiones de desarrollo de los routers Java y C++.</p>
+</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="Publicada la 2.1.0" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 con varias correcciones de SSU2</summary></details><p>Hemos aprendido muchas cosas desde el lanzamiento de la versión 2.0.0 en noviembre. A medida que los routers se han actualizad, la red ha pasado de aproximadamente el 1% a más del 60% a usar el nuevo protocolo de transporte SSU2. Primero, hemos confirmado que el protocolo SSU2 es sólido y seguro. En segundo lugar, sin embargo, hemos encontrado y corregido numerosos errores menores o raramente activados en la implementación del protocolo. Los efectos de estos errores se han acumulado, reducido el rendimiento de la red.</p>
+<p>Además, somos conscientes del aumento del número de túneles y la reducción de la tasa de éxito en la construcción de túneles en la red,
+posiblemente provocados por la nueva función de dirección transitoria I2P de Bitcoin,
+pero empeorados por nuestros errores en SSU2 y otros problemas de control de congestión.
+Estamos trabajando con Bitcoin y otros proyectos que no son de Bitcoin para reducir las demandas de la red I2P.
+Hemos mejorado nuestros algoritmos para reducir la carga de la red durante tiempos de congestión.
+También estamos colaborando con i2pd para desarrollar estrategias comunes de control de la congestión.</p>
+<p>Por lo tanto, hemos acelerado este lanzamiento en unas seis semanas, para hacer llegar las correcciones a todo el mundo.
+i2pd lanzó su versión 2.45.0 la semana pasada y los primeros resultados son alentadores.
+Los nuevos protocolos y las redes distribuidas son difíciles de desarrollar.
+La congestión puede llegar con poca advertencia y con pocas pistas de la causa.
+Gracias por su paciencia, ya que hemos diagnosticado y, con suerte, solucionado los problemas.</p>
 <p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
 de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
-</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Entradas recientes del blog" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>
+</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="Lanzamiento de la versión 2.0.0" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>Transporte SSU2 habilitado</summary></details><p>La versión 2.0.0 de I2P habilita nuestro nuevo transporte UDP SSU2 para todos los usuarios, después de completar funciones menores, pruebas y numerosas correcciones de errores.</p>
+<p>También tenemos correcciones en todas partes, incluso para el instalador, la base de datos de la red, la adición a la libreta de direcciones privada, el iniciador del navegador de Windows y UPnP IPv6.</p>
+<p>Como es habitual, recomendamos que actualice a esta versión. La mejor manera
+de mantener la seguridad y ayudar a la red, es ejecutar la última versión.</p>
+</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Entradas recientes del blog" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>Algunas publicaciones de blog recientes</summary></details><p>Aquí hay enlaces a varias publicaciones de blog recientes en nuestra web:</p>
 <ul>
-<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Overview of our new SSU2 transport</a></li>
-<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">A warning about I2P coins and other scams</a></li>
-<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">An interview with Konrad from diva.exchange</a></li>
-<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">An interview with Dustin from StormyCloud</a></li>
+<li>Descripción general sobre nuestro nuevo transporte SSU2</li>
+<li>Advertencia sobre monedas I2P y otras estafas</li>
+<li>Una entrevista con Konrad de diva.exchange</li>
+<li>Una entrevista con Dustin de StormyCloud1</li>
 </ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="Lanzamiento de la versión 1.9.0" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 con SSU2 para pruebas</summary></details><p>Hemos pasado los últimos tres meses trabajando en nuestro nuevo protocolo de transporte UDP "SSU2"
 con un pequeño número de probadores voluntarios.
 Esta versión completa la implementación, incluyendo pruebas de retransmisión y de pares.

data/translations/entries.fa.html

@@ -1,5 +1,173 @@
 <div>
-<header title="اخبار I2P">خوراک خبری و به روز رسانی‌های مسیریاب</header><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
+<header title="اخبار I2P">خوراک خبری و به روز رسانی‌های مسیریاب</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
+The bug primarily affected high-bandwidth routers.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
+We have added notification bubbles to several applications in the console to highlight application messages.
+We fixed a tunnel test bug that may have been affecting tunnel reliability.
+The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
+There are several dark theme fixes and improvements.</p>
+<p>We fixed the installer that previously failed on Java 21 or higher.
+We also fixed installing to directory paths that contain spaces on Linux.
+For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
+The workaround is using localhost and the server port, usually 7658, to bypass I2P.
+For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
+We apologize for the issue and are working on a fix.</p>
+</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
+<p>We have improved handling of congested routers in the network.
+Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
+We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
+Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
+<p>Access to information from the console and applications has been improved.
+Issues have been fixed in I2PSnark and SusiMail search.
+The netDB search embedded into the router console now operates in a more intuitive and useful way.
+Minor improvements have been made to diagnostic displays in advanced mode.</p>
+<p>Bugs have also been fixed to improve compatibility within the network.
+An issue with publishing leaseSets was solved which improves reliability major hidden services.
+I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
+This prevents torrents from being unnecessarily disrupted by these changes.
+We welcomed this contribution from a new contributor.
+A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
+This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
+<p>Newer routers will be favored when selecting floodfill routers.
+I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
+Legacy transport protocols are being removed, simplifying the code in the UDP transports.
+Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
+Additional tweaks were made to peer selection strategies.</p>
+<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
+We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
+If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
+Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
+With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
+This should help the network return to normal operation.
+Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
+Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
+This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
+Reachability of I2P sites is badly degraded.</p>
+<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
+Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
+</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
+<p>New features have been added to I2PSnark like the ability to search through torrents.
+Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
+We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
+New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
+Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
+<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
+This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
+This investigation uncovered one minor isolation-piercing event which we repaired.
+This issue was discovered and fixed internally by the I2P team.</p>
+<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
+This should result in improved delivery and availability for these downstream products.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
+It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
+<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
+This will help the network limit the effect of tunnel spam.
+It will also help the network heal during and after DDOS attacks.</p>
+<p>The NetDb changes also help secure individual routers and the applications that use them. 
+Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
+This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
+<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
+CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
+An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
+The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
+The attacker then sends the same message directly to the router.
+The router passes the message to the bloom filter, and is dropped.
+This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
+This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
+Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
+Users of Java I2P are recommended to update immediately to avoid the attack.</p>
+<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
+This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
+<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
+<p>This release also contains a tweakable blocklist.
+Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
+Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
+This feature is off-by-default and is only recommended for advanced users at this time.</p>
+<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
+It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
+This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
+Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
+This issue has also been resolved.
+The docker container is now also compatible with Podman.</p>
+<p>This release syncs translations with transifex and updates the GeoIP database.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
+This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
+The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
+<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
+This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
+This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
+We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
+<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
+zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
+As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
+We thank zzz for providing these services for such a long time.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
+Our investigations and mitigations continue.</p>
+<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
+We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
+However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
+The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
+<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
+We ask for your patience as we work to improve I2P.</p>
+</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
+  The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
+  Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
+  Mitigation strategies are being investigated and implemented gradually.</p>
+<p>While the attack has degraded performance, the network remains intact and usable.
+  Java I2P routers appear to be handling the issues better than i2pd routers for now.
+  Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
+</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
+As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
+First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
+Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
+Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
+<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
+possibly triggered by Bitcoin's new I2P transient address feature,
+but made worse by our SSU2 bugs and other congestion control problems.
+We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
+We have improved our algorithms to reduce network load during times of congestion.
+We are also collaborating with i2pd to develop common congestion control strategies.</p>
+<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
+i2pd released their version 2.45.0 last week and the early results are encouraging.
+New protocols, and distributed networks, are difficult to develop.
+Congestion can arrive with little warning and with little clue of the cause.
+Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
+<p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید. بهترین روش برای تامین امنیت و کمک به شبکه، به‌روز رسانی به آخرین نسخه است.</p>
+</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
 <p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
 <p>مانند همیشه ما توصیه می کنیم به این نسخه به روز رسانی کنید. بهترین روش برای تامین امنیت و کمک به شبکه، به‌روز رسانی به آخرین نسخه است.</p>
 </article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Recent Blog Posts" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>

data/translations/entries.fi.html

@@ -1,5 +1,174 @@
 <div>
-<header title="I2P-uutiset">Uutissyöte ja reititinpäivitykset</header><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
+<header title="I2P-uutiset">Uutissyöte ja reititinpäivitykset</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
+The bug primarily affected high-bandwidth routers.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
+We have added notification bubbles to several applications in the console to highlight application messages.
+We fixed a tunnel test bug that may have been affecting tunnel reliability.
+The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
+There are several dark theme fixes and improvements.</p>
+<p>We fixed the installer that previously failed on Java 21 or higher.
+We also fixed installing to directory paths that contain spaces on Linux.
+For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
+The workaround is using localhost and the server port, usually 7658, to bypass I2P.
+For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
+We apologize for the issue and are working on a fix.</p>
+</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
+<p>We have improved handling of congested routers in the network.
+Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
+We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
+Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
+<p>Access to information from the console and applications has been improved.
+Issues have been fixed in I2PSnark and SusiMail search.
+The netDB search embedded into the router console now operates in a more intuitive and useful way.
+Minor improvements have been made to diagnostic displays in advanced mode.</p>
+<p>Bugs have also been fixed to improve compatibility within the network.
+An issue with publishing leaseSets was solved which improves reliability major hidden services.
+I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
+This prevents torrents from being unnecessarily disrupted by these changes.
+We welcomed this contribution from a new contributor.
+A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
+This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
+<p>Newer routers will be favored when selecting floodfill routers.
+I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
+Legacy transport protocols are being removed, simplifying the code in the UDP transports.
+Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
+Additional tweaks were made to peer selection strategies.</p>
+<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
+We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
+If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
+Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
+With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
+This should help the network return to normal operation.
+Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
+Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
+This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
+Reachability of I2P sites is badly degraded.</p>
+<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
+Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
+</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
+<p>New features have been added to I2PSnark like the ability to search through torrents.
+Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
+We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
+New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
+Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
+<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
+This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
+This investigation uncovered one minor isolation-piercing event which we repaired.
+This issue was discovered and fixed internally by the I2P team.</p>
+<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
+This should result in improved delivery and availability for these downstream products.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
+It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
+<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
+This will help the network limit the effect of tunnel spam.
+It will also help the network heal during and after DDOS attacks.</p>
+<p>The NetDb changes also help secure individual routers and the applications that use them. 
+Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
+This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
+<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
+CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
+An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
+The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
+The attacker then sends the same message directly to the router.
+The router passes the message to the bloom filter, and is dropped.
+This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
+This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
+Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
+Users of Java I2P are recommended to update immediately to avoid the attack.</p>
+<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
+This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
+<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
+<p>This release also contains a tweakable blocklist.
+Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
+Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
+This feature is off-by-default and is only recommended for advanced users at this time.</p>
+<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
+It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
+This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
+Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
+This issue has also been resolved.
+The docker container is now also compatible with Podman.</p>
+<p>This release syncs translations with transifex and updates the GeoIP database.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
+This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
+The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
+<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
+This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
+This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
+We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
+<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
+zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
+As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
+We thank zzz for providing these services for such a long time.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
+Our investigations and mitigations continue.</p>
+<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
+We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
+However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
+The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
+<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
+We ask for your patience as we work to improve I2P.</p>
+</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
+  The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
+  Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
+  Mitigation strategies are being investigated and implemented gradually.</p>
+<p>While the attack has degraded performance, the network remains intact and usable.
+  Java I2P routers appear to be handling the issues better than i2pd routers for now.
+  Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
+</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
+As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
+First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
+Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
+Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
+<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
+possibly triggered by Bitcoin's new I2P transient address feature,
+but made worse by our SSU2 bugs and other congestion control problems.
+We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
+We have improved our algorithms to reduce network load during times of congestion.
+We are also collaborating with i2pd to develop common congestion control strategies.</p>
+<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
+i2pd released their version 2.45.0 last week and the early results are encouraging.
+New protocols, and distributed networks, are difficult to develop.
+Congestion can arrive with little warning and with little clue of the cause.
+Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
 <p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
 <p>As usual, we recommend that you update to this release. The best way to
 maintain security and help the network is to run the latest release.</p>

data/translations/entries.fr.html

@@ -1,22 +1,190 @@
 <div>
-<header title="Nouvelles d’I2P">Fil de nouvelles et mises à jour du routeur</header><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
-<p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
+<header title="Nouvelles d’I2P">Fil de nouvelles et mises à jour du routeur</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
+The bug primarily affected high-bandwidth routers.</p>
+<p>Comme d’habitude, nous recommandons que vous mettiez à jour vers cette version.
+La meilleure façon de maintenir la sécurité et d’aider le réseau est d’exécuter la dernière version</p>
+</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
+We have added notification bubbles to several applications in the console to highlight application messages.
+We fixed a tunnel test bug that may have been affecting tunnel reliability.
+The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
+There are several dark theme fixes and improvements.</p>
+<p>We fixed the installer that previously failed on Java 21 or higher.
+We also fixed installing to directory paths that contain spaces on Linux.
+For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
+<p>Comme d’habitude, nous recommandons que vous mettiez à jour vers cette version.
+La meilleure façon de maintenir la sécurité et d’aider le réseau est d’exécuter la dernière version</p>
+</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
+The workaround is using localhost and the server port, usually 7658, to bypass I2P.
+For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
+We apologize for the issue and are working on a fix.</p>
+</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P version 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P version 2.8.0</summary></details><p>Cette version améliore I2P en corrigeant des bogues, en retirant du code inutilisé, et en améliorant la stabilité du réseau.</p>
+<p>Nous avons amélioré la gestion de congestion des routeurs sur le réseau.
+Les problèmes avec l'UPnP et le passage de NAT ont été adressés afin d'améliorer la connectivité et l'envoi d'erreurs.
+Nous avons maintenant une stratégie plus agressive pour le retrait des jeux de baux de la BDréseau pour améliorer les performances des routeurs et atténuer leur surcharge.
+D'autres changements ont été implémentés pour réduire la visibilité d'évènements comme un routeur redémarrant ou s'éteignant</p>
+<p>Comme d’habitude, nous recommandons que vous mettiez à jour vers cette version.
+La meilleure façon de maintenir la sécurité et d’aider le réseau est d’exécuter la dernière version</p>
+</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P version 2.7.0" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P version 2.7.0</summary></details><p>Avec cette version, I2P 2.7.0 continue notre travail sur le réglage de bugs, l'amélioration des performances, et en rajoutant de nouvelles fonctionnalités. </p>
+<p>L'accès aux informations depuis le tableau de bord et les applications à été amélioré.
+Des erreurs ont été réglé dans la barre de recherche de I2PSnark et SusiMail.
+Le netDB embarqué dans le tableau de bord opère fonctionne d'une manière plus utile et plus intuitive.
+Plusieures améliorations mineures ont été effectuées dans les écrans de diagnostics dans le mode avancé. </p>
+<p>Bugs have also been fixed to improve compatibility within the network.
+An issue with publishing leaseSets was solved which improves reliability major hidden services.
+I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
+This prevents torrents from being unnecessarily disrupted by these changes.
+We welcomed this contribution from a new contributor.
+A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
+<p>Comme d’habitude, nous recommandons que vous mettiez à jour vers cette version.
+La meilleure façon de maintenir la sécurité et d’aider le réseau est d’exécuter la dernière version</p>
+</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
+This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
+<p>Comme d’habitude, nous recommandons que vous mettiez à jour vers cette version.
+La meilleure façon de maintenir la sécurité et d’aider le réseau est d’exécuter la dernière version</p>
+</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
+<p>Newer routers will be favored when selecting floodfill routers.
+I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
+Legacy transport protocols are being removed, simplifying the code in the UDP transports.
+Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
+Additional tweaks were made to peer selection strategies.</p>
+<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
+We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
+If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
+Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
+<p>Comme d’habitude, nous recommandons que vous mettiez à jour vers cette version.
+La meilleure façon de maintenir la sécurité et d’aider le réseau est d’exécuter la dernière version</p>
+</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
+<p>Comme d’habitude, nous recommandons que vous mettiez à jour vers cette version.
+La meilleure façon de maintenir la sécurité et d’aider le réseau est d’exécuter la dernière version</p>
+</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
+With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
+This should help the network return to normal operation.
+Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
+Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
+<p>Comme d’habitude, nous recommandons que vous mettiez à jour vers cette version.
+La meilleure façon de maintenir la sécurité et d’aider le réseau est d’exécuter la dernière version</p>
+</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
+This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
+Reachability of I2P sites is badly degraded.</p>
+<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
+Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
+</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
+<p>New features have been added to I2PSnark like the ability to search through torrents.
+Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
+We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
+New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
+Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
+<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
+This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
+This investigation uncovered one minor isolation-piercing event which we repaired.
+This issue was discovered and fixed internally by the I2P team.</p>
+<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
+This should result in improved delivery and availability for these downstream products.</p>
+<p>Comme d’habitude, nous recommandons que vous mettiez à jour vers cette version.
+La meilleure façon de maintenir la sécurité et d’aider le réseau est d’exécuter la dernière version</p>
+</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
+It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
+<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
+This will help the network limit the effect of tunnel spam.
+It will also help the network heal during and after DDOS attacks.</p>
+<p>The NetDb changes also help secure individual routers and the applications that use them. 
+Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
+This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
+<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
+<p>Comme d’habitude, nous recommandons que vous mettiez à jour vers cette version.
+La meilleure façon de maintenir la sécurité et d’aider le réseau est d’exécuter la dernière version</p>
+</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
+CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
+An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
+The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
+The attacker then sends the same message directly to the router.
+The router passes the message to the bloom filter, and is dropped.
+This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
+This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
+Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
+Users of Java I2P are recommended to update immediately to avoid the attack.</p>
+<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
+This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
+<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
+<p>This release also contains a tweakable blocklist.
+Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
+Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
+This feature is off-by-default and is only recommended for advanced users at this time.</p>
+<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
+It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
+<p>Comme d’habitude, nous recommandons que vous mettiez à jour vers cette version.
+La meilleure façon de maintenir la sécurité et d’aider le réseau est d’exécuter la dernière version</p>
+</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
+This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
+Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
+This issue has also been resolved.
+The docker container is now also compatible with Podman.</p>
+<p>This release syncs translations with transifex and updates the GeoIP database.</p>
+<p>Comme d’habitude, nous recommandons que vous mettiez à jour vers cette version.
+La meilleure façon de maintenir la sécurité et d’aider le réseau est d’exécuter la dernière version</p>
+</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
+This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
+The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
+<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
+This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
+This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
+We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
+<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
+zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
+As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
+We thank zzz for providing these services for such a long time.</p>
+<p>Comme d’habitude, nous recommandons que vous mettiez à jour vers cette version.
+La meilleure façon de maintenir la sécurité et d’aider le réseau est d’exécuter la dernière version</p>
+</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
+Our investigations and mitigations continue.</p>
+<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
+We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
+However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
+The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
+<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
+We ask for your patience as we work to improve I2P.</p>
+</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
+  The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
+  Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
+  Mitigation strategies are being investigated and implemented gradually.</p>
+<p>While the attack has degraded performance, the network remains intact and usable.
+  Java I2P routers appear to be handling the issues better than i2pd routers for now.
+  Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
+</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
+As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
+First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
+Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
+Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
+<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
+possibly triggered by Bitcoin's new I2P transient address feature,
+but made worse by our SSU2 bugs and other congestion control problems.
+We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
+We have improved our algorithms to reduce network load during times of congestion.
+We are also collaborating with i2pd to develop common congestion control strategies.</p>
+<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
+i2pd released their version 2.45.0 last week and the early results are encouraging.
+New protocols, and distributed networks, are difficult to develop.
+Congestion can arrive with little warning and with little clue of the cause.
+Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
 <p>Comme d’habitude, nous recommandons que vous mettiez à jour vers cette version. La meilleure façon de maintenir la sécurité et d’aider le réseau est d’exécuter la dernière version.</p>
-</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Recent Blog Posts" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>
+</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 sortie" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>Transport SSU2 activé</summary></details><p>La version 2.0.0 d'I2P active nos nouveaux transports UDP SSU2 pour tout les utilisateurs, après la finalisation de petites fonctionnalités, d'essais et de plusieurs correctifs de bug.</p>
+<p>Nous avons aussi des correctifs de partout y compris le programme d'installation, la base de données de réseau, ajouts au carnet d'adresse privé, le lanceur de navigateur Windows et IPv6 UPnP.</p>
+<p>Comme d’habitude, nous recommandons que vous mettiez à jour vers cette version. La meilleure façon de maintenir la sécurité et d’aider le réseau est d’exécuter la dernière version.</p>
+</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Billets de blogue récents" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>Quelques billets de blogue récents</summary></details><p>Voici des liens vers plusieurs billets de blogue récents sur notre site web :</p>
 <ul>
-<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Overview of our new SSU2 transport</a></li>
-<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">A warning about I2P coins and other scams</a></li>
-<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">An interview with Konrad from diva.exchange</a></li>
-<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">An interview with Dustin from StormyCloud</a></li>
-</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 sortie" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 avec SSU2 pour tester</summary></details><p>Nous avons passé les trois dernier mois à travailler sur notre nouveau protocole de transport UDP "SSU2"
+<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Aperçu de notre nouveau transport SSU2</a></li>
+<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">Un avertissement sur les jetons I2P et d'autres arnaques</a></li>
+<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">Une interview avec Konrad de diva.exchange</a></li>
+<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">Une interview avec Dustin de StormyCloud</a></li>
+</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 sortie" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 avec SSU2 à tester</summary></details><p>Nous avons passé les trois dernier mois à travailler sur notre nouveau protocole de transport UDP "SSU2"
 avec un petit nombre de testeurs bénévole.
-Cette sortie complète l'implémentation incluant le relai et le test de pair.
+Cette sortie complète l'implémentation du relai et le test de pair.
 Nous l'activerons par défaut pour les plateformes Android et ARM et aléatoirement sur un petit pourcentage d'autres réseaux.
 Cela nous permettra de faire beaucoup plus de tests dans les trois prochain mois, finaliser la fonction de migration de connexion et corriger les problèmes restants.
-Nous prévoyons de l'activer pour tout le monde dans la prochaine Version prévue pour novembre.
+Nous prévoyons de l'activer pour tout le monde dans la prochaine version prévue pour novembre.
 Une configuration manuelle n'est pas nécessaire.</p>
-<p>Naturellement, il y a aussi la collection habituelle de correctifs de bogue dans cette version.
-Nous avons aussi ajouté un détecteur d'impasse automatique qui a déjà trouvé une impasse rare qui est désormais corrigée.</p>
+<p>Naturellement, il y a aussi la suite habituelle de correctifs de bogue dans cette version.
+Nous avons aussi ajouté un détecteur d'impasse automatique qui a déjà trouvé une impasse rare qui est maintenant corrigée.</p>
 <p>Comme d’habitude, nous recommandons que vous mettiez à jour vers cette version. La meilleure façon de maintenir la sécurité et d’aider le réseau est d’exécuter la dernière version.</p>
 </article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="Nouveau mandataire sortant exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>Nouveau mandataire sortant</summary></details><p>Des "mandataires sortants" I2P (nœuds de sortie) peuvent être utilisés pour accéder à Internet à travers
 votre tunnel mandataire HTML.
@@ -32,8 +200,8 @@ en 2 endroits : <b>mandataires sortant</b> et <b>mandataire sortant SSL</b>.
 Après modification, <b>défilez vers le bas et cliquer Enregistrer</b>.
 Voir notre <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">billet de blogue pour une capture d'écran</a>.
 Pour les instructions Android et les capture d'écrans, voir <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">le blogue de notbob</a>.</p>
-<p>Les mises à jour de routeur ne se mettront pas à jour avec votre configuration, vous devez la modifier manuellement.
-Merci à StormyCloud pour leur soutien, et s'il-vous plaît, veuillez considérer à faire un <a href="http://stormycloud.i2p/donate.html">don</a>.</p>
+<p>Les mises à jour de routeur ne se mettront pas à jour votre configuration, vous devez la modifier manuellement.
+Merci à StormyCloud pour leur soutien, et s'il-vous plaît, veuillez penser à faire un <a href="http://stormycloud.i2p/donate.html">don</a>.</p>
 </article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 sortie" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 avec des correctifs de bogue</summary></details><p>Cette version inclut des correctifs de bogue dans i2psnark,
 le routeur, I2CP et UPnP.
 Les correctifs de routeur adresse les bogues des redémarrages rapides, IPv6, test de pair SSU,
@@ -42,18 +210,18 @@ Le traitement de la famille de routeur et la classification Sybil ont aussi ét
 significativement améliorés.</p>
 <p>Ensemble avec i2pd, nous sommes en train de développer notre nouveau transport UDP, SSU2.
 SSU2 amènera des améliorations substantielles à la performance et la sécurité.
-Il nous permettra aussi de remplacer enfin notre dernier usage du chiffrement extrêmement lent de ElGamal,
-complétant la mise à niveau de la cryptographie entière que nous avions commencé il y a maintenant 9 ans.
-Cette sortie contient aussi une implémentation préliminaire qui est désactivé par défaut.
+Il nous permettra aussi de remplacer enfin notre dernière utilisation du chiffrement extrêmement lent de ElGamal,
+finalisant la mise à niveau de la cryptographie que nous avions commencé il y a maintenant 9 ans.
+Cette version contient aussi une implémentation préliminaire qui est désactivé par défaut.
 Si vous souhaitez participer au test, veuillez voir nos informations actuelles
 sur zzz.i2p.</p>
 <p>Comme d’habitude, nous recommandons que vous mettiez à jour vers cette version. La meilleure façon de maintenir la sécurité et d’aider le réseau est d’exécuter la dernière version.</p>
-</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Installer la mise à jour indispensable Java/Jpackage" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>La vulnérabilité récente des "Signatures Psychiques" Java ont affecté I2P. Les utilisateurs actuels de
+</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Installer les mises à jour indispensable Java/Jpackage" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>La vulnérabilité récente des "Signatures Psychiques" Java ont affecté I2P. Les utilisateurs actuels de
 I2P sur Linux, ou n'importe quel utilisateur d'I2P qui utilise un MVJ non groupé devrait mettre à jour
-son MVJ ou basculer vers une version qui ne contient pas la vulnérabilité, en dessous de
+leur MVJ ou basculer vers une version qui ne contient pas la vulnérabilité, en dessous de
 Java 15.</p>
-<p>Les nouveaux paquets I2P facile d'installation ont été généré en utilisant la dernière version de la
-Machine Java Virtuelle. Plus de détails ont été publiés dans les fils de nouveautés des paquets
+<p>Les nouveaux paquets I2P facile d'installation ont été générés en utilisant la dernière version de la
+Machine Java Virtuelle. Plus d'informations ont été publiés dans les fils de nouveautés des paquets
 respectifs</p>
 </article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 sorti" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 avec améliorations de performance et de fiabilité</summary></details><p>La version 1.7.0 contient plusieurs améliorations de performance et de fiabilité.</p>
 <p>Il y a désormais des messages contextuels dans la zone de notification, pour les plateformes qui ne les prenait pas en charge.
@@ -66,30 +234,30 @@ Les utilisateurs des applications BOB restants devrait demander aux développeur
 Nous étions conscient du problème peu après la sortie mais cela nous a pris presque deux mois pour trouver la cause.
 Nous l'avons éventuellement identifié comme un bogue dans i2pd 2.40.0,
 et le correctif sera dans la version 2.41.0 qui sortira à peu près en même temps que cette sortie.
-Sur le chemin, nous avons fait plusieurs changement du côté de l'I2P Java pour améliorer la
-robustesse des recherches et marchés de la base de donnée de réseau et éviter les pairs peu performants dans la sélection tunnel de pair.
+Sur le chemin, nous avons fait plusieurs changement du côté du I2P Java pour améliorer la
+robustesse des marchés et des recherches de base de donnée réseau et éviter les pairs peu performants dans la sélection du tunnel de pair.
 Cela devrait aider le réseau à être plus robuste même en présence de routeurs boghei ou malicieux.
-De plus, nous commençons un programme joint pour tester une pré-sortie des routeurs i2pd et Java I2P
-ensemble dans un test réseau isolé pour que nous trouvions plus de problèmes avant les sorties et pas après.</p>
-<p>Dans d'autres nouvelles, nous continuons à beaucoup progresser sur le design de notre nouveau transport UDP "SSU2 (suggestion 159)
+De plus, nous commençons un programme joint pour tester une version préliminaire des routeurs i2pd et Java I2P
+dans un test réseau isolé pour que nous trouvions plus de problèmes avant les sorties et non après.</p>
+<p>Dans d'autres nouvelles, nous continuons à progresser sur le design de notre nouveau transport UDP "SSU2 (suggestion 159)
 et avons commencer l'implémentation.
 SSU2 amènera des améliorations substantielles à la performance et la sécurité.
-Cela nous permettra aussi de remplacer enfin notre dernier usage du chiffrement extrêmement lent ElGamal,
-complétant la mise à niveau de la cryptographie entière que nous avions commencé il y a maintenant 9 ans.
+Cela nous permettra aussi de remplacer enfin notre dernière utilisation du chiffrement extrêmement lent ElGamal,
+finalisant la mise à niveau de la cryptographie que nous avions commencé il y a maintenant 9 ans.
 Nous nous attendons a commencer les tests joints avec i2pd bientôt, et le sortir sur le réseau plus tard cette année.</p>
 <p>Comme d’habitude, nous recommandons que vous mettiez à jour vers cette version. La meilleure façon de maintenir la sécurité et d’aider le réseau est d’exécuter la dernière version.</p>
-</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 sortie" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 permet de nouveaux messages de construction de tunnel</summary></details><p>Cette version complète la sortie de deux protocoles majeurs développé en 2021.
-La transition au chiffrage X25519 pour les routeurs est accéléré et nous nous attendons à ce que presque tout les routeurs soit ressaisis d'ici la fin de l'année.
-Les messages de construction de tunnel courts sont activés pour un réduction importante de bande passante.</p>
+</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 sortie" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 permet de nouveaux messages de construction de tunnel</summary></details><p>Cette version finalise la sortie de deux protocoles majeurs développés en 2021.
+La transition au chiffrage X25519 pour les routeurs est accélérée et nous nous attendons à ce que presque tout les routeurs soit ressaisis d'ici la fin de l'année.
+Les messages de construction de tunnel courts sont activés pour une réduction de bande passante considérable.</p>
 <p>Nous avons ajouté une sélection de panneau de thème au nouveau sorcier d'installation.
 Nous avons amélioré la performance SSU et corrigé un problème avec les messages de test pair SSU.
 Le filtre de construction de tunnel Bloom a été ajusté pour réduire l'utilisation de la mémoire.
 Nous avons amélioré la prise en charge pour les greffons non Java.</p>
-<p>Par ailleurs, nous faisons de l'excellent progrès sur le design de notre nouveau transport UDP "SSU2" et l'implémentation devrait débuter tôt dans l'année prochaine.</p>
+<p>Par ailleurs, nous progressons très bien sur le design de notre nouveau transport UDP "SSU2" et son implémentation devrait débuter tôt dans l'année prochaine.</p>
 <p>Comme d’habitude, nous recommandons que vous mettiez à jour vers cette version. La meilleure façon de maintenir la sécurité et d’aider le réseau est d’exécuter la dernière version.</p>
-</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 sortie" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 avec des nouveaux messages de construction de tunnel</summary></details><p>C'est bien ça, après 9 ans de versions 0.9.x, nous allons directement de 0.9.50 à 1.5.0.
-Cela ne signifiera pas un changement majeur d'API ou une affirmation que le développement est terminé.
-C'est simplement une reconnaissance de presque 20 ans de travail pour fournir de l'anonymat et de la sécurité à nos utilisateurs.</p>
+</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 sortie" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 avec des nouveaux messages de construction de tunnel</summary></details><p>Et oui, après 9 ans de versions 0.9.x, nous allons directement de 0.9.50 à 1.5.0.
+Cela ne signifiera pas de changement majeur d'API ou une affirmation que le développement est terminé.
+C'est simplement la reconnaissance de presque 20 ans de travail pour fournir de l'anonymat et de la sécurité à nos utilisateurs.</p>
 <p>Cette version finalise enfin l'implémentation de plus petits messages de construction de tunnel pour réduire la bande passante.
 Nous continuons de transitionner les routeurs réseaux au chiffrement X25519.
 Bien sûr il y a aussi de nombreux correctifs de bogues et améliorations de performance.</p>

data/translations/entries.gan.html

@@ -0,0 +1,522 @@
+<div>
+<header title="I2P 新聞">新闻订阅和软件更新</header><article id="urn:uuid:f2a6aabd-ee29-4f45-a8dd-7378e907016a" title="2.9.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2025/06/02/2.9.0_released" author="idk" published="2025-06-02T19:00:00Z" updated="2025-06-02T19:00:00Z"><details><summary>I2P 2.9.0 版本</summary></details><p>I2P 2.9.0 是一个维护版本，包括错误修复和新功能开发。</p>
+<p>改进了线程使用以提高 i2ptunnel 系统的性能。改进了 NTCP2 以抵御探测攻击。通知系统已集成到更多应用程序中，以便从 I2PSnark 和其他应用程序向用户提供更好的反馈。修复了自动播种注册问题。用户在充当播种时可能会观察到更多的资源使用情况。如果不希望出现这种情况，可在 /config 页面上禁用播种模式。</p>
+<p>控制台中新增了全局地图功能，可在网络数据库视图中显示路由器位置。这些都是帮助路由器建立隧道和匿名提供服务的对等节点。</p>
+<p>关于隧道的自动带宽管理、数据报 2 协议和后量子密码学的实现工作仍在继续。在两个版本后，即 2.11.0，I2P 将需要 Java 17。</p>
+<p>如往常一样，我们建议您升级到这个版本。
+维护安全并帮助网络的最佳方式就是运行最新版本。</p>
+</article><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 发布" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 版本</summary></details><p>2.8.2 修复了在 2.8.1 版本中引入的导致 SHA256 失败的错误。
+该错误主要影响高带宽路由器。</p>
+<p>如往常一样，我们建议您升级到这个版本。
+维护安全并帮助网络的最佳方式就是运行最新版本。</p>
+</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 发布" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 版本</summary></details><p>2.8.1 修复了 2.8.0 中出现问题的本地站点访问问题。
+我们在控制台中为多个应用程序添加了通知气泡，以突出显示应用的消息。
+我们修复了可能影响隧道可靠性的隧道测试错误。
+地址簿现在有一个新的“最新”选项卡，显示从您的订阅中添加的最新主机名。
+对暗色主题进行了若干处修复和改进。</p>
+<p>我们修复了之前在 Java 21 或更高版本上失败的安装程序。
+我们还修复了在 Linux 上安装到包含空格的目录路径出现的问题。
+对于使用 Docker 的用户，我们更新了过时的 Docker 容器和容器库。</p>
+<p>如往常一样，我们建议您升级到这个版本。
+维护安全并帮助网络的最佳方式就是运行最新版本。</p>
+</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="2.8.0 访问本地站点失败" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 本地访问错误</summary></details><p>在 2.8.0 中，浏览本地站点（通过主机名或 b32）将失败。
+解决方法是使用 localhost 和服务器端口（通常为 7658）来绕过 I2P。
+例如，<a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>。
+我们对此问题深表歉意并努力修复中。</p>
+</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 发布</summary></details><p>此版本通过修复错误、删除未使用的代码以及提高网络稳定性以改进 I2P。</p>
+<p>我们改进了网络中拥堵的路由器的处理。
+UPnP 和 NAT 遍历中的问题已解决，以改善连接性和错误回报。
+我们现在有一个更激进的策略来从 NetDb 中删除赁集，以提高路由器性能并减轻过载。
+另外有一些降低事件可观察性的更改，如路由器重启或关闭等。</p>
+<p>如往常一样，我们建议您升级到这个版本。
+维护安全并帮助网络的最佳方式就是运行最新版本。</p>
+</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 发布</summary></details><p>本次发布，I2P 2.7.0 继续修复错误，提高性能以及添加功能。</p>
+<p>从控制台和应用程序的信息访问已得到改进。
+I2PSnark 和 SusiMail 搜索中的问题已得到修复。
+路由器控制台中嵌入的 netDB 搜索的使用方式现在更直观、更实用。
+高级模式下的诊断显示亦有少量改进。</p>
+<p>另外修复了一些错误以提高网络内的兼容性。
+一个赁集发布的问题已解决，提高了主要隐藏服务的可靠性。
+当用户仅更改现有种子上的跟踪器时，I2PSnark 不再更改信息哈希。
+这可以防止种子因这些更改而受到不必要的干扰。
+我们欢迎这份来自新贡献者的工作。
+在处理流媒体库选项时的冲突已被解决以提高与其他 I2P 实现的兼容性。</p>
+<p>如往常一样，我们建议您升级到这个版本。
+维护安全并帮助网络的最佳方式就是运行最新版本。</p>
+</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 已发布" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 版本</summary></details><p>I2P 2.6.1 的发布是为了修复隐藏服务管理器应用程序中的用户界面错误。
+此错误导致滚动被禁用，从而使某些配置无法访问。</p>
+<p>如往常一样，我们建议您升级到这个版本。
+维护安全并帮助网络的最佳方式就是运行最新版本。</p>
+</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 已发布" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 版本</summary></details><p>本次发布的I2P 2.6.0版本继续致力于修复漏洞、添加新功能并提升网络的可靠性。</p>
+<p>当选择洪泛路由时，较新的路由将受到青睐。
+I2PSnark 除了修复漏洞之外，还获得了一些功能，这些功能可以提高PeX（对等节点交换）的性能。
+遗留的旧传输协议正在被移除，因此简化了UDP传输代码。
+本地主机上的目标节点将可以直接被本地客户端访问，而不需要请求它们的赁集，这可以提高性能和可测试性。
+另外对对等节点的选择策略进行了一些额外的调整。</p>
+<p>I2P 不再允许通过 Tor 建立 I2P 连接，从 Tor 出口IP地址建立的连接现在已被阻止。
+我们不鼓励这样做，因为它会降低I2P的性能，并浪费Tor出口节点的资源而无任何益处。
+如果您既运行Tor出口路由又运行I2P，我们鼓励您继续这样做，为两者使用不同的IP地址。
+非出口节点和Tor客户端不受此影响，无需任何更改。</p>
+<p>如往常一样，我们建议您升级到这个版本。
+维护安全并帮助网络的最佳方式就是运行最新版本。</p>
+</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 发布" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 包含 HTTP 修复</summary></details><p>I2P 2.5.2 版本是为了修复在 2.5.0 中引入的导致某些 HTTP 内容被截断的错误。</p>
+<p>如往常一样，我们建议您升级到这个版本。
+维护安全并帮助网络的最佳方式就是运行最新版本。</p>
+</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 已发布" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P 版本 2.5.1 已发布以解决拒绝服务攻击</summary></details><p>I2P 2.5.1 的发布是为了解决影响 I2P 网络和服务的拒绝服务攻击。
+在此版本中，我们禁用了 Sybil 攻击检测工具的基于 IP 的部分，这些部分旨在放大攻击的影响和持续时间。
+这应该有助于网络恢复正常运行。
+那些已禁用 Sybil 攻击检测工具的人可以安全地重新启用它。
+其他子系统也进行了调整，以改进路由信息验证和对等节点选择。</p>
+<p>如往常一样，我们建议您升级到这个版本。
+维护安全并帮助网络的最佳方式就是运行最新版本。</p>
+</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="暴风雨天气" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>网络天气：暴风雨。 I2P 正在遭受攻击。</summary></details><p>I2P 网络目前正遭受拒绝服务攻击。
+此攻击以不同的方式影响 I2P 和 i2pd，并对网络健康状况造成严重影响。
+I2P 站点可达性严重下降。</p>
+<p>如果您在 I2P 内部托管服务，并且该服务托管在洪泛路由上，则应考虑在禁用 Floodfill 的路由器上对该服务采用多宿主形式，以提高可达性。
+其他缓解措施正在讨论中，但长期的、可向后兼容的解决方案仍需进一步研究。</p>
+</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="新版本 I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>更多应用改善，NetDB隔离策略审计</summary></details><p>该版本 I2P 2.5.0 比 2.4.0 版本提供了更多面向用户的改进，后者侧重于实施 NetDB 隔离策略。</p>
+<p>I2PSnark增加了一些新功能，比如搜索种子。
+若干错误已经修复，以提高与其他I2P种子客户端如 BiglyBT 和 qBittorrent 的兼容性。
+我们要感谢所有与libtorrent和qBittorrent合作的开发人员，他们支持并改进了I2P支持。
+SusiMail还增加了一些新功能，包括支持邮件中的Markdown格式和将附件拖放到邮件中的功能。
+使用隐藏服务管理器创建的隧道现在支持“Keepalive”，这提高了性能和与网络技术的兼容性，使更复杂的I2P站点成为可能。</p>
+<p>在此版本中，我们还对 NetDB 进行了一些调整，以增强其对垃圾信息的韧性，并提高路由器阻挡可疑消息的能力。
+这是“审计” 2.4.0 版本中“子数据库隔离”防御实现的一部分。
+此次调查发现了一个小的隔离穿透事件并修复之。
+这个问题是 I2P 团队在内部发现并修复的。</p>
+<p>在这个版本中，我们对发布Android和Windows下游发行版的过程进行了一些改进。
+这将改善这些下游产品的交付和可用性。</p>
+<p>如往常一样，我们建议您升级到这个版本。
+维护安全并帮助网络的最佳方式就是运行最新版本。</p>
+</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 发布包含 Congestion 和 NetDB 安全提升" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 发布包含 Congestion 和 NetDB 安全提升</summary></details><p>此版本 I2P 2.4.0 持续努力提高 I2P 网络的安全性和稳定性。
+其中包含对网络数据库的大幅改进，网络数据库是 I2P 网络中用于发现对等节点的基本结构。</p>
+<p>拥塞控制的改进将使路由器能够通过避开拥堵的对等节点从而提高网络稳定性。
+这将有助于网络限制隧道垃圾信息造成的影响。
+它还将有助于在 DDOS 攻击期间和之后修复网络。</p>
+<p>NetDb 的更改还有助于保护各个路由器以及使用它们的应用程序的安全。
+路由器现在可以通过将 NetDB 分成多个“子DB”来防御攻击者，我们使用这些“子DB”来防止应用程序和路由器之间的信息泄漏。
+这同时改进了 Java 路由器可用的有关其 NetDB 活动的信息，并简化了我们对多宿主应用程序的支持。</p>
+<p>还包括 I2PSnark 和 SusiMail 应用程序中的许多错误修复和功能增强。</p>
+<p>如往常一样，我们建议您升级到这个版本。
+维护安全并帮助网络的最佳方式就是运行最新版本。</p>
+</article><article id="urn:uuid:" title="I2P 2.3.0 新版本 - 安全修复，可调的黑名单，DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - 安全修复，可调的黑名单，DTG API</summary></details><p>此版本包含 CVE-2023-36325 的修复。
+CVE-2023-36325 是一个发生在布隆过滤器中的上下文混淆错误。
+攻击者制作包含唯一 messageID 的 I2NP 消息，并将该 messageID 发送给客户端。
+该消息在通过布隆过滤器后，不允许在第二条消息中重复使用。
+随后，攻击者将相同的消息直接发送给路由。
+路由器将消息传递给布隆过滤器并被丢弃。
+这泄露了之前已经看到的 messageID 信息，使攻击者有充分的理由相信路由器承载了客户端。
+这个问题已经通过将布隆过滤器的功能分离到不同的上下文中得到了解决，这些上下文中是基于消息是通过客户端隧道，还是探测隧道直接发送到路由的。
+在正常情况下，这种攻击需要数天才能成功执行，并且可能受到攻击期间路由重启和对误报的灵敏度等若干因素的干扰。
+建议使用 Java I2P 的用户立即更新以免受攻击。</p>
+<p>在修复这个上下文混淆错误的过程中，我们修改了一些策略来防御这类型的泄漏。
+这包括对 netDb 的调整、速率限制机制和洪泛路由的行为。</p>
+<p>此版本添加了 not_bob 作为第二个默认hosts来源，并把<a href="http://notbob.i2p">notbob.i2p</a>和<a href="http://ramble.i2p">ramble.i2p</a>添加到控制台主页。</p>
+<p>这个版本还包含一个可调整的黑名单。
+黑名单是半永久性的，每个被封禁的IP地址会被一直屏蔽，直到路由器重新启动。
+在 sybil 攻击期间观察到黑名单爆炸性增长的用户可以通过将黑名单配置为按一定时间段使条目过期来缩短超时间隔。
+此功能在默认情况下是关闭的，目前仅建议高级用户使用。</p>
+<p>该版本还包括一个API，用于使用桌面GUI(DTG)修改插件。
+现在可以将菜单项添加到系统托盘中，从而更直观地启动使用本地应用接口的插件。</p>
+<p>如往常一样，我们建议您升级到这个版本。
+维护安全并帮助网络的最佳方式就是运行最新版本。</p>
+</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="新版本 2.2.1，包含Docker，Ubuntu Lunar和Debian Sid的打包修复" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - 2.2.0 的维护修复</summary></details><p>I2P 2.2.0 版本向前推进以加快缓解 DDOS 攻击后，我们了解到一些开发问题，因此有必要构建和发布新包。
+此发布修复了 Ubuntu Lunar 和 Debian Sid 中的一个问题，即使用更新后的版本的 jakarta 包无法访问路由器控制台。
+Docker 包未正确读取参数，导致无法访问配置文件。
+此问题也已解决。
+docker 容器现在也与 Podman 兼容。</p>
+<p>本发布与 transifex 同步翻译并更新 GeoIP 数据库。</p>
+<p>如往常一样，我们建议您升级到这个版本。
+维护安全并帮助网络的最佳方式就是运行最新版本。</p>
+</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="新版本 2.2.0，包含DDOS攻击的缓解措施和 Streaming 子系统的调整" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>DDOS攻击的缓解措施和 Streaming 子系统的调整</summary></details><p>我们已选择将 2.2.0 的发布日期提前到今天，即 2023 年 3 月 13 日。
+此版本包括对网络数据库、洪泛和节点选择组件的修改，提高了路由器抵御 DDOS 攻击的能力。
+攻击可能会持续进行，但对这些系统的改进将通过帮助路由识别和降低路由评分来帮助减轻 DDOS 攻击的风险。</p>
+<p>此版本还为 Streaming 子系统添加了重放保护，以防止可以捕获加密数据包的攻击者通过将其发送给意外的接收者来重新使用它。
+这是一个向后兼容的更改，因此旧路由器仍然能够使用新路由器的流媒体功能。
+此问题由 I2P 开发团队在内部发现并修复，与 DDOS 攻击无关。
+我们从未在实际环境遇到过重放流数据包，并且不相信此时针对 I2P 网络发生过流重放攻击。</p>
+<p>您可能已经注意到，这些发行说明和发行版本身已由 idk 而非 zzz 签署。
+zzz 已选择退出该项目，他的职责由其他团队成员承担。
+因此，该项目正致力于更换网络统计基础设施并将开发论坛移至 i2pforum.i2p。
+我们感谢 zzz 长期以来提供这些服务。</p>
+<p>如往常一样，我们建议您升级到这个版本。
+维护安全并帮助网络的最佳方式就是运行最新版本。</p>
+</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS 消息进展" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS 消息进展</summary></details><p>我们已经确认攻击者控制了大量的路由器。
+我们的调查和缓解措施仍在继续当中。</p>
+<p>这是提醒人们即使在 20 年后，I2P 网络规模仍然相对较小的好时候。
+我们没有证据表明攻击者正试图对任何特定用户或隐藏服务进行去匿名化。
+但是，如果您有高风险威胁模型，您应该仔细考虑 I2P 目前是否提供了您需要的保护。
+从长远来看，最好的解决方案是宣传并发展 I2P 网络以提高我们用户的安全性。</p>
+<p>我们将在有必要时在新闻推送和<a href="http://zzz.i2p">zzz.i2p</a>提供更多信息。
+在我们努力改进 I2P 的过程中，请您耐心等待。</p>
+</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="关于最近的拒绝服务攻击" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P 保持完好，但性能受损</summary></details><p>I2P 网络目前正受到拒绝服务攻击的影响。
+网络的洪泛功能受到影响，导致响应中断，隧道构建成功率下降。
+网络参与者在连接到 I2P 站点和使用 I2P 服务时遇到困难。
+我们在正在逐步调查和实施缓解策略。</p>
+<p>虽然攻击降低了性能，但网络仍然完好无损且可用。
+目前，Java I2P 路由器似乎比 i2pd 路由器能更好地处理这些问题。
+下周，各种缓解措施应该会开始出现在 Java 和 C++ 路由器的开发版本中。</p>
+</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 包含大量 SSU2 修复</summary></details><p>自 11 月发布 2.0.0 以来，我们获知了一些情况。
+随着路由器更新到该版本，网络对我们新的 SSU2 传输协议的支持率从大约 1% 提高到 60% 以上。
+首先，我们已经确认 SSU2 是一个可靠、设计良好且安全的协议。
+其次，我们发现并修复了协议推行中的许多小错误或很少触发的错误。
+这些错误累积起来的影响降低了网络的性能。</p>
+<p>此外，我们还注意到网络中隧道数量的增加和隧道构建成功率的下降，
+可能是由比特币新的 I2P 临时地址功能触发的，
+但由于我们的 SSU2 错误和其他拥塞控制问题而变得更差。
+我们正在与比特币和其他非比特币项目合作，以减少 I2P 网络需求。
+我们改进了算法以减少拥塞期间的网络负载。
+我们还与 i2pd 合作开发通用的拥塞控制策略。</p>
+<p>因此，我们将此版本的发布时间加快了大约六周，以便向所有人发布修复程序。
+i2pd 上周发布了他们的 2.45.0 版，早期的结果令人鼓舞。
+新协议和分布式网络的开发很困难。
+拥塞可能会在没有任何警告和原因的情况下出现。
+感谢您的耐心等待，因为我们已经诊断并希望解决问题。</p>
+<p>一如往常一般，我們建議您更新到這個版本，要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
+</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 全面启用</summary></details><p>I2P 2.0.0版本在完成了小特性开发、测试和若干错误修复以后还为所有用户启用了我们新的SSU2协议。</p>
+<p>我们也修复了各种问题，包括安装包、网络数据库、私有地址簿添加，Windows浏览器启动程序，和IPv6 UPnP。</p>
+<p>一如往常一般，我們建議您更新到這個版本，要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
+</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="最近的博客文章" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>部分最近的博客文章</summary></details><p>这是我们网站部分最近的博客文章的链接：</p>
+<ul>
+<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">有关我们新的 SSU2 协议的概述</a></li>
+<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">有关I2P币及其他骗局的警告</a></li>
+<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">与divs.exchange的Konrad的访谈</a></li>
+<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">与StormyCloud的Dustin的访谈</a></li>
+</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 包含 SSU2 测试</summary></details><p>我们在过去的三个月里与少量志愿测试者一起研究我们新的UDP传输协议 "SSU2"
+这个版本完成了完整的实现，包括中继和对等节点测试。
+我们默认在安卓和ARM平台上启用它，并在一小部分其它路由上随机启用。
+这将使我们能够在未来三个月内做更多的测试，完成连接迁移功能，
+并修复任何剩余的问题。
+我们计划在11月发布的下一个发布版本中为所有人启用该功能，
+无需手动配置。</p>
+<p>当然，这个发布版本也包含了一些常见的错误修复。
+我们还增加了一个自动死锁检测器，它已经找出一个很少见的死锁。这个死锁已经被修复。</p>
+<p>一如往常一般，我們建議您更新到這個版本，要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
+</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="新出口代理 exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>新出口代理</summary></details><p>I2P出口代理（exit nodes）可以使你通过一个HTTP代理隧道访问互联网。
+在我们的 <a href="http://i2p-projekt.i2p/en/meetings/314">月度会议</a>上,
+<b>exit.stormycloud.i2p</b> 已经成为我们官方推荐的出口代理，替代早已死去的 <b>false.i2p</b>。
+欲了解 <a href="http://stormycloud.i2p/"> StormyCloud 组织</a>的更多信息，请访问
+<a href="http://stormycloud.i2p/outproxy.html">出口代理</a>、
+<a href="http://stormycloud.i2p/tos.html">服务条款</a>、
+<a href="http://stormycloud.i2p/">StormyCloud 网站</a>。 </p>
+<p>我们建议你修改 <a href="/i2ptunnel/edit?tunnel=0">匿名服务管理器配置</a>来确保 <b>exit.stormycloud.i2p</b>存在于两个地方： <b>出口代理</b> 和 <b>SSL出口代理</b>。
+修改之后，<b>向下滑、点击保存</b>。
+ <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">在我们的博客文章上查看截图</a>。
+你可以在 <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">notbob的博客</a>上查看Android版的说明和截图。</p>
+<p>路由器更新不会更新你的配置，你必须手动修改。
+非常感谢 StormyCloud 的支持。如果可能的话，请考虑<a href="http://stormycloud.i2p/donate.html">给他们捐赠</a>。</p>
+</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 包含错误修复</summary></details><p>本更新包含i2psnark，
+路由器，I2CP和UPnP的错误修复。
+修复了路由器软重启、IPv6、SSU 对等节点测试、网络数据库存储和隧道构建中的地址错误。
+路由家族处理和Sybil分级也明显改善了。</p>
+<p>和i2pd一起，我们开发了新的UDP传输，SSU2。
+SSU2将带来实质性的性能和安全性改进。
+它还将让我们最终替换我们最后使用的非常慢的 ElGamal 加密，
+完成我们从约9年前开始的加密的完全升级。
+本发布包含一个默认关闭的初步版本。
+如果你想参与测试，请关注zzz.i2p的当前消息。</p>
+<p>一如往常一般，我們建議您更新到這個版本，要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
+</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="安装必要的 Java/Jpackage 升级" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>最近Java的“Psychic Signatures”漏洞影响到I2P。当前Linux的I2P用户，或任何正在使用非捆绑JVM的I2P用户应当更新
+他们的JVM或切换到 Java 15 以下
+不包含该漏洞的版本。</p>
+<p>新的I2P一键安装包已使用
+JVM的最新发布生成。更多详情已发布在各
+同捆包的新闻源中。</p>
+</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 包含可靠性和性能提升</summary></details><p>1.7.0 更新包含若干性能和可靠性的改善。</p>
+<p>对于支持的平台，现在系统托盘中会弹出信息。
+i2psnark 现在有一个新的种子编辑器。
+还大大降低了 NTCP2 的CPU占用。</p>
+<p>在新安装中，长期不受支持的 BOB 接口已被移除。
+除了 Debian 包以外，现有的安装将继续使用之。
+其余任何 BOB 应用的用户都应该要求开发人员切换到 SAMv3 协议。</p>
+<p>我们得知自 1.6.1 发布以来，网络可靠性不断恶化。
+我们在发布以后很快就意识到了这个问题，然而我们花了近两个月才找到原因。
+我们最终确认为 i2pd 2.40.0 中的一个bug，
+这个修复将在 2.41.0 中和这个版本同时发布。
+在此过程中，我们在 Java I2P 中做了一些修改，以改善
+网络数据库查找和存储的健壮性，并在隧道节点选择中避开性能较差的对等节点。
+这将使网络在存在异常路由或恶意路由的情况下更健壮。
+此外，我们正在启动一个联合项目，在同一个隔离的测试网络中测试 i2pd 和 Java I2P 路由
+的预发布版本，这样我们就可以在发布前而不是发布以后发现更多问题。</p>
+<p>其他方面，我们在设计新的 UDP 传输“SSU2”（提案159）
+中继续取得重大进展并开始推行。
+SSU2 将带来实质上的性能和安全提升。
+这还将让我们能最终取代最后使用的，非常慢的 ElGamal 加密，
+完成约9年前开始的全加密升级。
+我们预计很快就会开始和 i2pd 进行联合测试，并在今年晚些时候向全网络推出。</p>
+<p>一如往常一般，我們建議您更新到這個版本，要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
+</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 启用新的隧道搭建信息</summary></details><p>该更新完成了2021年开发的两个主要协议更新的推出。
+为路由迁移至 X25519 加密的步伐加快了，我们预计绝大部分路由在今年年底能完成切换。
+短隧道构建信息已启用以减少带宽使用。</p>
+<p>我们为新安装向导增添了一个主题选择面板。
+我们改善了 SSU 表现，修复了一个 SSU 对等节点测试信息的问题。
+调整了隧道构建布隆过滤器以降低内存使用。
+我们改善了非Java插件的支持。</p>
+<p>另外，我们在设计新的 UDP 传输协议 SSU2 方面取得了重大进展，预计明年年初开始推行。</p>
+<p>一如往常一般，我們建議您更新到這個版本，要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
+</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 包含新的隧道搭建信息</summary></details><p>是的没错，在 0.9.x 发布9年后，我们直接从 0.9.50 跳到 1.5.0。
+这并不意味着有重大的API更改，也不意味着开发已经完成。
+这仅仅是对近20年来为我们的用户提供匿名和安全的工作的认可。</p>
+<p>此更新完成了更小的隧道构建消息的实现从而减少带宽使用。
+我们继续迁移网络的路由至 X25519 加密。
+当然也有许多错误修复和性能提升。</p>
+<p>一如往常一般，我們建議您更新到這個版本，要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
+</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="Muwire 桌面版漏洞" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Muwire 桌面版漏洞</summary></details><p>Muwire 桌面版应用的独立安装包中发现一个安全漏洞。
+其不影响控制台插件，并和以往发现的插件问题无关。
+如果你正在运行 Muwire桌面版应用，你应当立即<a href="http://muwire.i2p/">升级到 0.8.8</a>。</p>
+<p>问题详情将在2021年7月15日于<a href="http://muwire.i2p/security.html">muwire.i2p</a>公布。</p>
+</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="Muwire 插件漏洞" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Muwire 插件漏洞</summary></details><p>Muwire 插件中发现一个安全漏洞。
+其不影响桌面客户端的独立安装包。
+如果你正在运行 Muwire 插件，你应当立即<a href="/configplugins">升级到 0.8.7-b1</a>。</p>
+<p>更多有关漏洞和及时的安全建议的信息见于<a href="http://muwire.i2p/security.html">muwire.i2p</a>。</p>
+</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 发布" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 包含 IPv6 修复</summary></details><p>0.9.50 继续为路由加密密钥迁移至 ECIES-X25519。
+我们已为补种启用 DNS over HTTPS 以保护用户免受被动 DNS 窥探。
+还有若干对 IPv6 地址的修复和提升，包括新的 UPnP 支持。</p>
+<p>我们终于修复了一些 SusiMail 长期存在的错误。
+对带宽限制器的修改应该能改善网络隧道表现。
+在我们的 Docker 容器有几处改善。
+我们已经提升了对网络中可能的恶意和异常路由的防御。</p>
+<p>一如往常一般，我們建議您更新到這個版本，要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
+</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 发布" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0.9.49 包含SSU修复及更快速的加密</summary></details><p>0.9.49 继续使 I2P 更快更安全。
+我们对 SSU (UDP) 传输做了若干改进和修复，速度应有所提高。
+同时此更新开始为路由迁移至新的，更快的 ECIES-X25519 加密。
+（至今目标地址采用此加密已有数个更新）
+这几年，我们一直致力于新加密的规范和协议，
+现已经接近尾声了！迁移会在数个更新中完成。</p>
+<p>对于此更新，为尽量减少中断，只有新安装的以及极小比例的现有安装
+（重启时随机选择）会采用新加密。
+如果你的路由确实“重新键入”以使用新加密，在你重启后的几天内，它可能会比平时流量更少或可靠性更低。
+这是正常现象，因为你的路由生成了一个新的身份。
+你的路由性能随后会恢复正常。</p>
+<p>以往我们在改变默认签名类型时已两次“重新键入”网络，
+但这是首次更改默认加密方式。
+希望一切都能顺利进行，我们正逐步确定。</p>
+<p>一如往常一般，我們建議您更新到這個版本，要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
+</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 发布" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 包含性能提升</summary></details><p>0.9.48 在大多数服务上启用了我们的新端到端加密协议（提案144）。
+我们已经添加对新隧道建立的信息加密（提案152）的初步支持。
+整个路由的性能都有显著提高。</p>
+<p>Ubuntu Xenial (16.04 长期支持版) 的软件包已不再支持。
+使用该平台的用户应当升级以继续获得 I2P 更新。</p>
+<p>一如往常一般，我們建議您更新到這個版本，要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
+</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 发布" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 启用了新的加密</summary></details><p>0.9.47 在一些服务中默认启用了我们的新端到端加密协议（提案 144）。
+Sybil 分析和屏蔽工具现在已默认启用。</p>
+<p>现在需要 Java 8 或更高版本。
+Debian 软件包 Wheezy 和 Stretch，以及 Ubuntu 软件包 Trusty 和 Precise 现已不再支持。
+使用上述平台的用户需要升级以继续获得 I2P 更新。</p>
+<p>一如往常一般，我們建議您更新到這個版本，要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
+</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="0.9.46 发布" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 包含错误修复</summary></details><p>0.9.46 包含 streaming 库显著的性能提升。
+我们已经完成了 ECIES 加密（提案144）的开发，现在可以选择启用它以进行测试。</p>
+<p>仅 Windows 用户：
+本发布修复了一个可被本地用户利用的本地提权漏洞。
+请尽快应用更新。
+感谢 Blaze Infosec 披露此问题。</p>
+<p>这是最后一个支持 Java 7、Debian 软件包 Wheezy 和 Stretch 以及 Ubuntu 软件包 Precise 和 Trusty 的发布。
+使用上述平台的用户务必升级以获得未来的 I2P 更新。</p>
+<p>一如往常一般，我們建議您更新到這個版本，要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
+</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 发布" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 包含了错误修复</summary></details><p>0.9.45包含了隐身模式和带宽测试的重要修复。
+这是一个对于控制台暗色主题的更新。
+我们继续努力提高性能并开发新的端到端加密(提案 144)。</p>
+<p>一如往常一般，我們建議您更新到這個版本，要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
+</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="0.9.44 发布" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 包含了错误修复</summary></details><p>0.9.44 包含一个隐藏服务处理新加密类型中拒绝服务问题的重要修复。所有用户都应尽快更新。</p>
+<p>发布版本包含新端到端加密的初始支持（提案 144）。此项目上的工作仍在继续，尚未准备好使用。有一些控制台主页的更改，及 i2psnark 中新的嵌入式 HTML5 媒体播放器。包含对受到防火墙限制的 IPv6 网络的额外修复。隧道建立的修复应当使得一些用户更快的启动。</p>
+<p>一如往常一般，我們建議您更新到這個版本，要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
+</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="0.9.43 已发布" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 包含了错误修复</summary></details><p>在 0.9.43 更新版本中，我们继续致力于更强的安全性，隐私功能和性能提升。我们的新的租契集规范 (LS2) 实现现在已完成。我们正在开始用于未来发布版本的更强大快速的端到端加密（提案 144）实现。一些 IPv6 探测问题已修复，当然还有一些其他错误修复。</p>
+<p>一如往常一般，我們建議您更新到這個版本，要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
+</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="0.9.42 已发布" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 包含了错误修复</summary></details><p>0.9.42 继续使 I2P 更快更稳定.
+此版本包含了几处改动以提高 UDP 传输速度。
+我们拆分了设置文件，以便将来进一步模块化。
+我们将继续努力，将关于更快、更安全的加密的建议付诸实践。
+理所当然地， 还有许多错误修复。</p>
+<p>一如往常一般，我們建議您更新到這個版本，要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
+</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="0.9.41 已发布" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.41 包含了错误修复</summary></details><p>0.9.41 继续着手落实提案 123 引入的新功能，
+包括对加密的租契集做客户端级别的身份验证。
+控制台的 I2P 标志及若干图标已更新。
+更新了 Linux 安装程序。</p>
+<p>启动速度在树莓派（Raspberry Pi）等平台上更快了。
+已修正若干缺陷，包括部分严重影响底层网络消息的问题。</p>
+<p>一如往常一般，我們建議您更新到這個版本，要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
+</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="0.9.40 已发布" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 有新的图标</summary></details><p>0.9.40 支持新的租契集格式。
+我们已禁用旧的 NTCP 1 传输协议。
+有一个新的 SusiDNS 导入功能，以及一个用于传入连接的新的脚本化过滤机制。</p>
+<p>我们对 OSX 原生的安装程序做了很多改进，以及更新了 IzPack 安装程序。
+继续使用新的图标焕新控制台。
+如往常一样，我们还修复了许多缺陷！</p>
+<p>一如往常一般，我們建議您更新到這個版本，要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
+</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 已发布" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 带有性能提升</summary></details><p>0.9.39 包含了针对新网络库格式的大量更新(proposal 123).
+我们将 i2pcontrol 插件作为一个 webapp 打包进来从而支持 RPC 应用的开发.
+另外还有众多的性能提升和bug修复.</p>
+<p>我们移除了午夜和经典主题以减轻维护压力.
+之前使用这些主题的用户现在将会看到暗或者亮色调主题.
+另外主页有了新的的图标，这是控制台更新的第一步.</p>
+<p>一如往常一般，我們建議您更新到這個版本，要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
+</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38 已发布" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 含有全新安装向导</summary></details><p>0.9.38 含有一个若为首次安装则会启动的向导，还有一个带宽测试器。我们已经支持最新的GeoIP数据库格式。我们的网站上有一个新的配置Firefox的安装包和一个新的本地Mac OSX安装包。我们继续努力支持新的“LS2”网络数据库格式。</p>
+<p>这次更新还有大量的bug修复，包括修复了susimail附件的一些问题，还含有针对纯IPv6路由器的一个修复。</p>
+<p>一如往常一般，我們建議您更新到這個版本，要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
+</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="35C3 旅行报告" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>35C3 会议上的I2P</summary></details><p>I2P 团队大多数人出席了莱比锡的 35C3 会议。每天都开会，回顾上一年，阐述了我们2019年的发展和设计目标。</p>
+<p>项目愿景和新的路线图见<a href="http://i2p-projekt.i2p/en/get-involved/roadmap">此文</a>。</p>
+<p>我们为网页和控制台在LS2，Testnet和可用性提升上继续努力。
+一个计划已在Tails，Debian和Ubuntu Disco中就位。我们在安卓和I2P_Bote的修复上仍需要人手。</p>
+</article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="0.9.37 已发布" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37，NTCP2 已启用</summary></details><p>0.9.37版启用了更快更安全的传输协议NTCP2。</p>
+<p>一如往常一般，我們建議您更新到這個版本，要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
+</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="0.9.36 已发布" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36，NTCP2 及缺陷修复</summary></details><p>0.9.36包含一个新的，更安全的传输协议，叫作NTCP2。
+此协议默认禁用，但是您可以启用它。在<a href="/configadvanced">高级设置</a>中设置 <tt>i2np.ntcp2.enable=true</tt>，然后重新启动。
+在下个发布中，NTCP2将被启用。</p>
+<p>此发布也包含性能优化和缺陷修复</p>
+<p>一如往常一般，我們建議您更新到這個版本，要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
+</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 发布" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35，SusiMail 文件夹及 SSL 向导</summary></details><p>0.9.35 在Susimail中加入了文件夹的支持，以及在您的隐藏服务页面用于建立HTTPS的新SSL向导。
+我们如同往常一样收集错误修复，尤其是在Susimail中</p>
+<p>我们正在为0.9.36中的几部分而努力，包括新的OSX安装包以及更快、更安全的被称为NTCP2的传输协议。</p>
+<p>7月20-22号 I2P 将在纽约市HOPE。欢迎拜访并打招呼！</p>
+<p>一如往常一般，我們建議您更新到這個版本，要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
+</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 发布" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 包含错误修复</summary></details><p>0.9.34包含大量错误修复！
+同时还有Susimail、IPV6处理和隧道对等节点选择。
+我们在UPnP中加入了IGD2模式的支持。
+您还可以在将来的发布中看到更多的改进。</p>
+<p>一如往常一般，我們建議您更新到這個版本，要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
+</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="0.9.33 发布" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 包含错误修复</summary></details><p>0.9.33包含大量的错误修复，包括i2psnark，i2ptunnel，streaming和SusiMail。
+对于那些不能直接访问补种页面的用户，我们现在提供几种形式的代理用于补种。
+我们现在在隐藏服务管理器中默认设置了比率限制。
+对于高流量服务器，如有必要请浏览并调整限制。</p>
+<p>一如往常一般，我們建議您更新到這個版本，要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
+</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="Kaiser，Meltdown和Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>安全问题几乎在每种系统中均有所发现</summary></details><p>在全球范围内几乎所有已售出的电脑里的现代CPU中发现了很严重的问题，包括移动设备。这些安全漏洞名为“Kaiser”，“Meltdown”，“Spectre”。</p>
+<p>KAISER/KPTI 的白皮书可在<a href="https://gruss.cc/files/kaiser.pdf" target="_blank">KAISER.pdf</a>中找到，Meltdown在<a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a>，以及SPECTRE在<a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a>。英特尔第一响应列于<a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">Intels response</a>之下。</p>
+<p>当有可用更新时，更新系统对于我们的I2P使用者来说很重要。Windows 10系统补丁已从现在起可用，随后不久则是Windows 7和8。MacOS的补丁同样也已可用。大多Linux系统也同样具有包含修复的内核。这同样适用于安卓系统，在2018年1月2日的安全补丁中就包含此问题的补丁。请在可行时尽快更新您的系统。</p>
+</article><article id="urn:uuid:a6fc490b-2877-4cbf-afa8-d6e7d4637440" title="新年快乐！- 来自34C3" href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>新年与 I2P 在34C3</summary></details><p>I2P团队祝各位新年快乐！</p>
+<p>从2017年12月27日至30日，在莱比锡举行的34C3会议上，不少于7位 I2P 团队成员参加了会议。除了在桌上的<a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" target="_blank">会议</a>以外，我们还会见了从四面八方来的I2P的朋友。
+会议的结果已发布在<a href="http://zzz.i2p" target="_blank">zzz.i2p</a>。</p>
+<p>此外我们分发了很多贴纸，并将有关我们项目的信息提供给任何询问的人。
+我们的年度I2P晚餐取得了圆满成功，感谢所有与会人士对I2P的持续支持。</p>
+</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="0.9.32 发布" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 包含控制台升级</summary></details><p>0.9.32包含若干路由控制台和有关web应用（地址簿，i2psnark和Susimail）的修复。
+我们亦同时修改了处理用于发布路由信息的配置主机名的方式，以消除一些通过DNS的网络穷举攻击。
+我们已经在控制台中加入了一些检查以抵御重绑定攻击。</p>
+<p>一如往常一般，我們建議您更新到這個版本，要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
+</article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="0.9.31 版本發佈" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>0.9.31 含控制面板更新</summary></details><p>您可以很輕易的發現這個版本的變化！
+我們改進了路由器控制面板，使的它更容易上手，
+使用時變得更加容易連接和加強了對不同瀏覽器的支持，
+網頁也顯得更加整潔。
+這是我們長期計劃中的第一步，設計一個對使用者更加友好的路由器控制面板。
+我們還為 i2psnark 添加了 torrent 評級和評論。</p>
+<p>一如往常一般，我們建議您更新到這個版本，要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
+</article><article id="urn:uuid:2ce9a846-4d7e-11e7-b788-00163e5e6c1b" title="召集翻譯員" href="https://www.transifex.com/otf/I2P/announcements/7243/" author="str4d" published="2017-06-10T12:00:00Z" updated="2017-06-10T12:00:00Z"><details><summary>即將發佈的 0.9.31 版本有比一般版本需要更多翻譯的部分</summary></details><p>在即將發佈的 0.9.31 版本裡的使用者介面，將會迎來重大的更新，
+請注意我們將會有比平常更多的文字需要被翻譯。
+如果您是翻譯人員，我們期望您在這次版本發佈前
+留給我們更多的時間，加速翻譯的進度。
+我們也特意提早了三個禮拜，公佈需要翻譯的資料。</p>
+<p>如果您還不是 I2P 的翻譯員，現在是一個加入的好時機！
+請參考
+<a href="http://i2p-projekt.i2p/en/get-involved/guides/new-translators" target="_blank">新翻譯者指南</a>
+了解如何參與這個偉大的項目。</p>
+</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="0.9.30 已发布" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>0.9.30 更新到 Jetty 9 </summary></details><p>從 0.9.30 版本開始，支持了新的 Jetty 9 和 Tomcat 8 。
+之前的版本將不再獲得支持，並且在即將發布的 Debian Stretch 和 Ubuntu Zesty 中不能使用。
+路由器會調整 jetty.xml 這個配置檔案，將每個 Jetty 網站遷移到新的 Jetty 9 設置。
+這些動作應該可以適用於不是很老的和沒有手動修改過的配置，但如果是很老舊的版本和手動修改過配置，可能就不適用這個升級方式。
+請確認你的 Jetty 網站在升級後正常運作，如果有任何問題需要幫助，請利用 IRC 與我們聯繫（只提供英文幫助）。</p>
+<p>請注意有幾個插件與 Jetty 9 不兼容，必須要更新。
+以下的幾個插件已更新，適用於 0.9.30 版本，並且請先重啟路由器後再安裝他們：
+i2pbote 0.4.6; zzzot 0.15.0。
+以下幾個插件（列出當前版本）還不適用於 0.9.30 版本。
+你可以聯繫這幾個插件的開發人員，了解新版本開發的進度：
+BwSchedule 0.0.36; i2pcontrol 0.11。</p>
+<p>這一個版本還支持將之前的 DSA-SHA1 後台服務（2014及更早的版本）升級到更安全的 EdDSA 簽名類型。
+如果您需要更詳細的信息，請參閱<a href="http://zzz.i2p/topics/2271">zzz.i2p</a>，其中包括使用指南和常見問題解答。</p>
+<p>請注意：在非 Android ARM 平台上（例如Raspberry Pi），Blockfile 資料庫將會在重新啟動時升級，這可能需要幾分鐘的時間。
+請耐心等待！</p>
+<p>一如往常一般，我們建議您更新到這個版本，要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
+</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="0.9.29 已发布" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29包含缺陷修复</summary></details><p>版本 0.9.29 修正了的許多故障申報裡面的問題，包括壓縮信息損壞的解決方法。
+新版本支持 IPv6 上的 NTP。
+我們添加了對 Docker 先期版本的支持。
+我們轉換好了新的線上幫助文件。
+我們現在允許HTTP表頭使用同源參照位址通過 HTTP代理。
+我們修正了許多在Java 9下的問題，雖然我們並不推薦在一般情況下使用Java 9。</p>
+<p>一如往常的，我們建議您更新到這個版本。要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
+</article><article id="urn:uuid:cb742cac-df38-11e6-aed3-00163e5e6c1b" title="I2P-Bote安全漏洞" href="http://bote.i2p/news/0.4.5/" author="str4d" published="2017-01-20T12:00:00Z" updated="2017-01-20T12:00:00Z"><details><summary>I2P-Bote安全漏洞</summary></details><p>I2P-Bote 版本 0.4.5 修復了所有早期存在插件中的安全漏洞
+這對 Android 版本的程式沒有影響。</p>
+<p>當用戶打開電子郵件時，大部分的內容經過編碼調整。 但是，
+附件的檔案名稱沒有經過編碼處理，當瀏覽器的 JavaScript 功能是開啟的時候，
+容易被利用來執行惡意代碼。 現在，這個部分已經被加進編碼處理的範圍內，
+並且我們還對全部的頁面，額外增加了內容管理安全政策。</p>
+<p>所有 I2P-Bote 的使用者，當  I2P 0.9.29 版本在2月中旬發佈後，
+I2P-Bote 會在路由器重啟時自動更新。 但是，在這新舊版本交接的時候，
+為了保險起見，我們建議您
+<a href="http://bote.i2p/install/">按照安裝頁面上的操作指示</a>
+手動進行升級。</p>
+</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="0.9.28 版本發佈" href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>0.9.28 版本含錯誤修正</summary></details><p>版本 0.9.28 修復了 25個以上的故障報修，和升級了許多隨附軟體（包括Jetty）。
+增進了 IPv6 最新版本中出現的 peer test 的功能。
+我們對其它可能帶有惡意的主機來的連線，不斷改進偵測和阻止它的能力。
+我們針對Java 9做了一點初級的修復，雖然我們並不推薦在一般情況下使用 Java 9。</p>
+<p>I2P 的護法們將會出現在 33C3，請不要只是在外旁觀，請您提供如何將 I2P 做的更好的意見和想法。
+在這次會議裡面，我們將會討論 2017 的項目路線圖和排定優先順序。</p>
+<p>一如往常的，我們建議您更新到這個版本。要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
+</article><article id="urn:uuid:00015ff6-b556-11e6-adb4-00163e5e6c1a" title="I2P-Bote安全漏洞" href="http://bote.i2p/news/0.4.4/" author="str4d" published="2016-11-28T12:00:00Z" updated="2016-11-28T12:00:00Z"><details><summary>I2P-Bote安全漏洞</summary></details><p>I2P-Bote 版本 0.4.4 修復了所有早期存在插件中的安全漏洞
+這對 Android 版本的程式沒有影響。</p>
+<p>缺乏對 CSRF 攻擊的防護，意味當使用者使用  I2P-Bote 的時候，沒有把瀏覽器 JavaScript 功能
+關閉，同時在不知情的情況下打開了一個惡意網站。你有可能不自覺的觸發 CSRF 攻擊，
+而使你的 I2P-Bote 在你不知情下送出信息。可能發生的一種情形是駭客有可能利用這個漏洞
+提取到 I2P-Bote 的私鑰地址，而我們現在沒有辦法證明這個安全漏洞是存在的。    </p>
+<p>當 0.9.28 版本在12月中旬發佈之後，所有的 I2P-Bote 使用者將會在重啟路由器後，
+得到自動更新。 但是，如果您是 I2P 或 I2P-Bote 的固定使用者，遇到新舊版本交接，
+比較保險的做法是
+<a href="http://bote.i2p/install/">按照安裝頁面上的操作指示</a>手動進行升級。
+如果您是 I2P-Bote 的固定使用者，而且您習慣打開瀏覽器的 JavaScript 功能，
+您可以考慮在新版本發佈後，產生新的 I2P-Bote 地址，放棄舊的地址，降低您被攻擊的風險。</p>
+</article><article id="urn:uuid:c1d01ac3-81e7-4acd-bacd-d9178089e8c3" title="0.9.27 版本發佈" href="http://i2p-projekt.i2p/en/blog/post/2016/10/17/0.9.27-Release" author="zzz" published="2016-10-17T12:00:00Z" updated="2016-10-17T12:00:00Z"><details><summary>0.9.27 版本含錯誤修復</summary></details><p>版本 0.9.27 修復了一些問題。
+之前 0.9.26版本，更新了加速密碼加密解密速度的 GMP 庫，但那只適用於新安裝和 Debian/Ubuntu 版本的軟體，現在 0.9.27 版本可以直接透過網路，更新原生的密碼加密庫。
+我們也改進了 IPv6 的傳輸能力、SSU peer test 測試和隱藏模式。</p>
+<p>在<a href="http://i2p-projekt.i2p/en/blog/post/2016/06/01/I2P-Summer-Dev">I2P 夏季</a>期間，我們更新了許多插件，您的路由器將在重新啟動後自動更新它們。</p>
+<p>一如往常的，我們建議您更新到這個版本。要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
+</article><article id="urn:uuid:7e818120-88f8-401a-88fe-8db4ba20ad4d" title="I2P 在 Stack Exchange 上的計劃書" href="https://area51.stackexchange.com/proposals/99297/i2p" author="zzz" published="2016-06-07T13:00:00Z" updated="2016-06-07T13:00:00Z"><details><summary>I2P 將項目計劃書放在 Stack Exchange 上了！</summary></details><p>I2P 將項目計劃書放在 Stack Exchange 上了！
+請您<a href="https://area51.stackexchange.com/proposals/99297/i2p">踴躍參與</a>，我們將啟動項目的 Beta 階段。</p>
+</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="0.9.26 版本發佈" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>0.9.26版本包含了密碼部分的更新，改進了 Debian 的安裝包，和修復了錯誤 </summary></details><p>版本 0.9.26 做了一個重大升級，把軟體原生的密碼加密庫更新了，
+一個新的帶簽章的地址簿訂閱協議，
+並對 Debian / Ubuntu 安裝包進行了重大改進。</p>
+<p>加密学方面，我们升级到 GMP 6.0.0，并添加较新处理器的支持，这可以大幅加速密码运算。
+另外，我们现在使用常数时间的 GMP 函数以防止侧信道攻击。
+出于谨慎，GMP 更改只对新的安装和 Debian/Ubuntu 构建启用；我们会在 0.9.27 发布时更新它们。</p>
+<p>對於 Debian / Ubuntu 版本，我們在軟件包裡添加了幾個隨附軟體，
+包括 Jetty 8 和 geoip，並刪除了對應的隨附軟體源代碼。</p>
+<p>我們整合修復了一些問題，包括定時器的問題
+這會造成隨著時間推移，軟體的不穩定和性能下降。
+再次提醒您，我們建議所有使用者更新到最新版本。
+這將會是幫助網絡良好的成長並保持安全的最佳方式。</p>
+</article><article id="urn:uuid:c6f7228d-3330-4422-a651-ef9d8ca3484b" title="0.9.25 釋出" href="http://i2p-projekt.i2p/en/blog/post/2016/03/22/0.9.25-Release" author="zzz" published="2016-03-22T12:00:00Z" updated="2016-03-22T12:00:00Z"><details><summary>0.9.25 包含 SAM 3.3、QR 码及缺陷修复</summary></details><p>0.9.25 包含 SAM 的一个主要新版本 v3.3，以支持复杂的多协议应用程序。
+增加了 QR 码用于与其他人分享隐身服务。
+增加了“身份”图像用于视觉上区分地址。</p>
+<p>我们在控制台中添加了新的“路由器家族”配置页面，
+这可以让您更容易的声明您的一组路由器是由同一个人运行。
+这会添加一些变更以增加网络容量，并能提升隧道构建成功率。</p>
+<p>一如往常的，我們建議您更新到這個版本。要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
+</article><article id="urn:uuid:8390114d-8e50-45fd-8b4d-3e613bdd034e" title="0.9.24 釋出" href="http://i2p-projekt.i2p/en/blog/post/2016/01/27/0.9.24-Release" author="zzz" published="2016-01-27T18:00:00Z" updated="2016-01-27T18:00:00Z"><details><summary>0.9.24包含了一些漏洞修補和加速器</summary></details><p>0.9.24 包含新版本的 SAM (v3.2) 和众多问题修复和效率改进。
+注意，这是首个必需使用 Java 7 的发布版本。
+请尽快升级到 Java 7 或 8。
+如果您在使用 Java 6，您的路由将不会自动更新。</p>
+<p>為了避免古早的共享資料庫造成麻煩，我們要把它移除。
+如果某些古早I2P-Bote外掛(0.2.10以下，飢餓流浪漢所簽屬)，允許互動郵件存取協定，那移除後它們會崩潰。
+比較建議的修復是，用當今str4d簽署的I2P-Bote外掛來取代古早的。
+更多細節請參考 <a href="http://bote.i2p/news/0.4.3">這篇</a>。</p>
+<p>我們舉辦了完美的<a href="http://i2p-projekt.i2p/en/blog/post/2016/01/23/32C3">32C3-30號混沌通訊大會</a>，而且對於我們2016的計畫有順利進展。
+Echelon的演講包括了I2P的歷史和現狀，他的投影片在 <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/ccc/2015/I2P_Still_alive.pdf">這裡</a>(PDF)。
+Str4d出席了<a href="http://www.realworldcrypto.com/rwc2016/program">現實世界加密</a>也演說了我們的加密遷移，他的投影片在<a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/rwc/2016/rwc2016-str4d-slides.pdf">這裡</a> (PDF)。</p>
+<p>一如往常的，我們建議您更新到這個版本。要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
+</article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="0.9.23 釋出" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>0.9.23 版本修正個數個程式錯誤，並且對於 I2PSnark 做了些許的改良</summary></details><p>嗨，I2P！這是在由 zzz 簽署發行的49個版本之後，由我(str4d)簽署的第一份發行版。這是個是對於所有人員與事物的重要冗餘測試。</p>
+<p><b>做點家事</b></p>
+<p>我的簽名金鑰已經在路由更新上超過兩年了(自 0.9.9)，所以如果您正在使用這版本的I2P，那麼這個更新應該就像之前的一樣簡單。不過若您使用的是早於0.9.9的版本，您必須手動更新至目前版本。目前版本的更新資料夾可以在<a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/releases/">這裡</a>下載，而手動更新的介紹則在<a href="http://i2p-projekt.i2p/en/download#update">此處</a>。
+一旦您完成手動更新，您的路由器便會像往常一樣，找到0.9.23更新並下載。</p>
+<p>若您的 I2P 是經用套件管理系統安裝的話，那您並不會被這次變更所影響，可以如往常一般繼續更新。</p>
+<p><b>更新資訊</b></p>
+<p>迁移 RouterInfos 到新的、更强的 Ed25519 签名很顺利，预计已有至少一半的网络转换密钥。此次更新加速了密钥更新的过程。为了减少网络客户端的流失，您的路由器将在每次重启时有较小的概率转换到 Ed25519。在它转换密钥后，可预期的两天内将有更低的带宽，因为它需要将新的身份重新集成到网络。</p>
+<p>請注意，這是支援 Java 6 的最後一個版本，煩請盡速將您的 Java 更新到 7 或 8 版本。目前我們已經在處理 I2P 與 Java 9 的相容性問題，部分的成果會隨著此次的改版釋出。</p>
+<p>我們也有針對 I2PSnark 做了一些改善，也在路由控制台新增了一個可以查看舊聞的頁面。</p>
+<p>一如往常一般，我們建議您更新到這個版本，要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
+</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="0.9.22 釋出" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>帶著漏洞修復的0.9.22 開始轉移至 Ed25519</summary></details><p>0.9.22包含了修復i2psnark未完成便卡住的問題，和開始將路由資訊轉移至新的、更強的Ed25519簽署。
+為了減少網路擾動，您的路由器每次重啟只有一些機率會轉換至Ed25519。
+一旦密鑰更新了，您可以期待在幾天內看到更少的頻寬使用，因為它用了新身分重新融合到了網路中。
+如果一切順利，我們會在下個釋出版本加速更新密鑰的速率。</p>
+<p>在多倫多舉辦的 I2PCon 研討會完美結束了！
+所有的簡報以及影片皆以陳列於 <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">I2PCon 頁面</a>。</p>
+<p>一如往常一般，我們建議您更新到這個版本，要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
+</article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="0.9.21釋出" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>0.9.21釋出版本帶著增進的效能與漏洞的修復。</summary></details><p>0.9.21 包含几个更改，以增加网络容量、提高播种效率，并更有效率的使用带宽。我们已经迁移共享客户端隧道到 ECDSA 签名，并使用新的 "multisession" 功能为那些不支持 ECDSA 的站点添加一个 DSA 后备。</p>
+<p>2015年多洛伦 I2PCon 的报告人和时间表已经公布。查阅 <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon 页面</a>了解详细信息。在 <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a> 上预定您的座位。</p>
+<p>一如往常一般，我們建議您更新到這個版本，要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
+</article><article id="urn:uuid:53ba215d-6cf2-489c-8135-10248e06a141" title="I2PCon 多伦多报告人和时间表已公布" href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon" author="echelon" published="2015-07-19T18:00:00Z" updated="2015-07-22T12:00:00Z"><details><summary>2015年在多伦多的 I2PCon 报告人和时间表已公布</summary></details><p>2015年多洛伦 I2PCon 的报告人和时间表已经公布。查阅 <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon 页面</a>了解详细信息。在 <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a> 上预定您的座位。</p>
+</article>
+</div>

data/translations/entries.gl.html

@@ -1,5 +1,174 @@
 <div>
-<header title="Noticias I2P">Novas e actualizacións do router</header><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
+<header title="Noticias I2P">Novas e actualizacións do router</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
+The bug primarily affected high-bandwidth routers.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
+We have added notification bubbles to several applications in the console to highlight application messages.
+We fixed a tunnel test bug that may have been affecting tunnel reliability.
+The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
+There are several dark theme fixes and improvements.</p>
+<p>We fixed the installer that previously failed on Java 21 or higher.
+We also fixed installing to directory paths that contain spaces on Linux.
+For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
+The workaround is using localhost and the server port, usually 7658, to bypass I2P.
+For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
+We apologize for the issue and are working on a fix.</p>
+</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
+<p>We have improved handling of congested routers in the network.
+Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
+We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
+Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
+<p>Access to information from the console and applications has been improved.
+Issues have been fixed in I2PSnark and SusiMail search.
+The netDB search embedded into the router console now operates in a more intuitive and useful way.
+Minor improvements have been made to diagnostic displays in advanced mode.</p>
+<p>Bugs have also been fixed to improve compatibility within the network.
+An issue with publishing leaseSets was solved which improves reliability major hidden services.
+I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
+This prevents torrents from being unnecessarily disrupted by these changes.
+We welcomed this contribution from a new contributor.
+A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
+This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
+<p>Newer routers will be favored when selecting floodfill routers.
+I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
+Legacy transport protocols are being removed, simplifying the code in the UDP transports.
+Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
+Additional tweaks were made to peer selection strategies.</p>
+<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
+We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
+If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
+Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
+With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
+This should help the network return to normal operation.
+Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
+Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
+This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
+Reachability of I2P sites is badly degraded.</p>
+<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
+Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
+</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
+<p>New features have been added to I2PSnark like the ability to search through torrents.
+Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
+We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
+New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
+Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
+<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
+This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
+This investigation uncovered one minor isolation-piercing event which we repaired.
+This issue was discovered and fixed internally by the I2P team.</p>
+<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
+This should result in improved delivery and availability for these downstream products.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
+It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
+<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
+This will help the network limit the effect of tunnel spam.
+It will also help the network heal during and after DDOS attacks.</p>
+<p>The NetDb changes also help secure individual routers and the applications that use them. 
+Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
+This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
+<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
+CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
+An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
+The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
+The attacker then sends the same message directly to the router.
+The router passes the message to the bloom filter, and is dropped.
+This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
+This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
+Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
+Users of Java I2P are recommended to update immediately to avoid the attack.</p>
+<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
+This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
+<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
+<p>This release also contains a tweakable blocklist.
+Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
+Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
+This feature is off-by-default and is only recommended for advanced users at this time.</p>
+<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
+It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
+This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
+Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
+This issue has also been resolved.
+The docker container is now also compatible with Podman.</p>
+<p>This release syncs translations with transifex and updates the GeoIP database.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
+This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
+The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
+<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
+This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
+This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
+We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
+<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
+zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
+As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
+We thank zzz for providing these services for such a long time.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
+Our investigations and mitigations continue.</p>
+<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
+We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
+However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
+The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
+<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
+We ask for your patience as we work to improve I2P.</p>
+</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
+  The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
+  Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
+  Mitigation strategies are being investigated and implemented gradually.</p>
+<p>While the attack has degraded performance, the network remains intact and usable.
+  Java I2P routers appear to be handling the issues better than i2pd routers for now.
+  Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
+</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
+As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
+First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
+Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
+Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
+<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
+possibly triggered by Bitcoin's new I2P transient address feature,
+but made worse by our SSU2 bugs and other congestion control problems.
+We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
+We have improved our algorithms to reduce network load during times of congestion.
+We are also collaborating with i2pd to develop common congestion control strategies.</p>
+<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
+i2pd released their version 2.45.0 last week and the early results are encouraging.
+New protocols, and distributed networks, are difficult to develop.
+Congestion can arrive with little warning and with little clue of the cause.
+Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
 <p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
 <p>As usual, we recommend that you update to this release. The best way to
 maintain security and help the network is to run the latest release.</p>

data/translations/entries.he.html

@@ -1,5 +1,174 @@
 <div>
-<header title="חדשות I2P">הזנת חדשות, ועדכוני נתב</header><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
+<header title="חדשות I2P">הזנת חדשות, ועדכוני נתב</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
+The bug primarily affected high-bandwidth routers.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
+We have added notification bubbles to several applications in the console to highlight application messages.
+We fixed a tunnel test bug that may have been affecting tunnel reliability.
+The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
+There are several dark theme fixes and improvements.</p>
+<p>We fixed the installer that previously failed on Java 21 or higher.
+We also fixed installing to directory paths that contain spaces on Linux.
+For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
+The workaround is using localhost and the server port, usually 7658, to bypass I2P.
+For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
+We apologize for the issue and are working on a fix.</p>
+</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
+<p>We have improved handling of congested routers in the network.
+Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
+We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
+Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
+<p>Access to information from the console and applications has been improved.
+Issues have been fixed in I2PSnark and SusiMail search.
+The netDB search embedded into the router console now operates in a more intuitive and useful way.
+Minor improvements have been made to diagnostic displays in advanced mode.</p>
+<p>Bugs have also been fixed to improve compatibility within the network.
+An issue with publishing leaseSets was solved which improves reliability major hidden services.
+I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
+This prevents torrents from being unnecessarily disrupted by these changes.
+We welcomed this contribution from a new contributor.
+A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
+This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
+<p>Newer routers will be favored when selecting floodfill routers.
+I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
+Legacy transport protocols are being removed, simplifying the code in the UDP transports.
+Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
+Additional tweaks were made to peer selection strategies.</p>
+<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
+We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
+If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
+Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
+With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
+This should help the network return to normal operation.
+Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
+Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
+This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
+Reachability of I2P sites is badly degraded.</p>
+<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
+Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
+</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
+<p>New features have been added to I2PSnark like the ability to search through torrents.
+Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
+We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
+New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
+Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
+<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
+This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
+This investigation uncovered one minor isolation-piercing event which we repaired.
+This issue was discovered and fixed internally by the I2P team.</p>
+<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
+This should result in improved delivery and availability for these downstream products.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
+It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
+<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
+This will help the network limit the effect of tunnel spam.
+It will also help the network heal during and after DDOS attacks.</p>
+<p>The NetDb changes also help secure individual routers and the applications that use them. 
+Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
+This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
+<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
+CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
+An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
+The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
+The attacker then sends the same message directly to the router.
+The router passes the message to the bloom filter, and is dropped.
+This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
+This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
+Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
+Users of Java I2P are recommended to update immediately to avoid the attack.</p>
+<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
+This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
+<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
+<p>This release also contains a tweakable blocklist.
+Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
+Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
+This feature is off-by-default and is only recommended for advanced users at this time.</p>
+<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
+It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
+This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
+Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
+This issue has also been resolved.
+The docker container is now also compatible with Podman.</p>
+<p>This release syncs translations with transifex and updates the GeoIP database.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
+This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
+The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
+<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
+This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
+This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
+We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
+<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
+zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
+As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
+We thank zzz for providing these services for such a long time.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
+Our investigations and mitigations continue.</p>
+<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
+We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
+However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
+The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
+<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
+We ask for your patience as we work to improve I2P.</p>
+</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
+  The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
+  Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
+  Mitigation strategies are being investigated and implemented gradually.</p>
+<p>While the attack has degraded performance, the network remains intact and usable.
+  Java I2P routers appear to be handling the issues better than i2pd routers for now.
+  Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
+</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
+As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
+First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
+Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
+Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
+<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
+possibly triggered by Bitcoin's new I2P transient address feature,
+but made worse by our SSU2 bugs and other congestion control problems.
+We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
+We have improved our algorithms to reduce network load during times of congestion.
+We are also collaborating with i2pd to develop common congestion control strategies.</p>
+<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
+i2pd released their version 2.45.0 last week and the early results are encouraging.
+New protocols, and distributed networks, are difficult to develop.
+Congestion can arrive with little warning and with little clue of the cause.
+Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
 <p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
 <p>As usual, we recommend that you update to this release. The best way to
 maintain security and help the network is to run the latest release.</p>

data/translations/entries.hu.html

@@ -1,5 +1,175 @@
 <div>
-<header title="I2P Hírek">Hírfolyam és router frissítések</header><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
+<header title="I2P Hírek">Hírfolyam és router frissítések</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
+The bug primarily affected high-bandwidth routers.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
+We have added notification bubbles to several applications in the console to highlight application messages.
+We fixed a tunnel test bug that may have been affecting tunnel reliability.
+The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
+There are several dark theme fixes and improvements.</p>
+<p>We fixed the installer that previously failed on Java 21 or higher.
+We also fixed installing to directory paths that contain spaces on Linux.
+For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
+The workaround is using localhost and the server port, usually 7658, to bypass I2P.
+For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
+We apologize for the issue and are working on a fix.</p>
+</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
+<p>We have improved handling of congested routers in the network.
+Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
+We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
+Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
+<p>Access to information from the console and applications has been improved.
+Issues have been fixed in I2PSnark and SusiMail search.
+The netDB search embedded into the router console now operates in a more intuitive and useful way.
+Minor improvements have been made to diagnostic displays in advanced mode.</p>
+<p>Bugs have also been fixed to improve compatibility within the network.
+An issue with publishing leaseSets was solved which improves reliability major hidden services.
+I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
+This prevents torrents from being unnecessarily disrupted by these changes.
+We welcomed this contribution from a new contributor.
+A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
+This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
+<p>Newer routers will be favored when selecting floodfill routers.
+I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
+Legacy transport protocols are being removed, simplifying the code in the UDP transports.
+Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
+Additional tweaks were made to peer selection strategies.</p>
+<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
+We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
+If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
+Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
+With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
+This should help the network return to normal operation.
+Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
+Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
+This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
+Reachability of I2P sites is badly degraded.</p>
+<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
+Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
+</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
+<p>New features have been added to I2PSnark like the ability to search through torrents.
+Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
+We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
+New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
+Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
+<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
+This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
+This investigation uncovered one minor isolation-piercing event which we repaired.
+This issue was discovered and fixed internally by the I2P team.</p>
+<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
+This should result in improved delivery and availability for these downstream products.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
+It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
+<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
+This will help the network limit the effect of tunnel spam.
+It will also help the network heal during and after DDOS attacks.</p>
+<p>The NetDb changes also help secure individual routers and the applications that use them. 
+Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
+This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
+<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
+CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
+An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
+The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
+The attacker then sends the same message directly to the router.
+The router passes the message to the bloom filter, and is dropped.
+This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
+This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
+Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
+Users of Java I2P are recommended to update immediately to avoid the attack.</p>
+<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
+This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
+<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
+<p>This release also contains a tweakable blocklist.
+Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
+Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
+This feature is off-by-default and is only recommended for advanced users at this time.</p>
+<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
+It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
+This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
+Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
+This issue has also been resolved.
+The docker container is now also compatible with Podman.</p>
+<p>This release syncs translations with transifex and updates the GeoIP database.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
+This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
+The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
+<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
+This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
+This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
+We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
+<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
+zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
+As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
+We thank zzz for providing these services for such a long time.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
+Our investigations and mitigations continue.</p>
+<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
+We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
+However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
+The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
+<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
+We ask for your patience as we work to improve I2P.</p>
+</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
+  The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
+  Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
+  Mitigation strategies are being investigated and implemented gradually.</p>
+<p>While the attack has degraded performance, the network remains intact and usable.
+  Java I2P routers appear to be handling the issues better than i2pd routers for now.
+  Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
+</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
+As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
+First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
+Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
+Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
+<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
+possibly triggered by Bitcoin's new I2P transient address feature,
+but made worse by our SSU2 bugs and other congestion control problems.
+We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
+We have improved our algorithms to reduce network load during times of congestion.
+We are also collaborating with i2pd to develop common congestion control strategies.</p>
+<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
+i2pd released their version 2.45.0 last week and the early results are encouraging.
+New protocols, and distributed networks, are difficult to develop.
+Congestion can arrive with little warning and with little clue of the cause.
+Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
+<p>Mint mindig, azt ajánljuk hogy frissítsen erre a kiadásra.
+A legjobb módja a biztonság fenntartásának és a hálózat segítésének az,
+hogy a legfrissebb kiadást futtatod.</p>
+</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
 <p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
 <p>Mint mindig, azt ajánljuk hogy frissítsen erre a kiadásra.
 A legjobb módja a biztonság fenntartásának és a hálózat segítésének az,

data/translations/entries.id.html

@@ -1,210 +1,178 @@
 <div>
-<header title="Berita I2P">Umpan berita, dan pembaruan router</header><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
-<p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
+<header title="Berita I2P">Umpan berita, dan pembaruan router</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
+The bug primarily affected high-bandwidth routers.</p>
+<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik mempertahankan keamanan dan membantu jaringan adalah menjalankan rilisilis terbaru.</p>
+</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
+We have added notification bubbles to several applications in the console to highlight application messages.
+We fixed a tunnel test bug that may have been affecting tunnel reliability.
+The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
+There are several dark theme fixes and improvements.</p>
+<p>We fixed the installer that previously failed on Java 21 or higher.
+We also fixed installing to directory paths that contain spaces on Linux.
+For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
+<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik mempertahankan keamanan dan membantu jaringan adalah menjalankan rilisilis terbaru.</p>
+</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
+The workaround is using localhost and the server port, usually 7658, to bypass I2P.
+For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
+We apologize for the issue and are working on a fix.</p>
+</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
+<p>We have improved handling of congested routers in the network.
+Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
+We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
+Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
+<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik mempertahankan keamanan dan membantu jaringan adalah menjalankan rilisilis terbaru.</p>
+</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
+<p>Access to information from the console and applications has been improved.
+Issues have been fixed in I2PSnark and SusiMail search.
+The netDB search embedded into the router console now operates in a more intuitive and useful way.
+Minor improvements have been made to diagnostic displays in advanced mode.</p>
+<p>Bugs have also been fixed to improve compatibility within the network.
+An issue with publishing leaseSets was solved which improves reliability major hidden services.
+I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
+This prevents torrents from being unnecessarily disrupted by these changes.
+We welcomed this contribution from a new contributor.
+A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
+<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik mempertahankan keamanan dan membantu jaringan adalah menjalankan rilisilis terbaru.</p>
+</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 telah dirilis" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 dirilis</summary></details><p>I2P 2.6.1 dirilis dalam rangka memperbaiki bug Antar-Muka di dalam aplikasi Hidden Service Manager.
+Bug ini menyebabkan tidak bisa melakukan pengguliran, membuat beberapa konfigurasi tidak dapat diakses.</p>
+<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik mempertahankan keamanan dan membantu jaringan adalah menjalankan rilisilis terbaru.</p>
+</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 telah dirilis" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 dirilis</summary></details><p>Perilisan I2P 2.6.0 ini, melanjutkan pekerjaan kami dalam memperbaiki bug, penambahan fitur, dan meningkatkan keandalan jaringan.</p>
+<p>Newer routers will be favored when selecting floodfill routers.
+I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
+Legacy transport protocols are being removed, simplifying the code in the UDP transports.
+Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
+Additional tweaks were made to peer selection strategies.</p>
+<p>I2P tidak lagi mengizinkan I2P-over-Tor, sambungan dari Tor keluar alamat IP kini diblok.
+Kami tidak menyarankan hal ini karena hal itu menurunkan kinerja I2P dan menggunakan seluruh sumber daya Tor keluar tanpa manfaat.
+Jika Anda adalah orang yang suka membantu yang menjalankan baik Tor Exit dan I2P, kami menyarankan Anda untuk lanjut melakukan hal tersebut, menggunakan alamat IP berbeda untuk masing-masing.
+Non-exit relai dan klien Tor tidak terpengaruh oleh hal ini dan tidak perlu melakukan perubahan apapun.</p>
+<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik mempertahankan keamanan dan membantu jaringan adalah menjalankan rilisilis terbaru.</p>
+</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 dengan perbaikan HTTP</summary></details><p>I2P 2.5.2 dirilis untuk memperbaiki sebuah bug yang ditemukan di versi 2.5.0 yang kadang membuat konten HTTP menjadi terpotong.</p>
+<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik mempertahankan keamanan dan membantu jaringan adalah menjalankan rilisilis terbaru.</p>
+</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 dirilis" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>Rilis I2P 2.5.1 dirilis untuk mengatasi serangan denial of service (DOS)</summary></details><p>I2P 2.5.1 dirilis untuk mengatasi serangan DOS yang mempengaruhi jaringan dan layanan I2P.
+Dengan rilis ini kami menonaktifkan bagian berbasis IP dari alat pendeteksi serangan Sybil yang ditargetkan untuk memperkuat efek dan durasi serangan.
+Ini akan membantu jaringan kembali ke operasi normal.
+Anda yang telah menonaktifkan alat deteksi serangan Sybil dapat mengaktifkannya kembali dengan aman.
+Penyesuaian pada subsistem lain untuk meningkatkan validasi Routerinfo dan pemilihan peer juga telah dilakukan.</p>
+<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik mempertahankan keamanan dan membantu jaringan adalah menjalankan rilisilis terbaru.</p>
+</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Cuaca Badai" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Cuaca Jaringan: Badai. I2P sedang diserang.</summary></details><p>Jaringan I2P saat ini berada dalam serangan DOS.
+Serangan ini mempengaruhi I2P dan i2pd tetapi dengan cara yang berbeda dan mempunyai dampak serius pada kesehatan jaringan.
+Jangkauan situs I2P sangat terdegradasi.</p>
+<p>Jika Anda me-hosting layanan di dalam I2P dan di-hosting di floodfill router, Anda harus mempertimbangkan multihoming layanan pada router yang floodfill-nya dinonaktifkan, untuk meningkatkan jangkauan.
+Mitigasi lain sedang dibahas tetapi solusi jangka panjang dan kompatibel dengan versi -versi sebelumnya masih sedang dikerjakan.
+</p>
+</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="Rilis baru I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>Lebih Banyak Peningkatan Aplikasi, Audit strategi Isolasi NetDB</summary></details><p>Rilis I2P 2.5.0 ini memberikan lebih banyak perbaikan bagi pengguna dibandingkan rilis 2.4.0, yang berfokus pada penerapan strategi isolasi NetDB.</p>
+<p>Fitur-fitur baru telah ditambahkan ke I2PSnark seperti kemampuan untuk mencari melalui torrent. Bug telah diperbaiki untuk meningkatkan kompatibilitas dengan klien I2P torrent lainnya seperti BiglyBT dan qBittorrent. Kami ingin mengucapkan terima kasih kepada semua pengembang yang telah bekerja dengan libtorrent dan qBittorrent untuk mengaktifkan dan meningkatkan dukungan I2P mereka. Fitur-fitur baru juga telah ditambahkan ke SusiMail termasuk dukungan untuk pemformatan Markdown di dalam email dan kemampuan untuk drag-and-drop lampiran ke dalam email. Tunnels dibuat dengan Hidden Services manager sekarang mendukung "Keepalive" yang meningkatkan kinerja dan kompatibilitas dengan teknologi web, memungkinkan situs I2P yang lebih canggih.</p>
+<p>Selama rilis ini kami juga membuat beberapa penyesuaian terhadap NetDB untuk meningkatkan ketahanannya terhadap spam dan untuk meningkatkan kemampuan router untuk menolak pesan yang mencurigakan. Ini adalah bagian dari upaya untuk "mengaudit" penerapan pertahanan "Sub-DB isolation" dari rilis 2.4.0. Investigasi ini mengungkap satu peristiwa kecil yang mengganggu isolasi, yang sudah kami perbaiki. Masalah ini ditemukan dan diperbaiki secara internal oleh tim I2P.</p>
+<p>Selama rilis ini beberapa perbaikan dilakukan pada proses rilis distribusi hilir kami untuk Android dan Windows. Ini akan menghasilkan peningkatan pengiriman dan ketersediaan untuk produk-produk downstream.</p>
+<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik mempertahankan keamanan dan membantu jaringan adalah menjalankan rilisilis terbaru.</p>
+</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="Rilis I2P 2.4.0 dengan peningkatan Congestion dan keamanan NetDB" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>Rilis I2P 2.4.0 dengan peningkatan Congestion dan keamanan NetDB</summary></details><p>Rilis ini, I2P 2.4.0, melanjutkan upaya kami untuk meningkatkan keamanan dan stabilitas jaringan I2P. Rilis ini berisi perbaikan signifikan pada Network Database, sebuah struktur penting dalam jaringan I2P yang digunakan untuk menemukan peers.</p>
+<p>Perubahan penanganan congestion akan meningkatkan stabilitas jaringan dengan memberikan router kemampuan untuk meringankan peers yang macet dengan cara menghindari mereka. Ini akan membantu jaringan membatasi efek tunnel spam. Ini juga akan membantu pemulihan jaringan selama dan setelah serangan DDOS.</p>
+<p>Perubahan NetDB juga membantu mengamankan setiap router dan aplikasi yang menggunakannya. Router sekarang dapat bertahan dengan memisahkan NetDB menjadi beberapa "sub-DB" yang kami gunakan untuk mencegah kebocoran informasi antara aplikasi dan router. Ini juga meningkatkan informasi yang tersedia untuk router Java tentang aktivitas NetDB mereka dan menyederhanakan dukungan kami untuk aplikasi multihoming.</p>
+<p>Juga termasuk sejumlah perbaikan bug dan peningkatan di seluruh aplikasi I2PSNark dan SusiMail.</p>
+<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik mempertahankan keamanan dan membantu jaringan adalah menjalankan rilisilis terbaru.</p>
+</article><article id="urn:uuid:" title="Rilis Baru I2P 2.3.0 - Perbaikan Keamanan, blocklist yang Dapat Diubah, API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Perbaikan Keamanan, Blocklist yang dapat diubah, DTG API</summary></details><p>Rilis ini berisi perbaikan untuk CVE-2023-36325. CVE-2023-36325 adalah bug contex-confusing yang terjadi di filter bloom. Penyerang membuat pesan I2NP yang berisi messageID unik, dan mengirimkan messageID tersebut ke sebuah klien. Pesan tersebut, setelah melewati filter Bloom, tidak diizinkan untuk digunakan kembali di dalam pesan kedua. Penyerang kemudian mengirim pesan yang sama langsung ke router. Router meneruskan pesan ke filter bloom lalu pesan tersebut dibuang. Ini membocorkan informasi yang telah dilihat oleh MessageID sebelumnya, memberi penyerang alasan yang kuat untuk percaya bahwa router menjadi hosting klien. Ini telah diperbaiki dengan memisahkan fungsionalitas filter bloom ke dalam konteks yang berbeda, apakah pesan turun ke tunnel klien atau tunnel eksplorasi, dikirim ke router secara langsung. Dalam keadaan normal, serangan ini membutuhkan waktu beberapa hari untuk berhasil dan dapat dikacaukan oleh beberapa faktor seperti router yang memulai kembali selama fase serangan dan sensitivitas terhadap false-positive. Pengguna Java I2P disarankan untuk segera mengupdate untuk menghindari serangan.</p>
+<p>Dalam rangka memperbaiki bug contex confusion ini, kami telah merevisi beberapa strategi kami untuk membuat kode secara defensif, terhadap jenis kebocoran ini. Hal ini termasuk penyesuaian pada netDb, mekanisme rate-limiting, dan perilaku router floodfill.</p>
+<p>Rilis ini menambahkan not_bob sebagai penyedia host default kedua, dan menambahkan <a href="http://notbob.i2p">notbob.i2p</a> dan <a href="http://ramble.i2p">ramble.i2p</a> ke beranda console.</p>
+<p>Rilis ini juga berisi blocklist yang dapat diubah. Blocklist ini bersifat semi-permanen, di mana masing-masing alamat IP yang diblokir biasanya diblokir sampai router di-restart. Pengguna yang mengamati pertumbuhan bloklist eksplosif selama serangan sybil dapat memilih untuk waktu yang lebih pendek dengan mengkonfigurasi blocklist untuk meng-kedaluwarsa entri pada interval tertentu. Fitur ini tidak aktif secara default dan saat ini hanya direkomendasikan untuk pengguna tingkat lanjut.</p>
+<p>Rilis ini juga menyertakan API untuk memodifikasi plugin dengan Desktop GUI (DTG). Sekarang dimungkinkan untuk menambahkan item menu ke system tray, memungkinkan peluncuran plugin yang lebih intuitif yang menggunakan antarmuka aplikasi asli.</p>
+<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik mempertahankan keamanan dan membantu jaringan adalah menjalankan rilisilis terbaru.</p>
+</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="Rilis baru 2.2.1, perbaikan paket untuk Docker, Ubuntu Lunar dan Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - rilis pemeliharaan untuk 2.2.0</summary></details><p>Setelah rilis I2P 2.2.0, yang dikedepankan untuk mempercepat mitigasi serangan DDOS, kami belajar tentang beberapa masalah berkembang yang membuatnya perlu untuk membangun dan merilis paket baru. Rilis ini memperbaiki masalah dalam Ubuntu Lunar dan Debian Sid di mana konsol router tidak dapat diakses menggunakan versi terbaru dari paket jakarta. Paket Docker tidak membaca argumen dengan benar, sehingga file konfigurasi tidak dapat diakses. Masalah ini juga telah teratasi. Kontainer Docker sekarang juga kompatibel dengan Podman.</p>
+<p>Rilis ini menyinkronkan terjemahan dengan transifex dan memperbarui database GeoIP.</p>
+<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik mempertahankan keamanan dan membantu jaringan adalah menjalankan rilisilis terbaru.</p>
+</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="Rilis Baru 2.2.0, Mitigasi terhadap serangan DDOS dan penyesuaian pada subsistem Streaming" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigasi terhadap serangan DDOS dan penyesuaian pada subsistem Streaming</summary></details><p>Kami telah memilih untuk memajukan tanggal rilis 2.2.0, yang akan terjadi hari ini, 13 Maret 2023. Rilis ini mencakup perubahan pada komponen NetDB, Floodfill, dan Peer-Selection yang meningkatkan kemampuan router untuk bertahan dari serangan DDOS. Serangan ini kemungkinan akan terus berlanjut, tetapi perbaikan sistem ini akan membantu mengurangi risiko serangan DDOS dengan membantu router mengidentifikasi dan menurunkan prioritas router yang tampak berbahaya.</p>
+<p>Rilis ini juga menambahkan perlindungan replay ke subsistem Streaming, yang mencegah penyerang yang dapat menangkap paket terenkripsi untuk dapat menggunakannya kembali, dengan mengirimkannya ke penerima yang tidak dituju. Ini adalah perubahan yang backward-compatible, sehingga router versi sebelumnya masih dapat menggunakan kemampuan streaming dari router yang lebih baru. Masalah ini ditemukan dan diperbaiki secara internal, oleh tim pengembangan I2P, dan tidak terkait dengan serangan DDOS. Kami belum pernah menemukan paket streaming replay di luar I2P dan tidak yakin serangan streaming replay pernah terjadi terhadap jaringan I2P saat ini.</p>
+<p>Seperti yang mungkin Anda perhatikan, catatan rilis ini dan rilis itu sendiri telah ditandatangani oleh idk, bukan ZZZ. zzz telah memilih untuk keluar dari proyek dan tanggung jawabnya diambil alih oleh anggota tim lainnya. Dengan demikian, proyek ini sedang berupaya mengganti infrastruktur statistik jaringan dan memindahkan forum pengembangan ke i2pforum.i2p. Kami berterima kasih kepada zzz karena telah menyediakan layanan ini untuk waktu yang lama.</p>
+<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik mempertahankan keamanan dan membantu jaringan adalah menjalankan rilisilis terbaru.</p>
+</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="Pembaruan DDoS" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>Pembaruan DDoS</summary></details><p>Kami telah mengkonfirmasi bahwa penyerang mengendalikan sejumlah besar router. Investigasi dan mitigasi kami masih berlanjut.</p>
+<p>Ini saat yang tepat untuk mengingatkan semua oranag bahwa bahkan setelah 20 tahun, jaringan I2P masih relatif kecil. Kami tidak memiliki bukti bahwa penyerang berupaya mendeanonimkan pengguna atau layanan tersembunyi tertentu. Namun, jika Anda memiliki model ancaman berisiko tinggi, Anda harus hati-hati mempertimbangkan apakah I2P saat ini memberikan perlindungan yang Anda butuhkan. Solusi terbaik dalam jangka panjang adalah menyebarkan dan menumbuhkan jaringan I2P untuk meningkatkan keamanan pengguna kami.</p>
+<p>Kami akan memberikan informasi tambahan di sini di news feed dan di <a href="http://zzz.i2p">zzz.i2</a> seperlunya. Kami meminta kesabaran Anda saat kami berupaya meningkatkan I2P.</p>
+</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="Tentang serangan DDOS baru -baru ini" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P tetap utuh dengan gangguan kinerja</summary></details><p>Jaringan I2P saat ini dipengaruhi oleh serangan DDOS. Fungsi jaringan floodfill telah terpengaruh, mengakibatkan respons terganggu dan tingkat keberhasilan pembangunan tunnel menurun. Peserta jaringan telah mengalami kesulitan yang terhubung ke situs I2P dan menggunakan layanan I2P. Strategi mitigasi sedang diselidiki dan diterapkan secara bertahap.</p>
+<p>Meskipun serangan tersebut telah menurunkan kinerja, jaringan tetap utuh dan dapat digunakan. Router Java I2P tampaknya menangani masalah ini lebih baik daripada router i2pd untuk saat ini. Berbagai mitigasi harus mulai muncul di dev build untuk router Java dan C ++ di pekan depan.</p>
+</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 dengan banyak perbaikan SSU2</summary></details><p>Kami telah mempelajari beberapa hal sejak rilis 2.0.0 kami pada bulan November. Karena router telah diperbarui ke rilis tersebut, dukungan jaringan telah berubah dari sekitar 1% menjadi lebih dari 60% untuk protokol transport SSU2 baru kami. Pertama, kami telah mengkonfirmasi bahwa SSU2 adalah protokol yang solid, dirancang dengan baik, dan aman. Kedua, namun, kami telah menemukan dan memperbaiki banyak bug minor atau yang jarang dipicu dalam implementasi protokol. Secara kumulatif, dampak bug ini telah menurunkan kinerja jaringan.</p>
+<p>Juga, kami menyadari peningkatan jumlah tunnel dan pengurangan tingkat keberhasilan pembuatan tunnel dalam jaringan, mungkin dipicu oleh fitur alamat transien I2P baru Bitcoin, tetapi diperburuk oleh bug SSU2 kami dan masalah kontrol congestion lainnya. Kami bekerja dengan Bitcoin dan proyek non-Bitcoin lainnya untuk mengurangi tuntutan jaringan I2P. Kami telah meningkatkan algoritma kami untuk mengurangi beban jaringan selama masa congestion. Kami juga berkolaborasi dengan i2pd untuk mengembangkan strategi pengendalian congestion umum.</p>
+<p>Oleh karena itu, kami telah mempercepat rilis ini sekitar enam pekan, untuk mengirimkan perbaikan kepada semua orang. i2pd merilis versi 2.45.0 pekan lalu dan hasil awalnya menggembirakan. Protokol baru, dan jaringan terdistribusi, sulit dikembangkan. Congestion bisa tiba dengan sedikit peringatan dan dengan sedikit petunjuk untuk penyebabnya. Terima kasih atas kesabaran Anda karena kami telah mendiagnosis dan semoga masalahnya dapat diperbaiki.</p>
 <p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
-</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Recent Blog Posts" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>
+</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>Transportasi SSU2 diaktifkan</summary></details><p>I2P release 2.0.0 mengaktifkan UDP transport SSU2 baru kami untuk semua pengguna, setelah menyelesaikan fitur kecil, pengujian, dan banyak perbaikan bug.</p>
+<p>Kami juga membuat banyak perbaikan, termasuk untuk installer, database jaringan, menambah buku alamat pribadi, peluncur Windows Browser, dan IPV6 UPNP.</p>
+<p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
+</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Postingan Blog Terbaru" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>Beberapa posting blog terbaru</summary></details><p>Berikut tautan ke beberapa posting blog terbaru di situs web kami:</p>
 <ul>
-<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Overview of our new SSU2 transport</a></li>
-<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">A warning about I2P coins and other scams</a></li>
-<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">An interview with Konrad from diva.exchange</a></li>
-<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">An interview with Dustin from StormyCloud</a></li>
-</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 with SSU2 for testing</summary></details><p>We have spent the last three months working on our new UDP transport protocol "SSU2"
-with a small number of volunteer testers.
-This release completes the implementation, including relay and peer testing.
-We are enabling it by default for Android and ARM platforms, and a small percentage of other routers at random.
-This will allow us to do much more testing in the next three months, finish the connection migration feature,
-and fix any remaining issues.
-We plan to enable it for everyone in the next release scheduled for November.
-No manual configuration is necessary.</p>
-<p>Of course, there's the usual collection of bug fixes in this release as well.
-We also added an automatic deadlock detector that has already found a rare deadlock that is now fixed.</p>
+<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transportasi">Tinjauan umum transport SSU2 baru kami</a></li>
+<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">Peringatan tentang koin I2P dan penipuan lainnya</a></li>
+<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">Wawancara dengan Konrad dari diva.exchange</a></li>
+<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">Wawancara dengan Dustin dari StormyCloud</a></li>
+</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 dengan SSU2 untuk pengujian</summary></details><p>Kami telah menghabiskan tiga bulan terakhir mengembangkan protokol transportasi UDP baru kami "SSU2" dengan sejumlah kecil penguji sukarela. Rilis ini menyelesaikan implementasi, termasuk pengujian relay dan peer. Kami mengaktifkannya secara default untuk platform Android dan ARM, dan sebagian kecil dari router lain secara acak. Ini akan memungkinkan kami untuk melakukan lebih banyak pengujian dalam tiga bulan ke depan, menyelesaikan fitur migrasi koneksi, dan memperbaiki masalah yang tersisa. Kami berencana untuk mengaktifkannya untuk semua orang pada rilis berikutnya yang dijadwalkan pada bulan November. Tidak diperlukan konfigurasi manual.</p>
+<p>Tentu saja, ada banyak perbaikan bug di rilis ini. Kami juga menambahkan detektor deadlok otomatis yang telah menemukan deadlock langka yang sekarang sudah diperbaiki.</p>
 <p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
-</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="New Outproxy exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>New Outproxy</summary></details><p>I2P "outproxies" (exit nodes) may be used to access the internet through
-your HTTP proxy tunnel.
-As approved at our <a href="http://i2p-projekt.i2p/en/meetings/314">monthly meeting</a>,
-<b>exit.stormycloud.i2p</b> is now our official, recommended outproxy, replacing the long-dead <b>false.i2p</b>.
-For more information on the StormyCloud <a href="http://stormycloud.i2p/">organization</a>,
-<a href="http://stormycloud.i2p/outproxy.html">outproxy</a>,
-and <a href="http://stormycloud.i2p/tos.html">terms of service</a>,
-see the <a href="http://stormycloud.i2p/">StormyCloud website</a>.</p>
-<p>We suggest you change your <a href="/i2ptunnel/edit?tunnel=0">Hidden Services Manager configuration</a>
-to specify <b>exit.stormycloud.i2p</b>
-in two places: <b>Outproxies</b> and <b>SSL Outproxies</b>.
-After editing, <b>scroll down and click Save</b>.
-See our <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">blog post for a screenshot</a>.
-For Android instructions and screenshots see <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">notbob's blog</a>.</p>
-<p>Router updates will not update your configuration, you must edit it manually.
-Thanks to StormyCloud for their support, and please consider a <a href="http://stormycloud.i2p/donate.html">donation</a>.</p>
-</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 with bug fixes</summary></details><p>This release includes bug fixes in i2psnark,
-the router, I2CP, and UPnP.
-Router fixes address bugs in soft restart, IPv6, SSU peer testing,
-network database stores, and tunnel building.
-Router family handling and Sybil classification have also been
-significantly improved.</p>
-<p>Together with i2pd, we are developing our new UDP transport, SSU2.
-SSU2 will bring substantial performance and security improvements.
-It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
-completing the full cryptography upgrade we started about 9 years ago.
-This release contains a preliminary implementation which is disabled by default.
-If you wish to participate in testing, please look for current information
-on zzz.i2p.</p>
+</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="Outproxy baru exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>Outproxy baru</summary></details><p>I2P "Outproxies" (exit node) dapat digunakan untuk mengakses internet melalui tunnel proxy HTTP Anda. Sebagaimana disetujui dalam <a href="http://i2p-projekt.i2p/en/meetings/314">pertemuan bulanan</a>kami, <b>exit.stormycloud.i2p</b> kini menjadi proksi resmi kami yang direkomendasikan, menggantikan <b>false.i2p</b>yang sudah lama tidak aktif. Untuk informasi lebih lanjut tentang <a href="http://stormycloud.i2p/">organisasi</a>StormyCloud, <a href="http://stormycloud.i2p/outproxy.html">outproxy</a>, dan <a href="http://stormycloud.i2p/tos.html">persyaratan layanan</a>, lihat <a href="http://stormycloud.i2p/">situs web StormyCloud</a>.</p>
+<p>Kami menyarankan Anda mengubah <a href="/i2ptunnel/edit?tunnel=0">konfigurasi Hidden Services Manager Anda </a> untuk menentukan <b>exit.stormycloud.i2p </b> di dua tempat: <b>Outproxies </b> dan <b>SSL Outproxies &lt;/bo B3&gt;. Setelah mengedit, <b>scroll ke bawah dan klik Simpan</b>. Lihat posting blog <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">kami untuk melihat tangkapan layar </a>. Untuk instruksi di Android dan tangkapan layar, lihat&lt;A6&gt;Blog notbob .</b></p>
+<p>Pembaruan router tidak akan memperbarui konfigurasi Anda, Anda harus mengeditnya secara manual. Terima kasih kepada StormyCloud atas dukungannya, dan mohon pertimbangkan untuk memberikan<a href="http://stormycloud.i2p/donate.html">donasi</a>.</p>
+</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 dengan perbaikan bug</summary></details><p>Rilis ini termasuk perbaikan bug di I2PSNark, router, I2CP, dan UPnP. Router memperbaiki bug alamat dalam soft restart, IPv6, pengujian peer SSU, penyimpanan database jaringan, dan pembangunan tunnel. Penanganan family router dan klasifikasi Sybil juga telah ditingkatkan secara signifikan.</p>
+<p>Bersama dengan i2pd, kami mengembangkan transport UDP baru kami, SSU2. SSU2 akan memberikan peningkatan kinerja dan keamanan yang substansial. Hal ini juga memungkinkan kami untuk mengganti enkripsi ElGamal yang sangat lambat, menyelesaikan peningkatan kriptografi penuh yang kami mulai sekitar 9 tahun yang lalu. Rilis ini berisi implementasi awal yang dinonaktifkan secara default. Jika Anda ingin berpartisipasi dalam pengujian, silakan cari informasi saat ini di zzz.I2Pp.</p>
 <p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
-</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Install essential Java/Jpackage updates" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>The recent Java "Psychic Signatues" vulnerability affects I2P. Current users of
-I2P on Linux, or any users of I2P who are using a non-bundled JVM should update
-their JVM or switch to a version which does not contain the vulnerability, below
-Java 15.</p>
-<p>New I2P Easy-Install bundles have been generated using the latest release of the
-Java Virtual Machine. Further details have been published in the respective
-bundle newsfeeds.</p>
-</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 with reliability and performance improvements</summary></details><p>The 1.7.0 release contains several performance and reliability improvements.</p>
-<p>There are now popup messages in the system tray, for those platforms that support it.
-i2psnark has a new torrent editor.
-The NTCP2 transport now uses much less CPU.</p>
-<p>The long-deprecated BOB interface is removed for new installs.
-It will continue to work in existing installs, except for Debian packages.
-Any remaining users of BOB applications should ask the developers to convert to the SAMv3 protocol.</p>
-<p>We know that since our 1.6.1 release, network reliability has steadily deteriorated.
-We were aware of the problem soon after the release, but it took us almost two months to find the cause.
-We eventually identified it as a bug in i2pd 2.40.0,
-and the fix will be in their 2.41.0 release coming out about the same time as this release.
-Along the way, we've made several changes on the Java I2P side to improve the
-robustness of network database lookups and stores, and avoid poorly-performing peers in tunnel peer selection.
-This should help the network be more robust even in the presence of buggy or malicious routers.
-Additionally, we're starting a joint program to test pre-release i2pd and Java I2P routers
-together in an isolated test network, so we can find more problems before the releases, not after.</p>
-<p>In other news, we continue to make great progress on the design of our new UDP transport "SSU2" (proposal 159)
-and have started implementation.
-SSU2 will bring substantial performance and security improvements.
-It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
-completing a full cryptography upgrade that started about 9 years ago.
-We expect to start joint testing with i2pd soon, and roll it out to the network later this year.</p>
+</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Instal pembaruan penting Java/Jpackage" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>Kerentanan Java "Psychic Signatues" baru-baru ini mempengaruhi I2P. Pengguna I2P saat ini di Linux, atau pengguna I2P mana pun yang menggunakan JVM yang tidak dibundel harus memperbarui JVM mereka atau beralih ke versi yang tidak mengandung kerentanan, di bawah Java 15.</p>
+<p>Bundel I2P Easy-Install baru telah dibuat menggunakan rilis terbaru Java Virtual Machine. Rincian lebih lanjut telah diterbitkan di bundle newsfeeds masing -masing.</p>
+</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 dengan peningkatan keandalan dan kinerja</summary></details><p>Rilis 1.7.0 berisi beberapa peningkatan kinerja dan keandalan.</p>
+<p>Sekarang ada pesan popup di system tray, untuk platform yang mendukungnya. i2psnark memiliki editor torrent baru. Transport NTCP2 sekarang menggunakan lebih sedikit CPU.</p>
+<p>Antarmuka BOB, yang sudah lama tidak digunakan lagi, sudah dihapus untuk instalasi baru. Ini akan terus berfungsi pada instalasi yang sudah ada, kecuali untuk paket Debian. Pengguna aplikasi BOB yang tersisa harus meminta pengembang untuk mengkonversi ke protokol SAMv3.</p>
+<p>Kami tahu bahwa sejak rilis 1.6.1, keandalan jaringan terus menurun. Kami menyadari masalah ini setelah rilis dikeluarkan, namun kami memerlukan waktu hampir dua bulan untuk menemukan penyebabnya. Kami akhirnya mengidentifikasinya sebagai bug di i2pd 2.40.0, dan perbaikannya akan dilakukan pada rilis 2.41.0 yang akan dirilis pada waktu yang hampir bersamaan dengan rilis ini. Sejalan dengan ini, kami telah membuat beberapa perubahan di sisi Java I2P untuk meningkatkan ketahanan pencarian database jaringan dan store, dan menghindari peers yang berkinerja buruk dalam pemilihan tunnel peers. Ini akan membantu jaringan menjadi lebih kuat bahkan di hadapan router yang punya banyak bug atau berniat jahat. Selain itu, kami memulai program bersama untuk menguji router i2pd pra-rilis dan router Java I2P bersama-sama dalam jaringan pengujian yang terisolasi, sehingga kami dapat menemukan lebih banyak masalah sebelum rilis, bukan setelahnya.</p>
+<p>Dalam berita lain, kami terus membuat kemajuan besar dalam desain transport UDP baru kami "SSU2" (proposal 159) dan telah memulai implementasi. SSU2 akan memberikan peningkatan kinerja dan keamanan yang substansial. Hal ini juga memungkinkan kami untuk menggantikan penggunaan terakhir kami atas enkripsi ElGamal yang sangat lambat, menyelesaikan peningkatan kriptografi penuh yang dimulai sekitar 9 tahun yang lalu. Kami berharap dapat segera memulai pengujian bersama dengan i2pd, dan meluncurkannya ke jaringan pada akhir tahun ini.</p>
 <p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
-</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 enables new tunnel build messages</summary></details><p>This release completes the rollout of two major protocol updates developed in 2021.
-The transition to X25519 encryption for routers is accelerated, and we expect almost all routers to be rekeyed by the end of the year.
-Short tunnel build messages are enabled for a significant bandwidth reduction.</p>
-<p>We added a theme selection panel to the new install wizard.
-We've improved SSU performance and fixed an issue with SSU peer test messages.
-The tunnel build Bloom filter was adjusted to reduce memory usage.
-We have enhanced support for non-Java plugins.</p>
-<p>In other news, we are making excellent progress on the design of our new UDP transport SSU2 and expect to start implementation early next year.</p>
+</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 mengaktifkan pesan pembuatan tunnel baru</summary></details><p>Rilis ini melengkapi peluncuran dua pembaruan protokol utama yang dikembangkan pada tahun 2021. Transisi ke enkripsi X25519 untuk router dipercepat, dan kami memperkirakan hampir semua router akan mendapat rekey pada akhir tahun ini. Pesan pembuatan short tunnel diaktifkan untuk pengurangan bandwidth yang signifikan.</p>
+<p>Kami menambahkan panel pemilihan tema ke wizard penginstalan baru. Kami telah meningkatkan kinerja SSU dan memperbaiki masalah dengan pesan uji peer SSU. Filter Bloom pembuatan tunnel telah disesuaikan untuk mengurangi penggunaan memori. Kami telah meningkatkan dukungan untuk plugin non-Java.</p>
+<p>Dalam berita lain, kami membuat kemajuan yang sangat baik pada desain UDP Transport SSU2 baru kami dan berharap untuk memulai implementasi awal tahun depan.</p>
 <p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
-</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 with new tunnel build messages</summary></details><p>Yes, that's right, after 9 years of 0.9.x releases, we are going straight from 0.9.50 to 1.5.0.
-This does not signify a major API change, or a claim that development is now complete.
-It is simply a recognition of almost 20 years of work to provide anonymity and security for our users.</p>
-<p>This release finishes implementation of smaller tunnel build messages to reduce bandwidth.
-We continue the transition of the network's routers to X25519 encryption.
-Of course there are also numerous bug fixes and performance improvements.</p>
+</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 dengan pesan tunnel build baru</summary></details><p>Ya, benar, setelah 9 tahun rilis 0.9.x, kita langsung beralih dari 0.9.50 ke 1.5.0. Hal ini tidak menandakan adanya perubahan besar pada API, atau klaim bahwa pengembangan telah selesai. Ini hanyalah pengakuan atas kerja keras selama hampir 20 tahun untuk memberikan anonimitas dan keamanan bagi pengguna kami.</p>
+<p>Rilis ini menyelesaikan implementasi pesan tunnel build yang lebih kecil untuk mengurangi bandwidth. Kami melanjutkan transisi router jaringan ke enkripsi X25519. Tentu saja ada banyak juga perbaikan bug dan peningkatan kinerja.</p>
 <p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
-</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="MuWire Desktop Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Muwire Desktop Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire standalone desktop application.
-It does not affect the console plugin, and is not related to the previously-announced plugin issue.
-If you are running the MuWire desktop application you should <a href="http://muwire.i2p/">update to version 0.8.8</a> immediately.</p>
-<p>Details of the issue will be published on <a href="http://muwire.i2p/security.html">muwire.i2p</a>
-on July 15, 2021.</p>
-</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="MuWire Plugin Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Muwire Plugin Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire plugin.
-It does not affect the standalone desktop client.
-If you are running the MuWire plugin you should <a href="/configplugins">update to version 0.8.7-b1</a> immediately.</p>
-<p>See <a href="http://muwire.i2p/security.html">muwire.i2p</a>
-for more information about the vulnerability and updated security recommendations.</p>
-</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 with IPv6 fixes</summary></details><p>0.9.50 continues the transition to ECIES-X25519 for router encryption keys.
-We have enabled DNS over HTTPS for reseeding to protect users from passive DNS snooping.
-There are numerous fixes and improvements for IPv6 addresses, including new UPnP support.</p>
-<p>We have finally fixed some longstanding SusiMail corruption bugs.
-Changes to the bandwidth limiter should improve network tunnel performance.
-There are several improvements in our Docker containers.
-We have improved our defenses for possible malicious and buggy routers in the network.</p>
+</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="Kerentanan Desktop MuWire" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Kerentanan Desktop MuWire</summary></details><p>Kerentanan keamanan telah ditemukan dalam aplikasi desktop standalone MuWire. Ini tidak mempengaruhi plugin console, dan tidak terkait dengan masalah plugin yang diumumkan sebelumnya. Jika Anda menjalankan aplikasi desktop MuWire, Anda harus <a href="http://muwire.i2p/">segera memperbarui ke versi 0.8.8</a>.</p>
+<p>Detail masalah ini akan dipublikasikan di <a href="http://muwire.i2p/security.html">muwire.i2p</a> pada 15 Juli 2021.</p>
+</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="Kerentanan Plugin MuWire" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Kerentanan Plugin MuWire</summary></details><p>Kerentanan keamanan telah ditemukan di plugin MuWire. Itu tidak mempengaruhi klien desktop standalone. Jika Anda menjalankan plugin MuWire, Anda harus <a href="/configplugins">segera memperbarui ke versi 0.8.7-b1</a>.</p>
+<p>Lihat <a href="http://muwire.i2p/security.html">muwire.i2p </a> untuk informasi lebih lanjut tentang kerentanan dan rekomendasi keamanan yang diperbarui.</p>
+</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 dengan perbaikan IPv6</summary></details><p>0.9.50 melanjutkan transisi ke ECIES-X25519 untuk kunci enkripsi router. Kami telah mengaktifkan DNS melalui HTTPS untuk reseeding guna melindungi pengguna dari DNS snooping pasif. Ada banyak perbaikan dan peningkatan untuk alamat IPv6, termasuk dukungan UPnP baru.</p>
+<p>Kami akhirnya telah memperbaiki beberapa bug korupsi SusiMailmail yang sudah berlangsung lama. Perubahan pada batasan bandwidth akan meningkatkan kinerja tunnel jaringan. Ada beberapa perbaikan pada container Docker kami. Kami telah meningkatkan pertahanan kami untuk kemungkinan router berbahaya dan rentan di dalam jaringan.</p>
 <p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
-</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0.9.49 with SSU fixes and faster crypto</summary></details><p>0.9.49 continues the work to make I2P faster and more secure.
-We have several improvements and fixes for the SSU (UDP) transport that should result in faster speeds.
-This release also starts the migration to new, faster ECIES-X25519 encryption for routers.
-(Destinations have been using this encryption for a few releases now)
-We've been working on the specifications and protocols for new encryption for several years,
-and we are getting close to the end of it! The migration will take several releases to complete.</p>
-<p>For this release, to minimize disruption, only new installs and a very small percentage of existing installs
-(randomly selected at restart) will be using the new encryption.
-If your router does "rekey" to use the new encryption, it may have lower traffic or less reliability than usual for several days after you restart.
-This is normal, because your router has generated a new identity.
-Your performance should recover after a while.</p>
-<p>We have "rekeyed" the network twice before, when changing the default signature type,
-but this is the first time we've changed the default encryption type.
-Hopefully it will all go smoothly, but we're starting slowly to be sure.</p>
+</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0.9.49 dengan perbaikan SSU dan kripto yang lebih cepat</summary></details><p>0.9.49 melanjutkan membuat I2P lebih cepat dan lebih aman. Kami memiliki beberapa perbaikan dan perbaikan pada transportasi SSU (UDP) yang akan menghasilkan kecepatan lebih tinggi. Rilis ini juga memulai migrasi ke enkripsi baru, ECIES-X25519 yang lebih cepat untuk router. (Destinations telah menggunakan enkripsi ini untuk beberapa rilis sekarang) Kami telah mengerjakan spesifikasi dan protokol untuk enkripsi baru selama beberapa tahun, dan kami hampir selesai! Migrasi ini akan memerlukan beberapa rilis untuk diselesaikan.</p>
+<p>Untuk rilis ini, untuk meminimalkan gangguan, hanya instalasi baru dan persentase yang sangat kecil dari instalasi yang sudah ada (dipilih secara acak saat restart) yang akan menggunakan enkripsi baru. Jika router Anda melakukan "rekey" untuk menggunakan enkripsi baru, mungkin memiliki lalu lintas yang lebih rendah atau lebih sedikit keandalan dari biasanya selama beberapa hari setelah Anda restart. Ini normal karena router Anda telah menghasilkan identitas baru. Performa Anda akan pulih setelah beberapa saat.</p>
+<p>Kami telah "rekey" jaringan dua kali sebelumnya, ketika mengubah tipe signatur default, tetapi ini adalah pertama kalinya kami mengubah jenis enkripsi default. Mudah-mudahan semuanya berjalan lancar, tapi kami memulainya perlahan-lahan untuk memastikannya.</p>
 <p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
-</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 with performance enhancements</summary></details><p>0.9.48 enables our new end-to-end encryption protocol (proposal 144) for most services.
-We have added preliminary support for new tunnel build message encryption (proposal 152).
-There are significant performance improvements throughout the router.</p>
-<p>Packages for Ubuntu Xenial (16.04 LTS) are no longer supported.
-Users on that platform should upgrade so you may continue to receive I2P updates.</p>
+</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 dengan peningkatan kinerja</summary></details><p>0.9.48 mengaktifkan protokol enkripsi end-to-end kami yang baru (proposal 144) untuk sebagian besar layanan. Kami telah menambahkan dukungan awal untuk enkripsi pesan tunnel build baru (proposal 152). Ada peningkatan kinerja yang signifikan di seluruh router.</p>
+<p>Paket untuk Ubuntu Xenial (16.04 LTS) tidak lagi didukung. Pengguna pada platform tersebut harus melakukan upgrade distro sehingga Anda dapat terus menerima pembaruan I2P.</p>
 <p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
-</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 enables new encryption</summary></details><p>0.9.47 enables our new end-to-end encryption protocol (proposal 144) by default for some services.
-The Sybil analysis and blocking tool is now enabled by default.</p>
-<p>Java 8 or higher is now required.
-Debian packages for Wheezy and Stretch, and for Ubuntu Trusty and Precise, are no longer supported.
-Users on those platforms should upgrade so you may continue to receive I2P updates.</p>
+</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 menggunakan enkripsi baru</summary></details><p>0.9.47 mengaktifkan protokol enkripsi end-to-end kami yang baru (proposal 144) secara default untuk beberapa layanan. Alat analisis dan pemblokiran Sybil sekarang diaktifkan secara default.</p>
+<p>Java 8 atau lebih tinggi sekarang diperlukan. Paket Debian untuk Wheezy dan Stretch, serta untuk Ubuntu Trusty dan Precise, tidak lagi didukung. Pengguna di platform tersebut harus melakukan upgrade distro untuk terus menerima pembaruan I2P.</p>
 <p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
-</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="0.9.46 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 with bug fixes</summary></details><p>0.9.46 contains significant performance improvements in the streaming library.
-We have completed development of ECIES encryption (proposal 144) and there is now an option to enable it for testing.</p>
-<p>Windows users only:
-This release fixes a local privilege escalation vulnerability
-which could be exploited by a local user.
-Please apply the update as soon as possible.
-Thanks to Blaze Infosec for responsible disclosure of the issue.</p>
-<p>This is the last release to support Java 7, Debian packages Wheezy and Stretch, and Ubuntu packages Precise and Trusty.
-Users on those platforms must upgrade to receive future I2P updates.</p>
+</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="0.9.46 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 dengan perbaikan bug</summary></details><p>0.9.46 berisi peningkatan kinerja yang signifikan di streaming library. Kami telah menyelesaikan pengembangan enkripsi ECIES (proposal 144) dan sekarang ada opsi untuk mengaktifkannya untuk pengujian.</p>
+<p>Hanya untuk Pengguna Windows: Rilis ini memperbaiki kerentanan eskalasi hak istimewa lokal yang dapat dieksploitasi oleh pengguna lokal. Harap terapkan pembaruan sesegera mungkin. Terima kasih kepada Blaze Infosec atas pengungkapan masalah secara bertanggung-jawab.</p>
+<p>Ini adalah rilis terakhir yang mendukung Java 7, paket Debian Wheezy and Stretch, dan paket Ubuntu Precise dan Trusty. Pengguna di platform tersebut harus melakukan upgrade distro untuk menerima pembaruan I2P di masa depan.</p>
 <p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
 </article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 telah rilis" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 dengan perbaikan bug</summary></details><p>0.9.45 berisi perbaikan penting untuk mode sembunyi dan pengujian lebar pita (bandwidth). 
 Ada pembaruan untuk tampilan gelap pada konsol.
 Kami terus berupaya meningkatkan kinerja dan pengembangan enkripsi end-to-end yang baru (proposal 144).</p>
 <p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
-</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="0.9.44 telah rilis" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 dengan perbaikan bug</summary></details><p>0.9.44 contains an important fix for a denial of service issue in hidden services handling of new encryption types.
-All users should update as soon as possible.</p>
-<p>The release includes initial support for new end-to-end encryption (proposal 144).
-Work continues on this project, and it is not yet ready for use.
-There are changes to the console home page, and new embedded HTML5 media players in i2psnark.
-Additional fixes for firewalled IPv6 networks are included.
-Tunnel build fixes should result in faster startup for some users.</p>
+</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="0.9.44 telah rilis" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 dengan perbaikan bug</summary></details><p>0.9.44 berisi perbaikan penting untuk masalah denial of service dalam hidden service yang menangani jenis enkripsi baru. Semua pengguna harus memperbarui sesegera mungkin.</p>
+<p>Rilis ini mencakup dukungan awal untuk enkripsi end-to-end yang baru (proposal 144). Pekerjaan berlanjut pada proyek ini, dan belum siap digunakan. Ada perubahan pada halaman beranda console, dan embedded HTML5 media player baru di i2psnark. Perbaikan tambahan untuk jaringan IPv6 yang dilindungi firewall sudah disertakan. Perbaikan Tunnel Build akan menghasilkan startup yang lebih cepat untuk beberapa pengguna.</p>
 <p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
-</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="0.9.43 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 with bug fixes</summary></details><p>In the 0.9.43 release, we continue work on stronger security and privacy features and performance improvements.
-Our implementation of the new leaseset specification (LS2) is now complete.
-We are beginning our implementation of stronger and faster end-to-end encryption (proposal 144) for a future release.
-Several IPv6 address detection issues have been fixed, and there of course are several other bug fixes.</p>
+</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="0.9.43 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 dengan perbaikan bug</summary></details><p>Dalam rilis 0.9.43, kami terus bekerja pada fitur keamanan dan privasi yang lebih kuat dan peningkatan kinerja. Implementasi spesifikasi leaseset baru (LS2) kami sekarang lengkap. Kami memulai implementasi enkripsi end-to-end yang lebih kuat dan lebih cepat (proposal 144) untuk rilis di masa depan. Beberapa masalah deteksi alamat IPv6 telah diperbaiki, dan tentunya ada beberapa perbaikan bug lainnya.</p>
 <p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
-</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="0.9.42 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 with bug fixes</summary></details><p>0.9.42 continues the work to make I2P faster and more reliable.
-It includes several changes to speed up our UDP transport.
-We have split up the configuration files to enable future work for more modular packaging.
-We continue work to implement new proposals for faster and more secure encryption.
-There are, of course, a lot of bug fixes also.</p>
+</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="0.9.42 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 dengan perbaikan bug</summary></details><p>0.9.42 melanjutkan pekerjaan untuk membuat I2P lebih cepat dan lebih dapat diandalkan. Ini mencakup beberapa perubahan untuk mempercepat transport UDP kami. Kami telah membagi file konfigurasi untuk memungkinkan pekerjaan di masa depan untuk pengemasan yang lebih modular. Kami terus berupaya menerapkan proposal baru untuk enkripsi yang lebih cepat dan aman. Tentu saja ada banyak perbaikan bug juga.</p>
 <p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
-</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="0.9.41 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.41 with bug fixes</summary></details><p>0.9.41 continues the work to implement new features for proposal 123,
-including per-client authentication for encrypted leasesets.
-The console has an updated I2P logo and several new icons.
-We've updated the Linux installer.</p>
-<p>Startup should be faster on platforms such as Raspberry Pi.
-We've fixed several bugs, including some serious ones affecting low-level network messages.</p>
+</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="0.9.41 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.41 dengan perbaikan bug</summary></details><p>0.9.41 melanjutkan pekerjaan untuk mengimplementasikan fitur-fitur baru untuk proposal 123, termasuk otentikasi per klien untuk leaseset terenkripsi. Console memiliki logo I2P yang diperbarui dan beberapa ikon baru. Kami telah memperbarui penginstal Linux.</p>
+<p>Startup akan lebih cepat pada beberapa platform seperti Raspberry Pi. Kami telah memperbaiki beberapa bug, termasuk beberapa yang serius yang mempengaruhi pesan jaringan tingkat rendah.</p>
 <p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
-</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="0.9.40 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 with new icons</summary></details><p>0.9.40 includes support for the new encrypted leaseset format.
-We disabled the old NTCP 1 transport protocol.
-There's a new SusiDNS import feature, and a new scripted filtering mechanism for incoming connections.</p>
-<p>We've made a lot of improvements to the OSX native installer, and we've updated the IzPack installer as well.
-The work continues on refreshing the console with new icons.
-As usual, we've fixed lots of bugs also!</p>
+</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="0.9.40 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 dengan ikon baru</summary></details><p>0.9.40 menyertakan dukungan untuk format leaseset terenkripsi yang baru. Kami menonaktifkan protokol transport NTCP 1 yang lama. Ada fitur impor SusiDNS baru, dan mekanisme penyaringan skrip baru untuk koneksi yang masuk.</p>
+<p>Kami telah melakukan banyak perbaikan pada penginstal OSX, dan kami telah memperbarui penginstal IzPack juga. Pekerjaan terus dilakukan untuk menyegarkan console dengan ikon baru. Seperti biasa, kami juga memperbaiki banyak bug!</p>
 <p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
-</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 with performance improvements</summary></details><p>0.9.39 includes extensive changes for the new network database types (proposal 123).
-We've bundled the i2pcontrol plugin as a webapp to support development of RPC applications.
-There are numerous performance improvements and bug fixes.</p>
-<p>We've removed the midnight and classic themes to reduce the maintenance burden;
-previous users of those themes will now see the dark or light theme.
-There's also new home page icons, a first step in updating the console.</p>
+</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 dengan peningkatan kinerja</summary></details><p>0.9.39 mencakup perubahan ekstensif untuk tipe database jaringan baru (proposal 123). Kami telah menggabungkan plugin I2pcontrol sebagai webapp untuk mendukung pengembangan aplikasi RPC. Ada banyak peningkatan kinerja dan perbaikan bug.</p>
+<p>Kami telah menghapus tema midnight dan classic untuk mengurangi beban pemeliharaan; Pengguna sebelumnya dari tema -tema tersebut sekarang akan melihat tema dark atau light. Ada juga ikon halaman beranda baru, langkah pertama dalam memperbarui console.</p>
 <p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
-</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 with new setup wizard</summary></details><p>0.9.38 includes a new first-install wizard with a bandwidth tester.
-We've added support for the latest GeoIP database format.
-There's a new Firefox profile installer and a new, native Mac OSX installer on our website.
-Work continues on supporting the new "LS2" netdb format.</p>
-<p>This release also contains plenty of bug fixes, including several issues with susimail attachments, and a fix for IPv6-only routers.</p>
+</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 dengan wizard pengaturan baru</summary></details><p>0.9.38 termasuk wizard instal pertama dengan tester bandwidth. Kami telah menambahkan dukungan untuk format database GeoIP terbaru. Ada penginstal profil Firefox baru dan penginstal Mac OSX asli di situs web kami. Pekerjaan terus dilakukan untuk mendukung format netdb "LS2" yang baru.</p>
+<p>Rilis ini juga berisi banyak perbaikan bug, termasuk beberapa masalah dengan lampiran susimail, dan perbaikan untuk router khusus IPv6.</p>
 <p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
-</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="35C3 Trip Report" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P at 35C3</summary></details><p>The I2P team was mostly all in attendance at 35C3 in Leipzig.
-Daily meetings were held to review the past year and cover our development and design goals for 2019.</p>
-<p>The Project Vision and new Roadmap can be <a href="http://i2p-projekt.i2p/en/get-involved/roadmap">reviewed here</a>.</p>
-<p>Work will continue on LS2, the Testnet, and usability improvements to our website and console.
-A plan is in place to be in Tails, Debian and Ubuntu Disco. We still need people to work on Android and I2P_Bote fixes.</p>
+</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="Laporan kunjungan 35C3" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P di 35C3</summary></details><p>Tim I2P sebagian besar hadir di 35C3 di Leipzig. Pertemuan harian diadakan untuk meninjau tahun lalu dan membahas tujuan pengembangan dan desain kami di tahun 2019.</p>
+<p>Visi proyek dan roadmap baru dapat<a href="http://i2p-projekt.i2p/en/get-involved/roadmap">diulas di sini </a>.</p>
+<p>Pekerjaan akan dilanjutkan pada LS2, Testnet, dan peningkatan kegunaan pada situs web dan console kami. Ada rencana untuk menggunakan Tails, Debian, dan Ubuntu Disco. Kami masih membutuhkan orang untuk mengerjakan perbaikan Android dan I2P_BOTE.</p>
 </article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="0.9.37 Dirilis" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37 dengan NTCP2 telah diaktifkan</summary></details><p>0.9.37 memungkinkan protokol transportasi yang lebih cepat dan aman yang disebut sebagai NTCP2.</p>
 <p>Seperti biasanya, kami merekomendasikan agar Anda memperbarui ke rilis ini. Cara terbaik untuk mengelola keamanan dan bantuan pada jaringan adalah dengan menjalankan rilis terbaru.</p>
 </article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="0.9.36 dirilis" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 memiliki perbaikan NTCP2 dan bug</summary></details><p>0.9.36 memiliki transport protocol yang baru dan lebih aman bernama NTCP2.
@@ -247,8 +215,7 @@ Makan malam tahunan kita adalah sukses besar sebagai tanda terima kasih kepada s
 Versi-versi sebelumnya tidak didukung lagi dan tidak tersedia di rilis Debian Stretch and Ubuntu Zesty mendatang.
 Router akan memigrasikan file konfigurasi jetty.xml untuk setiap situs Jetty ke setup Jetty 9 yang baru. 
 Ini seharusnya berfungsi untuk konfigurasi yang baru dan tidak dimodifikasi, namun mungkin tidak berfungsi untuk pengaturan yang dimodifikasi atau yang sangat lama. 
-Pastikan situs web Jetty Anda berfungsi setelah melakukan pembaruan, dan hubungi kami di IRC jika memerlukan bantuan.
-</p>
+Pastikan situs web Jetty Anda berfungsi setelah melakukan pembaruan, dan hubungi kami di IRC jika memerlukan bantuan.</p>
 <p>Beberapa plugin tidak kompatibel dengan Jetty 9 sehingga harus diperbarui. 
 Plugin-plugin berikut telah diperbarui untuk bekerja dengan 0.9.30, dan router Anda harus memperbaruinya setelah restart: 
 I2pbote 0.4.6; Zzzot 0.15.0 

data/translations/entries.it.html

@@ -1,5 +1,173 @@
 <div>
-<header title="I2P News">News feed e aggiornamenti dei router</header><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
+<header title="I2P News">News feed e aggiornamenti dei router</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
+The bug primarily affected high-bandwidth routers.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
+We have added notification bubbles to several applications in the console to highlight application messages.
+We fixed a tunnel test bug that may have been affecting tunnel reliability.
+The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
+There are several dark theme fixes and improvements.</p>
+<p>We fixed the installer that previously failed on Java 21 or higher.
+We also fixed installing to directory paths that contain spaces on Linux.
+For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
+The workaround is using localhost and the server port, usually 7658, to bypass I2P.
+For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
+We apologize for the issue and are working on a fix.</p>
+</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
+<p>We have improved handling of congested routers in the network.
+Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
+We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
+Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
+<p>Access to information from the console and applications has been improved.
+Issues have been fixed in I2PSnark and SusiMail search.
+The netDB search embedded into the router console now operates in a more intuitive and useful way.
+Minor improvements have been made to diagnostic displays in advanced mode.</p>
+<p>Bugs have also been fixed to improve compatibility within the network.
+An issue with publishing leaseSets was solved which improves reliability major hidden services.
+I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
+This prevents torrents from being unnecessarily disrupted by these changes.
+We welcomed this contribution from a new contributor.
+A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
+This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
+<p>Newer routers will be favored when selecting floodfill routers.
+I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
+Legacy transport protocols are being removed, simplifying the code in the UDP transports.
+Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
+Additional tweaks were made to peer selection strategies.</p>
+<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
+We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
+If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
+Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
+With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
+This should help the network return to normal operation.
+Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
+Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
+This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
+Reachability of I2P sites is badly degraded.</p>
+<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
+Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
+</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
+<p>New features have been added to I2PSnark like the ability to search through torrents.
+Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
+We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
+New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
+Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
+<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
+This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
+This investigation uncovered one minor isolation-piercing event which we repaired.
+This issue was discovered and fixed internally by the I2P team.</p>
+<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
+This should result in improved delivery and availability for these downstream products.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
+It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
+<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
+This will help the network limit the effect of tunnel spam.
+It will also help the network heal during and after DDOS attacks.</p>
+<p>The NetDb changes also help secure individual routers and the applications that use them. 
+Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
+This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
+<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
+CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
+An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
+The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
+The attacker then sends the same message directly to the router.
+The router passes the message to the bloom filter, and is dropped.
+This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
+This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
+Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
+Users of Java I2P are recommended to update immediately to avoid the attack.</p>
+<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
+This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
+<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
+<p>This release also contains a tweakable blocklist.
+Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
+Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
+This feature is off-by-default and is only recommended for advanced users at this time.</p>
+<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
+It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
+This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
+Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
+This issue has also been resolved.
+The docker container is now also compatible with Podman.</p>
+<p>This release syncs translations with transifex and updates the GeoIP database.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
+This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
+The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
+<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
+This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
+This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
+We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
+<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
+zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
+As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
+We thank zzz for providing these services for such a long time.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
+Our investigations and mitigations continue.</p>
+<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
+We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
+However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
+The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
+<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
+We ask for your patience as we work to improve I2P.</p>
+</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
+  The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
+  Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
+  Mitigation strategies are being investigated and implemented gradually.</p>
+<p>While the attack has degraded performance, the network remains intact and usable.
+  Java I2P routers appear to be handling the issues better than i2pd routers for now.
+  Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
+</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
+As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
+First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
+Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
+Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
+<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
+possibly triggered by Bitcoin's new I2P transient address feature,
+but made worse by our SSU2 bugs and other congestion control problems.
+We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
+We have improved our algorithms to reduce network load during times of congestion.
+We are also collaborating with i2pd to develop common congestion control strategies.</p>
+<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
+i2pd released their version 2.45.0 last week and the early results are encouraging.
+New protocols, and distributed networks, are difficult to develop.
+Congestion can arrive with little warning and with little clue of the cause.
+Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
+<p>Come sempre consigliamo ad ogni utente di aggiornare il proprio sistema a questa versione. Il modo migliore per essere anonimi ed aiutare gli altri ad esserlo è eseguire un software aggiornato.</p>
+</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
 <p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
 <p>Come sempre consigliamo ad ogni utente di aggiornare il proprio sistema a questa versione. Il modo migliore per essere anonimi ed aiutare gli altri ad esserlo è eseguire un software aggiornato.</p>
 </article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Recent Blog Posts" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>

data/translations/entries.ja.html

@@ -1,5 +1,162 @@
 <div>
-<header title="I2P ニュース">ニュースフィードとルータのアップデート</header><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 リリース" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 トランスポート有効</summary></details><p>I2Pは小さな機能、試験及び非常に多いバグ修正の達成後に2.0.0をリリースし、全ユーザーに新しいUDPトランスポートのSSU2を有効にします。</p>
+<header title="I2P ニュース">ニュースフィードとルーターの更新</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 リリース" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 リリース</summary></details><p>2.8.2は、2.8.1のリリースで導入されてしまった、SHA256の不具合を原因とするバグを修正します。
+このバグは主に、高帯域幅のルーターに影響します。</p>
+<p>例によって、このリリースに更新することをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
+</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 リリース" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 リリース</summary></details><p>2.8.1は、2.8.0の端末内にあるサイトへアクセスする際の欠陥を修正します。
+我々はアプリケーションのメッセージを強調するため、コンソール内のいくつかのアプリケーションに、通知の泡を追加しました。
+我々は、トンネルの信頼性に影響しうる、トンネル試験のバグを修正しました。
+アドレス帳は今、購読から追加された最近のホスト名を表示する「最新」タブを備えます。
+ダークテーマのいくつか修正と改善があります。</p>
+<p>我々は、Java 21以上で以前に不調だったインストーラーを修正しました。
+我々はまた、Linux上で空白を含むディレクトリーパスへのインストールを修正しました。
+Dockerを使用する方々のためには、我々は古いDockerコンテナとコンテナのライブラリを更新しました。</p>
+<p>例によって、このリリースに更新することをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
+</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
+The workaround is using localhost and the server port, usually 7658, to bypass I2P.
+For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
+We apologize for the issue and are working on a fix.</p>
+</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 リリース" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 リリース</summary></details><p>このリリースでは、バグ修正、不使用コードの削除、及びネットワーク安定性の改善によってI2Pを改善します。</p>
+<p>我々は、ネットワーク内の混雑したルーターの扱いを改善しました。
+UPnPとNATトラバーサルでの問題は、接続の改善とエラー報告によって対処されました。
+ルーターのパフォーマンス改善と負担軽減のため、NetDBから不要なleasesetを除去する、更なる能動的な方策があります。
+他の変更には、ルーターの再起動またはシャットダウン時などに、可観測性を減らす実装があります。</p>
+<p>例によって、このリリースに更新することをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
+</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
+<p>Access to information from the console and applications has been improved.
+Issues have been fixed in I2PSnark and SusiMail search.
+The netDB search embedded into the router console now operates in a more intuitive and useful way.
+Minor improvements have been made to diagnostic displays in advanced mode.</p>
+<p>Bugs have also been fixed to improve compatibility within the network.
+An issue with publishing leaseSets was solved which improves reliability major hidden services.
+I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
+This prevents torrents from being unnecessarily disrupted by these changes.
+We welcomed this contribution from a new contributor.
+A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
+<p>例によって、このリリースに更新することをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
+</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
+This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
+<p>例によって、このリリースに更新することをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
+</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
+<p>Newer routers will be favored when selecting floodfill routers.
+I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
+Legacy transport protocols are being removed, simplifying the code in the UDP transports.
+Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
+Additional tweaks were made to peer selection strategies.</p>
+<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
+We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
+If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
+Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
+<p>例によって、このリリースに更新することをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
+</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 リリース" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 - HTTPの修正</summary></details><p>I2P 2.5.2では、2.5.0で発生した一部のHTTPコンテンツを切り詰めてしまうバグを修正しました。</p>
+<p>例によって、このリリースに更新することをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
+</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 リリース" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>サービス拒否攻撃に対処するI2Pリリース2.5.1をリリース</summary></details><p>I2P 2.5.1 は、I2Pネットワークとサービスに影響を及ぼすサービス拒否攻撃に対処するためにリリースされました。
+このリリースでは、攻撃の効果と期間を増幅するために標的にされたSybil攻撃検知器のIPに基づく部分を無効化しました。
+これにより、ネットワークは正常な動作に戻るはずです。
+Sybil攻撃検知器を無効にしている人は、安全に再び有効にしてください。
+また、ルーター情報の検証とピア選択を改善するために、他のサブシステムの調整も行われました。</p>
+<p>例によって、このリリースに更新することをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
+</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="荒天" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>ネットワーク天気: 荒天。I2Pは攻撃に曝されている。</summary></details><p>I2Pネットワークは現在、サービス拒否攻撃を受けています。
+
+この攻撃はI2Pとi2pdに影響を与えますが、その方法は異なっており、ネットワークの健全性に深刻な影響を及ぼしています。
+I2Pサイトの到達可能性はひどく低下しています。</p>
+<p>I2P内でサービスをホスティングしており、それがFloodfillルーターでホスティングされている場合、到達可能性を改善するために、Floodfillを無効にしたルーターを追加してサービスの冗長性を高めることを検討すべきです。
+その他の緩和策も検討されていますが、長期的で下位互換性のある解決策はまだ中で作業中です。</p>
+</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="新リリース I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>アプリケーションの更なる改善、NetDB分離計画の調査</summary></details><p>このリリース、I2P 2.5.0は、NetDB分離計画の実装に焦点を当てた2.4.0のリリースよりも更に、利用者が触れる部分の改善を提供します。</p>
+<p>I2PSnarkへ、トレント全体を検索する新機能が追加されました。
+BiglyBTとqBittorrentのような他のI2Pトレントクライアントでバグが修正され、互換性が改善されます。
+libtorrentとqBittorrentでI2Pのサポートの有効化と改善をするために作業した開発者全員に感謝します。
+SusiMailもまた、新機能が追加され、電子メール内でマークダウン形式のためのサポートと、電子メール内へ添付をドラッグアンドドロップする機能が追加されました。
+秘匿サービスマネージャーで作成されたトンネルは今、性能と、ウェブ技術との互換性を改善する「Keepalive」をサポートします。</p>
+<p>このリリースを通じて我々はまた、怪しいメッセージを却下するルーターの機能を改善するためと、スパムへの回復力を改善するために、NetDBにいくつかの調整を行いました。
+これは、2.4.0のリリースからの「Sub-DB分離」防御の実装「調査」への取り組みの一部です。
+この研究は我々が修復した一つの小さな分離穿孔を扱いません。
+この問題はI2Pチームによって発見され、内部で修復されました。</p>
+<p>このリリースを通じて、AndroidとWindows用の我々の下流の配布にて、リリースの過程にいくつかの改善を行いました。
+その結果、これらの下流の所産の配送と入手しやすさが改善されるはずです。</p>
+<p>例によって、このリリースに更新することをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
+</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
+It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
+<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
+This will help the network limit the effect of tunnel spam.
+It will also help the network heal during and after DDOS attacks.</p>
+<p>The NetDb changes also help secure individual routers and the applications that use them. 
+Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
+This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
+<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
+<p>例によって、このリリースに更新することをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
+</article><article id="urn:uuid:" title="新リリース I2P 2.3.0 - セキュリティ修正、微調整可能なブロック一覧、DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - セキュリティ修正、微調整可能なブロック一覧、DTG API</summary></details><p>このリリースにはCVE-2023-36325のための修正が含まれます。
+CVE-2023-36325は、bloomフィルターに発生するコンテキスト混乱バグです。
+攻撃者は、唯一無二のmessageIDを含むI2NPメッセージを作成し、そのmessageIDをクライアントに送信します。
+そのメッセージは、bloomフィルターを通過した後、二回目のメッセージで再使用することができません。
+攻撃者はその後、同じメッセージをルーターへ直接送信します。
+ルーターはそのメッセージをbloomフィルターに渡し、削除します。
+これによって、messageIDが以前に見たことがあるという情報が漏れてしまい、攻撃者は、ルーターがクライアントをホストしていると信じる強い根拠を与えてしまいます。
+この問題は、bloomフィルターの機能を、メッセージがクライアントトンネルを通ったか、調査トンネルを通ったか、ルーターに直接送られたかに基づいて、異なるコンテキストに分離することで解決されました。
+通常の状況下で、この攻撃は成功するまでに数日かかり、攻撃する段階の間にルーターが再起動したり、誤検知の影響を受けやすいなど、いくつかの要因によって混乱する可能性があります。
+Java I2Pの利用者は、この攻撃を回避するために直ちに更新することを推奨します。</p>
+<p>このコンテキスト混乱バグを修正する過程で、我々はこの種の漏洩に対して防御的なコードを書くために、いくつかの計略を改めました。
+これには、netDb、転送量制限機構、floodfillルーターの動作に対する微調整が含まれます。</p>
+<p>このリリースは、初期設定の第二のhosts提供者としてnot_bobを追加し、更に、コンソールホームページに<a href="http://notbob.i2p">notbob.i2p</a>と<a href="http://ramble.i2p">ramble.i2p</a>を追加しました。</p>
+<p>このリリースには、微調整可能なブロック一覧も含まれています。
+ブロック一覧は半永続的で、ブロックされたIPアドレスは通常、ルーターが再起動するまでブロックされます。
+sybil攻撃中にブロック一覧の爆発的な増加を観測したユーザーは、ブロック一覧が一定間隔で項目を失効するように設定することで、より短いタイムアウトを選択することができます。
+この機能は初期設定では無効になっており、現時点では高度な利用者にのみ推奨されます。</p>
+<p>このリリースには、Desktop GUI(DTG)でプラグインを変更するためのAPIも含まれています。
+システムトレイにメニュー項目を追加できるようになり、ネイティブアプリケーションインタフェースを使用するプラグインをより直感的に起動できるようになりました。</p>
+<p>例によって、このリリースに更新することをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
+</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="新リリース 2.2.1。Docker、Ubuntu Lunar、及びDebian Sid用のパッケージ化" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - 2.2.0用の保守リリース</summary></details><p>DDOS攻撃用の緩和策を短期で仕上げるため、前倒しにしたI2P 2.2.0リリースの後、いくつかの開発中の問題が判明し、新しいパッケージの構築とリリースが必要になりました。
+このリリースでは、Ubuntu LunarおよびDebian Sidにおいて、jakartaパッケージの更新版を使用してルーターコンソールにアクセスできない問題を修正します。
+Dockerパッケージでは引数を正しく読み込まず、その結果、構成ファイルにアクセスできないことがありました。
+この問題も解決されています。
+DockerコンテナはPodmanにも対応しました。</p>
+<p>このリリースでは、transifexと翻訳を同期させ、GeoIPデータベースを更新します。</p>
+<p>例によって、このリリースに更新することをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
+</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="2.2.0 新リリース。DDOS攻撃への緩和策と、ストリーミングサブシステムへの微調整" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>DDOS攻撃への緩和策と、ストリーミングサブシステムへの微調整</summary></details><p>我々は2.2.0のリリース日を、2023年3月13日の本日に行い、前倒しにする方針を決定しました。
+このリリースはDDOS攻撃を切り抜けるためのルーターの能力を改善するNetDb、Floodfill、及びピア選択の構成要素に渡る変更が含みます。
+今後も攻撃は続くと思われますが、これらのシステムへの改善により、ルーターが悪意があると思われるルーターを特定し、優先順位を下げることで、DDOS攻撃の危険を軽減する助けになるでしょう。</p>
+<p>このリリースでは、ストリーミングサブシステムに再生保護が追加され、暗号化パケットを捕らえられる攻撃者が、意図しない受信者にパケットを送信して再利用できるようになることを防ぎます。
+
+これは後方互換性のある変更であるため、古いルーターでも新しいルーターのストリーミング機能を使用することが可能です。
+この問題は、I2P開発チームが内部で発見し修正したもので、DDOS攻撃とは関係ありません。
+また、現時点で再生したストリーミングパケットに遭遇したことはなく、I2Pネットワークに対してストリーミング再生攻撃が行われたことはないと考えています。</p>
+<p>お気づきかもしれませんが、このリリースノートとリリースそのものは、zzzではなくidkが署名しています。
+zzzはプロジェクトから離れることを選択し、彼の使命はチームの他の一員によって担われています。
+そのため、プロジェクトはネットワーク統計の基盤を交換し、開発フォーラムをi2pforum.i2pに移行する作業を行っています。
+長い間、これらのサービスを提供してくれたzzzに感謝します。</p>
+<p>例によって、このリリースに更新することをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
+</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
+Our investigations and mitigations continue.</p>
+<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
+We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
+However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
+The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
+<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
+We ask for your patience as we work to improve I2P.</p>
+</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
+  The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
+  Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
+  Mitigation strategies are being investigated and implemented gradually.</p>
+<p>While the attack has degraded performance, the network remains intact and usable.
+  Java I2P routers appear to be handling the issues better than i2pd routers for now.
+  Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
+</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 リリース" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 非常に多いSSU2の修正</summary></details><p>我々は11月中にあった2.0.0のリリースから、幾つかの事を学びました。
+ルーターがこのリリースに更新されたことで、ネットワークでは、私たちの新しいSSU2トランスポートプロトコルが、約1％から60％以上になりました。
+まず、SSU2が堅牢であり、良き設計であり、安全なプロトコルであることを確認しました。
+しかし、2つ目は、プロトコルの実装において、細かいバグや稀に発生するバグを多数発見し、修正したことです。
+これらのバグの影響が累積して、ネットワークの性能が低下しています。</p>
+<p>また、Bitcoinの新しいI2Pトランジェントアドレス機能によって引き起こされた可能性がある、
+ネットワークにおけるトンネル数の増加や、トンネル構築の成功率の低下も確認されていますが、
+私たちのSSU2バグと他の輻輳制御の問題によって悪化しています。
+我々は、Bitcoinや他の非Bitcoinプロジェクトと協力して、I2Pネットワーク需要を減らしています。
+私たちは、輻輳時のネットワーク負荷を軽減するために、アルゴリズムを改善しました。
+また、i2pdと協力し、共通の輻輳制御戦略を開発しています。</p>
+<p>そのため、今回のリリースは6週間ほど前倒しにして、皆様に修正をお届けすることにしました。
+i2pdは先週、バージョン2.45.0をリリースしましたが、初期の成果は妙妙たるものです。
+新しいプロトコルと分散型ネットワークは、開発するには困難です。
+輻輳は、ほとんど前触れもなく、原因の手掛かりもわからないままやってくるものです。
+診断の結果、問題が解決されればよいのですが、ご迷惑をおかけしました。</p>
+<p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
+</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 リリース" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 トランスポート有効</summary></details><p>I2Pは小さな機能、試験及び非常に多いバグ修正の達成後に2.0.0をリリースし、全ユーザーに新しいUDPトランスポートのSSU2を有効にします。</p>
 <p>我々はまた、インストーラー、ネットワークデータベース、非公開アドレス帳への追加、Windowsブラウザランチャー、及びIPv6 UPnPを含めた修正を成し遂げました。</p>
 <p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
 </article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="最近のブログ投稿" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>幾つかの最近のブログ投稿</summary></details><p>我々のウェブサイト上の幾つかの最近のブログ投稿へのリンク:</p>
@@ -14,8 +171,7 @@
 我々は、AndroidとARMの装置、および無作為に他のルーターのごく一部で、初期設定でこれを有効にしています。
 これにより、今後3ヶ月でより多くの試験を行い、接続の移行機能を完成させ、残っている問題を修正することができます。
 11月に予定されている次のリリースでは、全員がこの機能を利用できるようにする予定です。
-手動での設定は必要ありません。
-</p>
+手動での設定は必要ありません。</p>
 <p>もちろん、このリリースには通常のバグ修正も含まれています。
 また、自動停頓検出機能を追加し、すでに稀な停頓を発見し、現在では修正されています。</p>
 <p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
@@ -63,11 +219,11 @@ SSU2は、パフォーマンスとセキュリティを大幅に改善させる
 間もなくi2pdとの共同検査を開始し、今年後半にはネットワークに展開する予定です。</p>
 <p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
 </article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 リリース" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 新トンネルの構築メッセージを有効化</summary></details><p>今回のリリースでは、2021年に開発された2つのメジャーなプロトコルアップデートの展開が完了しました。
-ルーターのX25519暗号化への移行が加速され、年内にほぼすべてのルーターが再キーされる見込みです。
+ルーターのX25519暗号化への移行が加速され、年内にほぼすべてのルーターが鍵交換される見込みです。
 短いトンネル構築メッセージが有効になり、大幅な帯域幅の削減が可能になりました。</p>
 <p>新規インストールウィザードにテーマ選択パネルを追加しました。
 SSUのパフォーマンスを改善し、SSUのピアテストメッセージに関する問題を修正しました。
-トンネル構築のBloomフィルタを調整し、メモリ使用量を削減しました。
+トンネル構築のBloomフィルターを調整し、メモリ使用量を削減しました。
 Java以外のプラグインのサポートを強化しました。</p>
 <p>その他のニュースとしては、新しいUDP transport SSU2の設計が順調に進んでおり、来年初めには実装を開始できる見込みです。</p>
 <p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
@@ -88,7 +244,7 @@ MuWireのデスクトップアプリケーションを使用している場合
 MuWireプラグインを使用している場合は、直ちに<a href="/configplugins">バージョン0.8.7-b1にアップデートしてください</a>。</p>
 <p>脆弱性の詳細および最新のセキュリティ推奨事項に関する更新については
 <a href="http://muwire.i2p/security.html">muwire.i2p</a>をご覧ください。</p>
-</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 リリース" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 IPv6の修正</summary></details><p>0.9.50では、ルーターの暗号化鍵をECIES-X25519に移行しました。
+</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 リリース" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 IPv6の修正</summary></details><p>0.9.50では、ルーターの暗号鍵をECIES-X25519に移行しました。
 受動的なDNS詮索からユーザーを保護するため、再シードにDNS over HTTPSを有効にしました。
 新しいUPnPのサポートを含む、IPv6アドレスに多数の修正と改善が行われています。</p>
 <p>長年にわたり発生していたSusiMailの破損バグをようやく修正しました。
@@ -105,10 +261,10 @@ SSU (UDP) トランスポートに関するいくつかの改善と修正によ
 そして、完成に近づいています！移行が完了するまでには、数回のリリースが必要です。</p>
 <p>今回のリリースでは、混乱を最小限に抑えるため、新規インストールと既存のインストールのごく一部のみが新しい暗号化を使用します。
 (再起動時にランダムに選択) は新しい暗号化を使用します。
-ルーターが新しい暗号を使用するために「再キー」した場合、再起動後数日間は通常よりもトラフィックや信頼性が低下することがあります。
+ルーターが新しい暗号を使用するために「鍵交換」した場合、再起動後数日間は通常よりもトラフィックや信頼性が低下することがあります。
 これは、 ルーターが新しいアイデンティティを生成したためで、正常な動作です。
 しばらくすると、パフォーマンスが回復するはずです。</p>
-<p>過去に2回、デフォルトの署名の種類を変更する際に、ネットワークを「再キー」したことがあります。
+<p>過去に2回、デフォルトの署名の種類を変更する際に、ネットワークを「鍵交換」したことがあります。
 今回は初めてデフォルトの暗号化タイプを変更しました。
 うまくいけばスムーズにいくのですが、念のためゆっくり始めています。</p>
 <p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
@@ -275,7 +431,7 @@ Java 9向けの予備的修正を行いました。ただしまだ Java 9 の通
 Androidアプリへの影響はありません。</p>
 <p>CSRF保護の不足のため、ユーザがI2P-Bote起動中にJavaScript有効のブラウザ上で悪意のあるサイトを読み込むと、
 敵対者がI2P-Bote上で当該ユーザとしてメッセージ送信などのアクションを発火できてしまっていました。
-I2P-Boteアドレスの秘密キーの抽出もできていた可能性がありますが、これについての実証は行われていません。</p>
+I2P-Boteアドレスの秘密鍵の抽出もできていた可能性がありますが、これについての実証は行われていません。</p>
 <p>全I2P-Boteユーザは12月半ばにリリースされた I2P 0.9.28 以降、初回のルーター再起動で自動更新されるでしょう。
 しかし移行期にI2P・I2P-Bote を使用するつもりならば、安全のために、<a href="http://bote.i2p/install/">インストールページの指示に従い</a>、手動でアップグレードすることを推奨します。
 また、あなたが日ごろI2P-Bote起動中にJavaScript有効でサイトを閲覧している場合、新たな I2P-Boteアドレスの生成を検討すべきです。</p>
@@ -314,26 +470,26 @@ Str4d は <a href="http://www.realworldcrypto.com/rwc2016/program">Real World Cr
 </article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="0.9.23 リリース" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>0.9.23 様々なバグ修正、I2PSnarkの細かな改善</summary></details><p>こんにちはI2P！ zzzがこれまで49のリリースに署名してきましたが、これは初めて私（str4d）が署名したリリースです。
 これは人員を含めたあらゆる事柄に関する冗長性の重要なテストです。</p>
 <p><b>保全作業</b></p>
-<p>私の署名キーは2年以上（0.9.9以降）にわたってルーターアップデート内にあります。
+<p>私の署名鍵は2年以上（0.9.9以降）にわたってルーターアップデート内にあります。
 ですから、最近のバージョンのI2Pを使用中なら、このアップデートは他の更新と変わらず簡単に済みます。
 しかし、0.9.9よりも古いバージョンを動かしている場合、まず手動で最近のものにアップデートする必要があります。
 最近のバージョン向けのアップデートファイルは <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/releases/">こちら</a> でダウンロードでき、手動でのアップデート方法の説明は <a href="http://i2p-projekt.i2p/en/download#update">こちら</a> で閲覧できます。
 手動アップデートが終われば、ルーターが 0.9.23 のアップデートを通常通り探し出しダウンロードします。</p>
-<p>パッケージマネージャ経由でI2Pをインストールしている場合はこの変更の影響を受けません。いつも通りアップデートできます。</p>
-<p><b>アップデート詳細</b></p>
-<p>RouterInfoを 強固な新署名 Ed25519 に移行することはうまくいっており、少なくともネットワークの半分はキーが再発行されたと既に見られています。
-このリリースはそのキー再発行プロセスを加速するものです。
+<p>パッケージマネージャ経由でI2Pをインストールしている場合はこの変更の影響を受けません。いつも通り更新できます。</p>
+<p><b>更新詳細</b></p>
+<p>ルーター情報を強固な新署名 Ed25519 に移行することはうまくいっており、少なくともネットワークの半分は鍵交換されたと既に見られています。
+このリリースはその鍵交換過程を加速するものです。
 ネットワークチャーンを減らすため、各々の再起動時でEd25519に変換する確率は少なくなります。
-キー再発行の際、新しいアイデンティティでネットワークに再統合される何日かの間、使用帯域幅は少なくなるでしょう。</p>
+鍵交換の際、新しいアイデンティティでネットワークに再統合される何日かの間、使用帯域幅は少なくなるでしょう。</p>
 <p>これが Java 6 をサポートする最後のリリースであることに注意してください。
 Java 7 または 8 にできるだけ早く更新してください。
 来たる Java 9 とI2Pを互換にすべく作業を既に行っており、一部の作業はこのリリースに含まれています。</p>
 <p>また、I2PSnarkの細かな改善を行い、またルーターコンソールに過去のニュース項目閲覧のための新ページを追加しました。</p>
 <p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>
-</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="0.9.22がリリースされました" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 バグ修正とEd25519への移行を開始</summary></details><p>0.9.22 では、I2PSnark が完了前に固まることに対する修正を行いました。また RouterInfoを 強固な新署名 Ed25519 に移行し始めました。
-ネットワークチャーンを減らすため、各々の再起動時でEd25519に変換する確率は少なくなります。
-キー再発行の際、新しいアイデンティティでネットワークに再統合される何日かの間、使用帯域幅は少なくなるでしょう。
-全てがうまくいけば、キー再発行プロセスを次回のリリースで加速できるでしょう。</p>
+</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="0.9.22がリリースされました" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 バグ修正とEd25519への移行を開始</summary></details><p>0.9.22 では、I2PSnark が完了前に固まることに対する修正を行いました。また ルーター情報を強固な新署名 Ed25519 に移行し始めました。
+ネットワークチャーンを減らすため、あなたのルーターが各々の再起動時でEd25519に変換する確率は少なくなります。
+鍵交換の際、新しいアイデンティティでネットワークに再統合される何日かの間、使用帯域幅は少なくなるでしょう。
+全てがうまくいけば、鍵交換過程を次回のリリースで加速できるでしょう。</p>
 <p>I2PCon Toronto は大成功でした！
 プレゼンテーションと動画の全ては <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">I2PConページ</a> に一覧されています。</p>
 <p>例によって、このリリースにアップグレードすることをおすすめします。セキュリティを保ち、ネットワークに貢献する最高の方法は最新のリリースを動作させることです。</p>

data/translations/entries.ko.html

@@ -1,5 +1,174 @@
 <div>
-<header title="I2P 뉴스">뉴스 및 라우터 업데이트 사항</header><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
+<header title="I2P 뉴스">뉴스 및 라우터 업데이트 사항</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
+The bug primarily affected high-bandwidth routers.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
+We have added notification bubbles to several applications in the console to highlight application messages.
+We fixed a tunnel test bug that may have been affecting tunnel reliability.
+The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
+There are several dark theme fixes and improvements.</p>
+<p>We fixed the installer that previously failed on Java 21 or higher.
+We also fixed installing to directory paths that contain spaces on Linux.
+For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
+The workaround is using localhost and the server port, usually 7658, to bypass I2P.
+For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
+We apologize for the issue and are working on a fix.</p>
+</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
+<p>We have improved handling of congested routers in the network.
+Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
+We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
+Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
+<p>Access to information from the console and applications has been improved.
+Issues have been fixed in I2PSnark and SusiMail search.
+The netDB search embedded into the router console now operates in a more intuitive and useful way.
+Minor improvements have been made to diagnostic displays in advanced mode.</p>
+<p>Bugs have also been fixed to improve compatibility within the network.
+An issue with publishing leaseSets was solved which improves reliability major hidden services.
+I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
+This prevents torrents from being unnecessarily disrupted by these changes.
+We welcomed this contribution from a new contributor.
+A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
+This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
+<p>Newer routers will be favored when selecting floodfill routers.
+I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
+Legacy transport protocols are being removed, simplifying the code in the UDP transports.
+Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
+Additional tweaks were made to peer selection strategies.</p>
+<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
+We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
+If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
+Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
+With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
+This should help the network return to normal operation.
+Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
+Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
+This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
+Reachability of I2P sites is badly degraded.</p>
+<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
+Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
+</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
+<p>New features have been added to I2PSnark like the ability to search through torrents.
+Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
+We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
+New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
+Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
+<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
+This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
+This investigation uncovered one minor isolation-piercing event which we repaired.
+This issue was discovered and fixed internally by the I2P team.</p>
+<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
+This should result in improved delivery and availability for these downstream products.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
+It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
+<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
+This will help the network limit the effect of tunnel spam.
+It will also help the network heal during and after DDOS attacks.</p>
+<p>The NetDb changes also help secure individual routers and the applications that use them. 
+Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
+This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
+<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
+CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
+An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
+The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
+The attacker then sends the same message directly to the router.
+The router passes the message to the bloom filter, and is dropped.
+This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
+This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
+Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
+Users of Java I2P are recommended to update immediately to avoid the attack.</p>
+<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
+This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
+<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
+<p>This release also contains a tweakable blocklist.
+Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
+Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
+This feature is off-by-default and is only recommended for advanced users at this time.</p>
+<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
+It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
+This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
+Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
+This issue has also been resolved.
+The docker container is now also compatible with Podman.</p>
+<p>This release syncs translations with transifex and updates the GeoIP database.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
+This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
+The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
+<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
+This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
+This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
+We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
+<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
+zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
+As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
+We thank zzz for providing these services for such a long time.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
+Our investigations and mitigations continue.</p>
+<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
+We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
+However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
+The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
+<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
+We ask for your patience as we work to improve I2P.</p>
+</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
+  The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
+  Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
+  Mitigation strategies are being investigated and implemented gradually.</p>
+<p>While the attack has degraded performance, the network remains intact and usable.
+  Java I2P routers appear to be handling the issues better than i2pd routers for now.
+  Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
+</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
+As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
+First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
+Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
+Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
+<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
+possibly triggered by Bitcoin's new I2P transient address feature,
+but made worse by our SSU2 bugs and other congestion control problems.
+We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
+We have improved our algorithms to reduce network load during times of congestion.
+We are also collaborating with i2pd to develop common congestion control strategies.</p>
+<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
+i2pd released their version 2.45.0 last week and the early results are encouraging.
+New protocols, and distributed networks, are difficult to develop.
+Congestion can arrive with little warning and with little clue of the cause.
+Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
+<p>평소와 같이, 이 릴리즈로 업데이트하는 것을 권장합니다. 보안을 유지하고
+네트워크를 돕기 위한 가장 좋은 것은 최신 릴리즈를 사용하는 것입니다.</p>
+</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
 <p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
 <p>평소와 같이, 이 릴리즈로 업데이트하는 것을 권장합니다. 보안을 유지하고
 네트워크를 돕기 위한 가장 좋은 것은 최신 릴리즈를 사용하는 것입니다.</p>

data/translations/entries.nb.html

@@ -1,5 +1,174 @@
 <div>
-<header title="I2P-nyheter">Nyhetsstrøm og ruteroppdateringer</header><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
+<header title="I2P-nyheter">Nyhetsstrøm og ruteroppdateringer</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
+The bug primarily affected high-bandwidth routers.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
+We have added notification bubbles to several applications in the console to highlight application messages.
+We fixed a tunnel test bug that may have been affecting tunnel reliability.
+The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
+There are several dark theme fixes and improvements.</p>
+<p>We fixed the installer that previously failed on Java 21 or higher.
+We also fixed installing to directory paths that contain spaces on Linux.
+For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
+The workaround is using localhost and the server port, usually 7658, to bypass I2P.
+For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
+We apologize for the issue and are working on a fix.</p>
+</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
+<p>We have improved handling of congested routers in the network.
+Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
+We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
+Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
+<p>Access to information from the console and applications has been improved.
+Issues have been fixed in I2PSnark and SusiMail search.
+The netDB search embedded into the router console now operates in a more intuitive and useful way.
+Minor improvements have been made to diagnostic displays in advanced mode.</p>
+<p>Bugs have also been fixed to improve compatibility within the network.
+An issue with publishing leaseSets was solved which improves reliability major hidden services.
+I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
+This prevents torrents from being unnecessarily disrupted by these changes.
+We welcomed this contribution from a new contributor.
+A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
+This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
+<p>Newer routers will be favored when selecting floodfill routers.
+I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
+Legacy transport protocols are being removed, simplifying the code in the UDP transports.
+Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
+Additional tweaks were made to peer selection strategies.</p>
+<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
+We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
+If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
+Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
+With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
+This should help the network return to normal operation.
+Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
+Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
+This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
+Reachability of I2P sites is badly degraded.</p>
+<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
+Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
+</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
+<p>New features have been added to I2PSnark like the ability to search through torrents.
+Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
+We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
+New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
+Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
+<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
+This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
+This investigation uncovered one minor isolation-piercing event which we repaired.
+This issue was discovered and fixed internally by the I2P team.</p>
+<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
+This should result in improved delivery and availability for these downstream products.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
+It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
+<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
+This will help the network limit the effect of tunnel spam.
+It will also help the network heal during and after DDOS attacks.</p>
+<p>The NetDb changes also help secure individual routers and the applications that use them. 
+Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
+This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
+<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
+CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
+An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
+The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
+The attacker then sends the same message directly to the router.
+The router passes the message to the bloom filter, and is dropped.
+This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
+This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
+Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
+Users of Java I2P are recommended to update immediately to avoid the attack.</p>
+<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
+This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
+<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
+<p>This release also contains a tweakable blocklist.
+Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
+Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
+This feature is off-by-default and is only recommended for advanced users at this time.</p>
+<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
+It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
+This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
+Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
+This issue has also been resolved.
+The docker container is now also compatible with Podman.</p>
+<p>This release syncs translations with transifex and updates the GeoIP database.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
+This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
+The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
+<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
+This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
+This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
+We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
+<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
+zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
+As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
+We thank zzz for providing these services for such a long time.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
+Our investigations and mitigations continue.</p>
+<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
+We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
+However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
+The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
+<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
+We ask for your patience as we work to improve I2P.</p>
+</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
+  The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
+  Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
+  Mitigation strategies are being investigated and implemented gradually.</p>
+<p>While the attack has degraded performance, the network remains intact and usable.
+  Java I2P routers appear to be handling the issues better than i2pd routers for now.
+  Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
+</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
+As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
+First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
+Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
+Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
+<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
+possibly triggered by Bitcoin's new I2P transient address feature,
+but made worse by our SSU2 bugs and other congestion control problems.
+We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
+We have improved our algorithms to reduce network load during times of congestion.
+We are also collaborating with i2pd to develop common congestion control strategies.</p>
+<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
+i2pd released their version 2.45.0 last week and the early results are encouraging.
+New protocols, and distributed networks, are difficult to develop.
+Congestion can arrive with little warning and with little clue of the cause.
+Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
+<p>Som vanlig, anbefales det at du oppdaterer til denne utgaven. Den beste måten
+å ta hånd om sikkerheten og å hjelpe nettverket ved å kjøre siste utgave.</p>
+</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
 <p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
 <p>Som vanlig, anbefales det at du oppdaterer til denne utgaven. Den beste måten
 å ta hånd om sikkerheten og å hjelpe nettverket ved å kjøre siste utgave.</p>

data/translations/entries.nl.html

@@ -1,5 +1,173 @@
 <div>
-<header title="I2P-nieuws">Nieuwsoverzicht en routerupdates</header><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
+<header title="I2P-nieuws">Nieuwsoverzicht en routerupdates</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
+The bug primarily affected high-bandwidth routers.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
+We have added notification bubbles to several applications in the console to highlight application messages.
+We fixed a tunnel test bug that may have been affecting tunnel reliability.
+The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
+There are several dark theme fixes and improvements.</p>
+<p>We fixed the installer that previously failed on Java 21 or higher.
+We also fixed installing to directory paths that contain spaces on Linux.
+For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
+The workaround is using localhost and the server port, usually 7658, to bypass I2P.
+For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
+We apologize for the issue and are working on a fix.</p>
+</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
+<p>We have improved handling of congested routers in the network.
+Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
+We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
+Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
+<p>Access to information from the console and applications has been improved.
+Issues have been fixed in I2PSnark and SusiMail search.
+The netDB search embedded into the router console now operates in a more intuitive and useful way.
+Minor improvements have been made to diagnostic displays in advanced mode.</p>
+<p>Bugs have also been fixed to improve compatibility within the network.
+An issue with publishing leaseSets was solved which improves reliability major hidden services.
+I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
+This prevents torrents from being unnecessarily disrupted by these changes.
+We welcomed this contribution from a new contributor.
+A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
+This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
+<p>Newer routers will be favored when selecting floodfill routers.
+I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
+Legacy transport protocols are being removed, simplifying the code in the UDP transports.
+Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
+Additional tweaks were made to peer selection strategies.</p>
+<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
+We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
+If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
+Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
+With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
+This should help the network return to normal operation.
+Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
+Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
+This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
+Reachability of I2P sites is badly degraded.</p>
+<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
+Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
+</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
+<p>New features have been added to I2PSnark like the ability to search through torrents.
+Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
+We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
+New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
+Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
+<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
+This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
+This investigation uncovered one minor isolation-piercing event which we repaired.
+This issue was discovered and fixed internally by the I2P team.</p>
+<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
+This should result in improved delivery and availability for these downstream products.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
+It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
+<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
+This will help the network limit the effect of tunnel spam.
+It will also help the network heal during and after DDOS attacks.</p>
+<p>The NetDb changes also help secure individual routers and the applications that use them. 
+Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
+This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
+<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
+CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
+An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
+The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
+The attacker then sends the same message directly to the router.
+The router passes the message to the bloom filter, and is dropped.
+This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
+This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
+Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
+Users of Java I2P are recommended to update immediately to avoid the attack.</p>
+<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
+This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
+<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
+<p>This release also contains a tweakable blocklist.
+Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
+Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
+This feature is off-by-default and is only recommended for advanced users at this time.</p>
+<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
+It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
+This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
+Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
+This issue has also been resolved.
+The docker container is now also compatible with Podman.</p>
+<p>This release syncs translations with transifex and updates the GeoIP database.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
+This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
+The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
+<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
+This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
+This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
+We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
+<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
+zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
+As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
+We thank zzz for providing these services for such a long time.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
+Our investigations and mitigations continue.</p>
+<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
+We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
+However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
+The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
+<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
+We ask for your patience as we work to improve I2P.</p>
+</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
+  The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
+  Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
+  Mitigation strategies are being investigated and implemented gradually.</p>
+<p>While the attack has degraded performance, the network remains intact and usable.
+  Java I2P routers appear to be handling the issues better than i2pd routers for now.
+  Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
+</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
+As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
+First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
+Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
+Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
+<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
+possibly triggered by Bitcoin's new I2P transient address feature,
+but made worse by our SSU2 bugs and other congestion control problems.
+We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
+We have improved our algorithms to reduce network load during times of congestion.
+We are also collaborating with i2pd to develop common congestion control strategies.</p>
+<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
+i2pd released their version 2.45.0 last week and the early results are encouraging.
+New protocols, and distributed networks, are difficult to develop.
+Congestion can arrive with little warning and with little clue of the cause.
+Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
+<p>Zoals gewoonlijk raden we aan om bij te werken naar deze uitgave. De beste manier om veiligheid te onderhouden en het netwerk te helpen is om de laatste uitgave te gebruiken.</p>
+</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
 <p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
 <p>Zoals gewoonlijk raden we aan om bij te werken naar deze uitgave. De beste manier om veiligheid te onderhouden en het netwerk te helpen is om de laatste uitgave te gebruiken.</p>
 </article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Recente Blog berichten" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>

data/translations/entries.pl.html

@@ -1,5 +1,159 @@
 <div>
-<header title="Wiadomości I2P">Kanał wiadomości i aktualizacji węzła</header><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
+<header title="Wiadomości I2P">Kanał wiadomości i aktualizacji węzła</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
+The bug primarily affected high-bandwidth routers.</p>
+<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
+</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
+We have added notification bubbles to several applications in the console to highlight application messages.
+We fixed a tunnel test bug that may have been affecting tunnel reliability.
+The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
+There are several dark theme fixes and improvements.</p>
+<p>We fixed the installer that previously failed on Java 21 or higher.
+We also fixed installing to directory paths that contain spaces on Linux.
+For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
+<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
+</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
+The workaround is using localhost and the server port, usually 7658, to bypass I2P.
+For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
+We apologize for the issue and are working on a fix.</p>
+</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
+<p>We have improved handling of congested routers in the network.
+Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
+We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
+Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
+<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
+</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
+<p>Access to information from the console and applications has been improved.
+Issues have been fixed in I2PSnark and SusiMail search.
+The netDB search embedded into the router console now operates in a more intuitive and useful way.
+Minor improvements have been made to diagnostic displays in advanced mode.</p>
+<p>Bugs have also been fixed to improve compatibility within the network.
+An issue with publishing leaseSets was solved which improves reliability major hidden services.
+I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
+This prevents torrents from being unnecessarily disrupted by these changes.
+We welcomed this contribution from a new contributor.
+A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
+<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
+</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="Wydano wersję 2.6.1" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1</summary></details><p>Wersja 2.6.1 została wydana w celu naprawy błędu interfejsu użytkownika panelu „Zarządzanie ukrytymi usługami”. Błąd ten uniemożliwiał przewijanie, przez co niektóre konfiguracje mogły być niedostępne.</p>
+<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
+</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
+<p>Newer routers will be favored when selecting floodfill routers.
+I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
+Legacy transport protocols are being removed, simplifying the code in the UDP transports.
+Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
+Additional tweaks were made to peer selection strategies.</p>
+<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
+We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
+If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
+Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
+<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
+</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
+<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
+</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
+With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
+This should help the network return to normal operation.
+Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
+Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
+<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
+</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
+This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
+Reachability of I2P sites is badly degraded.</p>
+<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
+Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
+</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
+<p>New features have been added to I2PSnark like the ability to search through torrents.
+Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
+We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
+New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
+Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
+<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
+This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
+This investigation uncovered one minor isolation-piercing event which we repaired.
+This issue was discovered and fixed internally by the I2P team.</p>
+<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
+This should result in improved delivery and availability for these downstream products.</p>
+<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
+</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
+It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
+<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
+This will help the network limit the effect of tunnel spam.
+It will also help the network heal during and after DDOS attacks.</p>
+<p>The NetDb changes also help secure individual routers and the applications that use them. 
+Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
+This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
+<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
+<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
+</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
+CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
+An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
+The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
+The attacker then sends the same message directly to the router.
+The router passes the message to the bloom filter, and is dropped.
+This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
+This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
+Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
+Users of Java I2P are recommended to update immediately to avoid the attack.</p>
+<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
+This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
+<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
+<p>This release also contains a tweakable blocklist.
+Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
+Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
+This feature is off-by-default and is only recommended for advanced users at this time.</p>
+<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
+It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
+<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
+</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
+This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
+Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
+This issue has also been resolved.
+The docker container is now also compatible with Podman.</p>
+<p>This release syncs translations with transifex and updates the GeoIP database.</p>
+<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
+</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
+This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
+The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
+<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
+This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
+This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
+We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
+<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
+zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
+As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
+We thank zzz for providing these services for such a long time.</p>
+<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
+</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
+Our investigations and mitigations continue.</p>
+<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
+We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
+However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
+The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
+<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
+We ask for your patience as we work to improve I2P.</p>
+</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
+  The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
+  Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
+  Mitigation strategies are being investigated and implemented gradually.</p>
+<p>While the attack has degraded performance, the network remains intact and usable.
+  Java I2P routers appear to be handling the issues better than i2pd routers for now.
+  Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
+</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
+As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
+First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
+Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
+Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
+<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
+possibly triggered by Bitcoin's new I2P transient address feature,
+but made worse by our SSU2 bugs and other congestion control problems.
+We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
+We have improved our algorithms to reduce network load during times of congestion.
+We are also collaborating with i2pd to develop common congestion control strategies.</p>
+<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
+i2pd released their version 2.45.0 last week and the early results are encouraging.
+New protocols, and distributed networks, are difficult to develop.
+Congestion can arrive with little warning and with little clue of the cause.
+Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
+<p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
+</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
 <p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
 <p>Jak zwykle, zalecamy aktualizację programu do niniejszej wersji. Nie musimy dodawać, że służy to zachowaniu bezpieczeństwa sieci oraz jej uczestników.</p>
 </article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Najnowsze posty na blogu" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>

data/translations/entries.pt.html

@@ -1,83 +1,234 @@
 <div>
-<header title="I2P - Notícias">Feed de notícias, e atualizações de "router"</header><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
-<p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
+<header title="I2P - Notícias">Feed de notícias, e atualizações de "router"</header><article id="urn:uuid:f2a6aabd-ee29-4f45-a8dd-7378e907016a" title="Versão 2.9.0 Lançada" href="http://i2p-projekt.i2p/en/blog/post/2025/06/02/2.9.0_released" author="idk" published="2025-06-02T19:00:00Z" updated="2025-06-02T19:00:00Z"><details><summary>Versão 2.9.0 da I2P</summary></details><p>A versão 2.9.0 da I2P é uma versão de manutenção que inclui correções de bugs e trabalho em novas funcionalidades.</p>
+<p>O uso de thread foi aprimorado para melhorar o desempenho do sistema i2ptunnel.
+O NTCP2 foi aprimorado para resistir a ataques de probing.
+O sistema de notificação foi integrado em mais aplicações para oferecer melhor feedback aos usuários do I2PSnark e das outras aplicações.
+A participação automática em floodfill foi corrigida.
+Os usuários podem observar uso de recursos mais elevado quando atuando como floodfill.
+Se isso não é desejado, o modo floodfill pode ser desabilitado na página /config.</p>
+<p>Uma nova funcionalidade de mapa global está disponível no console que mostra as localizações dos roteadores na sua visão do BD de rede.
+Eles são os pares que ajudam o seu roteador a construir túneis e oferecer serviços anonimamente.</p>
+<p>O trabalho continua em implementar gerenciamento de banda automático para túneis, o protocolo Datagram2 e criptografia pós-quântica.
+Em dois lançamentos, na versão 2.11.0, a I2P irá requerer Java 17.</p>
+<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
+</article><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="Versão 2.8.2 Lançada" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>Versão 2.8.2 da I2P</summary></details><p>A versão 2.8.2 corrige um bug que causa falhas de SHA256 que foi introduzido na versão 2.8.1.
+O bug afetou principalmente roteadores de alta largura de banda.</p>
+<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
+</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="Versão 2.8.1 da I2P Lançada" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>Versão 2.8.1 da I2P</summary></details><p>A versão 2.8.1 conserta acessos a sites locais que estavam quebrados na 2.8.0.
+Adicionamos bolhas de notificação em várias aplicações no painel para destacar mensagens da aplicação.
+Corrigimos um bug de teste de túnel que pode ter estado afetando a estabilidade de túnel.
+O catálogo de endereços agora possui uma nova aba "mais recente" que exibe os mais novos nomes de domínio adicionados de suas inscrições.
+Há várias correções e melhorias para tema escuro.</p>
+<p>Corrigimos o instalador que previamente falhava no Java 21 ou mais recente.
+Também corrigimos instalar em caminhos de diretórios que contêm espaços em Linux.
+Para aqueles de vocês que usam Docker, nós atualizamos bibliotecas e contêiner desatualizados do Docker.</p>
+<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
+</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Acesso a site local falha na 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>Bug de Acesso Local da 2.8.0</summary></details><p>Na 2.8.0, navegar para um site local (seja por nome de domínio ou b32) falhará.
+A solução paliativa é usar localhost e a porta do servidor, geralmente 7658, para contornar a I2P.
+Por exemplo, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
+Pedimos desculpas pelo problema e estamos trabalhando em uma correção.</p>
+</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="Versão 2.8.0 da I2P" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>Versão 2.8.0 da I2P</summary></details><p>Esta versão melhora a I2P corrigindo bugs, removendo código inutilizado e melhorando a estabilidade de rede.</p>
+<p>Aprimoramos o tratamento de roteadores congestionados na rede.
+Problemas com UPnP e NAT traversal foram tratados para aprimorar a conectividade e o relatório de erros.
+Nós agora temos uma estratégia mais agressiva para a remoção de leasesets do BD de rede para melhorar o desempenho do roteador e mitigar sobrecargas.
+Outras mudanças foram implantadas para reduzir a observabilidade de eventos como um roteador reiniciando ou desligando.</p>
+<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
+</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="Lançamento I2P 2.7.0" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>Lançamento I2P 2.7.0</summary></details><p>Esta versão, I2P 2.7.0, continua nosso trabalho corrigindo bugs, melhorando o desempenho e adicionando recursos.</p>
+<p>O acesso às informações do console e dos aplicativos foi aprimorado. Foram corrigidos problemas na pesquisa do I2PSnark e do SusiMail. A pesquisa netDB incorporada no console do roteador agora opera de maneira mais intuitiva e útil. Pequenas melhorias foram feitas nas telas de diagnóstico no modo avançado.</p>
+<p>Bugs também foram corrigidos para melhorar a compatibilidade dentro da rede. Um problema com a publicação de leaseSets foi resolvido, o que melhora a confiabilidade dos principais serviços ocultos. O I2PSnark não altera mais o infohash quando um usuário altera apenas os rastreadores em um torrent existente. Isso evita que os torrents sejam desnecessariamente interrompidos por essas mudanças. Congratulamo-nos com esta contribuição de um novo colaborador. Um conflito no tratamento de uma opção de biblioteca de streaming foi resolvido para melhorar a compatibilidade com outras implementações I2P.</p>
+<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
+</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="Versão 2.6.1 do I2P lançada" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>Versão 2.6.0 do I2P</summary></details><p>O I2P 2.6.1 é lançado para corrigir um erro na interface de utilizador da aplicação Gestor de serviços ocultos.
+Este erro fazia com que o scrolling fosse desativado, tornando inacessível alguma configuração.</p>
+<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
+</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="Versão 2.6.0 do I2P lançada" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>Versão 2.6.0 do I2P</summary></details><p>Esta versão, I2P 2.6.0, dá continuidade ao nosso trabalho de corrigir erros, adicionar funcionalidades, e aprimorar a confiabilidade da rede.</p>
+<p>Os roteadores mais novos serão favorecidos na seleção de roteadores de floodfill.
+O I2PSnark recebeu recursos que melhoram o desempenho do PeX (Peer Exchange), além de correções de erros.
+Os protocolos de transporte legados estão a ser removidos, simplificando o código nos transportes UDP.
+O destino hospedado localmente será acessível por clientes locais sem solicitar seu LeaseSet, melhorando o desempenho e a testabilidade.
+Foram feitos ajustes adicionais às estratégias de seleção de pares.</p>
+<p>O I2P não permite mais I2P-sobre-Tor, conexões de endereços IP de saída do Tor estão agora bloqueadas.
+Desencorajamos isso porque degrada o desempenho do I2P e usa os recursos das saídas do Tor sem nenhum benefício.
+Se for uma pessoa útil executando tanto uma saída Tor quanto o I2P, encorajamo-lo a continuar a fazer isso, usando endereços IP diferentes para cada um.
+Roteadores que não sejam de saída e clientes Tor não são afetados por isso e não precisam mudar nada.</p>
+<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
+</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="Versão 2.5.2 do I2P lançada" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 com correção de HTTP</summary></details><p>O I2P 2.5.2 foi lançado para corrigir um erro introduzido na versão 2.5.0 que causava o truncamento de alguns conteúdos HTTP.</p>
+<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
+</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="Versão 2.5.1 da I2P Lançada" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>Versão 2.5.1 da I2P lançada para tratar dos Ataques de Negação de Serviço</summary></details><p>A I2P 2.5.1 é lançada para tratar dos Ataques de Negação de Serviço afetando a rede e os serviços I2P.
+Com este lançamento nós desabilitamos as partes baseadas em IP da ferramenta de detecção de ataque Sybil que foram alvo para amplificar o efeito e a duração do ataque.
+Isso deve ajudar a rede a retornar a operação normal.
+Aqueles de vocês que desabilitaram a ferramenta de detecção de ataque Sybil podem reabilitá-la com segurança.
+Ajustes a outros subsistemas para aprimorar a validação de RouterInfo e seleção de par também foram realizados.</p>
+<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
+</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Tempo tempestuoso" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Clima da rede: tempestuoso. O I2P está sob ataque.</summary></details><p>A rede I2P está atualmente sob um ataque de negação de serviço.
+Este ataque afeta o I2P e o i2pd mas de formas diferentes e está a ter um efeito sério na saúde da rede.
+A acessibilidade dos sítios I2P está seriamente degradada.</p>
+<p>Se estiver a alojar um serviço dentro da I2P e este estiver alojado num roteador Floodfill, deve considerar o multihoming do serviço num roteador com Floodfill desativado para melhorar a acessibilidade.
+Estão a ser discutidas outras medidas de mitigação, mas ainda se está a trabalhar numa solução a longo prazo e compatível com as versões anteriores.</p>
+</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="Nova versão I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>Mais melhorias na aplicação, revisão da estratégia de isolamento de BD de rede</summary></details><p>Esta versão, I2P 2.5.0, fornece mais melhorias visíveis ao usuário do que a versão 2.4.0, que foi focada na implementação da estratégia de isolamento do BD de rede.</p>
+<p>Novas funcionalidades foram adicionadas ao I2PSnark, como a habilidade de pesquisar torrents.
+Bugs foram resolvidos para melhorar a compatibilidade com outros clientes de torrents I2P como o BiglyBT e o qBittorrent.
+Nós gostaríamos de agradecer a todos os desenvolvedores que trabalharam com a libtorrent e com o qBittorrent para proporcionar e melhorar seu suporte à I2P.
+Novas funcionalidades também foram adicionadas ao SusiMail, incluindo suporte a formatação Markdown em emails e a habilidade de arrastar e soltar anexos nos emails.
+Túneis criados com o gestor de Serviços Ocultos agora têm suporte a "Keepalive", o que melhora o desempenho e a compatibilidade com tecnologias web, permitindo sites I2P mais sofisticados.</p>
+<p>Durante essa versão nós também fizemos vários ajustes no BD de rede para melhorar sua resiliência a spam e para melhorar a capacidade do roteador de rejeitar mensagens suspeitas.
+Isso foi parte de um esforço para "revisar" a implementação de defesas de "Isolamento Sub-DB de rede" da versão 2.4.0.
+Essa investigação descobriu um pequeno evento de perfuração do isolamento, o que qual nós consertamos.
+Esse problema foi descoberto e resolvido internamente pelo time da I2P.</p>
+<p>Durante essa versão várias melhorias foram feitas no processo de lançamento das nossas distribuições downstream para Android e Windows.
+Isso deve resultar em uma melhor entrega e disponibilidade desses produtos downstream.</p>
+<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
+</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="Versão I2P 2.4.0 com melhorias de congestionamento e segurança do NetDB" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>Versão I2P 2.4.0 com melhorias de congestionamento e segurança do NetDB</summary></details><p>Esta versão, I2P 2.4.0, continua nosso esforço de melhorar a segurança e estabilidade da rede I2P.
+Ela contém melhorias significativas ao BD de rede, uma estrutura essencial dentro da rede I2P usada para descobrir seus pares.</p>
+<p>As mudanças no tratamento de congestão aperfeiçoarão a estabilidade da rede dando aos roteadores a possibilidade de aliviar pares congestionados evitando-os.
+Isso ajudará a rede a limitar a efetividade de spam de túnel.
+Isso também vai ajudar a rede a se regenerar durante e após ataques DDOS.</p>
+<p>As mudanças do BD de rede também ajudam a proteger roteadores individuais e as aplicações que os utilizam. 
+Roteadores agora podem se defender conta atacantes separando o BD de rede em vários "Sub-BDs", os quais nós utilizamos para prevenir vazamentos de informação entre aplicações e o roteador.
+Isso também aperfeiçoa a informação disponível aos roteadores Java sobre sua atividade de BD de rede e simplifica nosso suporte a aplicações multihoming.</p>
+<p>Também estão incluídas uma série de correções de bugs e melhorias nos aplicativos I2PSnark e SusiMail.</p>
+<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
+</article><article id="urn:uuid:" title="Nova versão I2P 2.3.0 - Correções de segurança, listas de bloqueio ajustáveis, API DTG" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Correções de segurança, listas de bloqueio ajustáveis, API DTG</summary></details><p>Essa versão contém correções para o CVE-2023-36325.
+O CVE-2023-36325 é um bug de confusão de contexto que ocorria no filtro de Bloom.
+Um atacante cria uma mensagem I2NP contendo um messageID único, e envia esse messageID para um cliente.
+A mensagem, após passar pelo filtro de Bloom, não é permitida ser reusada em uma segunda mensagem.
+O atacante então envia a mesma mensagem diretamente para o roteador.
+O roteador passa a mensagem para o filtro de Bloom, e é descartada.
+Isso vaza a informação de que o messageID já foi visto antes, dando ao atacante um forte motivo para acreditar que o roteador está hospedando o cliente.
+Isso foi corrigido separando a funcionalidade do filtro de Bloom em diferentes contextos com base em se uma mensagem chegou por um túnel de cliente, um túnel exploratório, ou foi enviada diretamente ao roteador.
+Sob circunstâncias normais, esse ataque leva vários dias para ter sucesso e pode ser confundido por vários outros fatores, tais como roteadores reiniciarem durante a fase do ataque e sensibilidade a falsos positivos.
+Recomenda-se que usuários da I2P Java atualizem a versão imediatamente para evitarem o ataque.</p>
+<p>No curso da correção desse bug de confusão de contexto, nós revisamos algumas de nossas estratégias de desenvolver código defensivamente, contra esses tipos de vazamentos.
+Isso inclui ajustes ao BD de rede, os mecanismos de limite de taxa, e o comportamento dos roteadores de floodfill.</p>
+<p>Essa versão adiciona o not_bob como um segundo provedor de hosts padrão, e adiciona o <a href="http://notbob.i2p">notbob.i2p</a> e o <a href="http://ramble.i2p">ramble.i2p</a> à página inicial do console.</p>
+<p>Essa versão também contém uma lista de bloqueio ajustável.
+Bloquear pela lista de bloqueio é semi permanente. Cada endereço IP bloqueado normalmente fica bloqueado até que o roteador seja reiniciado.
+Usuários que observarem crescimento explosivo da lista de bloqueio durante ataques Sybil podem optar por limites de tempo mais curtos configurando a lista de bloqueio para expirar entradas a um intervalo.
+Essa funcionalidade é desabilitada por padrão e só é recomendada para usuários avançados neste momento.</p>
+<p>Essa versão também inclui uma API para plugins modificarem com a GUI de Destkop (DTG).
+Agora é possível adicionar itens de menu à área de notificação do sistema, permitindo a inicialização mais intuitiva de plugins que usam interfaces nativas de aplicação.</p>
+<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
+</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="Nova versão 2.2.1, correções de empacotamento para Docker, Ubuntu Lunar e Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - versão de manutenção para 2.2.0</summary></details><p>Após o lançamento da I2P versão 2.2.0, que foi empurrada para frente para acelerar mitigações aos ataques DDOS, nós descobrimos alguns problemas de desenvolvimento que tornaram necessário construir e lançar novos pacotes.
+Essa versão corrige um problema no Ubuntu Lunar e no Debian Sid onde o console do roteador estava inacessível usando uma versão atualizada do pacote jakarta.
+Os pacotes Docker não estavam lendo argumentos corretamente, resultando em arquivos de configuração inacessíveis.
+Esse problema também foi resolvido.
+O contêiner docker é agora também compatível com o Podman.</p>
+<p>Esta versão sincroniza traduções com transifex e atualiza o banco de dados GeoIP.</p>
+<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
+</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="Nova versão 2.2.0, Mitigações para ataques DDOS e ajustes no subsistema Streaming" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Atenuações para ataques DDOS e ajustes no subsistema Streaming</summary></details><p>Optamos por antecipar a data de lançamento da versão 2.2.0, que ocorrerá hoje, 13 de março de 2023. Esta versão inclui alterações nos componentes NetDB, Floodfill e Peer-Selection que melhoram a capacidade do roteador de sobreviver a ataques DDOS. É provável que os ataques continuem, mas as melhorias nesses sistemas ajudarão a mitigar o risco de ataques DDOS, ajudando o roteador a identificar e despriorizar roteadores que parecem maliciosos.</p>
+<p>Essa versão também adiciona proteção contra repetição ao subsistema de Streaming, o que evita que um atacante que consiga capturar um pacote criptografado possa reusá-lo enviando-o para destinatários indesejados.
+Essa é uma mudança retrocompatível, então roteadores mais antigos continuarão sendo capazes de usar as capacidades de streaming de roteadores mais novos.
+Esse problema foi descoberto e resolvido internamente, pelo time de desenvolvimento da I2P, e não está relacionado aos ataques DDOS.
+Nós nunca encontramos um pacote de streaming repetido e não acreditamos que um ataque de repetição de streaming tenha algum dia acontecido contra a rede I2P neste momento.</p>
+<p>Como você pode ter notado, estas notas de lançamento e o lançamento da versão em si foram assinados pelo idk, e não pelo zzz.
+O zzz decidiu deixar o projeto e suas responsabilidades estão sendo apropriadas por outros membros do time.
+Como tal, o projeto está trabalhando em substituir a infraestrutura de estatísticas de rede e mover o fórum de desenvolvimento para i2pforum.i2p.
+Nós agradecemos o zzz por fornecer esses serviços por tanto tempo.</p>
+<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
+</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="Atualização de DDoS" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>Atualização de DDoS</summary></details><p>Nós confirmamos que o atacante controla um grande número de roteadores.
+Nossas investigações e mitigações continuam.</p>
+<p>Esse é um bom momento para lembrar as pessoas de que mesmo após 20 anos, a rede I2P é relativamente pequena.
+Nós não temos indícios de que o atacante está tentando desanonimizar algum usuário ou serviço oculto em particular.
+Todavia, se seu modelo de risco é de alto risco, você deve considerar cuidadosamente se a I2P atualmente oferece a proteção que você requer.
+A melhor solução a longo prazo é divulgar e a fazer crescer a rede I2P para aumentar a segurança de nossos usuários.</p>
+<p>Nós providenciaremos informações adicionais aqui no feed de notícias e em <a href="http://zzz.i2p">zzz.i2p</a> conforme necessário.
+Nós pedimos a sua paciência enquanto trabalhamos para melhorar a I2P.</p>
+</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="Sobre os recentes ataques de Negação de Serviço" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>A I2P continua intacta com desempenho prejudicado</summary></details><p>A rede I2P está atualmente sendo afetada por um ataque de Negação de Serviço.
+  A função de floodfill da rede foi afetada, resultando em respostas sendo prejudicadas e taxas de sucesso de construção de túnel caindo.
+  Participantes na rede têm sofrido dificuldades ao conectar a sites I2P e ao usar serviços I2P.
+  Estratégias de mitigação estão sendo investigadas e implementadas gradualmente.</p>
+<p>Embora o ataque tenha degradado o desempenho, a rede segue intacta e usável.
+  Roteadores I2P Java parecem estar lidando com esses problemas melhor do que os roteadores i2pd por agora.
+  Várias mitigações devem começar a aparecer nas construções de desenvolvimento tanto dos roteadores Java quanto dos roteadores C++ na próxima semana.</p>
+</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="Versão 2.1.0 Lançada" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 com diversas correções de SSU2</summary></details><p>Nós descobrimos várias coisas desde a nossa versão 2.0.0 em novembro.
+Conforme os roteadores atualizaram para essa versão, a rede foi de em torno de 1% para mais de 60% de suporte para nosso novo protocolo de transporte SSU2.
+Em primeiro lugar, nós confirmamos que o SSU2 é um protocolo seguro, bem projetado, e sólido.
+Em segundo lugar, contudo, nós encontramos e corrigimos diversos bugs pequenos ou de baixa ocorrência na implementação do protocolo.
+Cumulativamente, os efeitos desses bugs reduziram o desempenho da rede.</p>
+<p>Ainda, nós estamos a par do maior número de túneis e da menor taxa de sucesso de construção de túneis na rede,
+possivelmente causados pela nova funcionalidade do Bitcoin de endereço transiente da I2P,
+mas tornados piores pelos nossos bugs do SSU2 e outros problemas de controle de congestão.
+Nós estamos trabalhando com o Bitcoin e com outros projetos não Bitcoin para reduzir as demandas de rede da I2P.
+Nós aperfeiçoamos nossos algoritmos para reduzir a carga sobre a rede durante momentos de congestão.
+Nós também estamos colaborando com a i2pd para desenvolver estratégias em comum de controle de congestão.</p>
+<p>Portanto, nós aceleramos esse lançamento em cerca de seis semanas, para levar as correções para todo mundo.
+A i2pd lançou sua versão 2.45.0 na semana passada e os resultados iniciais são encorajadores.
+Novos protocolos, e redes distribuídas, são difíceis de desenvolver.
+A congestão pode chegar com pouco aviso e com pouco indício de causa.
+Obrigado por sua paciência enquanto nós diagnosticávamos e, assim se espera, resolvíamos os problemas.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Publicações recentes no blogue" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>
+</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="Versão 2.0.0 Lançada" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>Transporte SSU2 Habilitado</summary></details><p>A I2P versão 2.0.0 habilita nosso novo transporte UDP SSU2 para todos os usuários, após o término de pequenas funcionalidades, testes, e diversas correções de bugs.</p>
+<p>Nós também temos correções por todo o lugar, incluindo instalador, base de dados de rede, adição ao livro de endereços privado, inicializador de navegador do Windows, e UPnP IPV6.</p>
+<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
+</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Publicações recentes no blogue" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>Alguns posts recentes do blog</summary></details><p>Aqui estão links para diversas publicações recentes no nosso website:</p>
 <ul>
-<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Overview of our new SSU2 transport</a></li>
-<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">A warning about I2P coins and other scams</a></li>
-<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">An interview with Konrad from diva.exchange</a></li>
-<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">An interview with Dustin from StormyCloud</a></li>
-</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 with SSU2 for testing</summary></details><p>We have spent the last three months working on our new UDP transport protocol "SSU2"
-with a small number of volunteer testers.
-This release completes the implementation, including relay and peer testing.
-We are enabling it by default for Android and ARM platforms, and a small percentage of other routers at random.
-This will allow us to do much more testing in the next three months, finish the connection migration feature,
-and fix any remaining issues.
-We plan to enable it for everyone in the next release scheduled for November.
-No manual configuration is necessary.</p>
-<p>Of course, there's the usual collection of bug fixes in this release as well.
-We also added an automatic deadlock detector that has already found a rare deadlock that is now fixed.</p>
+<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Visão geral do nosso novo transporte SSU2</a></li>
+<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">Um aviso sobre moedas I2P e outros golpes</a></li>
+<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">Uma entrevista com o Konrad do diva.exchange</a></li>
+<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">Uma entrevista com o Dustin da StormyCloud</a></li>
+</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="Versão 1.9.0 Lançada" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 com SSU2 para testes</summary></details><p>Nós passamos os últimos três meses trabalhando em nosso novo protocolo de transporte UDP "SSU2"
+com um pequeno número de testadores voluntários.
+Essa versão completa a implementação, incluindo testes de par e de transmissor.
+Nós estamos o habilitando por padrão para as plataformas Android e ARM, e para uma pequena porcentagem de outros roteadores aleatoriamente.
+Isso nos permitirá fazer muito mais testes nos próximos três meses, terminar a funcionalidade de migração de conexão,
+e consertar quaisquer problemas restantes.
+Nós planejamos habilitá-lo para todo mundo no próximo lançamento agendado para novembro.
+Nenhuma configuração manual é necessária.</p>
+<p>Claro, há a coleção usual de correções de bugs nesta versão também. Também adicionamos um detector automático de deadlock que já encontrou um raro deadlock que agora está corrigido.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="New Outproxy exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>New Outproxy</summary></details><p>I2P "outproxies" (exit nodes) may be used to access the internet through
-your HTTP proxy tunnel.
-As approved at our <a href="http://i2p-projekt.i2p/en/meetings/314">monthly meeting</a>,
-<b>exit.stormycloud.i2p</b> is now our official, recommended outproxy, replacing the long-dead <b>false.i2p</b>.
-For more information on the StormyCloud <a href="http://stormycloud.i2p/">organization</a>,
-<a href="http://stormycloud.i2p/outproxy.html">outproxy</a>,
-and <a href="http://stormycloud.i2p/tos.html">terms of service</a>,
-see the <a href="http://stormycloud.i2p/">StormyCloud website</a>.</p>
-<p>We suggest you change your <a href="/i2ptunnel/edit?tunnel=0">Hidden Services Manager configuration</a>
-to specify <b>exit.stormycloud.i2p</b>
-in two places: <b>Outproxies</b> and <b>SSL Outproxies</b>.
-After editing, <b>scroll down and click Save</b>.
-See our <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">blog post for a screenshot</a>.
-For Android instructions and screenshots see <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">notbob's blog</a>.</p>
-<p>Router updates will not update your configuration, you must edit it manually.
-Thanks to StormyCloud for their support, and please consider a <a href="http://stormycloud.i2p/donate.html">donation</a>.</p>
-</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 with bug fixes</summary></details><p>This release includes bug fixes in i2psnark,
-the router, I2CP, and UPnP.
-Router fixes address bugs in soft restart, IPv6, SSU peer testing,
-network database stores, and tunnel building.
-Router family handling and Sybil classification have also been
-significantly improved.</p>
-<p>Together with i2pd, we are developing our new UDP transport, SSU2.
-SSU2 will bring substantial performance and security improvements.
-It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
-completing the full cryptography upgrade we started about 9 years ago.
-This release contains a preliminary implementation which is disabled by default.
-If you wish to participate in testing, please look for current information
-on zzz.i2p.</p>
+</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="Novo Outproxy exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>Novo Outproxy</summary></details><p>"Proxies de saída" (nodos de saída) da I2P podem ser usados para acessar a internet através
+do seu túnel de proxy HTTP.
+Conforme aprovado em nossa <a href="http://i2p-projekt.i2p/en/meetings/314">reunião mensal</a>,
+<b>exit.stormycloud.i2p</b> é agora nosso proxy de saída recomendado e oficial, substituindo o há muito morto <b>false.i2p</b>.
+Para mais informações sobre a <a href="http://stormycloud.i2p/">organização</a>,
+o <a href="http://stormycloud.i2p/outproxy.html">proxy de saída</a>,
+e os <a href="http://stormycloud.i2p/tos.html">termos de serviço</a> da StormyCloud,
+veja o <a href="http://stormycloud.i2p/">website da StormyCloud</a>.</p>
+<p>Nós sugerimos que você modifique a sua <a href="/i2ptunnel/edit?tunnel=0">configuração do Gerenciador de Serviços Ocultos</a>
+para especificar <b>exit.stormycloud.i2p</b>
+em dois lugares: <b>Proxies de Saída</b> e <b>Proxies de Saída SSL</b>.
+Após editar, <b>role para baixo e clique em Salvar</b>.
+Veja nossa <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">publicação no blog para uma captura de tela</a>.
+Para instruções para o Android e capturas de tela, veja o <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">blog do notbob</a>.</p>
+<p>As atualizações do roteador não atualizarão sua configuração, você deve editá-la manualmente. Obrigado a StormyCloud por seu apoio, e por favor, considere um <a href="http://stormycloud.i2p/donate.html">doação</a>.</p>
+</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 com correções de bugs</summary></details><p>Essa versão inclui correções de bugs no i2psnark,
+no roteador, I2CP, e UPnP.
+As correções no roteador tratam bugs no reinício suave, IPv6, testes de par SSU,
+armazenamento do banco de dados de rede, e construção de túnel.
+O tratamento de família de roteador e  classificação de Sybil também foram
+melhorados significativamente.</p>
+<p>Junto da i2pd, nós estamos desenvolvendo nosso novo transporte UDP, o SSU2.
+O SSU2 trará melhoras substanciais de desempenho e segurança.
+Ele também permitirá que nós finalmente substituamos nosso último uso da criptografia muito lenta ElGamal,
+completando a atualização completa de criptografia que nós iniciamos cerca de 9 anos atrás.
+Essa versão contém uma implementação preliminar que fica desabilitada por padrão.
+Se você deseja participar em testes, por favor, busque informações atuais
+em zzz.i2p.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Install essential Java/Jpackage updates" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>The recent Java "Psychic Signatues" vulnerability affects I2P. Current users of
-I2P on Linux, or any users of I2P who are using a non-bundled JVM should update
-their JVM or switch to a version which does not contain the vulnerability, below
-Java 15.</p>
-<p>New I2P Easy-Install bundles have been generated using the latest release of the
-Java Virtual Machine. Further details have been published in the respective
-bundle newsfeeds.</p>
-</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 with reliability and performance improvements</summary></details><p>The 1.7.0 release contains several performance and reliability improvements.</p>
-<p>There are now popup messages in the system tray, for those platforms that support it.
-i2psnark has a new torrent editor.
-The NTCP2 transport now uses much less CPU.</p>
-<p>The long-deprecated BOB interface is removed for new installs.
-It will continue to work in existing installs, except for Debian packages.
-Any remaining users of BOB applications should ask the developers to convert to the SAMv3 protocol.</p>
-<p>We know that since our 1.6.1 release, network reliability has steadily deteriorated.
-We were aware of the problem soon after the release, but it took us almost two months to find the cause.
-We eventually identified it as a bug in i2pd 2.40.0,
-and the fix will be in their 2.41.0 release coming out about the same time as this release.
-Along the way, we've made several changes on the Java I2P side to improve the
-robustness of network database lookups and stores, and avoid poorly-performing peers in tunnel peer selection.
-This should help the network be more robust even in the presence of buggy or malicious routers.
-Additionally, we're starting a joint program to test pre-release i2pd and Java I2P routers
-together in an isolated test network, so we can find more problems before the releases, not after.</p>
-<p>In other news, we continue to make great progress on the design of our new UDP transport "SSU2" (proposal 159)
-and have started implementation.
-SSU2 will bring substantial performance and security improvements.
-It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
-completing a full cryptography upgrade that started about 9 years ago.
-We expect to start joint testing with i2pd soon, and roll it out to the network later this year.</p>
+</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Instalar atualizações essenciais do Java/Jpackage" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>A recente vulnerabilidade Java de "Assinaturas Psíquicas" afeta a I2P. Usuários atuais da
+I2P no Linux, ou quaisquer usuários da I2P que estiverem usando uma JVM que não veio junto no pacote devem atualizar
+sua JVM ou mudar para uma versão que não contém a vulnerabilidade, abaixo
+do Java 15.</p>
+<p>Novos pacotes I2P Easy-Install foram gerados usando a versão mais recente doJava Virtual Machine. Mais detalhes foram publicados nos respectivosfeeds de notícias do pacote.</p>
+</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 com melhorias de confiabilidade e desempenho</summary></details><p>A versão 1.7.0 contém várias melhorias de desempenho e confiabilidade.</p>
+<p>Agora há mensagens pop-up na bandeja do sistema, para as plataformas que o suportam. i2psnark tem um novo editor de torrent. O transporte NTCP2 agora usa muito menos CPU.</p>
+<p>A há muito obsoleta interface BOB está removida para novas instalações.
+Ela continuará funcionando em instalações existentes, exceto em pacotes Debian.
+Quaisquer usuários de aplicações BOB que ainda restarem devem pedir aos desenvolvedores que as convertam para o protocolo SAMv3.</p>
+<p>Nós sabemos que desde a nossa versão 1.6.1, a estabilidade da rede tem deteriorado continuamente.
+Nós ficamos a par do problema logo após o lançamento, mas levou quase dois meses para nós encontrarmos a causa.
+Nós eventualmente a identificamos como um bug na i2pd 2.40.0,
+e a correção será na sua versão 2.41.0, que será lançada mais ou menos na mesma data que esta versão.
+Ao longo do caminho, nós fizemos várias mudanças do lado da I2P Java para melhorar a
+robustez dos armazenamentos e buscas na base de dados de rede, e evitar pares com desempenho ruim na seleção de par de túnel.
+Isso deve ajudar a rede a ficar mais robusta mesmo com a presença de roteadores problemáticos ou maliciosos.
+Ainda, nós estamos iniciando um programa conjunto para testar os roteadores I2P Java e i2pd pré-lançamento
+juntos em uma rede para testes isolada, para que possamos encontrar mais problemas antes dos lançamentos, não depois.</p>
+<p>Em outras novidades, nós continuamos a fazer bastante progresso no projeto do nosso novo transporte UDP "SSU2" (proposta 159)
+e começamos a implementação.
+O SSU2 trará melhoras substanciais de desempenho e segurança.
+Ele também permitirá que nós finalmente substituamos nosso último uso da criptografia muito lenta ElGamal,
+completando uma atualização completa de criptografia que começou cerca de 9 anos atrás.
+Nós esperamos iniciar a testar em conjunto com a i2pd logo, e disponibilizá-lo para a rede mais tarde neste ano.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
 </article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 permite novas mensagens de construção do túnel</summary></details><p>Este lançamento completa a implementação de duas grandes atualizações do protocolo desenvolvidas em 2021.
 A transição para a criptografia X25519 para roteadores é acelerada, e esperamos que quase todos os roteadores sejam chaveados novamente até o final do ano.
@@ -88,74 +239,61 @@ O filtro Bloom construído no túnel foi ajustado para reduzir o uso de memória
 Melhoramos o suporte para plugins não-Java.</p>
 <p>Em outras palavras, estamos fazendo excelentes progressos no projeto de nosso novo SSU2 de transporte UDP e esperamos começar a implementação no início do próximo ano.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 com novas mensagens de construção do túnel</summary></details><p>Yes, that's right, after 9 years of 0.9.x releases, we are going straight from 0.9.50 to 1.5.0.
-This does not signify a major API change, or a claim that development is now complete.
-It is simply a recognition of almost 20 years of work to provide anonymity and security for our users.</p>
-<p>This release finishes implementation of smaller tunnel build messages to reduce bandwidth.
-We continue the transition of the network's routers to X25519 encryption.
-Of course there are also numerous bug fixes and performance improvements.</p>
+</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 com novas mensagens de construção do túnel</summary></details><p>Sim, é isso mesmo, após nove anos de versões 0.9.x, nós estamos indo direto de 0.9.50 para 1.5.0.
+Isso não simboliza uma grande mudança de API, ou uma declaração de que o desenvolvimento agora está completo.
+É simplesmente um reconhecimento dos quase 20 anos de trabalho para proporcionar anonimato e segurança para nossos usuários.</p>
+<p>Essa versão finaliza a implementação de mensagens de criação de túnel menores para reduzir largura de banda.
+Nós continuamos a transição dos roteadores da rede para a criptografia X25519.
+Claro que há também diversas correções de bugs e melhorias de desempenho.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="MuWire Desktop Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Muwire Desktop Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire standalone desktop application.
-It does not affect the console plugin, and is not related to the previously-announced plugin issue.
-If you are running the MuWire desktop application you should <a href="http://muwire.i2p/">update to version 0.8.8</a> immediately.</p>
-<p>Details of the issue will be published on <a href="http://muwire.i2p/security.html">muwire.i2p</a>
-on July 15, 2021.</p>
-</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="MuWire Plugin Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Muwire Plugin Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire plugin.
-It does not affect the standalone desktop client.
-If you are running the MuWire plugin you should <a href="/configplugins">update to version 0.8.7-b1</a> immediately.</p>
-<p>See <a href="http://muwire.i2p/security.html">muwire.i2p</a>
-for more information about the vulnerability and updated security recommendations.</p>
-</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 com correções do IPv6</summary></details><p>0.9.50 continues the transition to ECIES-X25519 for router encryption keys.
-We have enabled DNS over HTTPS for reseeding to protect users from passive DNS snooping.
-There are numerous fixes and improvements for IPv6 addresses, including new UPnP support.</p>
-<p>We have finally fixed some longstanding SusiMail corruption bugs.
-Changes to the bandwidth limiter should improve network tunnel performance.
-There are several improvements in our Docker containers.
-We have improved our defenses for possible malicious and buggy routers in the network.</p>
+</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="Vulnerabilidade de desktop MuWire" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Muwire Desktop Vulnerability</summary></details><p>Uma vulnerabilidade de segurança foi descoberta na versão autônoma da aplicação de desktop do MuWire.
+Ela não afeta o plugin do console, e não está relacionada com o problema no plugin anunciado previamente.
+Se você executa a aplicação para desktop do MuWire, você deve <a href="http://muwire.i2p/">atualizar para a versão 0.8.8</a> imediatamente.</p>
+<p>Os detalhes da edição serão publicados em <a href="http://muwire.i2p/security.html">muwire.i2p</a>
+em 15 de julho de 2021.</p>
+</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="Vulnerabilidade de plug-in MuWire" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Vulnerabilidade de plug-in Muwire</summary></details><p>Foi detetada uma vulnerabilidade de segurança no plugin MuWire. Ele não afeta o cliente de desktop autônomo. Se você estiver executando o plugin MuWire, você deve <a href="/configplugins">Atualização para a versão 0.8.7-B1</a> imediatamente.</p>
+<p>Ver <a href="http://muwire.i2p/security.html">muwire.i2p</a>
+para obter mais informações sobre a vulnerabilidade e recomendações de segurança atualizadas.</p>
+</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 com correções do IPv6</summary></details><p>A versão 0.9.50 dá continuidade à transição ao ECIES-X25519 para chaves de criptografia dos roteadores.
+Nós habilitamos DNS sobre HTTPS para repropagação para proteger usuários contra snooping passivo de DNS.
+Há diversas correções e melhorias para endereços IPv6, incluindo o novo suporte aUPnP.</p>
+<p>Nós finalmente corrigimos alguns antigos bugs de corrupção no SusiMail.
+Mudanças no limitador de banda devem melhorar o desempenho de túnel da rede.
+Há várias melhorias no nossos contêiners Docker.
+Nós melhoramos nossas defesas contra possíveis roteadores com problemas ou maliciosos na rede.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0,9,49 com correções do SSU e criptografia mais rápida</summary></details><p>0.9.49 continues the work to make I2P faster and more secure.
-We have several improvements and fixes for the SSU (UDP) transport that should result in faster speeds.
-This release also starts the migration to new, faster ECIES-X25519 encryption for routers.
-(Destinations have been using this encryption for a few releases now)
-We've been working on the specifications and protocols for new encryption for several years,
-and we are getting close to the end of it! The migration will take several releases to complete.</p>
-<p>For this release, to minimize disruption, only new installs and a very small percentage of existing installs
-(randomly selected at restart) will be using the new encryption.
-If your router does "rekey" to use the new encryption, it may have lower traffic or less reliability than usual for several days after you restart.
-This is normal, because your router has generated a new identity.
-Your performance should recover after a while.</p>
-<p>We have "rekeyed" the network twice before, when changing the default signature type,
-but this is the first time we've changed the default encryption type.
-Hopefully it will all go smoothly, but we're starting slowly to be sure.</p>
+</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0,9,49 com correções do SSU e criptografia mais rápida</summary></details><p>A versão 0.9.49 dá continuidade ao trabalho para tornar a I2P mais rápida e mais segura.
+Nós temos várias melhorias e correções para o transporte SSU (UDP) que devem resultar em velocidades mais rápidas.
+Essa versão também dá início à migração para a nova e mais rápida criptografia ECIES-X25519 para os roteadores.
+(Destinos têm usado essa criptografia há alguns lançamentos agora)
+Nós temos trabalhado nas especificações e protocolos para a nova criptografia por vários anos,
+e nós estamos chegando perto de terminar! A migração levará diversos lançamentos para ser completada.</p>
+<p>Para esse lançamento, para minimizar o transtorno, apenas novas instalações e uma porcentagem muito pequena de instalações existentes
+(selecionadas aleatoriamente ao reiniciar) estarão usando a nova criptografia.
+Se seu roteador "rechavear" para usar a nova criptografia, ele pode ter tráfego menor ou menor estabilidade do que o normal por vários dias após você reiniciar.
+Isso é normal, porque seu roteador gerou uma nova identidade.
+Seu desempenho deveria ser recuperado após um tempo.</p>
+<p>Nós "rechaveamos" a rede duas vezes antes, ao alterar o tipo de assinatura padrão, mas esta é a primeira vez que mudamos o tipo de criptografia padrão. Espero que tudo corra bem, mas estamos começando devagar para ter certeza.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
 </article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 com melhorias de desempenho</summary></details><p>0.9.48 permite nosso novo protocolo de criptografia de ponta-a-ponta (proposta 144) para a maioria dos serviços.
 Adicionamos suporte preliminar para a criptografia de novas mensagens de construção de túnel (proposta 152).
 Há melhorias significativas de desempenho em todo o roteador.</p>
-<p>Packages for Ubuntu Xenial (16.04 LTS) are no longer supported.
-Users on that platform should upgrade so you may continue to receive I2P updates.</p>
+<p>Pacotes para Ubuntu Xenial (16.04 LTS) não são mais suportados. Os usuários nessa plataforma devem atualizar para que você possa continuar a receber atualizações I2P.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 permite nova criptografia</summary></details><p>0.9.47 enables our new end-to-end encryption protocol (proposal 144) by default for some services.
-The Sybil analysis and blocking tool is now enabled by default.</p>
-<p>Java 8 or higher is now required.
-Debian packages for Wheezy and Stretch, and for Ubuntu Trusty and Precise, are no longer supported.
-Users on those platforms should upgrade so you may continue to receive I2P updates.</p>
+</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 permite nova criptografia</summary></details><p>A versão 0.9.47 habilita nosso novo protocolo de criptografia de ponta a ponta (proposta 144) por padrão para alguns serviços. A ferramenta de análise e bloqueio Sybil agora está habilitada por padrão.</p>
+<p>Java 8 ou superior agora é necessário. Os pacotes Debian para Wheezy e Stretch, e para Ubuntu Trusty e Precise, não são mais suportados. Os usuários nessas plataformas devem atualizar para que você possa continuar a receber atualizações I2P.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="0.9.46 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 com correções de falha</summary></details><p>0.9.46 contains significant performance improvements in the streaming library.
-We have completed development of ECIES encryption (proposal 144) and there is now an option to enable it for testing.</p>
-<p>Windows users only:
-This release fixes a local privilege escalation vulnerability
-which could be exploited by a local user.
-Please apply the update as soon as possible.
-Thanks to Blaze Infosec for responsible disclosure of the issue.</p>
-<p>This is the last release to support Java 7, Debian packages Wheezy and Stretch, and Ubuntu packages Precise and Trusty.
-Users on those platforms must upgrade to receive future I2P updates.</p>
+</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="0.9.46 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 com correções de falha</summary></details><p>0.9.46 contém melhorias significativas de desempenho na biblioteca de streaming. Concluímos o desenvolvimento da criptografia ECIES (proposta 144) e agora há uma opção para habilitá-la para testes.</p>
+<p>Para usuários de Windows apenas:
+Essa versão corrige uma vulnerabilidade de escalação de privilégio local
+que poderia ser explorada por um usuário local.
+Por favor, aplique a atualização o mais breve possível.
+Obrigado à Blaze Infosec pela divulgação responsável do problema.</p>
+<p>Esta é a última versão a suportar Java 7, pacotes Debian Wheezy e Stretch, e pacotes Ubuntu Precise e Trusty. Os usuários nessas plataformas devem atualizar para receber atualizações futuras do I2P.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 com correções de falha</summary></details><p>0.9.45 contains important fixes for hidden mode and the bandwidth tester.
-There's an update to the console dark theme.
-We continue work on improving performance and the development of new end-to-end encryption (proposal 144).</p>
+</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 com correções de falha</summary></details><p>0.9.45 contém correções importantes para o modo oculto e o testador de largura de banda. Há uma atualização para o tema escuro do console. Continuamos a trabalhar na melhoria do desempenho e no desenvolvimento de uma nova encriptação de ponta a ponta (proposta 144).</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="Lançada versão 0.9.44" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 com correções de erros</summary></details><p>0.9.44 contains an important fix for a denial of service issue in hidden services handling of new encryption types.
-All users should update as soon as possible.</p>
+</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="Lançada versão 0.9.44" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 com correções de erros</summary></details><p>0.9.44 contém uma correção importante para um problema de negação de serviço no processamento de novos tipos de criptografia de serviços ocultos. Todos os usuários devem atualizar o mais rápido possível.</p>
 <p>Esse lançamento contém suporte inicial para uma nova criptografia ponta-a-ponta (proposta 144). 
 Este é trabalho em andamento e ainda não está pronto para uso.
 Há mudanças na pagina inicial do painel, e novos media players HTML5 embutidos no i2psnark.
@@ -190,206 +328,185 @@ Como de praxe, nós corrigimos muitas falhas!</p>
 </article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 com melhorias de desempenho</summary></details><p>0.9.39 inclui mudanças extensas para os novos tipos de base de dados da rede (proposta 123)
 Nós empacotamos a extensão i2pcontrol como um aplicativo web para suportar o desenvolvimento de aplicações RPC.
 Há numerosas melhorias de desempenho e correções de falha.  </p>
-<p>We've removed the midnight and classic themes to reduce the maintenance burden;
-previous users of those themes will now see the dark or light theme.
-There's also new home page icons, a first step in updating the console.</p>
+<p>Nós removemos os temas clássico e meia-noite para reduzir a carga de manutenção;
+usuários prévios desses temas agora verão os temas escuro ou claro.
+Também há novos ícones na página inicial, um primeiro passo na atualização do console.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 com o novo instalador passo-a-passo</summary></details><p>0.9.38 includes a new first-install wizard with a bandwidth tester.
-We've added support for the latest GeoIP database format.
-There's a new Firefox profile installer and a new, native Mac OSX installer on our website.
-Work continues on supporting the new "LS2" netdb format.</p>
-<p>This release also contains plenty of bug fixes, including several issues with susimail attachments, and a fix for IPv6-only routers.</p>
+</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 com o novo instalador passo-a-passo</summary></details><p>A versão 0.9.38 inclui um novo assistente de primeira instalação com um testador de largura de banda.
+Nós adicionamos suporte ao formato mais recente de base de dados de GeoIP.
+Agora há um novo instalador de perfil do Firefox e um novo instalador nativo para Mac OSX no nosso website.
+O trabalho continua para dar suporte ao novo formato de BD de rede "LS2".</p>
+<p>Esta versão também contém muitas correções de bugs, incluindo vários problemas com anexos susimail e uma correção para roteadores somente IPv6.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="35C3 Trip Report" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P no 35C3</summary></details><p>The I2P team was mostly all in attendance at 35C3 in Leipzig.
-Daily meetings were held to review the past year and cover our development and design goals for 2019.</p>
-<p>The Project Vision and new Roadmap can be <a href="http://i2p-projekt.i2p/en/get-involved/roadmap">reviewed here</a>.</p>
-<p>Work will continue on LS2, the Testnet, and usability improvements to our website and console.
-A plan is in place to be in Tails, Debian and Ubuntu Disco. We still need people to work on Android and I2P_Bote fixes.</p>
+</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="35C3 Relatório de Viagem" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P no 35C3</summary></details><p>A equipe I2P esteve praticamente toda presente no 35C3 em Leipzig. Foram realizadas reuniões diárias para revisar o ano passado e abordar nossas metas de desenvolvimento e design para 2019.</p>
+<p>A Visão do Projeto e o novo Roteiro podem ser <a href="http://i2p-projekt.i2p/en/get-involved/roadmap">Reveja aqui</a>.</p>
+<p>O trabalho continuará no LS2, no Testnet e nas melhorias de usabilidade do nosso site e console. Um plano está em vigor para estar no Tails, Debian e Ubuntu Disco. Ainda precisamos de pessoas para trabalhar no Android e I2P_Bote correções.</p>
 </article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="0.9.37 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37 com NTCP2 habilitado</summary></details><p>0.9.37 possibilita um protocolo de transporte mais seguro e rápido chamado NTCP2. </p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="0.9.36 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 with NTCP2 and bug fixes</summary></details><p>0.9.36 contains a new, more secure transport protocol called NTCP2.
-It is disabled by default, but you may enable it for testing by adding the <a href="/configadvanced">advanced configuration</a> <tt>i2np.ntcp2.enable=true</tt> and restarting.
-NTCP2 will be enabled in the next release.</p>
+</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="0.9.36 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 with NTCP2 and bug fixes</summary></details><p>A versão 0.9.36 contém um protocolo de transporte novo e mais seguro chamado NTCP2.
+Ele fica desabilitado por padrão, mas você pode habilitá-lo para testes adicionando a <a href="/configadvanced">configuração avançada</a> <tt>i2np.ntcp2.enable=true</tt> e reiniciando.
+O NTCP2 estará habilitado no próximo lançamento.</p>
 <p>Esse lançamento também contém várias melhorias de desempenho e correções de falha. </p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
 </article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="Lançada a versão 0.9.35" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>Versão 0.9.35 com pastas SusiMail e Assistente de SSL</summary></details><p>A versão 0.9.35 adiciona suporte para pastas no SusiMail, e um novo 'Assistente' de SSL Wizard para a configurar HTTPS no seu site da Web de "Serviço Oculto".
 Nós também temos a coleção usual de correções de erros, especialmente no SusiMail.</p>
 <p>Nós estamos a trabalhar muito em várias coisas para a versão 0.9.36, incluindo um novo instalador de OSX e um protocolo de transporte mais rápido e seguro, chamado de NTCP2.</p>
-<p>I2P will be at HOPE in New York City, July 20-22. Find us and say hello!</p>
+<p>A I2P estará na HOPE em Nova York, de 20 a 22 de julho. Encontre-nos e diga olá!</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="Lançada versão 0.9.34" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 com correções de erros</summary></details><p>0.9.34 contains a lot of bug fixes!
-It also has improvements in SusiMail, IPv6 handling, and tunnel peer selection.
-We add support for IGD2 schemas in UPnP.
-There's also preparation for more improvements you will see in future releases.</p>
+</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="Lançada versão 0.9.34" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 com correções de erros</summary></details><p>A versão 0.9.34 contém várias correções de bugs!
+Ela também inclui melhorias no SusiMail, tratamento de IPv6, e seleção de par de túnel.
+Nós adicionamos suporte para os esquemas IGD2 no UPnP.
+Há também preparação para mais melhorias que você verá em lançamentos futuros.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="0.9.33 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 com correções de falha</summary></details><p>0.9.33 contains a large number of bug fixes, including i2psnark, i2ptunnel, streaming, and SusiMail.
-For those who cannot access the reseed sites directly, we now support several types of proxies for reseeding.
-We now set rate limits by default in the hidden services manager.
-For those that run high-traffic servers, please review and adjust the limits as necessary.</p>
+</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="0.9.33 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 com correções de falha</summary></details><p>A versão 0.9.33 contém um grande número de correções de bugs, incluindo o i2psnark, o i2ptunnel, streaming, e o SusiMail.
+Para aqueles que não conseguem acessar os sites de repropagação diretamente, nós agora suportamos vários tipos de proxies para repropagação.
+Nós agora definimos limites de taxa por padrão no gerenciador de serviços ocultos.
+Para aqueles que executam servidores de alto tráfego, por favor, revisem e ajustem os limites conforme necessário.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER, Meltdown e Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Problemas de segurança encontrados em quase todos os sistemas</summary></details><p>A very serious issue has been found in modern CPUs which are found in nearly all sold computers worldwide, including mobiles. Those security issues are named "Kaiser", "Meltdown", and "Spectre".</p>
-<p>The whitepaper for KAISER/KPTI can be found under <a href="https://gruss.cc/files/kaiser.pdf" target="_blank">KAISER.pdf</a>, Meltdown under <a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a>, and SPECTRE under <a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a>. Intels first response is listed under <a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">Intels response</a>.</p>
-<p>It is important for our I2P users to update your system, as long as updates are available. Windows 10 patches are availble from now on, Windows 7 and 8 will follow soon. MacOS patches are already available, to. Lots of Linux systems have a newer Kernel with a included fix available, too. Same applies to Android, which security fix of 2nd Jan 2018 includes a patch for this issues.
-Please update your systems as soon as available and possible.</p>
+</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER, Meltdown e Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Problemas de segurança encontrados em quase todos os sistemas</summary></details><p>Um problema muito sério foi encontrado em CPUs modernas que são encontradas em quase todos os computadores vendidos em todo o mundo, incluindo celulares. Esses problemas de segurança são chamados de "Kaiser", "Meltdown" e "Spectre".</p>
+<p>O whitepaper do KAISER/KPTI pode ser encontrado em <a href="https://gruss.cc/files/kaiser.pdf" target="_blank">KAISER.pdf</a>, o do Meltdown em <a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a>, e o do SPECTRE em <a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a>. A primeira resposta da Intel está listada em <a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">resposta da Intel</a>.</p>
+<p>É importante para nossos usuários da I2P atualizar seu sistema, contando que atualizações estejam disponíveis. Patches para o Windows 10 estão disponíveis a partir de agora, Windows 7 e 8 virão logo em seguida. Patches para MacOS já estão disponíveis também. Muitos sistemas Linux têm um Kernel mais novo com uma correção incluída disponível também. O mesmo se aplica ao Android, cuja correção de segurança de 2 de janeiro de 2018 inclui um patch para esses problemas.
+Por favor, atualize seus sistemas o quanto antes estiver disponível e for possível.</p>
 </article><article id="urn:uuid:a6fc490b-2877-4cbf-afa8-d6e7d4637440" title="Bom ano! - 34C3" href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Bom ano e I2P em 34C3</summary></details><p>Bom ano da equipa do I2P!</p>
-<p>No less than 7 I2P team members did meet at the 34C3 in Leipzig from 27th til 30th december 2017. Beside the <a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" target="_blank">meetings</a> at our table we did meet lots of friends of I2P all over the place. 
-Results of the meetings are posted on <a href="http://zzz.i2p" target="_blank">zzz.i2p</a> already.</p>
-<p>Also we did hand out lots of stickers and gave information about our project to anyone asking. 
-Our annual I2P dinner was a full success as a thank you to all attendees for ongoing support of I2P.</p>
-</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="0.9.32 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 com atualizações do painel</summary></details><p>0.9.32 contains a number of fixes in the router console and associated webapps (addressbook, i2psnark, and susimail).
-We have also changed the way we handle configured hostnames for published router infos, to eliminate some network enumeration attacks via DNS.
-We have added some checks in the console to resist rebinding attacks.</p>
+<p>Não menos que 7 membros do time da I2P se encontraram no 34C3 em Leipzig de 27 a 30 de dezembro de 2017. Além dos <a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" target="_blank">encontros</a> na nossa mesa nós conhecemos vários amigos da I2P por todo o lugar. 
+Resultados dos encontros já estão publicados em <a href="http://zzz.i2p" target="_blank">zzz.i2p</a>.</p>
+<p>Também distribuímos muitos adesivos e demos informações sobre nosso projeto para quem quisesse. Nosso jantar anual I2P foi um sucesso total como um agradecimento a todos os participantes pelo apoio contínuo da I2P.</p>
+</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="0.9.32 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 com atualizações do painel</summary></details><p>A versão 0.9.32 contém várias correções no console do roteador e aplicações web associadas (livro de endereços, i2psnark, e susimail).
+Nós também mudamos a forma como nós lidamos com nomes de host configurados para informações de roteador publicadas, para eliminar alguns ataques de enumeração de rede via DNS.
+Nós adicionamos algumas verificações no console para resistir a ataques de revinculação.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="0.9.31 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>0.9.31 com atualizações do painel</summary></details><p>The changes in this release are much more noticeable than usual!
-We have refreshed the router console to make it easier to understand,
-improved accessibility and cross-browser support,
-and generally tidied things up.
-This is the first step in a longer-term plan to make the router console more user-friendly.
-We have also added torrent ratings and comments support to i2psnark.</p>
+</article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="0.9.31 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>0.9.31 com atualizações do painel</summary></details><p>As mudanças nessa versão são muito mais perceptíveis do que o normal!
+Nós renovamos o console do roteador para torná-lo mais fácil de entender,
+melhoramos a acessibilidade e suporte cross-browser ,
+e organizamos as coisas no geral.
+Esse é um primeiro passo em um plano de mais longo prazo para tornar o console do roteador mais amigável ao usuário.
+Nós também adicionamos suporte a classificações e comentários de torrents ao i2psnark.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:2ce9a846-4d7e-11e7-b788-00163e5e6c1b" title="Chamada para os Tradutores" href="https://www.transifex.com/otf/I2P/announcements/7243/" author="str4d" published="2017-06-10T12:00:00Z" updated="2017-06-10T12:00:00Z"><details><summary>The upcoming 0.9.31 release has more untranslated strings than usual</summary></details><p>In preparation for the 0.9.31 release, which brings with it significant updates
-to the user interface, we have a larger than normal collection of untranslated
-strings that need attention. If you're a translator, we would greatly appreciate
-it if you could set aside a little more time than usual during this release cycle
-in order to bring the translations up to speed. We have pushed the strings early
-to give you three weeks to work on them.</p>
-<p>If you're not currently an I2P translator, now would be a great time to get
-involved! Please see the
-<a href="http://i2p-projekt.i2p/en/get-involved/guides/new-translators" target="_blank">New Translator's Guide</a>
-for information on how to get started.</p>
-</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="0.9.30 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>0.9.30 atualizações para Jetty 9</summary></details><p>0.9.30 contains an upgrade to Jetty 9 and Tomcat 8.
-The previous versions are no longer supported, and are not available in the upcoming Debian Stretch and Ubuntu Zesty releases.
-The router will migrate the jetty.xml configuration file for each Jetty website to the new Jetty 9 setup.
-This should work for recent, unmodified configurations but may not work for modified or very old setups.
-Verify that your Jetty website works after upgrading, and contact us on IRC if you need assistance.</p>
-<p>Several plugins are not compatible with Jetty 9 and must be updated.
-The following plugins have been updated to work with 0.9.30, and your router should update them after restart:
+</article><article id="urn:uuid:2ce9a846-4d7e-11e7-b788-00163e5e6c1b" title="Chamada para os Tradutores" href="https://www.transifex.com/otf/I2P/announcements/7243/" author="str4d" published="2017-06-10T12:00:00Z" updated="2017-06-10T12:00:00Z"><details><summary>A próxima versão 0.9.31 tem mais strings não traduzidas do que o normal</summary></details><p>Em preparação para a versão 0.9.31, que traz consigo atualizações significativas
+à interface de usuário, nós temos uma coleção maior do que o normal de strings
+não traduzidas que precisam de atenção. Se você é um tradutor, nós ficaríamos muito felizes
+se você pudesse reservar um pouco mais de tempo do que o normal durante esse ciclo de lançamento
+para ajustar o ritmo das traduções. Nós disponibilizamos as strings mais cedo
+para dar a você três semanas para trabalhas nelas.</p>
+<p>Se você não é atualmente um tradutor I2P, agora seria um ótimo momento para se envolver! Por favor, veja o
+<a href="http://i2p-projekt.i2p/en/get-involved/guides/new-translators" target="_blank">Novo Guia do Tradutor</a>
+para obter informações sobre como começar.</p>
+</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="0.9.30 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>0.9.30 atualizações para Jetty 9</summary></details><p>A versão 0.9.30 contém uma atualização para o Jetty 9 e para o Tomcat 8.
+As versões anteriores não têm mais suporte, e não estão disponíveis nos futuros lançamentos Debian Stretch e Ubuntu Zesty.
+O roteador migrará o arquivo de configurações jetty.xml para cada website Jetty para a nova configuração do Jetty 9.
+Isso deve funcionar para configurações recentes e não modificadas, mas pode não funcionar para configurações modificadas ou muito antigas.
+Verifique que seu website Jetty funciona após atualizar, e nos contate no IRC se você precisar de assistência.</p>
+<p>Diversos plugins não são compatíveis com o Jetty 9 e precisam ser atualizados.
+Os seguintes plugins foram atualizados para funcionar com a 0.9.30, e seu roteador deve atualizá-los após reiniciar:
 i2pbote 0.4.6; zzzot 0.15.0.
-The following plugins (with current versions listed) will not work with 0.9.30.
-Contact the appropriate plugin developer for the status of new versions:
+Os seguintes plugin (com as versões atuais listadas) não funcionarão com a 0.9.30.
+Entre em contato com o desenvolvedor apropriado do plugin para o status das novas versões:
 BwSchedule 0.0.36; i2pcontrol 0.11.</p>
-<p>This release also supports migration of old (2014 and earlier) DSA-SHA1 hidden services to the more-secure EdDSA signature type.
-See <a href="http://zzz.i2p/topics/2271">zzz.i2p</a> for further information, including a guide and FAQ.</p>
-<p>Note: On non-Android ARM platforms such as the Raspberry Pi, the blockfile database will upgrade on restart, which may take several minutes.
-Please be patient.</p>
+<p>Esta versão também oferece suporte à migração de serviços ocultos DSA-SHA1 antigos (2014 e anteriores) para o tipo de assinatura EdDSA mais seguro. Ver <a href="http://zzz.i2p/topics/2271">zzz.i2p</a> para obter mais informações, incluindo um guia e perguntas frequentes.</p>
+<p>Nota: Em plataformas ARM não Android, como o Raspberry Pi, o banco de dados blockfile será atualizado na reinicialização, o que pode levar vários minutos. Por favor, seja paciente.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="0.9.29 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29 contém correções de erros</summary></details><p>0.9.29 contains fixes for numerous Trac tickets, including workarounds for corrupt compressed messages.
-We now support NTP over IPv6.
-We've added preliminary Docker support.
-We now have translated man pages.
-We now pass same-origin Referer headers through the HTTP proxy.
-There are more fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
-<p>As usual, we recommend that all users update to this release.
-The best way to help the network and stay secure is to run the latest release.</p>
-</article><article id="urn:uuid:cb742cac-df38-11e6-aed3-00163e5e6c1b" title="I2P - Vulnerabilidade de Segurança Bote" href="http://bote.i2p/news/0.4.5/" author="str4d" published="2017-01-20T12:00:00Z" updated="2017-01-20T12:00:00Z"><details><summary>I2P - Vulnerabilidade de Segurança Bote</summary></details><p>I2P-Bote 0.4.5 fixes a security vulnerability present in all earlier versions of the
-I2P-Bote plugin. The Android app was not affected.</p>
-<p>When showing emails to the user, most fields were being escaped. However, the filenames
-of attachments were not escaped, and could be used to execute malicious code in a browser
-with JavaScript enabled. These are now escaped, and additionally a Content Security Policy
-has been implemented for all pages.</p>
-<p>All I2P-Bote users will be upgraded automatically the first time they restart their router
-after I2P 0.9.29 is released in mid-February. However, for safety we recommend that you
-<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
-upgrade manually if you plan on using I2P or I2P-Bote in the intervening time.</p>
-</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="0.9.28 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>0.9.28 contém correções erro</summary></details><p>0.9.28 contains fixes for over 25 Trac tickets, and updates for a number of bundled software packages including Jetty.
-There are fixes for the IPv6 peer testing feature introduced last release.
-We continue improvements to detect and block peers that are potentially malicious.
-There are preliminary fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
-<p>I2P will be at 33C3, please stop by our table and give us your ideas on how to improve the network.
-We will review our 2017 roadmap and priorities 2017 at the Congress.</p>
-<p>As usual, we recommend that all users update to this release.
-The best way to help the network and stay secure is to run the latest release.</p>
-</article><article id="urn:uuid:00015ff6-b556-11e6-adb4-00163e5e6c1a" title="I2P - Vulnerabilidade de Segurança Bote" href="http://bote.i2p/news/0.4.4/" author="str4d" published="2016-11-28T12:00:00Z" updated="2016-11-28T12:00:00Z"><details><summary>I2P - Vulnerabilidade de Segurança Bote</summary></details><p>I2P-Bote 0.4.4 fixes a security vulnerability present in all earlier versions of the
-I2P-Bote plugin. The Android app was not affected.</p>
-<p>A lack of CSRF protection meant that if a user was running I2P-Bote and then loaded a
-malicious site in a browser with JavaScript enabled, the adversary could trigger actions
-in I2P-Bote on behalf of the user, such as sending messages. This might also have enabled
-extraction of private keys for I2P-Bote addresses, however no proof-of-exploit was tested
-for this.</p>
-<p>All I2P-Bote users will be upgraded automatically the first time they restart their router
-after I2P 0.9.28 is released in mid-December. However, for safety we recommend that you
-<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
-upgrade manually if you plan on using I2P or I2P-Bote in the intervening time. You should
-also consider generating new I2P-Bote addresses if you regularly browse sites with
-JavaScript enabled while running I2P-Bote.</p>
+</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="0.9.29 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29 contém correções de erros</summary></details><p>A versão 0.9.29 contém correções para diversos tickets Trac, incluindo alternativas para mensagens compactadas corrompidas.
+Nós agora suportamos NTP sobre IPv6.
+Nós adicionamos suporte preliminar ao Docker.
+Nós agora traduzimos as páginas de manual.
+Nós agora passamos headers Referer same-origin pelo proxy HTTP.
+Há mais correções para o Java 9, embora nós ainda não recomendemos o Java 9 para uso geral.</p>
+<p>Como de costume, recomendamos que todos os usuários atualizem para esta versão. A melhor maneira de ajudar a rede e manter-se segura é executar a versão mais recente.</p>
+</article><article id="urn:uuid:cb742cac-df38-11e6-aed3-00163e5e6c1b" title="I2P - Vulnerabilidade de Segurança Bote" href="http://bote.i2p/news/0.4.5/" author="str4d" published="2017-01-20T12:00:00Z" updated="2017-01-20T12:00:00Z"><details><summary>I2P - Vulnerabilidade de Segurança Bote</summary></details><p>O I2P-Bote 0.4.4 corrige uma vulnerabilidade de segurança presente em todas as versões anteriores doplug-in I2P-Bote. O aplicativo para Android não foi afetado.</p>
+<p>Ao mostrar emails para o usuário, a maioria dos campos estava sendo escapada. Contudo, os nomes de arquivos
+dos anexos não eram escapados, e poderiam ser usados para executar código malicioso em um navegador
+com JavaScript habilitado. Eles agora estão escapados, e adicionalmente a isso uma Política de Segurança de Conteúdo
+foi implementada para todas as páginas.</p>
+<p>Todos os usuários do I2P-Bote serão atualizados automaticamente na primeira vez que eles reiniciarem seu roteador
+após a versão 0.9.29 da I2P ser lançada na metade de fevereiro. Todavia, por segurança nós recomendamos que você
+<a href="http://bote.i2p/install/">siga as instruções na página de instalação</a> para
+atualizar manualmente se você planeja usar a I2P ou o I2P-Bote no meio-tempo.</p>
+</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="0.9.28 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>0.9.28 contém correções erro</summary></details><p>A versão 0.9.28 contém correções para mais de 25 tickets Trac, e atualizações para vários pacotes de software embutidos incluindo o Jetty.
+Há correções para a funcionalidade de teste de par IPv6 introduzida no último lançamento.
+Nós damos continuidade a melhorias para detectar e bloquear pares que sejam potencialmente maliciosos.
+Há correções preliminares para Java 9, embora nós ainda não recomendemos o Java 9 para uso geral.</p>
+<p>I2P estará em 33C3, por favor, pare em nossa mesa e nos dê suas ideias sobre como melhorar a rede. Revisaremos nosso roteiro de 2017 e nossas prioridades para 2017 no Congresso.</p>
+<p>Como de costume, recomendamos que todos os usuários atualizem para esta versão. A melhor maneira de ajudar a rede e manter-se segura é executar a versão mais recente.</p>
+</article><article id="urn:uuid:00015ff6-b556-11e6-adb4-00163e5e6c1a" title="I2P - Vulnerabilidade de Segurança Bote" href="http://bote.i2p/news/0.4.4/" author="str4d" published="2016-11-28T12:00:00Z" updated="2016-11-28T12:00:00Z"><details><summary>I2P - Vulnerabilidade de Segurança Bote</summary></details><p>O I2P-Bote 0.4.4 corrige uma vulnerabilidade de segurança presente em todas as versões anteriores doplug-in I2P-Bote. O aplicativo para Android não foi afetado.</p>
+<p>Uma ausência de proteção contra CSRF significava que se um usuário estava executando o I2P-Bote e então carregava um
+site malicioso em um navegador com JavaScript habilitado, o adversário poderia disparar ações
+no I2P-Bote em nome do usuário, tais como enviar mensagens. Isso pode ter permitido também
+a extração de chaves privadas para endereços I2P-Bote, contudo, nenhuma prova de exploração foi testada
+para isso.</p>
+<p>Todos os usuários do I2P-Bote serão atualizados automaticamente na primeira vez que eles reiniciarem seu roteador
+após a versão 0.9.28 da I2P ser lançada na metade de dezembro. Contudo, por segurança nós recomendamos que você
+<a href="http://bote.i2p/install/">siga as instruções na página de instalação</a> para
+atualizar manualmente se você planeja usar a I2P ou o I2P-Bote no meio-tempo. Você deveria
+também considerar gerar novos endereços I2P-Bote se você navega por sites regularmente com
+JavaScript habilitado enquanto executa o I2P-Bote.</p>
 </article><article id="urn:uuid:c1d01ac3-81e7-4acd-bacd-d9178089e8c3" title="Lançada a versão 0.9.27" href="http://i2p-projekt.i2p/en/blog/post/2016/10/17/0.9.27-Release" author="zzz" published="2016-10-17T12:00:00Z" updated="2016-10-17T12:00:00Z"><details><summary>A versão 0.9.27 contém correções de erros</summary></details><p>0.9.27 contém algumas correções de erros.
 Biblioteca GMP atualizada para aceleração de encriptação, que foi incorporada no lançamento da versão 0.9.26 apenas para novas instalações e compilações Debian, está agora incluída na atualização de rede para a versão 0.9.27.
 Existem alguns melhoramentos no transporte de IPv6, teste de peer SSU, e modo ocultado.</p>
-<p>We updated a number of plugins during <a href="http://i2p-projekt.i2p/en/blog/post/2016/06/01/I2P-Summer-Dev">I2P Summer</a> and your router will automatically update them after restart.</p>
-<p>As usual, we recommend that all users update to this release.
-The best way to help the network and stay secure is to run the latest release.</p>
-</article><article id="urn:uuid:7e818120-88f8-401a-88fe-8db4ba20ad4d" title="I2P Stack Exchange proposal" href="https://area51.stackexchange.com/proposals/99297/i2p" author="zzz" published="2016-06-07T13:00:00Z" updated="2016-06-07T13:00:00Z"><details><summary>I2P is now a proposed site on Stack Exchange!</summary></details><p>I2P is now a proposed site on Stack Exchange!
-Please <a href="https://area51.stackexchange.com/proposals/99297/i2p">commit to using it</a> so the beta phase can begin.</p>
-</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="0.9.26 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>0.9.26 contains crypto updates, Debian packaging improvements, and bug fixes</summary></details><p>0.9.26 contains a major upgrade to our native crypto library,
-a new addressbook subscription protocol with signatures,
-and major improvements to the Debian/Ubuntu packaging.</p>
-<p>For crypto, we have upgraded to GMP 6.0.0, and added support for newer processors,
-which will speed up crypto operations considerably.
-Also, we are now using constant-time GMP functions to prevent side-channel attacks.
-For caution, the GMP changes are enabled for new installs and Debian/Ubuntu builds only;
-we will include them for in-net updates in the 0.9.27 release.</p>
-<p>For Debian/Ubuntu builds, we have added dependencies on several packages,
-including Jetty 8 and geoip, and removed the equivalent bundled code.</p>
-<p>There's a collection of bug fixes also, including a fix for a timer bug
-that caused instability and performance degradations over time.
-As usual, we recommend that all users update to this release.
-The best way to help the network and stay secure is to run the latest release.</p>
-</article><article id="urn:uuid:c6f7228d-3330-4422-a651-ef9d8ca3484b" title="0.9.25 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2016/03/22/0.9.25-Release" author="zzz" published="2016-03-22T12:00:00Z" updated="2016-03-22T12:00:00Z"><details><summary>A versão 0.9.25 contém SAM 3.3, códigos QR, e correções de erros</summary></details><p>0.9.25 contains a major new version of SAM, v3.3, to support sophisticated multiprotocol applications.
-It adds QR codes for sharing hidden service addresses with others,
-and "identicon" images for visually distinguishing addresses.</p>
-<p>We've added a new "router family" configuration page in the console,
-to make it easier to declare that your group of routers is run by a single person.
-There are several changes to increase the capacity of the network and hopefully improve tunnel build success.</p>
-<p>As usual, we recommend that all users update to this release.
-The best way to help the network and stay secure is to run the latest release.</p>
-</article><article id="urn:uuid:8390114d-8e50-45fd-8b4d-3e613bdd034e" title="Lançada a versão 0.9.24" href="http://i2p-projekt.i2p/en/blog/post/2016/01/27/0.9.24-Release" author="zzz" published="2016-01-27T18:00:00Z" updated="2016-01-27T18:00:00Z"><details><summary>0.9.24 contains several bug fixes and speedups</summary></details><p>0.9.24 contains a new version of SAM (v3.2) and numerous bug fixes and efficiency improvements.
-Note that this release is the first to require Java 7.
-Please update to Java 7 or 8 as soon as possible.
-Your router will not automatically update if you are using Java 6.</p>
-<p>To prevent the problems caused by the ancient commons-logging library, we have removed it.
-This will cause very old I2P-Bote plugins (0.2.10 and below, signed by HungryHobo) to crash if they have IMAP enabled.
-The recommended fix is to replace your old I2P-Bote plugin with the current one signed by str4d.
-For more details, see <a href="http://bote.i2p/news/0.4.3">this post</a>.</p>
-<p>We had a great <a href="http://i2p-projekt.i2p/en/blog/post/2016/01/23/32C3">32C3 Congress</a> and are making good progress on our 2016 project plans.
-Echelon gave a talk on I2P's history and current status, and his slides are <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/ccc/2015/I2P_Still_alive.pdf">here</a> (pdf).
-Str4d attended <a href="http://www.realworldcrypto.com/rwc2016/program">Real World Crypto</a> and gave a talk on our crypto migration, 
-his slides are <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/rwc/2016/rwc2016-str4d-slides.pdf">here</a> (pdf).</p>
-<p>As usual, we recommend that all users update to this release.
-The best way to help the network and stay secure is to run the latest release.</p>
-</article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="0.9.23 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>0.9.23 contains a variety of bug fixes, and some minor improvements in I2PSnark</summary></details><p>Hello I2P! This is the first release signed by me (str4d), after 49 releases
-signed by zzz. This is an important test of our redundancy for all things,
-including people.</p>
+<p>Atualizamos uma série de plugins durante <a href="http://i2p-projekt.i2p/en/blog/post/2016/06/01/I2P-Summer-Dev">I2P Verão</a> e seu roteador irá atualizá-los automaticamente após a reinicialização.</p>
+<p>Como de costume, recomendamos que todos os usuários atualizem para esta versão. A melhor maneira de ajudar a rede e manter-se segura é executar a versão mais recente.</p>
+</article><article id="urn:uuid:7e818120-88f8-401a-88fe-8db4ba20ad4d" title="Proposta do I2P Stack Exchange" href="https://area51.stackexchange.com/proposals/99297/i2p" author="zzz" published="2016-06-07T13:00:00Z" updated="2016-06-07T13:00:00Z"><details><summary>I2P é agora um site proposto no Stack Exchange!</summary></details><p>I2P é agora um site proposto no Stack Exchange! Por favor <a href="https://area51.stackexchange.com/proposals/99297/i2p">comprometer-se a usá-lo</a> Assim, a fase beta pode começar.</p>
+</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="0.9.26 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>0.9.26 contém atualizações de criptografia, melhorias no empacotamento Debian e correções de bugs</summary></details><p>0.9.26 contém uma grande atualização para a nossa biblioteca de criptografia nativa, um novo protocolo de assinatura de catálogo de endereços com assinaturas e grandes melhorias para o pacote Debian / Ubuntu.</p>
+<p>Para criptografia, nós atualizamos para o GMP 6.0.0, e adicionamos suporte para novos processadores,
+o que acelerará as operações de criptografia consideravelmente.
+Ainda, nós agora estamos usando funções GMP de tempo constante para prevenir ataques de canal lateral.
+Por precaução, as mudanças de GMP estão habilitadas somente para novas instalações e construções Debian/Ubuntu;
+nós as incluiremos para atualizações em rede no lançamento da versão 0.9.27.</p>
+<p>Para compilações Debian/Ubuntu, adicionamos dependências em vários pacotes, incluindo Jetty 8 e geoip, e removemos o código empacotado equivalente.</p>
+<p>Há ainda uma coleção de correção de bugs, incluindo uma correção para um bug de temporizador
+que causava instabilidade e degradação de desempenho ao longo do tempo.
+Como de costume, nós recomendamos que todos os usuários atualizem para essa versão.
+A melhor forma de ajudar a rede e se manter seguro é executar a versão mais recente.</p>
+</article><article id="urn:uuid:c6f7228d-3330-4422-a651-ef9d8ca3484b" title="0.9.25 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2016/03/22/0.9.25-Release" author="zzz" published="2016-03-22T12:00:00Z" updated="2016-03-22T12:00:00Z"><details><summary>A versão 0.9.25 contém SAM 3.3, códigos QR, e correções de erros</summary></details><p>A versão 0.9.25 contém uma grande nova versão do SAM, v3.3, para dar suporte a aplicações multi protocolo sofisticadas.
+Ela adiciona QR codes para compartilhar endereços de serviços ocultos com os outros,
+e imagens "identicon" para distinguir endereços visualmente.</p>
+<p>Nós adicionamos uma nova página de configuração de "família do roteador" no console,
+para tornar mais fácil declarar que o seu grupo de roteadores é executado por uma única pessoa.
+Há várias mudanças para aumentar a capacidade da rede e, assim se espera, melhorar o sucesso de construção de túneis.</p>
+<p>Como de costume, recomendamos que todos os usuários atualizem para esta versão. A melhor maneira de ajudar a rede e manter-se segura é executar a versão mais recente.</p>
+</article><article id="urn:uuid:8390114d-8e50-45fd-8b4d-3e613bdd034e" title="Lançada a versão 0.9.24" href="http://i2p-projekt.i2p/en/blog/post/2016/01/27/0.9.24-Release" author="zzz" published="2016-01-27T18:00:00Z" updated="2016-01-27T18:00:00Z"><details><summary>0.9.24 contém várias correções de bugs e acelerações</summary></details><p>A versão 0.9.24 contém uma nova versão do SAM (v3.2) e várias correções de bugs e melhorias de eficiência.
+Note que essa versão é a primeira a requerer Java 7.
+Por favor, atualize para o Java 7 ou 8 o mais breve possível.
+Seu roteador não atualizará automaticamente se você estiver usando Java 6.</p>
+<p>Para prevenir os problemas causados pela antiga biblioteca commons-logging, nós a removemos.
+Isso fará com que plugins muito antigos do I2P-Bote (0.2.10 e anterior, assinados por HungryHobo) travem se eles tiverem IMAP habilitado.
+A correção recomendada é substituir seu antigo plugin do I2P-Bote pelo atual assinado pelo str4d.
+Para mais detalhes, veja <a href="http://bote.i2p/news/0.4.3">esta publicação</a>.</p>
+<p>Nós tivemos um ótimo <a href="http://i2p-projekt.i2p/en/blog/post/2016/01/23/32C3">Congresso 32C3</a> e estamos fazendo um bom progresso nos nossos planos de projeto de 2016.
+O Echelon deu uma palestra sobre a história da I2P e o status atual, e seus slides estão <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/ccc/2015/I2P_Still_alive.pdf">aqui</a> (pdf).
+O Str4d participou do <a href="http://www.realworldcrypto.com/rwc2016/program">Real World Crypto</a> e deu uma palestra sobre nossa migração de criptografia. 
+Seus slides estão <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/rwc/2016/rwc2016-str4d-slides.pdf">aqui</a> (pdf).</p>
+<p>Como de costume, recomendamos que todos os usuários atualizem para esta versão. A melhor maneira de ajudar a rede e manter-se segura é executar a versão mais recente.</p>
+</article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="0.9.23 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>0.9.23 contém uma variedade de correções de bugs, e algumas pequenas melhorias no I2PSnark</summary></details><p>Olá, I2P! Este é o primeiro lançamento assinado por mim (str4d), depois de 49 lançamentos
+assinados pelo zzz. Esse é um teste importante da nossa redundância para todas as coisas,
+incluindo pessoas.</p>
 <p><b>Limpeza</b></p>
-<p>My signing key has been in router updates for over two years (since 0.9.9), so
-if you are on a recent version of I2P this update should be just as easy as
-every other update. However, if you are running an older version than 0.9.9, you
-will first need to manually update to a recent version. Update files for recent
-versions can be downloaded
-<a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/releases/">here</a>,
-and instructions on how to manually update are provided
-<a href="http://i2p-projekt.i2p/en/download#update">here</a>. Once you have manually
-updated, your router will then find and download the 0.9.23 update as usual.</p>
-<p>If you installed I2P via a package manager, you are not affected by the change,
-and can update as usual.</p>
+<p>A minha chave de assinatura esteve em atualizações do roteador por mais de dois anos (desde a versão 0.9.9), então
+se você está em uma versão recente da I2P essa atualização deve ser tão fácil quanto
+qualquer outra. Todavia, se você estiver executando uma versão mais antiga do que a 0.9.9, você
+precisará primeiro atualizar manualmente para uma versão mais recente. Arquivos de atualização para versões
+recentes podem ser baixados
+<a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/releases/">aqui</a>,
+e instruções de como atualizar manualmente são providenciadas
+<a href="http://i2p-projekt.i2p/en/download#update">aqui</a>. Uma vez que você tenha atualizado
+manualmente, seu roteador então encontrará e baixará a atualização 0.9.23 como de costume.</p>
+<p>Se você instalou o I2P através de um gerenciador de pacotes, você não é afetado pela alteração e pode atualizar como de costume.</p>
 <p><b>Detalhes da atualização</b></p>
-<p>The migration of RouterInfos to new, stronger Ed25519 signatures is going well,
-with at least half of the network already estimated to have rekeyed. This
-release accelerates the rekeying process. To reduce network churn, your router
-will have a small probability of converting to Ed25519 at each restart. When it
-does rekey, expect to see lower bandwidth usage for a couple of days as it
-reintegrates into the network with its new identity.</p>
-<p>Note that this will be the last release to support Java 6. Please update to
-Java 7 or 8 as soon as possible. We are already working to make I2P compatible
-with the upcoming Java 9, and some of that work is in this release.</p>
-<p>We have also made some minor improvements in I2PSnark, and added a new page in
-the routerconsole for viewing older news items.</p>
+<p>A migração de informações de roteador para novas e mais fortes assinaturas Ed25519 está indo bem,
+com pelo menos metade da rede já estimada a ter rechaveado. Esse
+lançamento acelera o processo de rechaveamento. Para reduzir a agitação na rede, seu roteador
+terá uma pequena probabilidade de converter para Ed25519 a cada reinício. Quando ele
+rechavear, espere ver uso de banda reduzido por alguns dias enquanto ele se
+reintegra à rede com sua nova identidade.</p>
+<p>Note que essa será a última versão a suportar Java 6. Por favor, atualize para
+o Java 7 ou 8 o mais breve possível. Nós já estamos trabalhando em tornar a I2P compatível
+com o futuro Java 9, e um pouco desse trabalho está nesse lançamento.</p>
+<p>Também fizemos algumas pequenas melhorias no I2PSnark e adicionamos uma nova página noconsole do roteador para visualizar notícias mais antigas.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="Lançada a versão 0.9.22" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 with bug fixes and starts Ed25519 migration</summary></details><p>0.9.22 contains fixes for i2psnark getting stuck before completion, and begins the migration of router infos to new, stronger Ed25519 signatures.
-To reduce network churn, your router will have only a small probability of converting to Ed25519 at each restart.
-When it does rekey, expect to see lower bandwidth usage for a couple of days as it reintegrates into the network with its new identity.
-If all goes well, we will accelerate the rekeying process in the next release.</p>
-<p>I2PCon Toronto was a big success!
-All the presentations and videos are listed on the <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">I2PCon page</a>.</p>
+</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="Lançada a versão 0.9.22" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 com correções de bugs e inicia a migração Ed25519</summary></details><p>A versão 0.9.22 contém correções para o i2psnark ficando travado antes da finalização, e inicia a migração das informações de roteador para novas e mais fortes assinaturas Ed25519.
+Para reduzir a agitação na rede, seu roteador terá uma pequena probabilidade de converter para Ed25519 a cada reinício.
+Quando ele rechavear, espere ver uso de banda mais baixo por alguns dias enquanto ele se reintegra à rede com sua nova identidade.
+Se tudo ocorrer bem, nós aceleraremos o processo de rechaveamento no próximo lançamento.</p>
+<p>I2PCon Toronto foi um grande sucesso! Todas as apresentações e vídeos estão listados no <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">Página I2PCon</a>.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
 </article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="Lançada a versão 0.9.21" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>Versão 0.9.21 lançada com melhorias de desempenho e correções de falhas.</summary></details><p>A versão 0.9.21 contém diversas modificações que adicionam capacidade a rede, aumentam a eficiência das inundações,
 e usam a banda de maneira mais eficiente.

data/translations/entries.pt_BR.html

@@ -1,83 +1,234 @@
 <div>
-<header title="Notícias no I2P">Feed de notícias e atualizações do roteador</header><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
-<p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
+<header title="Notícias da I2P">Feed de notícias e atualizações do roteador</header><article id="urn:uuid:f2a6aabd-ee29-4f45-a8dd-7378e907016a" title="Versão 2.9.0 Lançada" href="http://i2p-projekt.i2p/en/blog/post/2025/06/02/2.9.0_released" author="idk" published="2025-06-02T19:00:00Z" updated="2025-06-02T19:00:00Z"><details><summary>Versão 2.9.0 da I2P</summary></details><p>A versão 2.9.0 da I2P é uma versão de manutenção que inclui correções de bugs e trabalho em novas funcionalidades.</p>
+<p>O uso de thread foi aprimorado para melhorar o desempenho do sistema i2ptunnel.
+O NTCP2 foi aprimorado para resistir a ataques de probing.
+O sistema de notificação foi integrado em mais aplicações para oferecer melhor feedback aos usuários do I2PSnark e das outras aplicações.
+A participação automática em floodfill foi corrigida.
+Os usuários podem observar uso de recursos mais elevado quando atuando como floodfill.
+Se isso não é desejado, o modo floodfill pode ser desabilitado na página /config.</p>
+<p>Uma nova funcionalidade de mapa global está disponível no console que mostra as localizações dos roteadores na sua visão do BD de rede.
+Eles são os pares que ajudam o seu roteador a construir túneis e oferecer serviços anonimamente.</p>
+<p>O trabalho continua em implementar gerenciamento de banda automático para túneis, o protocolo Datagram2 e criptografia pós-quântica.
+Em dois lançamentos, na versão 2.11.0, a I2P irá requerer Java 17.</p>
+<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
+</article><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="Versão 2.8.2 Lançada" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>Versão 2.8.2 da I2P</summary></details><p>A versão 2.8.2 corrige um bug que causa falhas de SHA256 que foi introduzido na versão 2.8.1.
+O bug afetou principalmente roteadores de alta largura de banda.</p>
+<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
+</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="Versão 2.8.1 Lançada" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>Versão 2.8.1 da I2P</summary></details><p>A versão 2.8.1 conserta acessos a sites locais que estavam quebrados na 2.8.0.
+Adicionamos bolhas de notificação em várias aplicações no painel para destacar mensagens da aplicação.
+Corrigimos um bug de teste de túnel que pode ter estado afetando a estabilidade de túnel.
+O catálogo de endereços agora possui uma nova aba "mais recente" que exibe os mais novos nomes de domínio adicionados de suas inscrições.
+Há várias correções e melhorias para tema escuro.</p>
+<p>Corrigimos o instalador que previamente falhava no Java 21 ou mais recente.
+Também corrigimos instalar em caminhos de diretórios que contêm espaços em Linux.
+Para aqueles de vocês que usam Docker, nós atualizamos bibliotecas e contêiner desatualizados do Docker.</p>
+<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
+</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Acesso a site local falha na 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>Bug de Acesso Local da 2.8.0</summary></details><p>Na 2.8.0, navegar para um site local (seja por nome de domínio ou b32) falhará.
+A solução paliativa é usar localhost e a porta do servidor, geralmente 7658, para contornar a I2P.
+Por exemplo, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
+Pedimos desculpas pelo problema e estamos trabalhando em uma correção.</p>
+</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="Versão 2.8.0 da I2P" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>Versão 2.8.0 da I2P</summary></details><p>Esta versão melhora a I2P corrigindo bugs, removendo código inutilizado e melhorando a estabilidade de rede.</p>
+<p>Aprimoramos o tratamento de roteadores congestionados na rede.
+Problemas com UPnP e NAT traversal foram tratados para aprimorar a conectividade e o relatório de erros.
+Nós agora temos uma estratégia mais agressiva para a remoção de leasesets do BD de rede para melhorar o desempenho do roteador e mitigar sobrecargas.
+Outras mudanças foram implantadas para reduzir a observabilidade de eventos como um roteador reiniciando ou desligando.</p>
+<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
+</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="Lançamento I2P 2.7.0" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>Lançamento I2P 2.7.0</summary></details><p>Esta versão, I2P 2.7.0, continua nosso trabalho corrigindo bugs, melhorando o desempenho e adicionando recursos.</p>
+<p>O acesso às informações do console e dos aplicativos foi aprimorado. Foram corrigidos problemas na pesquisa do I2PSnark e do SusiMail. A pesquisa netDB incorporada no console do roteador agora opera de maneira mais intuitiva e útil. Pequenas melhorias foram feitas nas telas de diagnóstico no modo avançado.</p>
+<p>Bugs também foram corrigidos para melhorar a compatibilidade dentro da rede. Um problema com a publicação de leaseSets foi resolvido, o que melhora a confiabilidade dos principais serviços ocultos. O I2PSnark não altera mais o infohash quando um usuário altera apenas os rastreadores em um torrent existente. Isso evita que os torrents sejam desnecessariamente interrompidos por essas mudanças. Congratulamo-nos com esta contribuição de um novo colaborador. Um conflito no tratamento de uma opção de biblioteca de streaming foi resolvido para melhorar a compatibilidade com outras implementações I2P.</p>
+<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
+</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="Versão 2.6.1 da I2P Lançada" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>Versão 2.6.1 da I2P</summary></details><p>A I2P 2.6.1 é lançada para corrigir um bug de Interface de Usuário na aplicação Gerenciador de Serviços Ocultos.
+Esse bug fazia com que a rolagem ficasse desabilitada, tornando algumas configurações inacessíveis.</p>
+<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
+</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="Versão 2.6.0 da I2P Lançada" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>Versão 2.6.0 da I2P</summary></details><p>Esta versão, I2P 2.6.0, dá continuidade ao nosso trabalho de corrigir bugs, adicionar funcionalidades, e aprimorar a confiabilidade da rede.</p>
+<p>Roteadores mais novos serão favorecidos ao escolher roteadores de floodfill.
+A I2PSnark recebeu funcionalidades que aprimoram o desempenho de PeX (Troca de pares), em adição a correções de bugs.
+Protocolos de transporte depreciados estão sendo removidos, simplificando o código nos transportes UDP.
+Destinos hospedados localmente serão alcançáveis por clientes locais sem solicitar seus LeaseSets, melhorando desempenho e testabilidade.
+Ajustes adicionais foram feitos nas estratégias de seleção de par.</p>
+<p>A I2P não mais permite I2P-sobre-Tor. Conexões a partir de endereços IP de saída do Tor são agora bloqueadas.
+Nós desencorajamos isso porque degrada o desempenho da I2P e usa os recursos das saídas do Tor sem gerar benefícios.
+Se você é uma pessoa que ajuda executando tanto uma saída do Tor quanto a I2P, nós encorajamos você a continuar fazendo isso, usando endereços IP diferentes para cada um.
+Relays que não são de saída e clientes Tor não são afetados por isso e não precisam mudar nada.</p>
+<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
+</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="Versão 2.5.2 da I2P Lançada" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 com correção de HTTP</summary></details><p>A I2P 2.5.2 é lançada para corrigir um bug introduzido na versão 2.5.0 que causava truncamento de alguns conteúdos HTTP. </p>
+<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
+</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="Versão 2.5.1 da I2P Lançada" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>Versão 2.5.1 da I2P lançada para tratar dos Ataques de Negação de Serviço</summary></details><p>A I2P 2.5.1 é lançada para tratar dos Ataques de Negação de Serviço afetando a rede e os serviços I2P.
+Com este lançamento nós desabilitamos as partes baseadas em IP da ferramenta de detecção de ataque Sybil que foram alvo para amplificar o efeito e a duração do ataque.
+Isso deve ajudar a rede a retornar a operação normal.
+Aqueles de vocês que desabilitaram a ferramenta de detecção de ataque Sybil podem reabilitá-la com segurança.
+Ajustes a outros subsistemas para aprimorar a validação de RouterInfo e seleção de par também foram realizados.</p>
+<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
+</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Clima Tempestuoso" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Clima da Rede: Tempestuoso. A I2P está sob ataque.</summary></details><p>A rede I2P no momento está sob um ataque de Negação de Serviço.
+Esse ataque afeta a I2P e a i2pd, mas de diferentes formas, e está tendo um sério efeito na saúde da rede.
+A alcançabilidade de sites I2P está gravemente degradada.</p>
+<p>Se você está hospedando um serviço dentro da I2P e ele está hospedado em um roteador de Floodfill, você deveria considerar fazer multihoming do serviço em um roteador com função de Floodfill desabilitada para melhorar a alcançabilidade.
+Outras mitigações estão sendo discutidas, mas ainda se está trabalhando em uma solução retrocompatível e de longo prazo.</p>
+</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="Nova versão I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>Mais melhorias na aplicação, revisão da estratégia de isolamento de BD de rede</summary></details><p>Esta versão, I2P 2.5.0, fornece mais melhorias visíveis ao usuário do que a versão 2.4.0, que foi focada na implementação da estratégia de isolamento do BD de rede.</p>
+<p>Novas funcionalidades foram adicionadas ao I2PSnark, como a possibilidade de pesquisar torrents.
+Bugs foram resolvidos para melhorar a compatibilidade com outros clientes de torrents I2P como o BiglyBT e o qBittorrent.
+Nós gostaríamos de agradecer a todos os desenvolvedores que trabalharam com a libtorrent e com o qBittorrent para proporcionar e melhorar seu suporte à I2P.
+Novas funcionalidades também foram adicionadas ao SusiMail, incluindo suporte a formatação Markdown em emails e a habilidade de arrastar e soltar anexos nos emails.
+Túneis criados com o gestor de Serviços Ocultos agora têm suporte a "Keepalive", o que melhora o desempenho e a compatibilidade com tecnologias web, permitindo sites I2P mais sofisticados.</p>
+<p>Durante essa versão nós também fizemos vários ajustes no BD de rede para melhorar sua resiliência a spam e para melhorar a capacidade do roteador de rejeitar mensagens suspeitas.
+Isso foi parte de um esforço para "revisar" a implementação de defesas de "Isolamento Sub-DB de rede" da versão 2.4.0.
+Essa investigação descobriu um pequeno evento de perfuração do isolamento, o que qual nós consertamos.
+Esse problema foi descoberto e resolvido internamente pelo time da I2P.</p>
+<p>Durante essa versão várias melhorias foram feitas no processo de lançamento das nossas distribuições downstream para Android e Windows.
+Isso deve resultar em uma melhor entrega e disponibilidade desses produtos downstream.</p>
+<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
+</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="Versão I2P 2.4.0 com melhorias de congestionamento e segurança do NetDB" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>Versão I2P 2.4.0 com melhorias de congestionamento e segurança do NetDB</summary></details><p>Esta versão, I2P 2.4.0, continua nosso esforço de melhorar a segurança e estabilidade da rede I2P.
+Ela contém melhorias significativas ao BD de rede, uma estrutura essencial dentro da rede I2P usada para descobrir seus pares.</p>
+<p>As mudanças no tratamento de congestão aperfeiçoarão a estabilidade da rede dando aos roteadores a possibilidade de aliviar pares congestionados evitando-os.
+Isso ajudará a rede a limitar a efetividade de spam de túnel.
+Isso também vai ajudar a rede a se regenerar durante e após ataques DDOS.</p>
+<p>As mudanças do BD de rede também ajudam a proteger roteadores individuais e as aplicações que os utilizam. 
+Roteadores agora podem se defender conta atacantes separando o BD de rede em vários "Sub-BDs", os quais nós utilizamos para prevenir vazamentos de informação entre aplicações e o roteador.
+Isso também aperfeiçoa a informação disponível aos roteadores Java sobre sua atividade de BD de rede e simplifica nosso suporte a aplicações multihoming.</p>
+<p>Também estão incluídas uma série de correções de bugs e melhorias nos aplicativos I2PSnark e SusiMail.</p>
+<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
+</article><article id="urn:uuid:" title="Nova versão I2P 2.3.0 - Correções de segurança, listas de bloqueio ajustáveis, API DTG" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Correções de segurança, listas de bloqueio ajustáveis, API DTG</summary></details><p>Essa versão contém correções para o CVE-2023-36325.
+O CVE-2023-36325 é um bug de confusão de contexto que ocorria no filtro de Bloom.
+Um atacante cria uma mensagem I2NP contendo um messageID único, e envia esse messageID para um cliente.
+A mensagem, após passar pelo filtro de Bloom, não é permitida ser reusada em uma segunda mensagem.
+O atacante então envia a mesma mensagem diretamente para o roteador.
+O roteador passa a mensagem para o filtro de Bloom, e é descartada.
+Isso vaza a informação de que o messageID já foi visto antes, dando ao atacante um forte motivo para acreditar que o roteador está hospedando o cliente.
+Isso foi corrigido separando a funcionalidade do filtro de Bloom em diferentes contextos com base em se uma mensagem chegou por um túnel de cliente, um túnel exploratório, ou foi enviada diretamente ao roteador.
+Sob circunstâncias normais, esse ataque leva vários dias para ter sucesso e pode ser confundido por vários outros fatores, tais como roteadores reiniciarem durante a fase do ataque e sensibilidade a falsos positivos.
+Recomenda-se que usuários da I2P Java atualizem a versão imediatamente para evitarem o ataque.</p>
+<p>No curso da correção desse bug de confusão de contexto, nós revisamos algumas de nossas estratégias de desenvolver código defensivamente, contra esses tipos de vazamentos.
+Isso inclui ajustes ao BD de rede, os mecanismos de limite de taxa, e o comportamento dos roteadores de floodfill.</p>
+<p>Essa versão adiciona o not_bob como um segundo provedor de hosts padrão, e adiciona o <a href="http://notbob.i2p">notbob.i2p</a> e o <a href="http://ramble.i2p">ramble.i2p</a> à página inicial do console.</p>
+<p>Essa versão também contém uma lista de bloqueio ajustável.
+Bloquear pela lista de bloqueio é semi permanente. Cada endereço IP bloqueado normalmente fica bloqueado até que o roteador seja reiniciado.
+Usuários que observarem crescimento explosivo da lista de bloqueio durante ataques Sybil podem optar por limites de tempo mais curtos configurando a lista de bloqueio para expirar entradas a um intervalo.
+Essa funcionalidade é desabilitada por padrão e só é recomendada para usuários avançados neste momento.</p>
+<p>Essa versão também inclui uma API para plugins modificarem com a GUI de Destkop (DTG).
+Agora é possível adicionar itens de menu à área de notificação do sistema, permitindo a inicialização mais intuitiva de plugins que usam interfaces nativas de aplicação.</p>
+<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
+</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="Nova versão 2.2.1, correções de empacotamento para Docker, Ubuntu Lunar e Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - versão de manutenção para 2.2.0</summary></details><p>Após o lançamento da I2P versão 2.2.0, que foi empurrada para frente para acelerar mitigações aos ataques DDOS, nós descobrimos alguns problemas de desenvolvimento que tornaram necessário construir e lançar novos pacotes.
+Essa versão corrige um problema no Ubuntu Lunar e no Debian Sid onde o console do roteador estava inacessível usando uma versão atualizada do pacote jakarta.
+Os pacotes Docker não estavam lendo argumentos corretamente, resultando em arquivos de configuração inacessíveis.
+Esse problema também foi resolvido.
+O contêiner docker é agora também compatível com o Podman.</p>
+<p>Esta versão sincroniza traduções com transifex e atualiza o banco de dados GeoIP.</p>
+<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
+</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="Nova versão 2.2.0, Mitigações para ataques DDOS e ajustes no subsistema Streaming" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Atenuações para ataques DDOS e ajustes no subsistema Streaming</summary></details><p>Optamos por antecipar a data de lançamento da versão 2.2.0, que ocorrerá hoje, 13 de março de 2023. Esta versão inclui alterações nos componentes NetDB, Floodfill e Peer-Selection que melhoram a capacidade do roteador de sobreviver a ataques DDOS. É provável que os ataques continuem, mas as melhorias nesses sistemas ajudarão a mitigar o risco de ataques DDOS, ajudando o roteador a identificar e despriorizar roteadores que parecem maliciosos.</p>
+<p>Essa versão também adiciona proteção contra repetição ao subsistema de Streaming, o que evita que um atacante que consiga capturar um pacote criptografado possa reusá-lo enviando-o para destinatários indesejados.
+Essa é uma mudança retrocompatível, então roteadores mais antigos continuarão sendo capazes de usar as capacidades de streaming de roteadores mais novos.
+Esse problema foi descoberto e resolvido internamente, pelo time de desenvolvimento da I2P, e não está relacionado aos ataques DDOS.
+Nós nunca encontramos um pacote de streaming repetido e não acreditamos que um ataque de repetição de streaming tenha algum dia acontecido contra a rede I2P neste momento.</p>
+<p>Como você pode ter notado, estas notas de lançamento e o lançamento da versão em si foram assinados pelo idk, e não pelo zzz.
+O zzz decidiu deixar o projeto e suas responsabilidades estão sendo apropriadas por outros membros do time.
+Como tal, o projeto está trabalhando em substituir a infraestrutura de estatísticas de rede e mover o fórum de desenvolvimento para i2pforum.i2p.
+Nós agradecemos ao zzz por fornecer esses serviços por tanto tempo.</p>
+<p>Como de costume, recomendamos que você atualize para esta versão. A melhor maneira de manter a segurança e ajudar a rede é executar a versão mais recente.</p>
+</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="Atualização de DDoS" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>Atualização de DDoS</summary></details><p>Nós confirmamos que o atacante controla um grande número de roteadores.
+Nossas investigações e mitigações continuam.</p>
+<p>Esse é um bom momento para lembrar as pessoas de que mesmo após 20 anos, a rede I2P é relativamente pequena.
+Nós não temos indícios de que o atacante está tentando desanonimizar algum usuário ou serviço oculto em particular.
+Todavia, se seu modelo de risco é de alto risco, você deve considerar cuidadosamente se a I2P atualmente oferece a proteção que você requer.
+A melhor solução a longo prazo é divulgar e fazer crescer a rede I2P para aumentar a segurança de nossos usuários.</p>
+<p>Nós providenciaremos informações adicionais aqui no feed de notícias e em <a href="http://zzz.i2p">zzz.i2p</a> conforme necessário.
+Nós pedimos a sua paciência enquanto trabalhamos para melhorar a I2P.</p>
+</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="Sobre os recentes ataques de Negação de Serviço" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>A I2P continua intacta com desempenho prejudicado</summary></details><p>A rede I2P está atualmente sendo afetada por um ataque de Negação de Serviço.
+  A função de floodfill da rede foi afetada, resultando em respostas sendo prejudicadas e taxas de sucesso de construção de túnel caindo.
+  Participantes na rede têm sofrido dificuldades ao conectar a sites I2P e ao usar serviços I2P.
+  Estratégias de mitigação estão sendo investigadas e implementadas gradualmente.</p>
+<p>Embora o ataque tenha degradado o desempenho, a rede segue intacta e usável.
+  Roteadores I2P Java parecem estar lidando com esses problemas melhor do que os roteadores i2pd por agora.
+  Várias mitigações devem começar a aparecer nas construções de desenvolvimento tanto dos roteadores Java quanto dos roteadores C++ na próxima semana.</p>
+</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="Versão 2.1.0 Lançada" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 com diversas correções de SSU2</summary></details><p>Nós descobrimos várias coisas desde a nossa versão 2.0.0 em novembro.
+Conforme os roteadores atualizaram para essa versão, a rede foi de em torno de 1% para mais de 60% de suporte para nosso novo protocolo de transporte SSU2.
+Em primeiro lugar, nós confirmamos que o SSU2 é um protocolo seguro, bem projetado, e sólido.
+Em segundo lugar, contudo, nós encontramos e corrigimos diversos bugs pequenos ou de baixa ocorrência na implementação do protocolo.
+Cumulativamente, os efeitos desses bugs reduziram o desempenho da rede.</p>
+<p>Ainda, nós estamos a par do maior número de túneis e da menor taxa de sucesso de construção de túneis na rede,
+possivelmente causados pela nova funcionalidade do Bitcoin de endereço transiente da I2P,
+mas tornados piores pelos nossos bugs do SSU2 e outros problemas de controle de congestão.
+Nós estamos trabalhando com o Bitcoin e com outros projetos não Bitcoin para reduzir as demandas de rede da I2P.
+Nós aperfeiçoamos nossos algoritmos para reduzir a carga sobre a rede durante momentos de congestão.
+Nós também estamos colaborando com a i2pd para desenvolver estratégias em comum de controle de congestão.</p>
+<p>Portanto, nós aceleramos esse lançamento em cerca de seis semanas, para levar as correções para todo mundo.
+A i2pd lançou sua versão 2.45.0 na semana passada e os resultados iniciais são encorajadores.
+Novos protocolos, e redes distribuídas, são difíceis de desenvolver.
+A congestão pode chegar com pouco aviso e com pouco indício de causa.
+Obrigado por sua paciência enquanto nós diagnosticávamos e, assim se espera, resolvíamos os problemas.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Posts Recentes do Blog" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>
+</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="Versão 2.0.0 Lançada" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>Transporte SSU2 Habilitado</summary></details><p>A I2P versão 2.0.0 habilita nosso novo transporte UDP SSU2 para todos os usuários, após o término de pequenas funcionalidades, testes, e diversas correções de bugs.</p>
+<p>Nós também temos correções por todo o lugar, incluindo instalador, base de dados de rede, adição ao livro de endereços privado, inicializador de navegador do Windows, e UPnP IPV6.</p>
+<p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
+</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Posts Recentes do Blog" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>Alguns posts recentes do blog</summary></details><p>Aqui estão links para diversas publicações recentes no nosso website:</p>
 <ul>
-<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Overview of our new SSU2 transport</a></li>
-<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">A warning about I2P coins and other scams</a></li>
-<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">An interview with Konrad from diva.exchange</a></li>
-<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">An interview with Dustin from StormyCloud</a></li>
-</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 with SSU2 for testing</summary></details><p>We have spent the last three months working on our new UDP transport protocol "SSU2"
-with a small number of volunteer testers.
-This release completes the implementation, including relay and peer testing.
-We are enabling it by default for Android and ARM platforms, and a small percentage of other routers at random.
-This will allow us to do much more testing in the next three months, finish the connection migration feature,
-and fix any remaining issues.
-We plan to enable it for everyone in the next release scheduled for November.
-No manual configuration is necessary.</p>
-<p>Of course, there's the usual collection of bug fixes in this release as well.
-We also added an automatic deadlock detector that has already found a rare deadlock that is now fixed.</p>
+<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Visão geral do nosso novo transporte SSU2</a></li>
+<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">Um aviso sobre moedas I2P e outros golpes</a></li>
+<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">Uma entrevista com o Konrad do diva.exchange</a></li>
+<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">Uma entrevista com o Dustin da StormyCloud</a></li>
+</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="Versão 1.9.0 Lançada" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 com SSU2 para testes</summary></details><p>Nós passamos os últimos três meses trabalhando em nosso novo protocolo de transporte UDP "SSU2"
+com um pequeno número de testadores voluntários.
+Essa versão completa a implementação, incluindo testes de par e de transmissor.
+Nós estamos o habilitando por padrão para as plataformas Android e ARM, e para uma pequena porcentagem de outros roteadores aleatoriamente.
+Isso nos permitirá fazer muito mais testes nos próximos três meses, terminar a funcionalidade de migração de conexão,
+e consertar quaisquer problemas restantes.
+Nós planejamos habilitá-lo para todo mundo no próximo lançamento agendado para novembro.
+Nenhuma configuração manual é necessária.</p>
+<p>Claro, há a coleção usual de correções de bugs nesta versão também. Também adicionamos um detector automático de deadlock que já encontrou um raro deadlock que agora está corrigido.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="New Outproxy exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>New Outproxy</summary></details><p>I2P "outproxies" (exit nodes) may be used to access the internet through
-your HTTP proxy tunnel.
-As approved at our <a href="http://i2p-projekt.i2p/en/meetings/314">monthly meeting</a>,
-<b>exit.stormycloud.i2p</b> is now our official, recommended outproxy, replacing the long-dead <b>false.i2p</b>.
-For more information on the StormyCloud <a href="http://stormycloud.i2p/">organization</a>,
-<a href="http://stormycloud.i2p/outproxy.html">outproxy</a>,
-and <a href="http://stormycloud.i2p/tos.html">terms of service</a>,
-see the <a href="http://stormycloud.i2p/">StormyCloud website</a>.</p>
-<p>We suggest you change your <a href="/i2ptunnel/edit?tunnel=0">Hidden Services Manager configuration</a>
-to specify <b>exit.stormycloud.i2p</b>
-in two places: <b>Outproxies</b> and <b>SSL Outproxies</b>.
-After editing, <b>scroll down and click Save</b>.
-See our <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">blog post for a screenshot</a>.
-For Android instructions and screenshots see <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">notbob's blog</a>.</p>
-<p>Router updates will not update your configuration, you must edit it manually.
-Thanks to StormyCloud for their support, and please consider a <a href="http://stormycloud.i2p/donate.html">donation</a>.</p>
-</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 with bug fixes</summary></details><p>This release includes bug fixes in i2psnark,
-the router, I2CP, and UPnP.
-Router fixes address bugs in soft restart, IPv6, SSU peer testing,
-network database stores, and tunnel building.
-Router family handling and Sybil classification have also been
-significantly improved.</p>
-<p>Together with i2pd, we are developing our new UDP transport, SSU2.
-SSU2 will bring substantial performance and security improvements.
-It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
-completing the full cryptography upgrade we started about 9 years ago.
-This release contains a preliminary implementation which is disabled by default.
-If you wish to participate in testing, please look for current information
-on zzz.i2p.</p>
+</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="Novo Outproxy exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>Novo Outproxy</summary></details><p>"Proxies de saída" (nodos de saída) da I2P podem ser usados para acessar a internet através
+do seu túnel de proxy HTTP.
+Conforme aprovado em nossa <a href="http://i2p-projekt.i2p/en/meetings/314">reunião mensal</a>,
+<b>exit.stormycloud.i2p</b> é agora nosso proxy de saída recomendado e oficial, substituindo o há muito morto <b>false.i2p</b>.
+Para mais informações sobre a <a href="http://stormycloud.i2p/">organização</a>,
+o <a href="http://stormycloud.i2p/outproxy.html">proxy de saída</a>,
+e os <a href="http://stormycloud.i2p/tos.html">termos de serviço</a> da StormyCloud,
+veja o <a href="http://stormycloud.i2p/">website da StormyCloud</a>.</p>
+<p>Nós sugerimos que você modifique a sua <a href="/i2ptunnel/edit?tunnel=0">configuração do Gerenciador de Serviços Ocultos</a>
+para especificar <b>exit.stormycloud.i2p</b>
+em dois lugares: <b>Proxies de Saída</b> e <b>Proxies de Saída SSL</b>.
+Após editar, <b>role para baixo e clique em Salvar</b>.
+Veja nossa <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">publicação no blog para uma captura de tela</a>.
+Para instruções para o Android e capturas de tela, veja o <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">blog do notbob</a>.</p>
+<p>As atualizações do roteador não atualizarão sua configuração, você deve editá-la manualmente. Obrigado a StormyCloud por seu apoio, e por favor, considere uma <a href="http://stormycloud.i2p/donate.html">doação</a>.</p>
+</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 com correções de bugs</summary></details><p>Essa versão inclui correções de bugs no i2psnark,
+no roteador, I2CP, e UPnP.
+As correções no roteador tratam bugs no reinício suave, IPv6, testes de par SSU,
+armazenamento do banco de dados de rede, e construção de túnel.
+O tratamento de família de roteador e  classificação de Sybil também foram
+melhorados significativamente.</p>
+<p>Junto da i2pd, nós estamos desenvolvendo nosso novo transporte UDP, o SSU2.
+O SSU2 trará melhoras substanciais de desempenho e segurança.
+Ele também permitirá que nós finalmente substituamos nosso último uso da criptografia muito lenta ElGamal,
+completando a atualização completa de criptografia que nós iniciamos cerca de 9 anos atrás.
+Essa versão contém uma implementação preliminar que fica desabilitada por padrão.
+Se você deseja participar em testes, por favor, busque informações atuais
+em zzz.i2p.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Install essential Java/Jpackage updates" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>The recent Java "Psychic Signatues" vulnerability affects I2P. Current users of
-I2P on Linux, or any users of I2P who are using a non-bundled JVM should update
-their JVM or switch to a version which does not contain the vulnerability, below
-Java 15.</p>
-<p>New I2P Easy-Install bundles have been generated using the latest release of the
-Java Virtual Machine. Further details have been published in the respective
-bundle newsfeeds.</p>
-</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 with reliability and performance improvements</summary></details><p>The 1.7.0 release contains several performance and reliability improvements.</p>
-<p>There are now popup messages in the system tray, for those platforms that support it.
-i2psnark has a new torrent editor.
-The NTCP2 transport now uses much less CPU.</p>
-<p>The long-deprecated BOB interface is removed for new installs.
-It will continue to work in existing installs, except for Debian packages.
-Any remaining users of BOB applications should ask the developers to convert to the SAMv3 protocol.</p>
-<p>We know that since our 1.6.1 release, network reliability has steadily deteriorated.
-We were aware of the problem soon after the release, but it took us almost two months to find the cause.
-We eventually identified it as a bug in i2pd 2.40.0,
-and the fix will be in their 2.41.0 release coming out about the same time as this release.
-Along the way, we've made several changes on the Java I2P side to improve the
-robustness of network database lookups and stores, and avoid poorly-performing peers in tunnel peer selection.
-This should help the network be more robust even in the presence of buggy or malicious routers.
-Additionally, we're starting a joint program to test pre-release i2pd and Java I2P routers
-together in an isolated test network, so we can find more problems before the releases, not after.</p>
-<p>In other news, we continue to make great progress on the design of our new UDP transport "SSU2" (proposal 159)
-and have started implementation.
-SSU2 will bring substantial performance and security improvements.
-It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
-completing a full cryptography upgrade that started about 9 years ago.
-We expect to start joint testing with i2pd soon, and roll it out to the network later this year.</p>
+</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Instalar atualizações essenciais do Java/Jpackage" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>A recente vulnerabilidade Java de "Assinaturas Psíquicas" afeta a I2P. Usuários atuais da
+I2P no Linux, ou quaisquer usuários da I2P que estiverem usando uma JVM que não veio junto no pacote devem atualizar
+sua JVM ou mudar para uma versão que não contém a vulnerabilidade, abaixo
+do Java 15.</p>
+<p>Novos pacotes I2P Easy-Install foram gerados usando a versão mais recente doJava Virtual Machine. Mais detalhes foram publicados nos respectivos feeds de notícias do pacote.</p>
+</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 com melhorias de confiabilidade e desempenho</summary></details><p>A versão 1.7.0 contém várias melhorias de desempenho e confiabilidade.</p>
+<p>Agora há mensagens pop-up na bandeja do sistema, para as plataformas que o suportam. i2psnark tem um novo editor de torrent. O transporte NTCP2 agora usa muito menos CPU.</p>
+<p>A há muito obsoleta interface BOB está removida para novas instalações.
+Ela continuará funcionando em instalações existentes, exceto em pacotes Debian.
+Quaisquer usuários de aplicações BOB que ainda restarem devem pedir aos desenvolvedores que as convertam para o protocolo SAMv3.</p>
+<p>Nós sabemos que desde a nossa versão 1.6.1, a estabilidade da rede tem deteriorado continuamente.
+Nós ficamos a par do problema logo após o lançamento, mas levou quase dois meses para nós encontrarmos a causa.
+Nós eventualmente a identificamos como um bug na i2pd 2.40.0,
+e a correção será na sua versão 2.41.0, que será lançada mais ou menos na mesma data que esta versão.
+Ao longo do caminho, nós fizemos várias mudanças do lado da I2P Java para melhorar a
+robustez dos armazenamentos e buscas na base de dados de rede, e evitar pares com desempenho ruim na seleção de par de túnel.
+Isso deve ajudar a rede a ficar mais robusta mesmo com a presença de roteadores problemáticos ou maliciosos.
+Ainda, nós estamos iniciando um programa conjunto para testar os roteadores I2P Java e i2pd pré-lançamento
+juntos em uma rede para testes isolada, para que possamos encontrar mais problemas antes dos lançamentos, não depois.</p>
+<p>Em outras novidades, nós continuamos a fazer bastante progresso no projeto do nosso novo transporte UDP "SSU2" (proposta 159)
+e começamos a implementação.
+O SSU2 trará melhoras substanciais de desempenho e segurança.
+Ele também permitirá que nós finalmente substituamos nosso último uso da criptografia muito lenta ElGamal,
+completando uma atualização completa de criptografia que começou cerca de 9 anos atrás.
+Nós esperamos iniciar a testar em conjunto com a i2pd logo, e disponibilizá-lo para a rede mais tarde neste ano.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
 </article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 permite novas mensagens de construção do túnel</summary></details><p>Este lançamento completa a implementação de duas grandes atualizações do protocolo desenvolvidas em 2021.
 A transição para a criptografia X25519 para roteadores é acelerada, e esperamos que quase todos os roteadores sejam chaveados novamente até o final do ano.
@@ -88,74 +239,61 @@ O filtro Bloom construído no túnel foi ajustado para reduzir o uso de memória
 Melhoramos o suporte para plugins não-Java.</p>
 <p>Em outras palavras, estamos fazendo excelentes progressos no projeto de nosso novo SSU2 de transporte UDP e esperamos começar a implementação no início do próximo ano.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 com novas mensagens de construção do túnel</summary></details><p>Yes, that's right, after 9 years of 0.9.x releases, we are going straight from 0.9.50 to 1.5.0.
-This does not signify a major API change, or a claim that development is now complete.
-It is simply a recognition of almost 20 years of work to provide anonymity and security for our users.</p>
-<p>This release finishes implementation of smaller tunnel build messages to reduce bandwidth.
-We continue the transition of the network's routers to X25519 encryption.
-Of course there are also numerous bug fixes and performance improvements.</p>
+</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 com novas mensagens de construção do túnel</summary></details><p>Sim, é isso mesmo, após nove anos de versões 0.9.x, nós estamos indo direto de 0.9.50 para 1.5.0.
+Isso não simboliza uma grande mudança de API, ou uma declaração de que o desenvolvimento agora está completo.
+É simplesmente um reconhecimento dos quase 20 anos de trabalho para proporcionar anonimato e segurança para nossos usuários.</p>
+<p>Essa versão finaliza a implementação de mensagens de criação de túnel menores para reduzir largura de banda.
+Nós continuamos a transição dos roteadores da rede para a criptografia X25519.
+Claro que há também diversas correções de bugs e melhorias de desempenho.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="MuWire Desktop Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Muwire Desktop Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire standalone desktop application.
-It does not affect the console plugin, and is not related to the previously-announced plugin issue.
-If you are running the MuWire desktop application you should <a href="http://muwire.i2p/">update to version 0.8.8</a> immediately.</p>
-<p>Details of the issue will be published on <a href="http://muwire.i2p/security.html">muwire.i2p</a>
-on July 15, 2021.</p>
-</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="MuWire Plugin Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Muwire Plugin Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire plugin.
-It does not affect the standalone desktop client.
-If you are running the MuWire plugin you should <a href="/configplugins">update to version 0.8.7-b1</a> immediately.</p>
-<p>See <a href="http://muwire.i2p/security.html">muwire.i2p</a>
-for more information about the vulnerability and updated security recommendations.</p>
-</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 com correções do IPv6</summary></details><p>0.9.50 continues the transition to ECIES-X25519 for router encryption keys.
-We have enabled DNS over HTTPS for reseeding to protect users from passive DNS snooping.
-There are numerous fixes and improvements for IPv6 addresses, including new UPnP support.</p>
-<p>We have finally fixed some longstanding SusiMail corruption bugs.
-Changes to the bandwidth limiter should improve network tunnel performance.
-There are several improvements in our Docker containers.
-We have improved our defenses for possible malicious and buggy routers in the network.</p>
+</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="Vulnerabilidade de desktop MuWire" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Vulnerabilidade do Muwire Desktop</summary></details><p>Uma vulnerabilidade de segurança foi descoberta na versão autônoma da aplicação de desktop do MuWire.
+Ela não afeta o plugin do console, e não está relacionada com o problema no plugin anunciado previamente.
+Se você executa a aplicação para desktop do MuWire, você deve <a href="http://muwire.i2p/">atualizar para a versão 0.8.8</a> imediatamente.</p>
+<p>Os detalhes da edição serão publicados em <a href="http://muwire.i2p/security.html">muwire.i2p</a>
+em 15 de julho de 2021.</p>
+</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="Vulnerabilidade de plug-in MuWire" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Vulnerabilidade de plug-in Muwire</summary></details><p>Foi detetada uma vulnerabilidade de segurança no plugin MuWire. Ele não afeta o cliente de desktop autônomo. Se você estiver executando o plugin MuWire, você deve <a href="/configplugins">atualizar para a versão 0.8.7-B1</a> imediatamente.</p>
+<p>Ver <a href="http://muwire.i2p/security.html">muwire.i2p</a>
+para obter mais informações sobre a vulnerabilidade e recomendações de segurança atualizadas.</p>
+</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 com correções do IPv6</summary></details><p>A versão 0.9.50 dá continuidade à transição ao ECIES-X25519 para chaves de criptografia dos roteadores.
+Nós habilitamos DNS sobre HTTPS para repropagação para proteger usuários contra snooping passivo de DNS.
+Há diversas correções e melhorias para endereços IPv6, incluindo o novo suporte aUPnP.</p>
+<p>Nós finalmente corrigimos alguns antigos bugs de corrupção no SusiMail.
+Mudanças no limitador de banda devem melhorar o desempenho de túnel da rede.
+Há várias melhorias no nossos contêiners Docker.
+Nós melhoramos nossas defesas contra possíveis roteadores com problemas ou maliciosos na rede.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0,9,49 com correções do SSU e criptografia mais rápida</summary></details><p>0.9.49 continues the work to make I2P faster and more secure.
-We have several improvements and fixes for the SSU (UDP) transport that should result in faster speeds.
-This release also starts the migration to new, faster ECIES-X25519 encryption for routers.
-(Destinations have been using this encryption for a few releases now)
-We've been working on the specifications and protocols for new encryption for several years,
-and we are getting close to the end of it! The migration will take several releases to complete.</p>
-<p>For this release, to minimize disruption, only new installs and a very small percentage of existing installs
-(randomly selected at restart) will be using the new encryption.
-If your router does "rekey" to use the new encryption, it may have lower traffic or less reliability than usual for several days after you restart.
-This is normal, because your router has generated a new identity.
-Your performance should recover after a while.</p>
-<p>We have "rekeyed" the network twice before, when changing the default signature type,
-but this is the first time we've changed the default encryption type.
-Hopefully it will all go smoothly, but we're starting slowly to be sure.</p>
+</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0.9.49 com correções do SSU e criptografia mais rápida</summary></details><p>A versão 0.9.49 dá continuidade ao trabalho para tornar a I2P mais rápida e mais segura.
+Nós temos várias melhorias e correções para o transporte SSU (UDP) que devem resultar em velocidades mais rápidas.
+Essa versão também dá início à migração para a nova e mais rápida criptografia ECIES-X25519 para os roteadores.
+(Destinos têm usado essa criptografia há alguns lançamentos agora)
+Nós temos trabalhado nas especificações e protocolos para a nova criptografia por vários anos,
+e nós estamos chegando perto de terminar! A migração levará diversos lançamentos para ser completada.</p>
+<p>Para esse lançamento, para minimizar o transtorno, apenas novas instalações e uma porcentagem muito pequena de instalações existentes
+(selecionadas aleatoriamente ao reiniciar) estarão usando a nova criptografia.
+Se seu roteador "rechavear" para usar a nova criptografia, ele pode ter tráfego menor ou menor estabilidade do que o normal por vários dias após você reiniciar.
+Isso é normal, porque seu roteador gerou uma nova identidade.
+Seu desempenho deveria ser recuperado após um tempo.</p>
+<p>Nós "rechaveamos" a rede duas vezes antes, ao alterar o tipo de assinatura padrão, mas esta é a primeira vez que mudamos o tipo de criptografia padrão. Espero que tudo corra bem, mas estamos começando devagar para ter certeza.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
 </article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 com melhorias de desempenho</summary></details><p>0.9.48 permite nosso novo protocolo de criptografia de ponta-a-ponta (proposta 144) para a maioria dos serviços.
 Adicionamos suporte preliminar para a criptografia de novas mensagens de construção de túnel (proposta 152).
 Há melhorias significativas de desempenho em todo o roteador.</p>
-<p>Packages for Ubuntu Xenial (16.04 LTS) are no longer supported.
-Users on that platform should upgrade so you may continue to receive I2P updates.</p>
+<p>Pacotes para Ubuntu Xenial (16.04 LTS) não são mais suportados. Os usuários nessa plataforma devem atualizar para que você possa continuar a receber atualizações I2P.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 permite nova criptografia</summary></details><p>0.9.47 enables our new end-to-end encryption protocol (proposal 144) by default for some services.
-The Sybil analysis and blocking tool is now enabled by default.</p>
-<p>Java 8 or higher is now required.
-Debian packages for Wheezy and Stretch, and for Ubuntu Trusty and Precise, are no longer supported.
-Users on those platforms should upgrade so you may continue to receive I2P updates.</p>
+</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 permite nova criptografia</summary></details><p>A versão 0.9.47 habilita nosso novo protocolo de criptografia de ponta a ponta (proposta 144) por padrão para alguns serviços. A ferramenta de análise e bloqueio Sybil agora está habilitada por padrão.</p>
+<p>Java 8 ou superior agora é necessário. Os pacotes Debian para Wheezy e Stretch, e para Ubuntu Trusty e Precise, não são mais suportados. Os usuários nessas plataformas devem atualizar para que você possa continuar a receber atualizações I2P.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="0.9.46 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 com correções de falha</summary></details><p>0.9.46 contains significant performance improvements in the streaming library.
-We have completed development of ECIES encryption (proposal 144) and there is now an option to enable it for testing.</p>
-<p>Windows users only:
-This release fixes a local privilege escalation vulnerability
-which could be exploited by a local user.
-Please apply the update as soon as possible.
-Thanks to Blaze Infosec for responsible disclosure of the issue.</p>
-<p>This is the last release to support Java 7, Debian packages Wheezy and Stretch, and Ubuntu packages Precise and Trusty.
-Users on those platforms must upgrade to receive future I2P updates.</p>
+</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="0.9.46 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 com correções de falha</summary></details><p>0.9.46 contém melhorias significativas de desempenho na biblioteca de streaming. Concluímos o desenvolvimento da criptografia ECIES (proposta 144) e agora há uma opção para habilitá-la para testes.</p>
+<p>Para usuários de Windows apenas:
+Essa versão corrige uma vulnerabilidade de escalação de privilégio local
+que poderia ser explorada por um usuário local.
+Por favor, aplique a atualização o mais breve possível.
+Obrigado à Blaze Infosec pela divulgação responsável do problema.</p>
+<p>Esta é a última versão a suportar Java 7, pacotes Debian Wheezy e Stretch, e pacotes Ubuntu Precise e Trusty. Os usuários nessas plataformas devem atualizar para receber atualizações futuras do I2P.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 com correções de falha</summary></details><p>0.9.45 contains important fixes for hidden mode and the bandwidth tester.
-There's an update to the console dark theme.
-We continue work on improving performance and the development of new end-to-end encryption (proposal 144).</p>
+</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 com correções de falha</summary></details><p>0.9.45 contém correções importantes para o modo oculto e o testador de largura de banda. Há uma atualização para o tema escuro do console. Continuamos a trabalhar na melhoria do desempenho e no desenvolvimento de uma nova encriptação de ponta a ponta (proposta 144).</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="0.9.44 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 com correções de falha</summary></details><p>0.9.44 contains an important fix for a denial of service issue in hidden services handling of new encryption types.
-All users should update as soon as possible.</p>
+</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="0.9.44 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 com correções de falha</summary></details><p>0.9.44 contém uma correção importante para um problema de negação de serviço no processamento de novos tipos de criptografia de serviços ocultos. Todos os usuários devem atualizar o mais rápido possível.</p>
 <p>Esse lançamento contém suporte inicial para uma nova criptografia ponta-a-ponta (proposta 144). 
 Este é trabalho em andamento e ainda não está pronto para uso.
 Há mudanças na pagina inicial do painel, e novos media players HTML5 embutidos no i2psnark.
@@ -190,206 +328,185 @@ Como de praxe, nós corrigimos muitas falhas!</p>
 </article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 com melhorias de desempenho</summary></details><p>0.9.39 inclui mudanças extensas para os novos tipos de base de dados da rede (proposta 123)
 Nós empacotamos a extensão i2pcontrol como um aplicativo web para suportar o desenvolvimento de aplicações RPC.
 Há numerosas melhorias de desempenho e correções de falha.  </p>
-<p>We've removed the midnight and classic themes to reduce the maintenance burden;
-previous users of those themes will now see the dark or light theme.
-There's also new home page icons, a first step in updating the console.</p>
+<p>Nós removemos os temas clássico e meia-noite para reduzir a carga de manutenção;
+usuários prévios desses temas agora verão os temas escuro ou claro.
+Também há novos ícones na página inicial, um primeiro passo na atualização do console.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 com o novo instalador passo-a-passo</summary></details><p>0.9.38 includes a new first-install wizard with a bandwidth tester.
-We've added support for the latest GeoIP database format.
-There's a new Firefox profile installer and a new, native Mac OSX installer on our website.
-Work continues on supporting the new "LS2" netdb format.</p>
-<p>This release also contains plenty of bug fixes, including several issues with susimail attachments, and a fix for IPv6-only routers.</p>
+</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 com o novo instalador passo-a-passo</summary></details><p>A versão 0.9.38 inclui um novo assistente de primeira instalação com um testador de largura de banda.
+Nós adicionamos suporte ao formato mais recente de base de dados de GeoIP.
+Agora há um novo instalador de perfil do Firefox e um novo instalador nativo para Mac OSX no nosso website.
+O trabalho continua para dar suporte ao novo formato de BD de rede "LS2".</p>
+<p>Esta versão também contém muitas correções de bugs, incluindo vários problemas com anexos susimail e uma correção para roteadores somente IPv6.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="35C3 Trip Report" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P no 35C3</summary></details><p>The I2P team was mostly all in attendance at 35C3 in Leipzig.
-Daily meetings were held to review the past year and cover our development and design goals for 2019.</p>
-<p>The Project Vision and new Roadmap can be <a href="http://i2p-projekt.i2p/en/get-involved/roadmap">reviewed here</a>.</p>
-<p>Work will continue on LS2, the Testnet, and usability improvements to our website and console.
-A plan is in place to be in Tails, Debian and Ubuntu Disco. We still need people to work on Android and I2P_Bote fixes.</p>
+</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="35C3 Relatório de Viagem" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P no 35C3</summary></details><p>A equipe I2P esteve praticamente toda presente no 35C3 em Leipzig. Foram realizadas reuniões diárias para revisar o ano passado e abordar nossas metas de desenvolvimento e design para 2019.</p>
+<p>A Visão do Projeto e o novo Roteiro podem ser <a href="http://i2p-projekt.i2p/en/get-involved/roadmap">Reveja aqui</a>.</p>
+<p>O trabalho continuará no LS2, no Testnet e nas melhorias de usabilidade do nosso site e console. Um plano está em vigor para estar no Tails, Debian e Ubuntu Disco. Ainda precisamos de pessoas para trabalhar no Android e I2P_Bote correções.</p>
 </article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="0.9.37 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37 com NTCP2 habilitado</summary></details><p>0.9.37 possibilita um protocolo de transporte mais seguro e rápido chamado NTCP2. </p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="0.9.36 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 with NTCP2 and bug fixes</summary></details><p>0.9.36 contains a new, more secure transport protocol called NTCP2.
-It is disabled by default, but you may enable it for testing by adding the <a href="/configadvanced">advanced configuration</a> <tt>i2np.ntcp2.enable=true</tt> and restarting.
-NTCP2 will be enabled in the next release.</p>
+</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="0.9.36 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 with NTCP2 and bug fixes</summary></details><p>A versão 0.9.36 contém um protocolo de transporte novo e mais seguro chamado NTCP2.
+Ele fica desabilitado por padrão, mas você pode habilitá-lo para testes adicionando a <a href="/configadvanced">configuração avançada</a> <tt>i2np.ntcp2.enable=true</tt> e reiniciando.
+O NTCP2 estará habilitado no próximo lançamento.</p>
 <p>Esse lançamento também contém várias melhorias de desempenho e correções de falha. </p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
 </article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>Versão 0.9.35 com pastas SusiMail e Assistente de SSL</summary></details><p>A versão 0.9.35 adiciona suporte para pastas no SusiMail, e um novo 'Assistente' de SSL Wizard para a configurar HTTPS no seu site da Web de "Serviço Oculto".
 Nós também temos a coleção usual de correções de erros, especialmente no SusiMail.</p>
 <p>Nós estamos trabalhando duro em muitas coisas para a versão 0.9.36, incluindo um instalador para OSX e um protocolo de transporte mais rápido e seguro chamado NTCP2. </p>
-<p>I2P will be at HOPE in New York City, July 20-22. Find us and say hello!</p>
+<p>A I2P estará na HOPE em Nova York, de 20 a 22 de julho. Encontre-nos e diga olá!</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 com correções de falha</summary></details><p>0.9.34 contains a lot of bug fixes!
-It also has improvements in SusiMail, IPv6 handling, and tunnel peer selection.
-We add support for IGD2 schemas in UPnP.
-There's also preparation for more improvements you will see in future releases.</p>
+</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 com correções de falha</summary></details><p>A versão 0.9.34 contém várias correções de bugs!
+Ela também inclui melhorias no SusiMail, tratamento de IPv6, e seleção de par de túnel.
+Nós adicionamos suporte para os esquemas IGD2 no UPnP.
+Há também preparação para mais melhorias que você verá em lançamentos futuros.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="0.9.33 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 com correções de falha</summary></details><p>0.9.33 contains a large number of bug fixes, including i2psnark, i2ptunnel, streaming, and SusiMail.
-For those who cannot access the reseed sites directly, we now support several types of proxies for reseeding.
-We now set rate limits by default in the hidden services manager.
-For those that run high-traffic servers, please review and adjust the limits as necessary.</p>
+</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="0.9.33 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 com correções de falha</summary></details><p>A versão 0.9.33 contém um grande número de correções de bugs, incluindo o i2psnark, o i2ptunnel, streaming, e o SusiMail.
+Para aqueles que não conseguem acessar os sites de repropagação diretamente, nós agora suportamos vários tipos de proxies para repropagação.
+Nós agora definimos limites de taxa por padrão no gerenciador de serviços ocultos.
+Para aqueles que executam servidores de alto tráfego, por favor, revisem e ajustem os limites conforme necessário.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER, Meltdown e Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Problemas de segurança encontrados em quase todos os sistemas</summary></details><p>A very serious issue has been found in modern CPUs which are found in nearly all sold computers worldwide, including mobiles. Those security issues are named "Kaiser", "Meltdown", and "Spectre".</p>
-<p>The whitepaper for KAISER/KPTI can be found under <a href="https://gruss.cc/files/kaiser.pdf" target="_blank">KAISER.pdf</a>, Meltdown under <a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a>, and SPECTRE under <a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a>. Intels first response is listed under <a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">Intels response</a>.</p>
-<p>It is important for our I2P users to update your system, as long as updates are available. Windows 10 patches are availble from now on, Windows 7 and 8 will follow soon. MacOS patches are already available, to. Lots of Linux systems have a newer Kernel with a included fix available, too. Same applies to Android, which security fix of 2nd Jan 2018 includes a patch for this issues.
-Please update your systems as soon as available and possible.</p>
+</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER, Meltdown e Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Problemas de segurança encontrados em quase todos os sistemas</summary></details><p>Um problema muito sério foi encontrado em CPUs modernas que são encontradas em quase todos os computadores vendidos em todo o mundo, incluindo celulares. Esses problemas de segurança são chamados de "Kaiser", "Meltdown" e "Spectre".</p>
+<p>O whitepaper do KAISER/KPTI pode ser encontrado em <a href="https://gruss.cc/files/kaiser.pdf" target="_blank">KAISER.pdf</a>, o do Meltdown em <a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a>, e o do SPECTRE em <a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a>. A primeira resposta da Intel está listada em <a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">resposta da Intel</a>.</p>
+<p>É importante para nossos usuários da I2P atualizar seu sistema, contando que atualizações estejam disponíveis. Patches para o Windows 10 estão disponíveis a partir de agora, Windows 7 e 8 virão logo em seguida. Patches para MacOS já estão disponíveis também. Muitos sistemas Linux têm um Kernel mais novo com uma correção incluída disponível também. O mesmo se aplica ao Android, cuja correção de segurança de 2 de janeiro de 2018 inclui um patch para esses problemas.
+Por favor, atualize seus sistemas o quanto antes estiver disponível e for possível.</p>
 </article><article id="urn:uuid:a6fc490b-2877-4cbf-afa8-d6e7d4637440" title="Feliz ano novo! - 34C3" href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Ano novo e I2P no 34C3</summary></details><p>Feliz ano novo da equipe do I2P para todos!</p>
-<p>No less than 7 I2P team members did meet at the 34C3 in Leipzig from 27th til 30th december 2017. Beside the <a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" target="_blank">meetings</a> at our table we did meet lots of friends of I2P all over the place. 
-Results of the meetings are posted on <a href="http://zzz.i2p" target="_blank">zzz.i2p</a> already.</p>
-<p>Also we did hand out lots of stickers and gave information about our project to anyone asking. 
-Our annual I2P dinner was a full success as a thank you to all attendees for ongoing support of I2P.</p>
-</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="0.9.32 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 com atualizações do painel</summary></details><p>0.9.32 contains a number of fixes in the router console and associated webapps (addressbook, i2psnark, and susimail).
-We have also changed the way we handle configured hostnames for published router infos, to eliminate some network enumeration attacks via DNS.
-We have added some checks in the console to resist rebinding attacks.</p>
+<p>Não menos que 7 membros do time da I2P se encontraram no 34C3 em Leipzig de 27 a 30 de dezembro de 2017. Além dos <a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" target="_blank">encontros</a> na nossa mesa nós conhecemos vários amigos da I2P por todo o lugar. 
+Resultados dos encontros já estão publicados em <a href="http://zzz.i2p" target="_blank">zzz.i2p</a>.</p>
+<p>Também distribuímos muitos adesivos e demos informações sobre nosso projeto para quem quisesse. Nosso jantar anual I2P foi um sucesso total como um agradecimento a todos os participantes pelo apoio contínuo da I2P.</p>
+</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="0.9.32 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 com atualizações do painel</summary></details><p>A versão 0.9.32 contém várias correções no console do roteador e aplicações web associadas (livro de endereços, i2psnark, e susimail).
+Nós também mudamos a forma como nós lidamos com nomes de host configurados para informações de roteador publicadas, para eliminar alguns ataques de enumeração de rede via DNS.
+Nós adicionamos algumas verificações no console para resistir a ataques de revinculação.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="0.9.31 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>0.9.31 com atualizações do painel</summary></details><p>The changes in this release are much more noticeable than usual!
-We have refreshed the router console to make it easier to understand,
-improved accessibility and cross-browser support,
-and generally tidied things up.
-This is the first step in a longer-term plan to make the router console more user-friendly.
-We have also added torrent ratings and comments support to i2psnark.</p>
+</article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="0.9.31 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>0.9.31 com atualizações do painel</summary></details><p>As mudanças nessa versão são muito mais perceptíveis do que o normal!
+Nós renovamos o console do roteador para torná-lo mais fácil de entender,
+melhoramos a acessibilidade e suporte cross-browser ,
+e organizamos as coisas no geral.
+Esse é um primeiro passo em um plano de mais longo prazo para tornar o console do roteador mais amigável ao usuário.
+Nós também adicionamos suporte a classificações e comentários de torrents ao i2psnark.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:2ce9a846-4d7e-11e7-b788-00163e5e6c1b" title="Chamada para tradutores" href="https://www.transifex.com/otf/I2P/announcements/7243/" author="str4d" published="2017-06-10T12:00:00Z" updated="2017-06-10T12:00:00Z"><details><summary>The upcoming 0.9.31 release has more untranslated strings than usual</summary></details><p>In preparation for the 0.9.31 release, which brings with it significant updates
-to the user interface, we have a larger than normal collection of untranslated
-strings that need attention. If you're a translator, we would greatly appreciate
-it if you could set aside a little more time than usual during this release cycle
-in order to bring the translations up to speed. We have pushed the strings early
-to give you three weeks to work on them.</p>
-<p>If you're not currently an I2P translator, now would be a great time to get
-involved! Please see the
-<a href="http://i2p-projekt.i2p/en/get-involved/guides/new-translators" target="_blank">New Translator's Guide</a>
-for information on how to get started.</p>
-</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="0.9.30 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>0.9.30 atualizações para Jetty 9</summary></details><p>0.9.30 contains an upgrade to Jetty 9 and Tomcat 8.
-The previous versions are no longer supported, and are not available in the upcoming Debian Stretch and Ubuntu Zesty releases.
-The router will migrate the jetty.xml configuration file for each Jetty website to the new Jetty 9 setup.
-This should work for recent, unmodified configurations but may not work for modified or very old setups.
-Verify that your Jetty website works after upgrading, and contact us on IRC if you need assistance.</p>
-<p>Several plugins are not compatible with Jetty 9 and must be updated.
-The following plugins have been updated to work with 0.9.30, and your router should update them after restart:
+</article><article id="urn:uuid:2ce9a846-4d7e-11e7-b788-00163e5e6c1b" title="Chamada para tradutores" href="https://www.transifex.com/otf/I2P/announcements/7243/" author="str4d" published="2017-06-10T12:00:00Z" updated="2017-06-10T12:00:00Z"><details><summary>A próxima versão 0.9.31 tem mais strings não traduzidas do que o normal</summary></details><p>Em preparação para a versão 0.9.31, que traz consigo atualizações significativas
+à interface de usuário, nós temos uma coleção maior do que o normal de strings
+não traduzidas que precisam de atenção. Se você é um tradutor, nós ficaríamos muito felizes
+se você pudesse reservar um pouco mais de tempo do que o normal durante esse ciclo de lançamento
+para ajustar o ritmo das traduções. Nós disponibilizamos as strings mais cedo
+para dar a você três semanas para trabalhas nelas.</p>
+<p>Se você não é atualmente um tradutor I2P, agora seria um ótimo momento para se envolver! Por favor, veja o
+<a href="http://i2p-projekt.i2p/en/get-involved/guides/new-translators" target="_blank">Novo Guia do Tradutor</a>
+para obter informações sobre como começar.</p>
+</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="0.9.30 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>0.9.30 atualizações para Jetty 9</summary></details><p>A versão 0.9.30 contém uma atualização para o Jetty 9 e para o Tomcat 8.
+As versões anteriores não têm mais suporte, e não estão disponíveis nos futuros lançamentos Debian Stretch e Ubuntu Zesty.
+O roteador migrará o arquivo de configurações jetty.xml para cada website Jetty para a nova configuração do Jetty 9.
+Isso deve funcionar para configurações recentes e não modificadas, mas pode não funcionar para configurações modificadas ou muito antigas.
+Verifique que seu website Jetty funciona após atualizar, e nos contate no IRC se você precisar de assistência.</p>
+<p>Diversos plugins não são compatíveis com o Jetty 9 e precisam ser atualizados.
+Os seguintes plugins foram atualizados para funcionar com a 0.9.30, e seu roteador deve atualizá-los após reiniciar:
 i2pbote 0.4.6; zzzot 0.15.0.
-The following plugins (with current versions listed) will not work with 0.9.30.
-Contact the appropriate plugin developer for the status of new versions:
+Os seguintes plugin (com as versões atuais listadas) não funcionarão com a 0.9.30.
+Entre em contato com o desenvolvedor apropriado do plugin para o status das novas versões:
 BwSchedule 0.0.36; i2pcontrol 0.11.</p>
-<p>This release also supports migration of old (2014 and earlier) DSA-SHA1 hidden services to the more-secure EdDSA signature type.
-See <a href="http://zzz.i2p/topics/2271">zzz.i2p</a> for further information, including a guide and FAQ.</p>
-<p>Note: On non-Android ARM platforms such as the Raspberry Pi, the blockfile database will upgrade on restart, which may take several minutes.
-Please be patient.</p>
+<p>Esta versão também oferece suporte à migração de serviços ocultos DSA-SHA1 antigos (2014 e anteriores) para o tipo de assinatura EdDSA mais seguro. Ver <a href="http://zzz.i2p/topics/2271">zzz.i2p</a> para obter mais informações, incluindo um guia e perguntas frequentes.</p>
+<p>Nota: Em plataformas ARM não Android, como o Raspberry Pi, o banco de dados blockfile será atualizado na reinicialização, o que pode levar vários minutos. Por favor, seja paciente.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="0.9.29 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29 contém correções de falha</summary></details><p>0.9.29 contains fixes for numerous Trac tickets, including workarounds for corrupt compressed messages.
-We now support NTP over IPv6.
-We've added preliminary Docker support.
-We now have translated man pages.
-We now pass same-origin Referer headers through the HTTP proxy.
-There are more fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
-<p>As usual, we recommend that all users update to this release.
-The best way to help the network and stay secure is to run the latest release.</p>
-</article><article id="urn:uuid:cb742cac-df38-11e6-aed3-00163e5e6c1b" title="Vulnerabilidade de Segurança do I2P-Bote" href="http://bote.i2p/news/0.4.5/" author="str4d" published="2017-01-20T12:00:00Z" updated="2017-01-20T12:00:00Z"><details><summary>Vulnerabilidade de Segurança do I2P-Bote</summary></details><p>I2P-Bote 0.4.5 fixes a security vulnerability present in all earlier versions of the
-I2P-Bote plugin. The Android app was not affected.</p>
-<p>When showing emails to the user, most fields were being escaped. However, the filenames
-of attachments were not escaped, and could be used to execute malicious code in a browser
-with JavaScript enabled. These are now escaped, and additionally a Content Security Policy
-has been implemented for all pages.</p>
-<p>All I2P-Bote users will be upgraded automatically the first time they restart their router
-after I2P 0.9.29 is released in mid-February. However, for safety we recommend that you
-<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
-upgrade manually if you plan on using I2P or I2P-Bote in the intervening time.</p>
-</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="0.9.28 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>0.9.28 contém correções de falha</summary></details><p>0.9.28 contains fixes for over 25 Trac tickets, and updates for a number of bundled software packages including Jetty.
-There are fixes for the IPv6 peer testing feature introduced last release.
-We continue improvements to detect and block peers that are potentially malicious.
-There are preliminary fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
-<p>I2P will be at 33C3, please stop by our table and give us your ideas on how to improve the network.
-We will review our 2017 roadmap and priorities 2017 at the Congress.</p>
-<p>As usual, we recommend that all users update to this release.
-The best way to help the network and stay secure is to run the latest release.</p>
-</article><article id="urn:uuid:00015ff6-b556-11e6-adb4-00163e5e6c1a" title="Vulnerabilidade de Segurança do I2P-Bote" href="http://bote.i2p/news/0.4.4/" author="str4d" published="2016-11-28T12:00:00Z" updated="2016-11-28T12:00:00Z"><details><summary>Vulnerabilidade de Segurança do I2P-Bote</summary></details><p>I2P-Bote 0.4.4 fixes a security vulnerability present in all earlier versions of the
-I2P-Bote plugin. The Android app was not affected.</p>
-<p>A lack of CSRF protection meant that if a user was running I2P-Bote and then loaded a
-malicious site in a browser with JavaScript enabled, the adversary could trigger actions
-in I2P-Bote on behalf of the user, such as sending messages. This might also have enabled
-extraction of private keys for I2P-Bote addresses, however no proof-of-exploit was tested
-for this.</p>
-<p>All I2P-Bote users will be upgraded automatically the first time they restart their router
-after I2P 0.9.28 is released in mid-December. However, for safety we recommend that you
-<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
-upgrade manually if you plan on using I2P or I2P-Bote in the intervening time. You should
-also consider generating new I2P-Bote addresses if you regularly browse sites with
-JavaScript enabled while running I2P-Bote.</p>
+</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="0.9.29 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29 contém correções de falha</summary></details><p>A versão 0.9.29 contém correções para diversos tickets Trac, incluindo alternativas para mensagens compactadas corrompidas.
+Nós agora suportamos NTP sobre IPv6.
+Nós adicionamos suporte preliminar ao Docker.
+Nós agora traduzimos as páginas de manual.
+Nós agora passamos headers Referer same-origin pelo proxy HTTP.
+Há mais correções para o Java 9, embora nós ainda não recomendemos o Java 9 para uso geral.</p>
+<p>Como de costume, recomendamos que todos os usuários atualizem para esta versão. A melhor maneira de ajudar a rede e manter-se segura é executar a versão mais recente.</p>
+</article><article id="urn:uuid:cb742cac-df38-11e6-aed3-00163e5e6c1b" title="Vulnerabilidade de Segurança do I2P-Bote" href="http://bote.i2p/news/0.4.5/" author="str4d" published="2017-01-20T12:00:00Z" updated="2017-01-20T12:00:00Z"><details><summary>Vulnerabilidade de Segurança do I2P-Bote</summary></details><p>O I2P-Bote 0.4.5 corrige uma vulnerabilidade de segurança presente em todas as versões anteriores doplug-in I2P-Bote. O aplicativo para Android não foi afetado.</p>
+<p>Ao mostrar emails para o usuário, a maioria dos campos estava sendo escapada. Contudo, os nomes de arquivos
+dos anexos não eram escapados, e poderiam ser usados para executar código malicioso em um navegador
+com JavaScript habilitado. Eles agora estão escapados, e adicionalmente a isso uma Política de Segurança de Conteúdo
+foi implementada para todas as páginas.</p>
+<p>Todos os usuários do I2P-Bote serão atualizados automaticamente na primeira vez que eles reiniciarem seu roteador
+após a versão 0.9.29 da I2P ser lançada na metade de fevereiro. Todavia, por segurança nós recomendamos que você
+<a href="http://bote.i2p/install/">siga as instruções na página de instalação</a> para
+atualizar manualmente se você planeja usar a I2P ou o I2P-Bote no meio-tempo.</p>
+</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="0.9.28 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>0.9.28 contém correções de falha</summary></details><p>A versão 0.9.28 contém correções para mais de 25 tickets Trac, e atualizações para vários pacotes de software embutidos incluindo o Jetty.
+Há correções para a funcionalidade de teste de par IPv6 introduzida no último lançamento.
+Nós damos continuidade a melhorias para detectar e bloquear pares que sejam potencialmente maliciosos.
+Há correções preliminares para Java 9, embora nós ainda não recomendemos o Java 9 para uso geral.</p>
+<p>I2P estará em 33C3, por favor, pare em nossa mesa e nos dê suas ideias sobre como melhorar a rede. Revisaremos nosso roteiro de 2017 e nossas prioridades para 2017 no Congresso.</p>
+<p>Como de costume, recomendamos que todos os usuários atualizem para esta versão. A melhor maneira de ajudar a rede e manter-se segura é executar a versão mais recente.</p>
+</article><article id="urn:uuid:00015ff6-b556-11e6-adb4-00163e5e6c1a" title="Vulnerabilidade de Segurança do I2P-Bote" href="http://bote.i2p/news/0.4.4/" author="str4d" published="2016-11-28T12:00:00Z" updated="2016-11-28T12:00:00Z"><details><summary>Vulnerabilidade de Segurança do I2P-Bote</summary></details><p>O I2P-Bote 0.4.4 corrige uma vulnerabilidade de segurança presente em todas as versões anteriores do plug-in I2P-Bote. O aplicativo para Android não foi afetado.</p>
+<p>Uma ausência de proteção contra CSRF significava que se um usuário estava executando o I2P-Bote e então carregava um
+site malicioso em um navegador com JavaScript habilitado, o adversário poderia disparar ações
+no I2P-Bote em nome do usuário, tais como enviar mensagens. Isso pode ter permitido também
+a extração de chaves privadas para endereços I2P-Bote, contudo, nenhuma prova de exploração foi testada
+para isso.</p>
+<p>Todos os usuários do I2P-Bote serão atualizados automaticamente na primeira vez que eles reiniciarem seu roteador
+após a versão 0.9.28 da I2P ser lançada na metade de dezembro. Contudo, por segurança nós recomendamos que você
+<a href="http://bote.i2p/install/">siga as instruções na página de instalação</a> para
+atualizar manualmente se você planeja usar a I2P ou o I2P-Bote no meio-tempo. Você deveria
+também considerar gerar novos endereços I2P-Bote se você navega por sites regularmente com
+JavaScript habilitado enquanto executa o I2P-Bote.</p>
 </article><article id="urn:uuid:c1d01ac3-81e7-4acd-bacd-d9178089e8c3" title="0.9.27 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2016/10/17/0.9.27-Release" author="zzz" published="2016-10-17T12:00:00Z" updated="2016-10-17T12:00:00Z"><details><summary>Versão 0.9.27 contém correções de erros</summary></details><p>0.9.27 contém algumas correções de erros.
 Biblioteca GMP atualizada para aceleração de encriptação, que foi incorporada no lançamento da versão 0.9.26 apenas para novas instalações e compilações Debian, está agora incluída na atualização de rede para a versão 0.9.27.
 Existem alguns melhoramentos no transporte de IPv6, teste de peer SSU, e modo ocultado.</p>
-<p>We updated a number of plugins during <a href="http://i2p-projekt.i2p/en/blog/post/2016/06/01/I2P-Summer-Dev">I2P Summer</a> and your router will automatically update them after restart.</p>
-<p>As usual, we recommend that all users update to this release.
-The best way to help the network and stay secure is to run the latest release.</p>
-</article><article id="urn:uuid:7e818120-88f8-401a-88fe-8db4ba20ad4d" title="I2P Stack Exchange proposal" href="https://area51.stackexchange.com/proposals/99297/i2p" author="zzz" published="2016-06-07T13:00:00Z" updated="2016-06-07T13:00:00Z"><details><summary>I2P is now a proposed site on Stack Exchange!</summary></details><p>I2P is now a proposed site on Stack Exchange!
-Please <a href="https://area51.stackexchange.com/proposals/99297/i2p">commit to using it</a> so the beta phase can begin.</p>
-</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="0.9.26 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>0.9.26 contains crypto updates, Debian packaging improvements, and bug fixes</summary></details><p>0.9.26 contains a major upgrade to our native crypto library,
-a new addressbook subscription protocol with signatures,
-and major improvements to the Debian/Ubuntu packaging.</p>
-<p>For crypto, we have upgraded to GMP 6.0.0, and added support for newer processors,
-which will speed up crypto operations considerably.
-Also, we are now using constant-time GMP functions to prevent side-channel attacks.
-For caution, the GMP changes are enabled for new installs and Debian/Ubuntu builds only;
-we will include them for in-net updates in the 0.9.27 release.</p>
-<p>For Debian/Ubuntu builds, we have added dependencies on several packages,
-including Jetty 8 and geoip, and removed the equivalent bundled code.</p>
-<p>There's a collection of bug fixes also, including a fix for a timer bug
-that caused instability and performance degradations over time.
-As usual, we recommend that all users update to this release.
-The best way to help the network and stay secure is to run the latest release.</p>
-</article><article id="urn:uuid:c6f7228d-3330-4422-a651-ef9d8ca3484b" title="0.9.25 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2016/03/22/0.9.25-Release" author="zzz" published="2016-03-22T12:00:00Z" updated="2016-03-22T12:00:00Z"><details><summary>A versão 0.9.25 contém SAM 3.3, códigos QR, e correções de erros</summary></details><p>0.9.25 contains a major new version of SAM, v3.3, to support sophisticated multiprotocol applications.
-It adds QR codes for sharing hidden service addresses with others,
-and "identicon" images for visually distinguishing addresses.</p>
-<p>We've added a new "router family" configuration page in the console,
-to make it easier to declare that your group of routers is run by a single person.
-There are several changes to increase the capacity of the network and hopefully improve tunnel build success.</p>
-<p>As usual, we recommend that all users update to this release.
-The best way to help the network and stay secure is to run the latest release.</p>
-</article><article id="urn:uuid:8390114d-8e50-45fd-8b4d-3e613bdd034e" title="0.9.24 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2016/01/27/0.9.24-Release" author="zzz" published="2016-01-27T18:00:00Z" updated="2016-01-27T18:00:00Z"><details><summary>0.9.24 contains several bug fixes and speedups</summary></details><p>0.9.24 contains a new version of SAM (v3.2) and numerous bug fixes and efficiency improvements.
-Note that this release is the first to require Java 7.
-Please update to Java 7 or 8 as soon as possible.
-Your router will not automatically update if you are using Java 6.</p>
-<p>To prevent the problems caused by the ancient commons-logging library, we have removed it.
-This will cause very old I2P-Bote plugins (0.2.10 and below, signed by HungryHobo) to crash if they have IMAP enabled.
-The recommended fix is to replace your old I2P-Bote plugin with the current one signed by str4d.
-For more details, see <a href="http://bote.i2p/news/0.4.3">this post</a>.</p>
-<p>We had a great <a href="http://i2p-projekt.i2p/en/blog/post/2016/01/23/32C3">32C3 Congress</a> and are making good progress on our 2016 project plans.
-Echelon gave a talk on I2P's history and current status, and his slides are <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/ccc/2015/I2P_Still_alive.pdf">here</a> (pdf).
-Str4d attended <a href="http://www.realworldcrypto.com/rwc2016/program">Real World Crypto</a> and gave a talk on our crypto migration, 
-his slides are <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/rwc/2016/rwc2016-str4d-slides.pdf">here</a> (pdf).</p>
-<p>As usual, we recommend that all users update to this release.
-The best way to help the network and stay secure is to run the latest release.</p>
-</article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="0.9.23 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>0.9.23 contains a variety of bug fixes, and some minor improvements in I2PSnark</summary></details><p>Hello I2P! This is the first release signed by me (str4d), after 49 releases
-signed by zzz. This is an important test of our redundancy for all things,
-including people.</p>
+<p>Atualizamos uma série de plugins durante <a href="http://i2p-projekt.i2p/en/blog/post/2016/06/01/I2P-Summer-Dev">I2P Verão</a> e seu roteador irá atualizá-los automaticamente após a reinicialização.</p>
+<p>Como de costume, recomendamos que todos os usuários atualizem para esta versão. A melhor maneira de ajudar a rede e manter-se segura é executar a versão mais recente.</p>
+</article><article id="urn:uuid:7e818120-88f8-401a-88fe-8db4ba20ad4d" title="Proposta do I2P Stack Exchange" href="https://area51.stackexchange.com/proposals/99297/i2p" author="zzz" published="2016-06-07T13:00:00Z" updated="2016-06-07T13:00:00Z"><details><summary>I2P é agora um site proposto no Stack Exchange!</summary></details><p>I2P é agora um site proposto no Stack Exchange! Por favor <a href="https://area51.stackexchange.com/proposals/99297/i2p">comprometer-se a usá-lo</a> Assim, a fase beta pode começar.</p>
+</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="0.9.26 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>0.9.26 contém atualizações de criptografia, melhorias no empacotamento Debian e correções de bugs</summary></details><p>0.9.26 contém uma grande atualização para a nossa biblioteca de criptografia nativa, um novo protocolo de assinatura de catálogo de endereços com assinaturas e grandes melhorias para o pacote Debian / Ubuntu.</p>
+<p>Para criptografia, nós atualizamos para o GMP 6.0.0, e adicionamos suporte para novos processadores,
+o que acelerará as operações de criptografia consideravelmente.
+Ainda, nós agora estamos usando funções GMP de tempo constante para prevenir ataques de canal lateral.
+Por precaução, as mudanças de GMP estão habilitadas somente para novas instalações e construções Debian/Ubuntu;
+nós as incluiremos para atualizações em rede no lançamento da versão 0.9.27.</p>
+<p>Para compilações Debian/Ubuntu, adicionamos dependências em vários pacotes, incluindo Jetty 8 e geoip, e removemos o código empacotado equivalente.</p>
+<p>Há ainda uma coleção de correção de bugs, incluindo uma correção para um bug de temporizador
+que causava instabilidade e degradação de desempenho ao longo do tempo.
+Como de costume, nós recomendamos que todos os usuários atualizem para essa versão.
+A melhor forma de ajudar a rede e se manter seguro é executar a versão mais recente.</p>
+</article><article id="urn:uuid:c6f7228d-3330-4422-a651-ef9d8ca3484b" title="0.9.25 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2016/03/22/0.9.25-Release" author="zzz" published="2016-03-22T12:00:00Z" updated="2016-03-22T12:00:00Z"><details><summary>A versão 0.9.25 contém SAM 3.3, códigos QR, e correções de erros</summary></details><p>A versão 0.9.25 contém uma grande nova versão do SAM, v3.3, para dar suporte a aplicações multi protocolo sofisticadas.
+Ela adiciona QR codes para compartilhar endereços de serviços ocultos com os outros,
+e imagens "identicon" para distinguir endereços visualmente.</p>
+<p>Nós adicionamos uma nova página de configuração de "família do roteador" no console,
+para tornar mais fácil declarar que o seu grupo de roteadores é executado por uma única pessoa.
+Há várias mudanças para aumentar a capacidade da rede e, assim se espera, melhorar o sucesso de construção de túneis.</p>
+<p>Como de costume, recomendamos que todos os usuários atualizem para esta versão. A melhor maneira de ajudar a rede e manter-se segura é executar a versão mais recente.</p>
+</article><article id="urn:uuid:8390114d-8e50-45fd-8b4d-3e613bdd034e" title="0.9.24 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2016/01/27/0.9.24-Release" author="zzz" published="2016-01-27T18:00:00Z" updated="2016-01-27T18:00:00Z"><details><summary>0.9.24 contém várias correções de bugs e acelerações</summary></details><p>A versão 0.9.24 contém uma nova versão do SAM (v3.2) e várias correções de bugs e melhorias de eficiência.
+Note que essa versão é a primeira a requerer Java 7.
+Por favor, atualize para o Java 7 ou 8 o mais breve possível.
+Seu roteador não atualizará automaticamente se você estiver usando Java 6.</p>
+<p>Para prevenir os problemas causados pela antiga biblioteca commons-logging, nós a removemos.
+Isso fará com que plugins muito antigos do I2P-Bote (0.2.10 e anterior, assinados por HungryHobo) travem se eles tiverem IMAP habilitado.
+A correção recomendada é substituir seu antigo plugin do I2P-Bote pelo atual assinado pelo str4d.
+Para mais detalhes, veja <a href="http://bote.i2p/news/0.4.3">esta publicação</a>.</p>
+<p>Nós tivemos um ótimo <a href="http://i2p-projekt.i2p/en/blog/post/2016/01/23/32C3">Congresso 32C3</a> e estamos fazendo um bom progresso nos nossos planos de projeto de 2016.
+O Echelon deu uma palestra sobre a história da I2P e o status atual, e seus slides estão <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/ccc/2015/I2P_Still_alive.pdf">aqui</a> (pdf).
+O Str4d participou do <a href="http://www.realworldcrypto.com/rwc2016/program">Real World Crypto</a> e deu uma palestra sobre nossa migração de criptografia. 
+Seus slides estão <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/rwc/2016/rwc2016-str4d-slides.pdf">aqui</a> (pdf).</p>
+<p>Como de costume, recomendamos que todos os usuários atualizem para esta versão. A melhor maneira de ajudar a rede e manter-se segura é executar a versão mais recente.</p>
+</article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="0.9.23 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>0.9.23 contém uma variedade de correções de bugs, e algumas pequenas melhorias no I2PSnark</summary></details><p>Olá, I2P! Este é o primeiro lançamento assinado por mim (str4d), depois de 49 lançamentos
+assinados pelo zzz. Esse é um teste importante da nossa redundância para todas as coisas,
+incluindo pessoas.</p>
 <p><b>Limpeza</b></p>
-<p>My signing key has been in router updates for over two years (since 0.9.9), so
-if you are on a recent version of I2P this update should be just as easy as
-every other update. However, if you are running an older version than 0.9.9, you
-will first need to manually update to a recent version. Update files for recent
-versions can be downloaded
-<a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/releases/">here</a>,
-and instructions on how to manually update are provided
-<a href="http://i2p-projekt.i2p/en/download#update">here</a>. Once you have manually
-updated, your router will then find and download the 0.9.23 update as usual.</p>
-<p>If you installed I2P via a package manager, you are not affected by the change,
-and can update as usual.</p>
+<p>A minha chave de assinatura esteve em atualizações do roteador por mais de dois anos (desde a versão 0.9.9), então
+se você está em uma versão recente da I2P essa atualização deve ser tão fácil quanto
+qualquer outra. Todavia, se você estiver executando uma versão mais antiga do que a 0.9.9, você
+precisará primeiro atualizar manualmente para uma versão mais recente. Arquivos de atualização para versões
+recentes podem ser baixados
+<a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/releases/">aqui</a>,
+e instruções de como atualizar manualmente são providenciadas
+<a href="http://i2p-projekt.i2p/en/download#update">aqui</a>. Uma vez que você tenha atualizado
+manualmente, seu roteador então encontrará e baixará a atualização 0.9.23 como de costume.</p>
+<p>Se você instalou o I2P através de um gerenciador de pacotes, você não é afetado pela alteração e pode atualizar como de costume.</p>
 <p><b>Detalhes da atualização</b></p>
-<p>The migration of RouterInfos to new, stronger Ed25519 signatures is going well,
-with at least half of the network already estimated to have rekeyed. This
-release accelerates the rekeying process. To reduce network churn, your router
-will have a small probability of converting to Ed25519 at each restart. When it
-does rekey, expect to see lower bandwidth usage for a couple of days as it
-reintegrates into the network with its new identity.</p>
-<p>Note that this will be the last release to support Java 6. Please update to
-Java 7 or 8 as soon as possible. We are already working to make I2P compatible
-with the upcoming Java 9, and some of that work is in this release.</p>
-<p>We have also made some minor improvements in I2PSnark, and added a new page in
-the routerconsole for viewing older news items.</p>
+<p>A migração de informações de roteador para novas e mais fortes assinaturas Ed25519 está indo bem,
+com pelo menos metade da rede já estimada a ter rechaveado. Esse
+lançamento acelera o processo de rechaveamento. Para reduzir a agitação na rede, seu roteador
+terá uma pequena probabilidade de converter para Ed25519 a cada reinício. Quando ele
+rechavear, espere ver uso de banda reduzido por alguns dias enquanto ele se
+reintegra à rede com sua nova identidade.</p>
+<p>Note que essa será a última versão a suportar Java 6. Por favor, atualize para
+o Java 7 ou 8 o mais breve possível. Nós já estamos trabalhando em tornar a I2P compatível
+com o futuro Java 9, e um pouco desse trabalho está nesse lançamento.</p>
+<p>Também fizemos algumas pequenas melhorias no I2PSnark e adicionamos uma nova página noconsole do roteador para visualizar notícias mais antigas.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
-</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="0.9.22 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 with bug fixes and starts Ed25519 migration</summary></details><p>0.9.22 contains fixes for i2psnark getting stuck before completion, and begins the migration of router infos to new, stronger Ed25519 signatures.
-To reduce network churn, your router will have only a small probability of converting to Ed25519 at each restart.
-When it does rekey, expect to see lower bandwidth usage for a couple of days as it reintegrates into the network with its new identity.
-If all goes well, we will accelerate the rekeying process in the next release.</p>
-<p>I2PCon Toronto was a big success!
-All the presentations and videos are listed on the <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">I2PCon page</a>.</p>
+</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="0.9.22 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 com correções de bugs e inicia a migração Ed25519</summary></details><p>A versão 0.9.22 contém correções para o i2psnark ficando travado antes da finalização, e inicia a migração das informações de roteador para novas e mais fortes assinaturas Ed25519.
+Para reduzir a agitação na rede, seu roteador terá uma pequena probabilidade de converter para Ed25519 a cada reinício.
+Quando ele rechavear, espere ver uso de banda mais baixo por alguns dias enquanto ele se reintegra à rede com sua nova identidade.
+Se tudo ocorrer bem, nós aceleraremos o processo de rechaveamento no próximo lançamento.</p>
+<p>A I2PCon Toronto foi um grande sucesso! Todas as apresentações e vídeos estão listados na <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">Página I2PCon</a>.</p>
 <p>Como de costume, recomendamos que você atualize para esse lançamento. A melhor maneira de manter a segurança e ajudar a rede é rodar a última versão lançada.</p>
 </article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="0.9.21 Lançado" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>Versão 0.9.21 lançada com melhorias de desempenho e correções de falhas.</summary></details><p>A versão 0.9.21 contém diversas modificações que adicionam capacidade a rede, aumentam a eficiência das inundações,
 e usam a banda de maneira mais eficiente.

data/translations/entries.ro.html

@@ -1,5 +1,173 @@
 <div>
-<header title="Ştiri I2P">Ştiri şi actualizări de router</header><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
+<header title="Ştiri I2P">Ştiri şi actualizări de router</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
+The bug primarily affected high-bandwidth routers.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
+We have added notification bubbles to several applications in the console to highlight application messages.
+We fixed a tunnel test bug that may have been affecting tunnel reliability.
+The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
+There are several dark theme fixes and improvements.</p>
+<p>We fixed the installer that previously failed on Java 21 or higher.
+We also fixed installing to directory paths that contain spaces on Linux.
+For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
+The workaround is using localhost and the server port, usually 7658, to bypass I2P.
+For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
+We apologize for the issue and are working on a fix.</p>
+</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
+<p>We have improved handling of congested routers in the network.
+Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
+We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
+Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
+<p>Access to information from the console and applications has been improved.
+Issues have been fixed in I2PSnark and SusiMail search.
+The netDB search embedded into the router console now operates in a more intuitive and useful way.
+Minor improvements have been made to diagnostic displays in advanced mode.</p>
+<p>Bugs have also been fixed to improve compatibility within the network.
+An issue with publishing leaseSets was solved which improves reliability major hidden services.
+I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
+This prevents torrents from being unnecessarily disrupted by these changes.
+We welcomed this contribution from a new contributor.
+A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
+This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
+<p>Newer routers will be favored when selecting floodfill routers.
+I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
+Legacy transport protocols are being removed, simplifying the code in the UDP transports.
+Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
+Additional tweaks were made to peer selection strategies.</p>
+<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
+We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
+If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
+Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
+With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
+This should help the network return to normal operation.
+Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
+Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
+This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
+Reachability of I2P sites is badly degraded.</p>
+<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
+Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
+</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
+<p>New features have been added to I2PSnark like the ability to search through torrents.
+Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
+We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
+New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
+Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
+<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
+This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
+This investigation uncovered one minor isolation-piercing event which we repaired.
+This issue was discovered and fixed internally by the I2P team.</p>
+<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
+This should result in improved delivery and availability for these downstream products.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
+It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
+<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
+This will help the network limit the effect of tunnel spam.
+It will also help the network heal during and after DDOS attacks.</p>
+<p>The NetDb changes also help secure individual routers and the applications that use them. 
+Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
+This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
+<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
+CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
+An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
+The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
+The attacker then sends the same message directly to the router.
+The router passes the message to the bloom filter, and is dropped.
+This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
+This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
+Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
+Users of Java I2P are recommended to update immediately to avoid the attack.</p>
+<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
+This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
+<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
+<p>This release also contains a tweakable blocklist.
+Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
+Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
+This feature is off-by-default and is only recommended for advanced users at this time.</p>
+<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
+It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
+This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
+Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
+This issue has also been resolved.
+The docker container is now also compatible with Podman.</p>
+<p>This release syncs translations with transifex and updates the GeoIP database.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
+This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
+The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
+<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
+This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
+This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
+We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
+<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
+zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
+As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
+We thank zzz for providing these services for such a long time.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
+Our investigations and mitigations continue.</p>
+<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
+We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
+However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
+The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
+<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
+We ask for your patience as we work to improve I2P.</p>
+</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
+  The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
+  Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
+  Mitigation strategies are being investigated and implemented gradually.</p>
+<p>While the attack has degraded performance, the network remains intact and usable.
+  Java I2P routers appear to be handling the issues better than i2pd routers for now.
+  Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
+</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
+As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
+First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
+Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
+Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
+<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
+possibly triggered by Bitcoin's new I2P transient address feature,
+but made worse by our SSU2 bugs and other congestion control problems.
+We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
+We have improved our algorithms to reduce network load during times of congestion.
+We are also collaborating with i2pd to develop common congestion control strategies.</p>
+<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
+i2pd released their version 2.45.0 last week and the early results are encouraging.
+New protocols, and distributed networks, are difficult to develop.
+Congestion can arrive with little warning and with little clue of the cause.
+Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
+<p>Ca de obicei, vă recomandăm ca toți utilizatorii să actualizeze la această versiune. Cel mai bun mod de a ajuta rețeua și a rămâne securizat este de a rula ultima versiune.</p>
+</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
 <p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
 <p>Ca de obicei, vă recomandăm ca toți utilizatorii să actualizeze la această versiune. Cel mai bun mod de a ajuta rețeua și a rămâne securizat este de a rula ultima versiune.</p>
 </article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Postări recente pe blog" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>

data/translations/entries.ru.html

@@ -1,5 +1,183 @@
 <div>
-<header title="Новости I2P">Новостной канал и обновления маршрутизатора</header><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
+<header title="Новости I2P">Новостной канал и обновления маршрутизатора</header><article id="urn:uuid:f2a6aabd-ee29-4f45-a8dd-7378e907016a" title="Вышла версия 2.9.0" href="http://i2p-projekt.i2p/en/blog/post/2025/06/02/2.9.0_released" author="idk" published="2025-06-02T19:00:00Z" updated="2025-06-02T19:00:00Z"><details><summary>Релиз I2P 2.9.0</summary></details><p>I2P 2.9.0 — это релиз с исправлением ошибок и небольшим количеством новых функций.</p>
+<p>Улучшена производительности системы i2ptunnel за счёт оптимизации использования потоков.
+В NTCP2 улучшена защита от зондирующих атак.
+Система уведомлений интегрирована в большее количество приложений, чтобы нагляднее отображать статусы в I2PSnark и других приложениях.
+Исправлена автоматическая регистрация флудфилда.
+Пользователи могут заметить повышенное использование ресурсов при работе в качестве floodfill.
+Если этот режим сильно нагружает систему, floodfill можно отключить на странице /config.</p>
+<p>В консоли доступна новая функция — глобальная карта, которая показывает местоположение маршрутизаторов в вашем представлении netDb.
+Это узлы, которые помогают вашему маршрутизатору строить туннели и предоставлять анонимную связность сети.</p>
+<p>Продолжаются работы по внедрению протокола Datagram2, постквантовой криптографии и автоматической подстройки пропускной способности для туннелей.
+Через два релиза, начиная с версии 2.11.0, для I2P потребуется Java 17.</p>
+<p>Как и всегда, мы рекомендуем вам обновиться.
+Лучший способ оставаться в безопасности и помогать сети - использовать самую свежую версию.</p>
+</article><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="Вышла 2.8.2" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>Релиз I2P 2.8.2</summary></details><p>В 2.8.2 исправлена проблема, приводящая к ошибкам SHA256, которая появилась в версии 2.8.1.
+Эта проблема проявлялась преимущественно у высокоскоростных маршрутизаторов.</p>
+<p>Как и всегда, мы рекомендуем вам обновиться.
+Лучший способ оставаться в безопасности и помогать сети - использовать самую свежую версию.</p>
+</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="Вышла 2.8.1" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>Релиз I2P 2.8.1</summary></details><p>В версии 2.8.1 исправлен доступ к локальным сайтам, которые не работали в 2.8.0. Мы добавили всплывающие уведомления в несколько приложений в консоли, чтобы выделять сообщения приложений.
+Мы исправили ошибку при тестировании туннеля, которая могла влиять на его стабильность.
+В адресной книге теперь есть новая вкладка «Последние», на которой отображаются самые новые имена хостов, добавленные из ваших подписок.
+Также была обновлена темная тема.</p>
+<p>Мы исправили установщик, который ранее не работал на Java 21 или выше.
+Мы также исправили установку в каталоги с пробелами в Linux.
+Для тех, кто использует Docker, мы обновили устаревшие контейнеры и библиотеки внутри контейнера.</p>
+<p>Как и всегда, мы рекомендуем вам обновиться.
+Лучший способ оставаться в безопасности и помогать сети - использовать самую свежую версию.</p>
+</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Проблемы доступа к локальным сайтам в версии 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 баг с локальным доступом</summary></details><p>В версии 2.8.0 переход на локальный сайт (по имени хоста или b32) завершится ошибкой.
+Обходным путем является использование localhost и порта сервера, обычно 7658, для доступа на сайт напрямую (вне I2P).
+Например, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
+Приносим свои извинения за возникшую проблему и работаем над ее устранением.</p>
+</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="Релиз I2P 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>Релиз I2P 2.8.0</summary></details><p>Этот релиз улучшает I2P, благодаря исправлениям ошибкок, удалению неиспользуемого кода и повышению стабильности сети.</p>
+<p>We have improved handling of congested routers in the network.
+Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
+We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
+Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
+<p>Как и всегда, мы рекомендуем вам обновиться.
+Лучший способ оставаться в безопасности и помогать сети - использовать самую свежую версию.</p>
+</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="Релиз I2P 2.7.0" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>Релиз I2P 2.7.0</summary></details><p>В этом релизе, I2P 2.7.0, продолжена работа над исправлением ошибок, улучшением производительности и добавлением новых возможностей.</p>
+<p>Улучшен доступ к информации из консоли и приложений.
+Исправлены проблемы в I2PSnark и поиске в SusiMail.
+Поиск по netDB, встроенный в консоль маршрутизатора, стал более интуитивным и полезеным.
+Незначительные улучшения в отображение диагностической информации в расширенном режиме.
+</p>
+<p>Также были исправлены ошибки для улучшения совместимости внутри сети.
+Решена проблема с публикацией контактных данных адресатов (LeaseSets), что повышает надежность основных скрытых сервисов.
+I2PSnark больше не меняет infohash, если пользователь меняет только трекеры в существующем торренте.
+Это предотвращает ненужное дублирование торрентов.
+За это изменение мы благодарим нового участника проекта.
+Исправлен конфликт при обработке опции потоковой библиотеки, для улучшения совместимости с другими реализациями I2P.
+</p>
+<p>Как и всегда, мы рекомендуем вам обновиться.
+Лучший способ оставаться в безопасности и помогать сети - использовать самую свежую версию.</p>
+</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="Релиз I2P 2.6.1" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>Релиз I2P 2.6.1</summary></details><p>Версия I2P 2.6.1 выпущена для исправления ошибки пользовательского интерфейса в приложении управления скрытыми сервисами.
+Эта ошибка приводила к неработающей прокрутке (скроллингу), что скрывало часть настроек.
+</p>
+<p>Как и всегда, мы рекомендуем вам обновиться.
+Лучший способ оставаться в безопасности и помогать сети - использовать самую свежую версию.</p>
+</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>В этом релизе, I2P 2.6.0, продолжена работа над исправлением ошибок, добавлением новых возможностей и улучшением сетевой стабильности.</p>
+<p>Newer routers will be favored when selecting floodfill routers.
+I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
+Legacy transport protocols are being removed, simplifying the code in the UDP transports.
+Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
+Additional tweaks were made to peer selection strategies.</p>
+<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
+We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
+If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
+Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
+<p>Как и всегда, мы рекомендуем вам обновиться.
+Лучший способ оставаться в безопасности и помогать сети - использовать самую свежую версию.</p>
+</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
+<p>Как и всегда, мы рекомендуем вам обновиться.
+Лучший способ оставаться в безопасности и помогать сети - использовать самую свежую версию.</p>
+</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
+With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
+This should help the network return to normal operation.
+Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
+Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
+<p>Как и всегда, мы рекомендуем вам обновиться.
+Лучший способ оставаться в безопасности и помогать сети - использовать самую свежую версию.</p>
+</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
+This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
+Reachability of I2P sites is badly degraded.</p>
+<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
+Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
+</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="Новый релиз I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>Дополнительные улучшения приложений, аудит стратегии изоляции NetDB</summary></details><p>Этот выпуск, I2P 2.5.0, содержит больше улучшений, ориентированных на пользователя, чем выпуск 2.4.0, который был сосредоточен на реализации стратегии изоляции NetDB.</p>
+<p>В I2PSnark добавлены новые функции, например, возможность поиска по торрентам. Исправлены ошибки для улучшения совместимости с другими I2P-торрент-клиентами, такими как BiglyBT и qBittorrent. Мы хотели бы поблагодарить всех разработчиков, которые работали с libtorrent и qBittorrent, чтобы включить и улучшить их поддержку I2P. В SusiMail также добавлены новые функции, включая поддержку форматирования Markdown в письмах и возможность перетаскивать вложения в письма. Туннели, созданные с помощью менеджера Hidden Services, теперь поддерживают "Keepalive", что повышает производительность и совместимость с веб-технологиями, позволяя создавать более сложные I2P-сайты.</p>
+<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
+This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
+This investigation uncovered one minor isolation-piercing event which we repaired.
+This issue was discovered and fixed internally by the I2P team.</p>
+<p>В этом релизе были внесены некоторые улучшения в процесс выпуска наших последующих дистрибутивов для Android и Windows. Это должно привести к улучшению доставки и доступности этих последующих продуктов.</p>
+<p>Как и всегда, мы рекомендуем вам обновиться.
+Лучший способ оставаться в безопасности и помогать сети - использовать самую свежую версию.</p>
+</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="Релиз I2P 2.4.0 с улучшениями в области безопасности перегрузок и NetDB" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>Релиз I2P 2.4.0 с улучшениями в области безопасности перегрузок и NetDB</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
+It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
+<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
+This will help the network limit the effect of tunnel spam.
+It will also help the network heal during and after DDOS attacks.</p>
+<p>The NetDb changes also help secure individual routers and the applications that use them. 
+Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
+This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
+<p>Также включен ряд исправлений и улучшений в приложениях I2PSnark и SusiMail.</p>
+<p>Как и всегда, мы рекомендуем вам обновиться.
+Лучший способ оставаться в безопасности и помогать сети - использовать самую свежую версию.</p>
+</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
+CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
+An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
+The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
+The attacker then sends the same message directly to the router.
+The router passes the message to the bloom filter, and is dropped.
+This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
+This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
+Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
+Users of Java I2P are recommended to update immediately to avoid the attack.</p>
+<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
+This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
+<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
+<p>This release also contains a tweakable blocklist.
+Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
+Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
+This feature is off-by-default and is only recommended for advanced users at this time.</p>
+<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
+It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
+<p>Как и всегда, мы рекомендуем вам обновиться.
+Лучший способ оставаться в безопасности и помогать сети - использовать самую свежую версию.</p>
+</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
+This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
+Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
+This issue has also been resolved.
+The docker container is now also compatible with Podman.</p>
+<p>This release syncs translations with transifex and updates the GeoIP database.</p>
+<p>Как и всегда, мы рекомендуем вам обновиться.
+Лучший способ оставаться в безопасности и помогать сети - использовать самую свежую версию.</p>
+</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
+This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
+The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
+<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
+This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
+This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
+We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
+<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
+zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
+As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
+We thank zzz for providing these services for such a long time.</p>
+<p>Как и всегда, мы рекомендуем вам обновиться.
+Лучший способ оставаться в безопасности и помогать сети - использовать самую свежую версию.</p>
+</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
+Our investigations and mitigations continue.</p>
+<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
+We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
+However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
+The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
+<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
+We ask for your patience as we work to improve I2P.</p>
+</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
+  The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
+  Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
+  Mitigation strategies are being investigated and implemented gradually.</p>
+<p>While the attack has degraded performance, the network remains intact and usable.
+  Java I2P routers appear to be handling the issues better than i2pd routers for now.
+  Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
+</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="Вышла версия 2.1.0" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 с многочисленными изменениями в SSU2</summary></details><p>We have learned several things since our 2.0.0 release in November.
+As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
+First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
+Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
+Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
+<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
+possibly triggered by Bitcoin's new I2P transient address feature,
+but made worse by our SSU2 bugs and other congestion control problems.
+We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
+We have improved our algorithms to reduce network load during times of congestion.
+We are also collaborating with i2pd to develop common congestion control strategies.</p>
+<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
+i2pd released their version 2.45.0 last week and the early results are encouraging.
+New protocols, and distributed networks, are difficult to develop.
+Congestion can arrive with little warning and with little clue of the cause.
+Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
+<p>Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию.</p>
+</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
 <p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
 <p>Как обычно, мы рекомендуем вам обновиться до последней версии. Лучший способ оставаться в безопасности и помогать сети — использовать последнюю версию.</p>
 </article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Recent Blog Posts" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>

data/translations/entries.sv.html

@@ -1,5 +1,174 @@
 <div>
-<header title="I2P-nyheter">Nyheter och uppdateringar för routern</header><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
+<header title="I2P-nyheter">Nyheter och uppdateringar för routern</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
+The bug primarily affected high-bandwidth routers.</p>
+<p>Som vanligt rekommenderar vi att du uppdaterar till den här utgåvan.
+Det bästa sättet att upprätthålla säkerheten och hjälpa nätverket är att använda den senaste utgåvan.</p>
+</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
+We have added notification bubbles to several applications in the console to highlight application messages.
+We fixed a tunnel test bug that may have been affecting tunnel reliability.
+The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
+There are several dark theme fixes and improvements.</p>
+<p>We fixed the installer that previously failed on Java 21 or higher.
+We also fixed installing to directory paths that contain spaces on Linux.
+For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
+<p>Som vanligt rekommenderar vi att du uppdaterar till den här utgåvan.
+Det bästa sättet att upprätthålla säkerheten och hjälpa nätverket är att använda den senaste utgåvan.</p>
+</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
+The workaround is using localhost and the server port, usually 7658, to bypass I2P.
+For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
+We apologize for the issue and are working on a fix.</p>
+</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
+<p>We have improved handling of congested routers in the network.
+Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
+We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
+Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
+<p>Som vanligt rekommenderar vi att du uppdaterar till den här utgåvan.
+Det bästa sättet att upprätthålla säkerheten och hjälpa nätverket är att använda den senaste utgåvan.</p>
+</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
+<p>Access to information from the console and applications has been improved.
+Issues have been fixed in I2PSnark and SusiMail search.
+The netDB search embedded into the router console now operates in a more intuitive and useful way.
+Minor improvements have been made to diagnostic displays in advanced mode.</p>
+<p>Bugs have also been fixed to improve compatibility within the network.
+An issue with publishing leaseSets was solved which improves reliability major hidden services.
+I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
+This prevents torrents from being unnecessarily disrupted by these changes.
+We welcomed this contribution from a new contributor.
+A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
+<p>Som vanligt rekommenderar vi att du uppdaterar till den här utgåvan.
+Det bästa sättet att upprätthålla säkerheten och hjälpa nätverket är att använda den senaste utgåvan.</p>
+</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
+This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
+<p>Som vanligt rekommenderar vi att du uppdaterar till den här utgåvan.
+Det bästa sättet att upprätthålla säkerheten och hjälpa nätverket är att använda den senaste utgåvan.</p>
+</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
+<p>Newer routers will be favored when selecting floodfill routers.
+I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
+Legacy transport protocols are being removed, simplifying the code in the UDP transports.
+Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
+Additional tweaks were made to peer selection strategies.</p>
+<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
+We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
+If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
+Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
+<p>Som vanligt rekommenderar vi att du uppdaterar till den här utgåvan.
+Det bästa sättet att upprätthålla säkerheten och hjälpa nätverket är att använda den senaste utgåvan.</p>
+</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
+<p>Som vanligt rekommenderar vi att du uppdaterar till den här utgåvan.
+Det bästa sättet att upprätthålla säkerheten och hjälpa nätverket är att använda den senaste utgåvan.</p>
+</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
+With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
+This should help the network return to normal operation.
+Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
+Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
+<p>Som vanligt rekommenderar vi att du uppdaterar till den här utgåvan.
+Det bästa sättet att upprätthålla säkerheten och hjälpa nätverket är att använda den senaste utgåvan.</p>
+</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
+This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
+Reachability of I2P sites is badly degraded.</p>
+<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
+Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
+</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
+<p>New features have been added to I2PSnark like the ability to search through torrents.
+Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
+We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
+New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
+Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
+<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
+This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
+This investigation uncovered one minor isolation-piercing event which we repaired.
+This issue was discovered and fixed internally by the I2P team.</p>
+<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
+This should result in improved delivery and availability for these downstream products.</p>
+<p>Som vanligt rekommenderar vi att du uppdaterar till den här utgåvan.
+Det bästa sättet att upprätthålla säkerheten och hjälpa nätverket är att använda den senaste utgåvan.</p>
+</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
+It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
+<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
+This will help the network limit the effect of tunnel spam.
+It will also help the network heal during and after DDOS attacks.</p>
+<p>The NetDb changes also help secure individual routers and the applications that use them. 
+Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
+This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
+<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
+<p>Som vanligt rekommenderar vi att du uppdaterar till den här utgåvan.
+Det bästa sättet att upprätthålla säkerheten och hjälpa nätverket är att använda den senaste utgåvan.</p>
+</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
+CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
+An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
+The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
+The attacker then sends the same message directly to the router.
+The router passes the message to the bloom filter, and is dropped.
+This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
+This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
+Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
+Users of Java I2P are recommended to update immediately to avoid the attack.</p>
+<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
+This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
+<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
+<p>This release also contains a tweakable blocklist.
+Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
+Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
+This feature is off-by-default and is only recommended for advanced users at this time.</p>
+<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
+It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
+<p>Som vanligt rekommenderar vi att du uppdaterar till den här utgåvan.
+Det bästa sättet att upprätthålla säkerheten och hjälpa nätverket är att använda den senaste utgåvan.</p>
+</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
+This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
+Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
+This issue has also been resolved.
+The docker container is now also compatible with Podman.</p>
+<p>Den här utgåvan synkroniserar översättningar med transifex, och uppdaterar GeoIP databasen.</p>
+<p>Som vanligt rekommenderar vi att du uppdaterar till den här utgåvan.
+Det bästa sättet att upprätthålla säkerheten och hjälpa nätverket är att använda den senaste utgåvan.</p>
+</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
+This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
+The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
+<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
+This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
+This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
+We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
+<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
+zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
+As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
+We thank zzz for providing these services for such a long time.</p>
+<p>Som vanligt rekommenderar vi att du uppdaterar till den här utgåvan.
+Det bästa sättet att upprätthålla säkerheten och hjälpa nätverket är att använda den senaste utgåvan.</p>
+</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS-Uppdatering" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS-Uppdatering</summary></details><p>We have confirmed that the attacker controls a large number of routers.
+Our investigations and mitigations continue.</p>
+<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
+We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
+However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
+The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
+<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
+We ask for your patience as we work to improve I2P.</p>
+</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P förblir intakt med försämrad prestanda.</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
+  The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
+  Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
+  Mitigation strategies are being investigated and implemented gradually.</p>
+<p>While the attack has degraded performance, the network remains intact and usable.
+  Java I2P routers appear to be handling the issues better than i2pd routers for now.
+  Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
+</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Utgåva" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
+As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
+First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
+Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
+Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
+<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
+possibly triggered by Bitcoin's new I2P transient address feature,
+but made worse by our SSU2 bugs and other congestion control problems.
+We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
+We have improved our algorithms to reduce network load during times of congestion.
+We are also collaborating with i2pd to develop common congestion control strategies.</p>
+<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
+i2pd released their version 2.45.0 last week and the early results are encouraging.
+New protocols, and distributed networks, are difficult to develop.
+Congestion can arrive with little warning and with little clue of the cause.
+Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
+<p>Som vanligt rekommenderar vi att du uppdaterar till den här versionen. Det bästa sättet att
+upprätthålla säkerheten och hjälpa nätverket är att köra den senaste versionen.</p>
+</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
 <p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
 <p>Som vanligt rekommenderar vi att du uppdaterar till den här versionen. Det bästa sättet att
 upprätthålla säkerheten och hjälpa nätverket är att köra den senaste versionen.</p>
@@ -7,8 +176,8 @@ upprätthålla säkerheten och hjälpa nätverket är att köra den senaste vers
 <ul>
 <li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Overview of our new SSU2 transport</a></li>
 <li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">A warning about I2P coins and other scams</a></li>
-<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">An interview with Konrad from diva.exchange</a></li>
-<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">An interview with Dustin from StormyCloud</a></li>
+<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">En intervju med Konrad från diva.exchange</a></li>
+<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">En intervju med Dustin från StormyCloud</a></li>
 </ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 with SSU2 for testing</summary></details><p>We have spent the last three months working on our new UDP transport protocol "SSU2"
 with a small number of volunteer testers.
 This release completes the implementation, including relay and peer testing.
@@ -59,7 +228,7 @@ Java 15.</p>
 <p>New I2P Easy-Install bundles have been generated using the latest release of the
 Java Virtual Machine. Further details have been published in the respective
 bundle newsfeeds.</p>
-</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 with reliability and performance improvements</summary></details><p>The 1.7.0 release contains several performance and reliability improvements.</p>
+</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 Utgåva" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 med tillförlitlighet och förbättrad prestanda</summary></details><p>1.7.0 Utgåvan har flera förbättringar i prestanda och tillförlitlighet.</p>
 <p>There are now popup messages in the system tray, for those platforms that support it.
 i2psnark has a new torrent editor.
 The NTCP2 transport now uses much less CPU.</p>
@@ -83,7 +252,7 @@ completing a full cryptography upgrade that started about 9 years ago.
 We expect to start joint testing with i2pd soon, and roll it out to the network later this year.</p>
 <p>Som vanligt rekommenderar vi att du uppdaterar till den här versionen. Det bästa sättet att
 upprätthålla säkerheten och hjälpa nätverket är att köra den senaste versionen.</p>
-</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 enables new tunnel build messages</summary></details><p>This release completes the rollout of two major protocol updates developed in 2021.
+</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 Utgåva" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 enables new tunnel build messages</summary></details><p>This release completes the rollout of two major protocol updates developed in 2021.
 The transition to X25519 encryption for routers is accelerated, and we expect almost all routers to be rekeyed by the end of the year.
 Short tunnel build messages are enabled for a significant bandwidth reduction.</p>
 <p>We added a theme selection panel to the new install wizard.
@@ -93,7 +262,7 @@ We have enhanced support for non-Java plugins.</p>
 <p>In other news, we are making excellent progress on the design of our new UDP transport SSU2 and expect to start implementation early next year.</p>
 <p>Som vanligt rekommenderar vi att du uppdaterar till den här versionen. Det bästa sättet att
 upprätthålla säkerheten och hjälpa nätverket är att köra den senaste versionen.</p>
-</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 with new tunnel build messages</summary></details><p>Yes, that's right, after 9 years of 0.9.x releases, we are going straight from 0.9.50 to 1.5.0.
+</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 Utgiven" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 with new tunnel build messages</summary></details><p>Yes, that's right, after 9 years of 0.9.x releases, we are going straight from 0.9.50 to 1.5.0.
 This does not signify a major API change, or a claim that development is now complete.
 It is simply a recognition of almost 20 years of work to provide anonymity and security for our users.</p>
 <p>This release finishes implementation of smaller tunnel build messages to reduce bandwidth.

data/translations/entries.tk.html

@@ -1,5 +1,173 @@
 <div>
-<header title="I2P Habarlary">Habarlar lentasy we router täzelemeleri</header><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
+<header title="I2P Habarlary">Habarlar lentasy we router täzelemeleri</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
+The bug primarily affected high-bandwidth routers.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
+We have added notification bubbles to several applications in the console to highlight application messages.
+We fixed a tunnel test bug that may have been affecting tunnel reliability.
+The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
+There are several dark theme fixes and improvements.</p>
+<p>We fixed the installer that previously failed on Java 21 or higher.
+We also fixed installing to directory paths that contain spaces on Linux.
+For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
+The workaround is using localhost and the server port, usually 7658, to bypass I2P.
+For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
+We apologize for the issue and are working on a fix.</p>
+</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
+<p>We have improved handling of congested routers in the network.
+Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
+We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
+Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
+<p>Access to information from the console and applications has been improved.
+Issues have been fixed in I2PSnark and SusiMail search.
+The netDB search embedded into the router console now operates in a more intuitive and useful way.
+Minor improvements have been made to diagnostic displays in advanced mode.</p>
+<p>Bugs have also been fixed to improve compatibility within the network.
+An issue with publishing leaseSets was solved which improves reliability major hidden services.
+I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
+This prevents torrents from being unnecessarily disrupted by these changes.
+We welcomed this contribution from a new contributor.
+A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
+This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
+<p>Newer routers will be favored when selecting floodfill routers.
+I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
+Legacy transport protocols are being removed, simplifying the code in the UDP transports.
+Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
+Additional tweaks were made to peer selection strategies.</p>
+<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
+We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
+If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
+Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
+With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
+This should help the network return to normal operation.
+Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
+Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
+This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
+Reachability of I2P sites is badly degraded.</p>
+<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
+Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
+</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
+<p>New features have been added to I2PSnark like the ability to search through torrents.
+Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
+We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
+New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
+Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
+<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
+This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
+This investigation uncovered one minor isolation-piercing event which we repaired.
+This issue was discovered and fixed internally by the I2P team.</p>
+<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
+This should result in improved delivery and availability for these downstream products.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
+It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
+<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
+This will help the network limit the effect of tunnel spam.
+It will also help the network heal during and after DDOS attacks.</p>
+<p>The NetDb changes also help secure individual routers and the applications that use them. 
+Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
+This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
+<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
+CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
+An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
+The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
+The attacker then sends the same message directly to the router.
+The router passes the message to the bloom filter, and is dropped.
+This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
+This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
+Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
+Users of Java I2P are recommended to update immediately to avoid the attack.</p>
+<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
+This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
+<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
+<p>This release also contains a tweakable blocklist.
+Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
+Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
+This feature is off-by-default and is only recommended for advanced users at this time.</p>
+<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
+It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
+This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
+Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
+This issue has also been resolved.
+The docker container is now also compatible with Podman.</p>
+<p>This release syncs translations with transifex and updates the GeoIP database.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
+This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
+The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
+<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
+This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
+This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
+We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
+<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
+zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
+As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
+We thank zzz for providing these services for such a long time.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
+Our investigations and mitigations continue.</p>
+<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
+We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
+However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
+The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
+<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
+We ask for your patience as we work to improve I2P.</p>
+</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
+  The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
+  Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
+  Mitigation strategies are being investigated and implemented gradually.</p>
+<p>While the attack has degraded performance, the network remains intact and usable.
+  Java I2P routers appear to be handling the issues better than i2pd routers for now.
+  Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
+</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
+As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
+First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
+Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
+Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
+<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
+possibly triggered by Bitcoin's new I2P transient address feature,
+but made worse by our SSU2 bugs and other congestion control problems.
+We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
+We have improved our algorithms to reduce network load during times of congestion.
+We are also collaborating with i2pd to develop common congestion control strategies.</p>
+<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
+i2pd released their version 2.45.0 last week and the early results are encouraging.
+New protocols, and distributed networks, are difficult to develop.
+Congestion can arrive with little warning and with little clue of the cause.
+Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
+<p>Adatça bolşy ýaly bu wersiýa çenli täzelemekligi maslahat berýäris. Howpsuzlygy üpjün etmegiň we ulgama kömek etmegiň iň gowy ýoly - iň soňky wersiýany ulanmak.</p>
+</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
 <p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
 <p>Adatça bolşy ýaly bu wersiýa çenli täzelemekligi maslahat berýäris. Howpsuzlygy üpjün etmegiň we ulgama kömek etmegiň iň gowy ýoly - iň soňky wersiýany ulanmak.</p>
 </article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Recent Blog Posts" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>

data/translations/entries.tr.html

@@ -1,8 +1,193 @@
 <div>
-<header title="I2P Haberleri">Haber akışı ve yöneltici güncellemeleri</header><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 taşıyıcısı etkinleştirildi</summary></details><p>I2P 2.0.0 sürümü, küçük özelliklerin, denemelerin ve çok sayıda hata düzeltmesinin tamamlanmasından sonra yeni SSU2 UDP taşıyıcımızı tüm kullanıcılar için etkinleştirdi.</p>
-<p>Ayrıca kurucu, ağ veritabanı, kişisel adres defterine ekleme, Windows web tarayıcı başlatıcısı ve IPv6 UPnP ile birlikte pek çok düzeltme yaptık.</p>
+<header title="I2P Haberleri">Haber akışı ve yöneltici güncellemeleri</header><article id="urn:uuid:f2a6aabd-ee29-4f45-a8dd-7378e907016a" title="2.9.0 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2025/06/02/2.9.0_released" author="idk" published="2025-06-02T19:00:00Z" updated="2025-06-02T19:00:00Z"><details><summary>I2P 2.9.0 sürümü</summary></details><p>I2P 2.9.0, hata düzeltmeleri ve yeni özellikler üzerinde çalışılmış bir bakım sürümüdür.</p>
+<p>I2ptunnel sisteminin başarımını artırmak için işlem kullanımı iyileştirildi.
+NTCP2, inceleme saldırılarına direnecek şekilde geliştirildi.
+Bildirim sistemi, kullanıcılara I2PSnark ve diğer uygulamalardan daha iyi geri bildirim sağlamak için daha fazla uygulama ile bütünleştirildi.
+Otomatik doldurma kaydı düzeltildi.
+Kullanıcıların, otomatik doldurma olarak davranırken artan kaynak kullanımını gözlemleyebilmesi sağlandı.
+Bu özellik istenmiyorsa, /config sayfasından otomatik doldurma kipinin kapatılması sağlandı.</p>
+<p>Konsola, netDb görünümünüzde yönelticilerin konumlarını gösteren yeni bir küresel harita özelliği eklendi.
+Bunlar, yönelticinizin tüneller oluşturmasını ve hizmetleri anonim olarak sağlamasını sağlayan eşlerdir.</p>
+<p>Tüneller, Datagram2 iletişim kuralı ve Post-Quantum şifreleme için otomatik bant genişliği yönetimini ekleme çalışmaları sürüyor.
+İki sürüm içinde, I2P 2.11.0 sürümünde Java 17 kullanılması zorunlu olacak.</p>
+<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir.
+Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
+</article><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 sürümü</summary></details><p>2.8.2 sürümünde, 2.8.1 sürümünde tanıtılan SHA256 sorunlarına neden olan hata düzeltildi.
+Hata, öncelikle ban genişliği yüksek olan yönelticileri etkiledi.</p>
+<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir.
+Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
+</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 sürümü</summary></details><p>2.8.1 sürümünde 2.8.0 sürümünde bozulan yerel sitelere erişim sağlandı.
+Uygulama iletilerini vurgulamak için konsoldaki çeşitli uygulamalara bildirim balonları eklendi.
+Tünel güvenilirliğini etkileyebilecek bir tünel sınama hatası hazırladık.
+Adres defterine aboneliklerinizden eklenen en yeni sunucu adlarını görüntüleyen yeni bir "son" sekmesi eklendi.
+Birkaç karanlık tema düzeltmesi ve iyileştirmeler yapıldı.</p>
+<p>Daha önce Java 21 ve üzeri sürümlerde çalışmayan kurucu düzeltildi.
+Linux üzerinde boşluk içeren klasör yollarına kurulum da düzenlendi.
+Docker kullananlar için, eski Docker kapsayıcısını ve kapsayıcı kitaplıkları güncellendi.</p>
+<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir.
+Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
+</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="2.8.0 sürümündeki yerel site erişim sorunları" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 yerel erişim hatası</summary></details><p>2.8.0 sürümünde bir yerel siteye (sunucu adı veya b32 ile) gezinmek başarısız oluyordu.
+Geçici çözüm, I2P yönelticisini atlamak için localhost ve genellikle 7658 numaralı sunucu bağlantı noktasını kullanmak.
+Örnek: <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
+Bu sorun için özür dileriz. Düzeltmek için çalışıyoruz.</p>
+</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 sürümü" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 sürümü</summary></details><p>Bu sürümde, hataları düzelterek, kullanılmayan kodları kaldırarak ve ağ kararlılığını iyileştirerek I2P uygulamasını geliştiriyoruz.</p>
+<p>Ağdaki yoğun yönelticilerin işlenmesini iyileştirdik.
+UPnP ve NAT geçişindeki sorunlar, bağlantıyı ve hata bildirimini iyileştirmek için ele alındı.
+Artık yöneltici başarımını iyileştirmek ve aşırı yüklenmeyi azaltmak için NetDb içinden kiralama kümelerini kaldırmak üzere daha saldırgan bir strateji uyguluyoruz.
+Yönelticinin yeniden başlatılması veya kapanması gibi olayların gözlemlenebilirliğini azaltmak için başka değişiklikler yaptık.</p>
+<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir.
+Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
+</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 sürümü" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 sürümü</summary></details><p>I2P 2.7.0 sürümünde hataları düzelterek, başarımı iyileştirerek ve özellikler ekleyerek çalışmalarımızı sürdürüyoruz.</p>
+<p>Konsoldan ve uygulamalardan bilgilere erişim iyileştirildi.
+I2PSnark ve SusiMail aramasındaki sorunlar giderildi.
+Yöneltici konsoluna gömülü netDB araması artık daha sezgisel ve kullanışlı bir şekilde çalışıyor.
+Gelişmiş kipte tanılama ekranlarında küçük iyileştirmeler yapıldı.</p>
+<p>Ağ içindeki uyumluluğu iyileştirmek için hatalar da düzeltildi.
+Kiralama Kümelerini yayınlamayla ilgili bir sorun çözüldü ve bu da büyük gizli servislerin güvenilirliğini artırdı.
+I2PSnark üzerinde artık bir kullanıcı yalnızca var olan bir torrent üzerindeki izleyicileri değiştirdiğinde infohash değerinin değişmemesi sağlandı.
+Böylece, torrentlerin bu değişiklikler nedeniyle gereksiz yere kesintiye uğraması engellendi.
+Yeni bir katılımcının bu katkısını memnuniyetle karşıladık.
+Diğer I2P uygulamalarıyla uyumluluğu iyileştirmek için bir akış kitaplığı seçeneğinin işlenmesindeki bir çakışma sorunu çözüldü.</p>
+<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir.
+Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
+</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 sürümü</summary></details><p>I2P 2.6.1, Gizli Hizmetler Yöneticisi uygulamasındaki bir kullanıcı arayüzü hatasını düzeltmek için yayınlandı.
+Bu hata kaydırmanın etkisizleştirilmesine ve bazı yapılandırmaların erişilemez olmasına yol açıyordu.</p>
+<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir.
+Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
+</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Sürümü Yayınladı" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 sürümü</summary></details><p>I2P 2.6.0 sürümünde hataları düzelterek, özellikler ekleyerek ve ağın güvenilirliğini iyileştirerek çalışmalarımızı sürdürüyoruz.</p>
+<p>Otomatik doldurma yönelticileri seçilirken daha yeni yönelticilerin yeğlenmesi sağlandı.
+I2PSnark, hata düzeltmelerinin yanında PeX(Peer Exchange) başarımı iyileştiren özellikler aldı.
+Eski aktarım iletişim kuralları kaldırıldı ve UDP aktarımlarının kodu basitleştirildi.
+Yerel olarak barındırılan hedef, yerel istemciler tarafından Kiralama Kümelerini istemeden 
+erişilebilir oldu ve bu da başarım ve denenebilirliği artırdı.
+Eş seçimi stratejilerinde ayarlamalar yapıldı.</p>
+<p>I2P artık I2P-over-Tor kullanılmasına izin vermiyor, Tor çıkış IP adreslerinden gelen bağlantılar artık engelleniyor.
+Bunu önermiyoruz çünkü I2P başarımını düşürüyor ve hiçbir fayda sağlamadan Tor çıkış aktarıcılarının kaynaklarını tüketiyor.
+Hem Tor çıkış aktarıcısı hem de I2P işleten yardımsever bir kişiyseniz, bunu yapmayı sürdürmek için her birinde farklı IP adresleri kullanmanızı öneririz.
+Çıkış dışındaki aktarıcılar ve Tor istemcileri bundan etkilenmez ve herhangi bir şeyi değiştirmeleri gerekmez.</p>
+<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir.
+Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
+</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 sürümü HTTP düzeltmesi ile yayınlandı</summary></details><p>I2P 2.5.2 ile 2.5.0 sürümünde ortaya çıkan ve bazı HTTP içeriklerinin kırpılmasına neden olan bir hata düzeltildi.</p>
+<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir.
+Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
+</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="2.5.1 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P 2.5.1 hizmet reddi saldırılarının çözümüyle yayınlandı</summary></details><p>I2P 2.5.1, I2P ağını ve hizmetlerini etkileyen hizmet reddi saldırılarını çözmek için yayımlandı.
+Bu sürümde, Sybil saldırı algılama aracının, saldırının etkisini ve süresini artırmayı hedefleyen IP tabanlı kısımlarını kullanımdan kaldırıyoruz.
+Bu uygulama, ağın normal çalışmaya dönmesine yardımcı olacak.
+Sybil saldırı algılama aracını kapatmış olan kullanıcılar, aracı güvenle yeniden etkinleştirebilir.
+RouterInfo doğrulamasını ve eş seçimini iyileştirmek için diğer alt sistemlerde de ayarlamalar yapıldı.</p>
+<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir.
+Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
+</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Fırtınalı Hava" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Ağ havası: Fırtınalı. I2p saldırıya uğradı.</summary></details><p>I2P ağına hizmet reddi saldırısı yapılıyor.
+Bu saldırı I2P ve i2pd uygulamalarını farklı şekillerde etkiliyor ve ağ sağlığı üzerinde ciddi bir etkisi var.
+I2P sitelerinin erişilebilirliği büyük ölçüde bozuldu.</p>
+<p>I2P üzerinde barındırdığınız bir hizmet varsa ve bu hizmet bir otomatik doldurma yönelticisinde barındırılıyorsa erişilebilirliği artırmak için hizmeti otomatik doldurma kullanılmayan bir yönelticide birden fazla sunucuya bağlamayı düşünmelisiniz.
+Diğer azaltımlar tartışılıyor ancak uzun vadeli, geriye dönük uyumlu bir çözüm üzerinde çalışmayı sürdürüyoruz.</p>
+</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="Yeni I2P 2.5.0 sürümü yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>Ek uygulama iyileştirmeleri yapldı. NetDB yalıtım stratejisi denetimi</summary></details><p>I2P 2.5.0 sürümünde, ağ veri tabanı (NetDB) yalıtım stratejisinin uygulanmasına odaklanan 2.4.0 sürümüne göre kullanıcı tarafında ek iyileştirmeler yapıldı.</p>
+<p>I2PSnark üzerine torrentlerde arama yapma gibi yeni özellikler eklendi.
+BiglyBT ve qBittorrent gibi diğer I2P torrent istemcileriyle uyumluluğu artırmak için sorunlar düzeltildi.
+I2P desteklerini etkinleştirmek ve geliştirmek için libtorrent ve qBittorrent ile çalışan tüm geliştiricilere teşekkür ederiz.
+E-postalarda Markdown biçimlendirmesi desteği ve ek dosyaları e-postalara sürükleyip bırakma yeteneği ile birlikte yeni SusiMail özellikleri eklendi.
+Gizli hizmetler yöneticisiyle oluşturulan tüneller artık başarım ve internet teknolojileriyle uyumluluğu geliştirerek daha gelişmiş I2P sitelerinin önünü açan "Keepalive" özelliğini destekliyor.</p>
+<p>Bu sürüm ile, ağ veri tabanının (NetDB) istenmeyen iletilere karşı direncini artırmak ve yönelticinin şüpheli iletileri reddetme yeteneğini geliştirmek için de birkaç değişiklik yaptık.
+Bu,nlar 2.4.0 sürümündeki "Alt veri tabanı yalıtımı" savunmalarının uygulanmasını "denetleme" çabasının bir parçasıydı.
+Bu araştırma sırasında, küçük bir yalıtımı aşma durumu ortaya çıktı.
+Bu sorun, I2P ekibi tarafından içeride bulundu ve düzeltildi.</p>
+<p>Bu sürüm ile, Android ve Windows için alt dağıtımlarımızı yayınlama sürecinde çeşitli iyileştirmeler yaptık.
+Bu iyileştirmeler, bu alt ürünler için aktarım ve bulunabilirliği iyileştirmiş olmalı.</p>
+<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir.
+Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
+</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 sürümü tıkanıklık ve ağ veri tabanı (NetDB) güvenliği iyileştirmeleriyle yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 sürümü tıkanıklık ve ağ veri tabanı (NetDB) güvenliği iyileştirmeleriyle yayınlandı</summary></details><p>Bu sürümde, I2P 2.4.0, I2P ağının güvenliğini ve kararlılığını iyileştirme çabalarımızı sürdürüyor.
+Eşlerinizi keşfetmek için kullanılan I2P ağı içindeki önemli bir yapı olan ağ veri tabanında önemli iyileştirmeler bulunuyor.</p>
+<p>Tıkanıklık yönetimi değişiklikleri, yönelticilere tıkanıklık yaşayan eşlerden kaçınarak onları rahatlatma yeteneği vererek ağ kararlılığını artıracak.
+Böylece, ağda istenmeyen tünellerin etkisinin sınırlaması sağlanacak.
+Ayrıca DDOS saldırıları sırasında ve sonrasında ağın iyileşmesine de yardımcı olacak.</p>
+<p>Ağ veri tabanı değişiklikleri ayrıca tek tek yönelticilerin ve bunları kullanan uygulamaların güvenliğinin sağlanmasına da yardımcı oluyor.
+Yönlendiriciler artık ağ veri tabanını uygulamalarla yöneltici arasındaki bilgi sızıntısını önlemek için kullandığımız birden fazla "alt veri tabanına" ayırarak saldırganlara karşı savunma yapabiliyor.
+Bu aynı zamanda Java yönelticilerin ağ veri tabanı işlemleriyle ilgili güncel bilgilerini geliştiriyor ve çoklu sunucu uygulamalarına yönelik desteğimizi basitleştiriyor.</p>
+<p>Ayrıca I2PSnark ve SusiMail uygulamalarında çeşitli hata düzeltmeleri ve geliştirmeler de bulunuyor.</p>
+<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir.
+Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
+</article><article id="urn:uuid:" title="Yeni I2P 2.3.0 sürümü yayınlandı. Güvenlik düzeltmeleri, değiştirilebilir engelleme listeleri ve DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Güvenlik düzeltmeleri, değiştirilebilir engelleme listeleri ve DTG API</summary></details><p>Bu sürümde, CVE-2023-36325 için düzeltmeler bulunuyor.
+CVE-2023-36325, bloom süzgecinde ortaya çıkan bir bağlam karışıklığı hatasıdır.
+Saldırgan, benzersiz bir ileti kimliği olan bir I2NP iletisi oluşturur ve bu ileti kimliğini bir istemciye gönderir.
+İletinin bloom süzgecinden geçtikten sonra ikinci bir iletide kullanılmasına izin verilmez.
+Saldırgan daha sonra aynı iletiyi doğrudan yönelticiye gönderir.
+Yöneltici iletiyi bloom süzgecine iletir ve bırakır.
+Böylece, ileti kimliğinin daha önce görüldüğü bilgisini sızdırarak saldırgana istemciyi bu yönelticinin barındırdığına inanması için güçlü bir neden verir.
+Bu sorun, bloom süzgecinin işlevselliğinin, bir iletinin istemci tünelinden (bir keşif tüneli) gelip doğrudan yönelticiye gönderilip gönderilmediğine bağlı olarak farklı bağlamlara ayrılmasıyla düzeltildi.
+Normal koşullar altında, bu saldırının başarılı bir şekilde gerçekleştirilmesi birkaç gün sürer ve saldırı aşamasında yönelticilerin yeniden başlatılması ve hatalı doğru sonuçlara karşı duyarlılık gibi çeşitli faktörler nedeniyle kafa karıştırıcı olabilir.
+Saldırıyı önlemek için Java I2P kullanıcılarının hemen güncelleme yapması önerilir.</p>
+<p>Bu bağlam karışıklığı hatasını düzeltme sürecinde, bazı stratejilerimizin kodunu bu tür sızıntılara karşı savunma amacıyla değiştirdik.
+Bunlar ağ veri tabanı üzerinde yapılan değişiklikler, hız sınırlayıcı mekanizmaların ve otomatik doldurma yönelticilerinin davranışlarıdır.</p>
+<p>Bu sürümde ikinci varsayılan sunucu hizmeti sağlayıcısı olarak not_bob eklendi ve konsol ana sayfasına <a href="http://notbob.i2p">notbob.i2p</a> ile <a href="http://ramble.i2p">ramble.i2p</a> eklendi.</p>
+<p>Bu sürümde ayrıca değiştirilebilir bir engelleme listesi bulunuyor.
+Engelleme listesi yarı kalıcıdır. Engellenen her IP adresi normalde yöneltici yeniden başlatılana kadar engellenir.
+Sybil saldırıları sırasında engellenenler listesinin aşırı hızlı arttığını gözlemleyen kullanıcılar, engellenenler listesini belirli aralıklarla kayıtların süresi dolacak şekilde yapılandırarak daha kısa zaman aşımı süreleri kullanmayı yeğleyebilir.
+Bu özellik varsayılan olarak kapalıdır ve şu anda yalnızca uzman kullanıcıların kullanması önerilmektedir.</p>
+<p>Bu sürümde ayrıca eklentilerin Masaüstü görsel kullanıcı arayüzü (DTG) ile değiştirilebilmesi için bir API bulunuyor.
+Artık sistem tepsisine menü ögeleri eklenebilir. Böylece yerel uygulama arayüzlerini kullanan eklentiler daha sezgisel olarak başlatılabilir.</p>
+<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir.
+Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
+</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="Yeni 2.2.1 sürümü yayınlandı. Docker, Ubuntu, Lunar ve Debian Sid paketleme düzeltmeleri yapıldı" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - 2.2.0 sürümü için düzeltme sürümü</summary></details><p>DDOS saldırılarını zayıflatmayı hızlandırmak amacıyla öne alınan I2P 2.2.0 sürümünün ardından, yeni paketler oluşturmayı ve yayınlamayı gerekli kılan birkaç sorunu öğrendik.
+Bu sürüm, jakarta paketinin güncellenmiş bir sürümü kullanılarak yöneltici konsoluna erişilemeyen Ubuntu Lunar ve Debian Sid içindeki bir sorunu gideriyor.
+Docker paketleri bağımsız değişkenleri doğru okumuyordu ve bu da yapılandırma dosyalarına erişilememesine neden oluyordu.
+Bu sorun da çözüldü.
+Docker kapsayıcısı artık Podman ile de uyumlu.</p>
+<p>Bu sürümde, çevirileri transifex ile eşitlendi ve GeoIP ver itabanı güncellendi.</p>
+<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir.
+Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
+</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="Yeni 2.2.0, sürümünde DDOS saldırılarını zayıflatıldı ve akış alt sisteminde ince ayarlar yapıldı" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>DDOS saldırıları zayıflatıldı ve akış alt sisteminde ince ayarlar yapıldı</summary></details><p>Bugün yani 13 Mart 2023 tarihinde sunulacak olan 2.2.0 sürümünün çıkış tarihini erteledik.
+Bu sürümde, NetDB, Floodfill ve Peer-Selection bileşenlerinde, yönelticinin DDOS saldırılarına karşı hayatta kalma yeteneğini geliştiren bir değişiklik bulunuyor.
+Büyük olasılıkla saldırılar sürecektir. Ancak bu sistemlerde yapılan iyileştirmeler, yönelticinin kötü amaçlı görünen yönelticileri tanımlamasına ve önceliklerini kaldırmasına yardımcı olarak DDOS saldırısı riskini azaltmaya yardımcı olur.</p>
+<p>Bu sürümde ayrıca akış alt sistemine, şifrelenmiş bir paketi yakalayabilen bir saldırganın onu istenmeyen alıcılara göndererek yeniden kullanmasını önleyen yeniden oynatma koruması eklendi.
+Bu geriye dönük olarak uyumlu bir değişikliktir. Bu nedenle eski yönelticiler yeni yönelticilerin akış özelliklerini kullanmayı sürdürebilecektir.
+Bu sorun, I2P geliştirme ekibi tarafından keşfedildi, içeride düzeltildi ve DDOS saldırılarıyla ilgili değil.
+Vahşi doğada yeniden oynatılan bir akış paketiyle hiç karşılaşmadık ve şu anda I2P ağına karşı bir akış yeniden oynatma saldırısının gerçekleştiğine inanmıyoruz.</p>
+<p>Fark etmiş olabileceğiniz gibi, bu sürüm notları ve sürümün kendisi zzz tarafından değil idk tarafından imzalanmıştır.
+zzz projeden uzaklaşmayı seçti ve sorumlulukları diğer ekip üyeleri tarafından üstleniliyor.
+Bu nedenle proje, ağ istatistikleri altyapısını değiştirmeye ve geliştirme forumunu i2pforum.i2p üzerine taşımaya çalışıyor.
+Bu hizmetleri bu kadar uzun süre sağlayan zzz'ye teşekkür ediyoruz.</p>
+<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir.
+Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
+</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS güncellemesi" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS güncellemesi</summary></details><p>Saldırganın çok sayıda yönelticiyi kontrol ettiğini onayladık.
+Soruşturmalarımız ve zayıflatma çalışmalarımız sürüyor.</p>
+<p>Bu an, insanlara 20 yıl sonra bile I2P ağının nispeten küçük olduğunu hatırlatmak için iyi bir zaman.
+Saldırganın belirli bir kullanıcıyı veya gizli hizmeti anonimleştirmeye çalıştığına dair hiçbir kanıtımız yok.
+Ancak, yüksek riskli bir tehdit modeliniz varsa, I2P tarafından şu anda gerek duyduğunuz korumanın sağlanıp sağlanmadığını dikkatlice değerlendirmelisiniz.
+Uzun vadede en iyi çözüm, kullanıcılarımızın güvenliğini artırmak için bu bilgiyi yaymak ve I2P ağını büyütmektir.</p>
+<p>Gerektiğinde burada haber akışında ve <a href="http://zzz.i2p">zzz.i2p</a> üzerinde ek bilgi vereceğiz.
+Biz I2P geliştirmeleri üzerinde çalışırken sabırlı olmanızı rica ediyoruz.</p>
+</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="Son hizmet reddi (DDoS) saldırıları hakkında" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P bozulan başarımda bozulmadan kaldı</summary></details><p>I2P ağı şu anda bir hizmet reddi saldırısından etkileniyor.
+  Ağın otomatik doldurma işlevi etkilendi. Bu da yanıtların kesintiye uğramasına ve tünel oluşturma başarı oranlarının düşmesine neden oldu.
+  Ağa karkıda bulunanlar, I2P sitelerine bağlanma ve I2P hizmetlerini kullanma konusunda zorluklar yaşadı.
+  Zayıflatma stratejileri kademeli olarak araştırılıp uygulanıyor.</p>
+<p>Saldırı başarımı düşürmüş olsa da, ağ bozulmadan ve kullanılabilir durumda kaldı.
+  Java I2P yönelticileri, sorunlarla şimdilik i2pd yönlendiricilerinden daha iyi başa çıkıyor gibi görünüyor.
+  Önümüzdeki hafta hem Java hem de C++ yönelticilerinin geliştirme yapılarında çeşitli zayıflatmalar görünmeye başlayacak.</p>
+</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 sürümü çeşitli SSU2 düzeltmeleri ile yayınlandı</summary></details><p>Kasım ayında yayınlanan 2.0.0 sürümünden bu yana birçok şey öğrendik.
+Yönelticiler bu sürüme güncellendikçe, yeni SSU2 aktarım iletişim kuralımız 
+için ağ desteği %1 oranından yaklaşık olarak %60 oranının üzerine çıktı.
+İlk olarak, SSU2 iletişim kuralının sağlam, iyi tasarlanmış ve güvenli olduğunu doğruladık.
+İkinci olarak, iletişim kuralının uygulanmasında çok sayıda küçük ya da nadiren karşılaşılan 
+hatalar bulduk ve düzelttik.
+Bu hataların toplu etkisi ağın başarımını düşürüyordu.</p>
+<p>Ayrıca, muhtemelen yeni Bitcoin I2P geçici adres özelliği tarafından tetiklenen ve 
+SSU2 hatalarımız ile diğer tıkanıklık denetimi sorunlarımız tarafından daha da 
+kötü duruma gelerek, ağda tünel sayısının artmasına ve tünel oluşturma başarı 
+oranının azalmasına neden olan sorunların farkındayız.
+I2P ağ isteklerini azaltmak için Bitcoin ve Bitcoin dışındaki diğer projelerle birlikte çalışıyoruz.
+Sıkışıklık zamanlarında ağ yükünü azaltmak için algoritmalarımızı geliştirdik.
+Ayrıca ortak tıkanıklık denetleme stratejileri geliştirmek için i2pd ile işbirliği yapıyoruz.</p>
+<p>Bu nedenle, düzeltmeleri herkese ulaştırmak için bu sürümü yaklaşık altı hafta öne aldık.
+i2pd geçen hafta 2.45.0 sürümünü yayınladı ve erken sonuçlar cesaret verici.
+Yeni iletişim kurallarının ve dağıtılmış ağların geliştirilmesi zordur.
+Tıkanıklık, çok az uyarıyla ve nedeni hakkında çok az ipucuyla ortaya çıkabilir.
+Sorunları bulup çözdüğümüzü umuyoruz. Sabrınız için teşekkür ederiz.</p>
 <p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
-</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Son günlük yazıları" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>Son bir kaç günlük yazısı</summary></details><p>Web sitemizdeki son bir kaç günlük yazısının bağlantıları:</p>
+</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 taşıyıcısı etkinleştirildi</summary></details><p>I2P 2.0.0 sürümü, küçük özelliklerin, denemelerin ve çok sayıda hata düzeltmesinin tamamlanmasından sonra yeni SSU2 UDP taşıyıcımızı tüm kullanıcılar için etkinleştirdi.</p>
+<p>Ayrıca kurucu, ağ veri tabanı, kişisel adres defterine ekleme, Windows tarayıcı başlatıcısı ve IPv6 UPnP ile birlikte pek çok düzeltme yaptık.</p>
+<p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
+</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Son günlük yazıları" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>Son bir kaç günlük yazısı</summary></details><p>Sitemizdeki son bir kaç günlük yazısının bağlantıları:</p>
 <ul>
 <li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Yeni SSU2 taşıyıcımıza genel bakış</a></li>
 <li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">I2P taklitleri ve diğer dolandırıcılıklar hakkında uyarı</a></li>
@@ -27,7 +212,7 @@ Ayrıca, zaten düzeltilmiş olan nadir bir kilitlenme için otomatik bir kilitl
 <b>exit.stormycloud.i2p</b> uzun süredir kullanılmayan <b>false.i2p</b> 
 vekil sunucumuzun yerini alan resmi, önerilen dış vekil sunucumuzdur.
 StormyCloud <a href="http://stormycloud.i2p/">kuruluşu</a>, <a href="http://stormycloud.i2p/outproxy.html">çıkış vekil sunucusu</a> ve <a href="http://stormycloud.i2p/tos.html">hizmet koşulları</a> 
-hakkında ayrıntılı bilgi almak için <a href="http://stormycloud.i2p/">StormyCloud web sitesine</a> bakabilirsiniz.</p>
+hakkında ayrıntılı bilgi almak için <a href="http://stormycloud.i2p/">StormyCloud sitesine</a> bakabilirsiniz.</p>
 <p><a href="/i2ptunnel/edit?tunnel=0">Gizli Hizmetler Yöneticisi yapılandırmanızı</a>,
 iki yerde <b>exit.stormycloud.i2p</b> belirtecek şekilde değiştirmenizi 
 öneririz: <b>Outproxies</b> ve <b>SSL Outproxies</b>.
@@ -39,7 +224,7 @@ Teşekkürler StormyClod. Bağış yaparak bizi desteklemeyi düşünün.</p>
 </article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 sürümü bazı hata düzeltmeleri ile yayınlandı</summary></details><p>Bu sürümde, i2psnark, yöneltici, I2CP ve UPnP
 üzerinde yapılmış hata düzeltmeleri bulunuyor.
 Yöneltici, yumuşak yeniden başlatma, IPv6, SSU 
-eş sınaması, ağ veritabanı kaydetme ve tünel 
+eş sınaması, ağ veri tabanı kaydetme ve tünel 
 oluşturma adres hataları düzeltildi.
 Yöneltici ailesi kullanımı ve Sybil sınıflandırması da 
 önemli ölçüde iyileştirildi.</p>
@@ -48,9 +233,9 @@ SSU2, önemli başarım ve güvenlik iyileştirmeleri getirecek.
 Ayrıca, yaklaşık 9 yıl önce başlattığımız tam şifreleme 
 yükseltmesini tamamlıyoruz. Böylece çok yavaş ElGamal 
 şifrelemesini son kez kullanıyoruz ve nihayet değiştirebileceğiz.
-Bu sürümde, varsayılan olarak devre dışı bırakılmış bir ön 
-uygulama bulunuyor. Denemelere katılmak istiyorsanız, 
-zzz.i2p adresindeki güncel bilgileri bakabilirsiniz.</p>
+Bu sürümde, varsayılan olarak etkisizleştirilmiş bir ön 
+uygulama bulunuyor. Denemelere katkıda bulunmak
+istiyorsanız, zzz.i2p adresindeki güncel bilgileri bakabilirsiniz.</p>
 <p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
 </article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Temel Java/JPackage güncellemeleri kuruldu" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>Yeni bulunan Java "Psişik imzalar" güvenlik açığı I2P uygulamasını etkiliyor. 
 Linux için I2P kullanan veya kurulum paketinde bulunmayan bir JVM kullanan 
@@ -63,19 +248,19 @@ paketleri oluşturuldu. Ayrıntılı bilgi almak için paket haber akışlarına
 Yeni bir i2psnark torrent düzenleyicisi var.
 NTCP2 taşıyıcısı artık çok daha az işlemci kullanıyor.</p>
 <p>Uzun süredir kullanımdan kaldırılan BOB arayüzü, yeni kurulumlar için kaldırıldı.
-Debian paketleri dışında var olan kurulumlarda çalışmaya devam edecek.
+Debian paketleri dışında var olan kurulumlarda çalışmayı sürdürecek.
 BOB uygulamalarının kalan tüm kullanıcıları, geliştiricilerden SAMv3 iletişim kuralına geçmelerini istemelidir.</p>
 <p>1.6.1 sürümümüzden bu yana ağ güvenilirliğinin giderek kötüleştiğini biliyoruz.
 Yayınlandıktan hemen sonra sorunun farkındaydık, ancak nedenini bulmamız neredeyse iki ayımızı aldı.
 Sonunda bunu i2pd 2.40.0 sürümünde bir hata olarak belirledik. 
 Düzeltmesi, bu sürümle yaklaşık olarak aynı zamanda çıkan 2.41.0 sürümünde olacak.
-Bu arada, ağ veritabanı aramalarının ve depolarının sağlamlığını geliştirmek ile tünel eş seçiminde başarımı düşük olan 
+Bu arada, ağ veri tabanı aramalarının ve depolarının sağlamlığını geliştirmek ile tünel eş seçiminde başarımı düşük olan 
 eşlerden kaçınmak için Java I2P tarafında birkaç değişiklik yaptık.
 Böylece, hatalı veya kötü niyetli yönelticilerin varlığında bile ağ daha sağlam olmalı.
 Ayrıca, yayın öncesi i2pd ve Java I2P yönelticilerini yalıtılmış bir deneme ağında 
 birlikte denemek için ortak bir program başlatıyoruz. Böylece daha fazla sorunu 
 sürümler yayınlandıktan sonra değil, yayınlanmadan önce bulabiliriz.</p>
-<p>Diğer yandan, yeni UDP taşıyıcımız "SSU2" (159 numaralı öneri) tasarımında büyük ilerleme kaydetmeye devam ediyoruz 
+<p>Diğer yandan, yeni UDP taşıyıcımız "SSU2" (159 numaralı öneri) tasarımında büyük ilerleme kaydetmeyi sürdürüyoruz 
 ve kullanıma almaya başladık.
 SSU2, önemli başarım ve güvenlik iyileştirmeleri getirecek.
 Ayrıca, yaklaşık 9 yıl önce başlayan tam şifreleme yükseltmesini tamamlayarak, çok yavaş ElGamal şifrelemesini değiştirmeden önce son kez kullanacağız.
@@ -110,7 +295,7 @@ ayrıntılı bilgi almak için <a href="http://muwire.i2p/security.html">muwire.
 </article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 sürümü IPv6 düzeltmeleri ile yayınlandı</summary></details><p>0.9.50 sürümünde, yöneltici şifreleme anahtarları için ECIES-X25519 geçişi çalışmaları sürüyor.
 Kullanıcıları pasif DNS gözetlemesinden korumak için yeniden tohumlama işleminde HTTPS üzerinden DNS özelliği etkinleştirildi.
 Yeni UPnP desteği ile IPv6 adresleri için çok sayıda düzeltme ve iyileştirme yapıldı.</p>
-<p>Uzun süredir devam eden bazı SusiMail bozulma hataları nihayet düzeltildi.
+<p>Uzun süredir var olan bazı SusiMail bozulma hataları nihayet düzeltildi.
 Bant genişliği sınırlayıcısında yapılan değişiklikler ağ tüneli başarımını iyileştirmiş olmalı.
 Docker kapsayıcılarımızda birkaç iyileştirme yapıldı.
 Ağdaki olası kötü amaçlı ve hatalı yönelticilere karşı savunma geliştirildi.</p>
@@ -154,7 +339,7 @@ Bu platformları kullanan kullanıcıların gelecekteki I2P güncellemelerini al
 <p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
 </article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 sürümü bazı hata düzeltmeleri ile yayınlandı</summary></details><p>0.9.45 sürümünde gizli kip ve bant genişliği ölçümü için önemli düzeltmeler yapıldı.
 Pano karanlık temasında bir güncelleme yapıldı.
-Başarımı iyileştirme ve yeni uçtan uca şifreleme geliştirme çalışmalarına devam ediyoruz (144 numaralı öneri).</p>
+Başarımı iyileştirme ve yeni uçtan uca şifreleme geliştirme çalışmalarını sürdürüyoruz (144 numaralı öneri).</p>
 <p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
 </article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="0.9.44 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 sürümü bazı hata düzeltmeleri ile yayınlandı</summary></details><p>0.9.44 sürümünde gizli hizmetlerde yeni şifreleme türleri işlenirken hizmet reddi sorununa yol açan önemli bir hata düzeltildi.
 Tüm kullanıcıların en kısa sürede bu sürüme geçmesini öneriyoruz.</p>
@@ -172,7 +357,7 @@ Bazı IPv6 adres algılama sorunları ile bazı hatalar düzeltildi.</p>
 </article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="0.9.42 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 sürümü bazı hata düzeltmeleri ile yayınlandı</summary></details><p>0.9.42 sürümünde I2P platformunu daha hızlı ve daha sağlam kılma üzerine çalışıldı.
 UDP taşıyıcısını hızlandıracak bir kaç değişiklik yapıldı.
 Gelecekte daha modüler bir paket oluşturmak için yapılandırma dosyaları ayrıldı.
-Daha hızlı ve güvenli şifreleme için yeni fikirler üzerinde çalışmaya devam edildi.
+Daha hızlı ve güvenli şifreleme için yeni fikirler üzerinde çalışma sürdürüldü.
 Ayrıca çok sayıda hata düzeltmesi yapıldı.</p>
 <p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
 </article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="0.9.41 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.34 sürümü bazı hata düzeltmeleri ile yayınlandı</summary></details><p>0.9.41 sürümünde 123  numaralı önerideki yeni özellikleri ekleme çalışmaları sürdürüldü.
@@ -183,38 +368,38 @@ Linux kurucusu güncellendi.</p>
 Bazı alt düzey ağ iletilerini etkileyen ciddi sorunları ve bir kaç hatayı giderdik.</p>
 <p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
 </article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="0.9.40 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 sürümünde yeni simgeler eklendi</summary></details><p>0.9.40 sürümünde yeni "Şifrelenmiş kiralama kümesi" (EncryptedLeaseSet) biçimi destekleniyor. 
-Eski NTCP 1 taşıyıcı iletişim kuralı devre dışı bırakıldı.
+Eski NTCP 1 taşıyıcı iletişim kuralı etkisizleştirildi.
 Yeni SusiDNS içe aktarma özelliği ve geliş bağlantıları için yeni betik ile süzme yöntemi eklendi. </p>
 <p>OSX doğal kurucusu üzerinde birçok geliştirme yapıldı ve IzPack kurucusu da güncellendi.
 Pano simgelerini yenileme çalışması sürüyor.
 Her zamanki gibi pek çok hata düzeltildi. </p>
 <p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
-</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 sürümü başarım iyileştirmeleri ile yayınlandı.</summary></details><p>0.9.39 sürümünde yeni ağ veritabanı türleri (123  numaralı öneri) ile ilgili pek çok değişiklik yapıldı.
-RPC uygulamalarının geliştirilmesini desteklemek için i2pcontrol uygulama eki bir web uygulaması olarak eklendi.
+</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 sürümü başarım iyileştirmeleri ile yayınlandı.</summary></details><p>0.9.39 sürümünde yeni ağ veri tabanı türleri (123  numaralı öneri) ile ilgili pek çok değişiklik yapıldı.
+RPC uygulamalarının geliştirilmesini desteklemek için i2pcontrol uygulama eki bir internet uygulaması olarak eklendi.
 Çeşitli başarım iyileştirmeleri ve hata düzeltmeleri yapıldı.</p>
 <p>Bakım yükünü azaltmak için Gece Yarısı ve Klasik temaları kaldırıldı.
 Daha önce bu temaları kullanan kullanıcılar koyu ya da açık temayı seçebilir.
 Ayrıca yeni ana sayfa simgeleri ve ilk pano güncelleme adımı eklendi.</p>
 <p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
 </article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 sürümü yeni kurulum yardımcısı ile yayınlandı.</summary></details><p>0.9.38 sürümünde bant genişliği sınaması da bulunan yeni bir kurulum yardımcısı var.
-Son GeoIP veritabanı biçimi desteği eklendi.
-Web sitemize yeni bir Firefox profili kurucusu ve yeni bir doğal Mac OS X kurucusu eklendi.
-Yeni "LS2" "Ağ veritabanı" (NetDB) biçimini destekleme çalışmaları yapılıyor.</p>
+Son GeoIP veri tabanı biçimi desteği eklendi.
+Sitemize yeni bir Firefox profili kurucusu ve yeni bir doğal Mac OS X kurucusu eklendi.
+Yeni "LS2" "Ağ veri tabanı" (NetDB) biçimini destekleme çalışmaları yapılıyor.</p>
 <p>Bu sürümde ayrıca SusiMail ek dosyaları ile ilgili çeşitli sorunlar ve yalnızca IPv6 ile çalışan yönelticiler ile ilgili bir düzeltme gibi çok sayıda hata düzeltmesi yapıldı.</p>
 <p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
 </article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="35C3 Gezi Raporu" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P 35C3 Etkinliğinde</summary></details><p>I2P ekibi Leipzig'de düzenlenen 35C3 etkinliğine neredeyse tümüyle katıldı.
 Günlük toplantılarda geçen yıl yapılanlar gözden geçirildi ve 2019 yılı için tasarım ve geliştirme hedeflerine değinildi.</p>
 <p>Proje Vizyonu ve yeni Yol Haritasına <a href="http://i2p-projekt.i2p/en/get-involved/roadmap">buradan bakabilirsiniz</a>.</p>
-<p>LS2, Testnet ve web sitemiz ile panonun kullanılabilirliğini iyileştirme çalışmalarımız sürüyor.
+<p>LS2, Testnet ve sitemiz ile panonun kullanılabilirliğini iyileştirme çalışmalarımız sürüyor.
 Tails, Debian ve Ubuntu Disco üzerinde çalışmak için planımız üzerinde çalışıyoruz. Hala Android ve I2P_Bote düzeltmelerine yardımcı olacak insan kaynağına ihtiyacımız var.</p>
 </article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="0.9.37 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37 sürümünde NTCP2 etkinleştirildi</summary></details><p>0.9.37 sürümünde NTCP2 adında daha hızlı ve daha güvenli bir taşıyıcı iletişim kuralı kullanılıyor.</p>
 <p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
 </article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="0.9.36 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 sürümü NTCP2 ve hata düzeltmeleri ile yayınlandı</summary></details><p>0.9.36 sürümünde NTCP2 olarak adlandırılan yeni ve daha güvenli bir taşıyıcı iletişim kuralı bulunuyor.
-Varsayılan olarak devre dışı bırakılmıştır ancak denemek için <a href="/configadvanced">gelişmiş yapılandırma</a> bölümünden <tt>i2np.ntcp2.enable=true</tt> seçeneğini ekleyip yeniden başlarabilirsiniz.
+Varsayılan olarak etkisizleştirilmiştir ancak denemek için <a href="/configadvanced">gelişmiş yapılandırma</a> bölümünden <tt>i2np.ntcp2.enable=true</tt> seçeneğini ekleyip yeniden başlatabilirsiniz.
 NTCP2 gelecek sürümde varsayılan olarak etkinleştirilecek.</p>
 <p>Bu sürümde ayrıca bazı başarım iyileştirmeleri ve hata düzeltmeleri yapıldı.</p>
 <p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
-</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 sürümü SusiMail klasörleri ve SSL yardımcısı ile yayınlandı</summary></details><p>0.9.35 sürümünde SusiMail uygulaması için klasör desteği ile gizli hizmetler web siteniz için HTTPS kurulumu yapmanıza yardımcı olacak yeni bir SSL yardımcısı bulunuyor.
+</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 sürümü SusiMail klasörleri ve SSL yardımcısı ile yayınlandı</summary></details><p>0.9.35 sürümünde SusiMail uygulaması için klasör desteği ile gizli hizmetler siteniz için HTTPS kurulumu yapmanıza yardımcı olacak yeni bir SSL yardımcısı bulunuyor.
 Ayrıca özellikle SusiMail üzerinde olmak üzere çeşitli hata düzeltmeleri yapıldı.</p>
 <p>0.9.36 sürümüne hazırlık olarak, yeni bir OSX kurucusu ve NTCP2 olarak adlandırılan daha güvenli ve daha hızlı bir taşıyıcı iletişim kuralı gibi bir kaç şey üzerinde sıkı çalışıyoruz.</p>
 <p>I2P ekibi 20-22 Temmuz arasında New York City HOPE etkinliğine katılıyor. Merhaba demek için bizi bulun!</p>
@@ -238,13 +423,13 @@ Lütfen sistemlerinizi olabildiğince kısa sürede güncelleyin. </p>
 Görüşme sonuçları <a href="http://zzz.i2p" target="_blank">zzz.i2p</a> üzerine eklendi bile.</p>
 <p>Ayrıca çok sayıda etiket dağıttık ve soranlara projemiz hakkında bilgi verdik.
 Yıllık I2P yemeğimiz çok başarılıydı. Katılan herkese I2P projesini destekledikleri için teşekkür ederiz.</p>
-</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="0.9.32 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 sürümü pano güncellemeleri ile yayınlandı</summary></details><p>0.9.32 sürümünde yöneltici panosunda ve ilgili web uygulamalarında (adres defteri, i2psnark ve SusiMail) çeşitli hata düzeltmeleri yapıldı.
+</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="0.9.32 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 sürümü pano güncellemeleri ile yayınlandı</summary></details><p>0.9.32 sürümünde yöneltici panosunda ve ilgili internet uygulamalarında (adres defteri, i2psnark ve SusiMail) çeşitli hata düzeltmeleri yapıldı.
 Ayrıca DNS üzerinden yapılan bazı ağ listeleme saldırılarını engellemek amacıyla yayınlanmış yöneltici bilgileri için yapılandırılmış sunucu adlarının işlenme yöntemi değiştirildi.
 Yeniden bağlanma saldırılarını engellemek amacıyla panoya bazı denetimler eklendi.</p>
 <p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
 </article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="0.9.31 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>0.9.31 sürümü pano güncellemeleri ile yayınlandı</summary></details><p>Bu sürümde her zamankine göre daha çok fark edilecek değişiklikler yapıldı!
 Yöneltici panosunu yenilenerek görünümünü sadeleştirildi, erişimi kolaylaştırıldı, 
-farklı web tarayıcılarında kullanılabilmesini sağlandı ve içeriği toparlandı.
+farklı tarayıcılarda kullanılabilmesini sağlandı ve içeriği toparlandı.
 Bu işlemler yöneltici panosunun daha kullanıcı dostu bir arayüze sahip olması
 için uzun dönemde yapılacak işlemlerin ilk adımını oluşturdu.
 Ayrıca i2psnark üzerine torrent değerlendirme ve yorum yapma özelliği eklendi.</p>
@@ -260,9 +445,9 @@ bilgi almak için
 bölümüne bakabilirsiniz.</p>
 </article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="0.9.30 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>0.9.30 sürümünde Jetty uygulaması 9. sürüme güncellendi</summary></details><p>0.9.30 sürümünde Jetty 9 ve Tomcat 8 güncellemeleri bulunuyor.
 Önceki sürümler artık desteklenmiyor ve yakında yayınlanacak olan Debian Stretch ve Ubuntu Zesty sürümlerinde bulunmayacak.
-Yöneltici her web sitesi için eski jetty.xml yapılandırma dosyasını yeni Jetty 9 ayarlarına göre değiştirecek.
+Yöneltici her site için eski jetty.xml yapılandırma dosyasını yeni Jetty 9 ayarlarına göre değiştirecek.
 Son sürümlerde kullanılan ve üzerinde değişiklik yapılmamış ayarların sorunsuz çalışması gerekir. Ancak üzerinde değişiklik yapılmış ya da çok eski yapılandırma dosyaları çalışmayabilir.
-Güncelleme sonrasında Jetty web sitenizin çalıştığından emin olun. Yardıma gerek duyarsanız bizimle IRC kanalında görüşebilirsiniz.</p>
+Güncelleme sonrasında Jetty sitenizin çalıştığından emin olun. Yardıma gerek duyarsanız bizimle IRC kanalında görüşebilirsiniz.</p>
 <p>Jetty 9 ile uyumlu olmadığı için güncellenmesi gereken bir kaç uygulama eki var.
 Yönelticinizi yeniden başlatırsanız, şu uygulama eklerini 0.9.30 sürümüyle çalışabilecek şekilde güncellemesi beklenir:
 i2pbote 0.4.6; zzzot 0.15.0.
@@ -271,7 +456,7 @@ Yeni sürümlerin durumu ile uygulama eki geliştiricisi ile iletişim görüş
 BwSchedule 0.0.36; i2pcontrol 0.11.</p>
 <p>Bu sürüm ayrıca eski (2014 ve daha öncesi) DSA-SHA1 gizli hizmetlerinin daha güvenli EdDSA imza türüne aktarılmasını destekler.
 Ayrıntılı bilgi almak, rehber ve SSS için <a href="http://zzz.i2p/topics/2271">zzz.i2p</a> adresine bakabilirsiniz.</p>
-<p>Not: Raspberry Pi gibi Android çalıştırmayan ARM platformlarında, yeniden başlatma sırasında blok dosyası veritabanı güncellenir ve bu işlem bir kaç dakika sürebilir.
+<p>Not: Raspberry Pi gibi Android çalıştırmayan ARM platformlarında, yeniden başlatma sırasında blok dosyası veri tabanı güncellenir ve bu işlem bir kaç dakika sürebilir.
 Lütfen sabırla bekleyin.</p>
 <p>Her zamanki gibi yeni sürüme güncellemeniz önerilir. Güvenliği korumanın ve ağa yardımcı olmanın en iyi yolu güncel sürümü kullanmaktır.</p>
 </article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="0.9.29 Sürümü Yayınlandı" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29 sürümü bazı hata düzeltmeleri ile yayınlandı</summary></details><p>0.9.29 sürümünde, bozuk sıkıştırılmış iletilerle ilgili çözümleri de içeren çeşitli Trac bildirimleri düzeltildi
@@ -284,7 +469,7 @@ Java 9 için ek düzeltmeler yapıldı. Bununla birlikte henüz genel amaçlar i
 Ağa yardımcı olmak ve güvende kalmak için güncel sürümü kullanmalısınız.</p>
 </article><article id="urn:uuid:cb742cac-df38-11e6-aed3-00163e5e6c1b" title="I2P-Bote Güvenlik Açığı" href="http://bote.i2p/news/0.4.5/" author="str4d" published="2017-01-20T12:00:00Z" updated="2017-01-20T12:00:00Z"><details><summary>I2P-Bote Güvenlik Açığı</summary></details><p>I2P-Bote uygulama ekinin daha önceki sürümlerinde bulunan bir güvenlik açığı I2P-Bote 0.4.5 sürümünde giderildi. Android uygulaması etkilenmedi.</p>
 <p>E-postalar kullanıcılara görüntülenirken, çoğu alan atlanıyordu. Ancak eklerin dosya adları 
-atlanmadığından, bu alan JavaScript etkinleştirilmiş olan bir web tarayıcısında kötü niyetli 
+atlanmadığından, bu alan JavaScript etkinleştirilmiş olan bir tarayıcıda kötü niyetli 
 kodları yürütmek için kullanılabiliyordu. 
 Şimdi bu alanlar da atlanıyor ve ek olarak tüm sayfalar için bir İçerik Güvenliği İlkesi 
 uygulanıyor.</p>
@@ -301,11 +486,11 @@ Kongrede 2017 önceliklerini ve 2017 yol haritasını gözden geçireceğiz.</p>
 Ağa yardımcı olmak ve güvende kalmak için güncel sürümü kullanmalısınız.</p>
 </article><article id="urn:uuid:00015ff6-b556-11e6-adb4-00163e5e6c1a" title="I2P-Bote Güvenlik Açığı" href="http://bote.i2p/news/0.4.4/" author="str4d" published="2016-11-28T12:00:00Z" updated="2016-11-28T12:00:00Z"><details><summary>I2P-Bote Güvenlik Açığı</summary></details><p>I2P-Bote uygulama ekinin daha önceki sürümlerinde bulunan bir güvenlik açığı I2P-Bote 0.4.4 sürümünde giderildi. Android uygulaması etkilenmedi.</p>
 <p>CSRF korumasının olmaması, I2P-Bote çalıştıran bir kullanıcının JavaScript
-etkinleştirilmiş bir web tarayıcısında kötü amaçlı site bir site yüklemesi durumunda, 
+etkinleştirilmiş bir tarayıcıda kötü amaçlı site bir site yüklemesi durumunda, 
 diğer taraf kullanıcı adına I2P-Bote üzerinde ileti göndermek gibi işlemleri tetikleyebilir.
 Bu da etkinleştirilmiş olabilir
 Bu durum, herhangi bir denenmiş güvenlik açığı kanıtı olmasa da, I2P-Bote adreslerinin
-özel anahtarlarının ortaya çıkarılmasına yol açabilir.</p>
+kişisel anahtarlarının ortaya çıkarılmasına yol açabilir.</p>
 <p>Tüm I2P-Bote kullanıcılarının sürümleri, Aralık ayı ortasında I2P 0.9.28 sürümünün
 yayınlanmasından sonra yönelticilerini yeniden başlattıklarında otomatik olarak yükseltilecek.
 Bununla birlikte o zamana kadar olan aralıkta I2P ya da I2P-Bote kullanmayı planlıyorsanız güncellemeyi el ile yapmak için <a href="http://bote.i2p/install/">kurulum sayfasındaki adımları uygulamanız</a> önerilir.

data/translations/entries.uk.html

@@ -1,5 +1,174 @@
 <div>
-<header title="Новини I2P">Стрічка новин, та оновлення роутера</header><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
+<header title="Новини I2P">Стрічка новин, та оновлення роутера</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
+The bug primarily affected high-bandwidth routers.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
+We have added notification bubbles to several applications in the console to highlight application messages.
+We fixed a tunnel test bug that may have been affecting tunnel reliability.
+The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
+There are several dark theme fixes and improvements.</p>
+<p>We fixed the installer that previously failed on Java 21 or higher.
+We also fixed installing to directory paths that contain spaces on Linux.
+For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
+The workaround is using localhost and the server port, usually 7658, to bypass I2P.
+For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
+We apologize for the issue and are working on a fix.</p>
+</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
+<p>We have improved handling of congested routers in the network.
+Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
+We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
+Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
+<p>Access to information from the console and applications has been improved.
+Issues have been fixed in I2PSnark and SusiMail search.
+The netDB search embedded into the router console now operates in a more intuitive and useful way.
+Minor improvements have been made to diagnostic displays in advanced mode.</p>
+<p>Bugs have also been fixed to improve compatibility within the network.
+An issue with publishing leaseSets was solved which improves reliability major hidden services.
+I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
+This prevents torrents from being unnecessarily disrupted by these changes.
+We welcomed this contribution from a new contributor.
+A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
+This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
+<p>Newer routers will be favored when selecting floodfill routers.
+I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
+Legacy transport protocols are being removed, simplifying the code in the UDP transports.
+Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
+Additional tweaks were made to peer selection strategies.</p>
+<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
+We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
+If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
+Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
+With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
+This should help the network return to normal operation.
+Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
+Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
+This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
+Reachability of I2P sites is badly degraded.</p>
+<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
+Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
+</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
+<p>New features have been added to I2PSnark like the ability to search through torrents.
+Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
+We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
+New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
+Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
+<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
+This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
+This investigation uncovered one minor isolation-piercing event which we repaired.
+This issue was discovered and fixed internally by the I2P team.</p>
+<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
+This should result in improved delivery and availability for these downstream products.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
+It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
+<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
+This will help the network limit the effect of tunnel spam.
+It will also help the network heal during and after DDOS attacks.</p>
+<p>The NetDb changes also help secure individual routers and the applications that use them. 
+Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
+This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
+<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
+CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
+An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
+The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
+The attacker then sends the same message directly to the router.
+The router passes the message to the bloom filter, and is dropped.
+This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
+This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
+Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
+Users of Java I2P are recommended to update immediately to avoid the attack.</p>
+<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
+This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
+<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
+<p>This release also contains a tweakable blocklist.
+Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
+Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
+This feature is off-by-default and is only recommended for advanced users at this time.</p>
+<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
+It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
+This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
+Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
+This issue has also been resolved.
+The docker container is now also compatible with Podman.</p>
+<p>This release syncs translations with transifex and updates the GeoIP database.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
+This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
+The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
+<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
+This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
+This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
+We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
+<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
+zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
+As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
+We thank zzz for providing these services for such a long time.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
+Our investigations and mitigations continue.</p>
+<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
+We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
+However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
+The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
+<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
+We ask for your patience as we work to improve I2P.</p>
+</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
+  The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
+  Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
+  Mitigation strategies are being investigated and implemented gradually.</p>
+<p>While the attack has degraded performance, the network remains intact and usable.
+  Java I2P routers appear to be handling the issues better than i2pd routers for now.
+  Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
+</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
+As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
+First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
+Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
+Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
+<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
+possibly triggered by Bitcoin's new I2P transient address feature,
+but made worse by our SSU2 bugs and other congestion control problems.
+We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
+We have improved our algorithms to reduce network load during times of congestion.
+We are also collaborating with i2pd to develop common congestion control strategies.</p>
+<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
+i2pd released their version 2.45.0 last week and the early results are encouraging.
+New protocols, and distributed networks, are difficult to develop.
+Congestion can arrive with little warning and with little clue of the cause.
+Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
+<p>Як і зазвичай, ми рекомендуємо вам оновитись до цього реліза. Найкращий спосіб щоб
+підтримувати безпеку і допомогти мережі - використовувати найновіший реліз.</p>
+</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
 <p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
 <p>Як і зазвичай, ми рекомендуємо вам оновитись до цього реліза. Найкращий спосіб щоб
 підтримувати безпеку і допомогти мережі - використовувати найновіший реліз.</p>

data/translations/entries.vi.html

@@ -0,0 +1,605 @@
+<div>
+<header title="Tin Tức I2P">Tin tức, và các cập nhật bộ định tuyến</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
+The bug primarily affected high-bandwidth routers.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
+We have added notification bubbles to several applications in the console to highlight application messages.
+We fixed a tunnel test bug that may have been affecting tunnel reliability.
+The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
+There are several dark theme fixes and improvements.</p>
+<p>We fixed the installer that previously failed on Java 21 or higher.
+We also fixed installing to directory paths that contain spaces on Linux.
+For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
+The workaround is using localhost and the server port, usually 7658, to bypass I2P.
+For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
+We apologize for the issue and are working on a fix.</p>
+</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
+<p>We have improved handling of congested routers in the network.
+Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
+We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
+Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
+<p>Access to information from the console and applications has been improved.
+Issues have been fixed in I2PSnark and SusiMail search.
+The netDB search embedded into the router console now operates in a more intuitive and useful way.
+Minor improvements have been made to diagnostic displays in advanced mode.</p>
+<p>Bugs have also been fixed to improve compatibility within the network.
+An issue with publishing leaseSets was solved which improves reliability major hidden services.
+I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
+This prevents torrents from being unnecessarily disrupted by these changes.
+We welcomed this contribution from a new contributor.
+A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Đã Ra Mắt" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P Phát Hành 2.6.1</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
+This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
+<p>Newer routers will be favored when selecting floodfill routers.
+I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
+Legacy transport protocols are being removed, simplifying the code in the UDP transports.
+Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
+Additional tweaks were made to peer selection strategies.</p>
+<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
+We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
+If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
+Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
+With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
+This should help the network return to normal operation.
+Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
+Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
+This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
+Reachability of I2P sites is badly degraded.</p>
+<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
+Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
+</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
+<p>New features have been added to I2PSnark like the ability to search through torrents.
+Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
+We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
+New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
+Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
+<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
+This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
+This investigation uncovered one minor isolation-piercing event which we repaired.
+This issue was discovered and fixed internally by the I2P team.</p>
+<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
+This should result in improved delivery and availability for these downstream products.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
+It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
+<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
+This will help the network limit the effect of tunnel spam.
+It will also help the network heal during and after DDOS attacks.</p>
+<p>The NetDb changes also help secure individual routers and the applications that use them. 
+Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
+This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
+<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
+CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
+An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
+The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
+The attacker then sends the same message directly to the router.
+The router passes the message to the bloom filter, and is dropped.
+This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
+This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
+Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
+Users of Java I2P are recommended to update immediately to avoid the attack.</p>
+<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
+This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
+<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
+<p>This release also contains a tweakable blocklist.
+Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
+Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
+This feature is off-by-default and is only recommended for advanced users at this time.</p>
+<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
+It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
+This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
+Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
+This issue has also been resolved.
+The docker container is now also compatible with Podman.</p>
+<p>This release syncs translations with transifex and updates the GeoIP database.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
+This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
+The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
+<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
+This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
+This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
+We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
+<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
+zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
+As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
+We thank zzz for providing these services for such a long time.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
+Our investigations and mitigations continue.</p>
+<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
+We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
+However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
+The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
+<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
+We ask for your patience as we work to improve I2P.</p>
+</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
+  The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
+  Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
+  Mitigation strategies are being investigated and implemented gradually.</p>
+<p>While the attack has degraded performance, the network remains intact and usable.
+  Java I2P routers appear to be handling the issues better than i2pd routers for now.
+  Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
+</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
+As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
+First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
+Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
+Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
+<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
+possibly triggered by Bitcoin's new I2P transient address feature,
+but made worse by our SSU2 bugs and other congestion control problems.
+We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
+We have improved our algorithms to reduce network load during times of congestion.
+We are also collaborating with i2pd to develop common congestion control strategies.</p>
+<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
+i2pd released their version 2.45.0 last week and the early results are encouraging.
+New protocols, and distributed networks, are difficult to develop.
+Congestion can arrive with little warning and with little clue of the cause.
+Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
+<p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Recent Blog Posts" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>
+<ul>
+<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">Overview of our new SSU2 transport</a></li>
+<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">A warning about I2P coins and other scams</a></li>
+<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">An interview with Konrad from diva.exchange</a></li>
+<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">An interview with Dustin from StormyCloud</a></li>
+</ul></article><article id="urn:uuid:b998384f-08ae-4979-908b-2f57e72b05f5" title="1.9.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/8/22/1.9.0-Release" author="zzz" published="2022-08-22T12:00:00Z" updated="2022-08-22T12:00:00Z"><details><summary>1.9.0 with SSU2 for testing</summary></details><p>We have spent the last three months working on our new UDP transport protocol "SSU2"
+with a small number of volunteer testers.
+This release completes the implementation, including relay and peer testing.
+We are enabling it by default for Android and ARM platforms, and a small percentage of other routers at random.
+This will allow us to do much more testing in the next three months, finish the connection migration feature,
+and fix any remaining issues.
+We plan to enable it for everyone in the next release scheduled for November.
+No manual configuration is necessary.</p>
+<p>Of course, there's the usual collection of bug fixes in this release as well.
+We also added an automatic deadlock detector that has already found a rare deadlock that is now fixed.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:4c69e33a-6238-4b50-98ef-6ee00d2d8da7" title="New Outproxy exit.stormycloud.i2p" href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud" author="zzz" published="2022-08-05T11:00:00Z" updated="2022-08-05T11:00:00Z"><details><summary>New Outproxy</summary></details><p>I2P "outproxies" (exit nodes) may be used to access the internet through
+your HTTP proxy tunnel.
+As approved at our <a href="http://i2p-projekt.i2p/en/meetings/314">monthly meeting</a>,
+<b>exit.stormycloud.i2p</b> is now our official, recommended outproxy, replacing the long-dead <b>false.i2p</b>.
+For more information on the StormyCloud <a href="http://stormycloud.i2p/">organization</a>,
+<a href="http://stormycloud.i2p/outproxy.html">outproxy</a>,
+and <a href="http://stormycloud.i2p/tos.html">terms of service</a>,
+see the <a href="http://stormycloud.i2p/">StormyCloud website</a>.</p>
+<p>We suggest you change your <a href="/i2ptunnel/edit?tunnel=0">Hidden Services Manager configuration</a>
+to specify <b>exit.stormycloud.i2p</b>
+in two places: <b>Outproxies</b> and <b>SSL Outproxies</b>.
+After editing, <b>scroll down and click Save</b>.
+See our <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">blog post for a screenshot</a>.
+For Android instructions and screenshots see <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">notbob's blog</a>.</p>
+<p>Router updates will not update your configuration, you must edit it manually.
+Thanks to StormyCloud for their support, and please consider a <a href="http://stormycloud.i2p/donate.html">donation</a>.</p>
+</article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 with bug fixes</summary></details><p>This release includes bug fixes in i2psnark,
+the router, I2CP, and UPnP.
+Router fixes address bugs in soft restart, IPv6, SSU peer testing,
+network database stores, and tunnel building.
+Router family handling and Sybil classification have also been
+significantly improved.</p>
+<p>Together with i2pd, we are developing our new UDP transport, SSU2.
+SSU2 will bring substantial performance and security improvements.
+It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
+completing the full cryptography upgrade we started about 9 years ago.
+This release contains a preliminary implementation which is disabled by default.
+If you wish to participate in testing, please look for current information
+on zzz.i2p.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="Install essential Java/Jpackage updates" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>The recent Java "Psychic Signatues" vulnerability affects I2P. Current users of
+I2P on Linux, or any users of I2P who are using a non-bundled JVM should update
+their JVM or switch to a version which does not contain the vulnerability, below
+Java 15.</p>
+<p>New I2P Easy-Install bundles have been generated using the latest release of the
+Java Virtual Machine. Further details have been published in the respective
+bundle newsfeeds.</p>
+</article><article id="urn:uuid:5136d7e2-5957-4310-a69a-8882d9c88228" title="1.7.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/02/21/1.7.0-Release" author="zzz" published="2022-02-21T12:00:00Z" updated="2022-02-21T12:00:00Z"><details><summary>1.7.0 with reliability and performance improvements</summary></details><p>The 1.7.0 release contains several performance and reliability improvements.</p>
+<p>There are now popup messages in the system tray, for those platforms that support it.
+i2psnark has a new torrent editor.
+The NTCP2 transport now uses much less CPU.</p>
+<p>The long-deprecated BOB interface is removed for new installs.
+It will continue to work in existing installs, except for Debian packages.
+Any remaining users of BOB applications should ask the developers to convert to the SAMv3 protocol.</p>
+<p>We know that since our 1.6.1 release, network reliability has steadily deteriorated.
+We were aware of the problem soon after the release, but it took us almost two months to find the cause.
+We eventually identified it as a bug in i2pd 2.40.0,
+and the fix will be in their 2.41.0 release coming out about the same time as this release.
+Along the way, we've made several changes on the Java I2P side to improve the
+robustness of network database lookups and stores, and avoid poorly-performing peers in tunnel peer selection.
+This should help the network be more robust even in the presence of buggy or malicious routers.
+Additionally, we're starting a joint program to test pre-release i2pd and Java I2P routers
+together in an isolated test network, so we can find more problems before the releases, not after.</p>
+<p>In other news, we continue to make great progress on the design of our new UDP transport "SSU2" (proposal 159)
+and have started implementation.
+SSU2 will bring substantial performance and security improvements.
+It will also allow us to finally replace our last usage of the very slow ElGamal encryption,
+completing a full cryptography upgrade that started about 9 years ago.
+We expect to start joint testing with i2pd soon, and roll it out to the network later this year.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:edd3c726-6c3e-4840-9801-5d41627ec1cf" title="1.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/11/29/1.6.0-Release" author="zzz" published="2021-11-29T12:00:00Z" updated="2021-11-29T12:00:00Z"><details><summary>1.6.0 enables new tunnel build messages</summary></details><p>This release completes the rollout of two major protocol updates developed in 2021.
+The transition to X25519 encryption for routers is accelerated, and we expect almost all routers to be rekeyed by the end of the year.
+Short tunnel build messages are enabled for a significant bandwidth reduction.</p>
+<p>We added a theme selection panel to the new install wizard.
+We've improved SSU performance and fixed an issue with SSU peer test messages.
+The tunnel build Bloom filter was adjusted to reduce memory usage.
+We have enhanced support for non-Java plugins.</p>
+<p>In other news, we are making excellent progress on the design of our new UDP transport SSU2 and expect to start implementation early next year.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 with new tunnel build messages</summary></details><p>Yes, that's right, after 9 years of 0.9.x releases, we are going straight from 0.9.50 to 1.5.0.
+This does not signify a major API change, or a claim that development is now complete.
+It is simply a recognition of almost 20 years of work to provide anonymity and security for our users.</p>
+<p>This release finishes implementation of smaller tunnel build messages to reduce bandwidth.
+We continue the transition of the network's routers to X25519 encryption.
+Of course there are also numerous bug fixes and performance improvements.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:e7a0f375-817f-4c8f-a961-43a81467f560" title="MuWire Desktop Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-09T15:00:00Z" updated="2021-07-09T15:00:00Z"><details><summary>Muwire Desktop Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire standalone desktop application.
+It does not affect the console plugin, and is not related to the previously-announced plugin issue.
+If you are running the MuWire desktop application you should <a href="http://muwire.i2p/">update to version 0.8.8</a> immediately.</p>
+<p>Details of the issue will be published on <a href="http://muwire.i2p/security.html">muwire.i2p</a>
+on July 15, 2021.</p>
+</article><article id="urn:uuid:0de64d0d-8357-49cf-8eea-e1d889cd7387" title="MuWire Plugin Vulnerability" href="http://muwire.i2p/security.html" author="zlatinb" published="2021-07-07T11:00:00Z" updated="2021-07-07T11:00:00Z"><details><summary>Muwire Plugin Vulnerability</summary></details><p>A security vulnerability has been discovered in the MuWire plugin.
+It does not affect the standalone desktop client.
+If you are running the MuWire plugin you should <a href="/configplugins">update to version 0.8.7-b1</a> immediately.</p>
+<p>See <a href="http://muwire.i2p/security.html">muwire.i2p</a>
+for more information about the vulnerability and updated security recommendations.</p>
+</article><article id="urn:uuid:9a6591a3-e663-4758-95d1-9fa4e0526d48" title="0.9.50 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/05/17/0.9.50-Release" author="zzz" published="2021-05-17T12:00:00Z" updated="2021-05-17T12:00:00Z"><details><summary>0.9.50 with IPv6 fixes</summary></details><p>0.9.50 continues the transition to ECIES-X25519 for router encryption keys.
+We have enabled DNS over HTTPS for reseeding to protect users from passive DNS snooping.
+There are numerous fixes and improvements for IPv6 addresses, including new UPnP support.</p>
+<p>We have finally fixed some longstanding SusiMail corruption bugs.
+Changes to the bandwidth limiter should improve network tunnel performance.
+There are several improvements in our Docker containers.
+We have improved our defenses for possible malicious and buggy routers in the network.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f3629d00-d989-4082-9185-302139c1c9c3" title="0.9.49 Released" href="http://i2p-projekt.i2p/en/blog/post/2021/02/17/0.9.49-Release" author="zzz" published="2021-02-17T12:00:00Z" updated="2021-02-17T12:00:00Z"><details><summary>0.9.49 with SSU fixes and faster crypto</summary></details><p>0.9.49 continues the work to make I2P faster and more secure.
+We have several improvements and fixes for the SSU (UDP) transport that should result in faster speeds.
+This release also starts the migration to new, faster ECIES-X25519 encryption for routers.
+(Destinations have been using this encryption for a few releases now)
+We've been working on the specifications and protocols for new encryption for several years,
+and we are getting close to the end of it! The migration will take several releases to complete.</p>
+<p>For this release, to minimize disruption, only new installs and a very small percentage of existing installs
+(randomly selected at restart) will be using the new encryption.
+If your router does "rekey" to use the new encryption, it may have lower traffic or less reliability than usual for several days after you restart.
+This is normal, because your router has generated a new identity.
+Your performance should recover after a while.</p>
+<p>We have "rekeyed" the network twice before, when changing the default signature type,
+but this is the first time we've changed the default encryption type.
+Hopefully it will all go smoothly, but we're starting slowly to be sure.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:2f702241-c585-4151-a364-76c561621989" title="0.9.48 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/11/30/0.9.48-Release" author="zzz" published="2020-12-01T12:00:00Z" updated="2020-12-01T12:00:00Z"><details><summary>0.9.48 with performance enhancements</summary></details><p>0.9.48 enables our new end-to-end encryption protocol (proposal 144) for most services.
+We have added preliminary support for new tunnel build message encryption (proposal 152).
+There are significant performance improvements throughout the router.</p>
+<p>Packages for Ubuntu Xenial (16.04 LTS) are no longer supported.
+Users on that platform should upgrade so you may continue to receive I2P updates.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:12c0f414-175a-401e-a35c-47307627a050" title="0.9.47 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/08/24/0.9.47-Release" author="zzz" published="2020-08-24T12:00:00Z" updated="2020-08-24T12:00:00Z"><details><summary>0.9.47 enables new encryption</summary></details><p>0.9.47 enables our new end-to-end encryption protocol (proposal 144) by default for some services.
+The Sybil analysis and blocking tool is now enabled by default.</p>
+<p>Java 8 or higher is now required.
+Debian packages for Wheezy and Stretch, and for Ubuntu Trusty and Precise, are no longer supported.
+Users on those platforms should upgrade so you may continue to receive I2P updates.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:c9389925-50cd-47fe-abb2-20708f9d52b9" title="0.9.46 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/05/25/0.9.46-Release" author="zzz" published="2020-05-25T12:00:00Z" updated="2020-05-25T12:00:00Z"><details><summary>0.9.46 with bug fixes</summary></details><p>0.9.46 contains significant performance improvements in the streaming library.
+We have completed development of ECIES encryption (proposal 144) and there is now an option to enable it for testing.</p>
+<p>Windows users only:
+This release fixes a local privilege escalation vulnerability
+which could be exploited by a local user.
+Please apply the update as soon as possible.
+Thanks to Blaze Infosec for responsible disclosure of the issue.</p>
+<p>This is the last release to support Java 7, Debian packages Wheezy and Stretch, and Ubuntu packages Precise and Trusty.
+Users on those platforms must upgrade to receive future I2P updates.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:b35dd505-4fd2-451d-91c5-d148bc095869" title="0.9.45 Released" href="http://i2p-projekt.i2p/en/blog/post/2020/02/25/0.9.45-Release" author="zzz" published="2020-02-25T12:00:00Z" updated="2020-02-25T12:00:00Z"><details><summary>0.9.45 with bug fixes</summary></details><p>0.9.45 contains important fixes for hidden mode and the bandwidth tester.
+There's an update to the console dark theme.
+We continue work on improving performance and the development of new end-to-end encryption (proposal 144).</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:322cb1a3-e169-4879-a053-b99371ed85d5" title="0.9.44 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/12/01/0.9.44-Release" author="zzz" published="2019-12-01T12:00:00Z" updated="2019-12-01T12:00:00Z"><details><summary>0.9.44 with bug fixes</summary></details><p>0.9.44 contains an important fix for a denial of service issue in hidden services handling of new encryption types.
+All users should update as soon as possible.</p>
+<p>The release includes initial support for new end-to-end encryption (proposal 144).
+Work continues on this project, and it is not yet ready for use.
+There are changes to the console home page, and new embedded HTML5 media players in i2psnark.
+Additional fixes for firewalled IPv6 networks are included.
+Tunnel build fixes should result in faster startup for some users.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:18696206-3dc9-439c-9eab-b2d6bada1e7b" title="0.9.43 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/10/22/0.9.43-Release" author="zzz" published="2019-10-22T12:00:00Z" updated="2019-10-22T12:00:00Z"><details><summary>0.9.43 with bug fixes</summary></details><p>In the 0.9.43 release, we continue work on stronger security and privacy features and performance improvements.
+Our implementation of the new leaseset specification (LS2) is now complete.
+We are beginning our implementation of stronger and faster end-to-end encryption (proposal 144) for a future release.
+Several IPv6 address detection issues have been fixed, and there of course are several other bug fixes.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:b49344e5-2eff-4fb4-a52b-e8e5756e6319" title="0.9.42 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/08/27/0.9.42-Release" author="zzz" published="2019-08-27T12:00:00Z" updated="2019-08-27T12:00:00Z"><details><summary>0.9.42 with bug fixes</summary></details><p>0.9.42 continues the work to make I2P faster and more reliable.
+It includes several changes to speed up our UDP transport.
+We have split up the configuration files to enable future work for more modular packaging.
+We continue work to implement new proposals for faster and more secure encryption.
+There are, of course, a lot of bug fixes also.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f5c9ec1d-7a95-4a17-8be4-c41664125e2f" title="0.9.41 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/07/02/0.9.41-Release" author="zzz" published="2019-07-02T12:00:00Z" updated="2019-07-02T12:00:00Z"><details><summary>0.9.41 with bug fixes</summary></details><p>0.9.41 continues the work to implement new features for proposal 123,
+including per-client authentication for encrypted leasesets.
+The console has an updated I2P logo and several new icons.
+We've updated the Linux installer.</p>
+<p>Startup should be faster on platforms such as Raspberry Pi.
+We've fixed several bugs, including some serious ones affecting low-level network messages.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:6ed561d0-0f78-49e3-ab95-c6a10167155f" title="0.9.40 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/05/07/0.9.40-Release" author="zzz" published="2019-05-07T12:00:00Z" updated="2019-05-07T12:00:00Z"><details><summary>0.9.40 with new icons</summary></details><p>0.9.40 includes support for the new encrypted leaseset format.
+We disabled the old NTCP 1 transport protocol.
+There's a new SusiDNS import feature, and a new scripted filtering mechanism for incoming connections.</p>
+<p>We've made a lot of improvements to the OSX native installer, and we've updated the IzPack installer as well.
+The work continues on refreshing the console with new icons.
+As usual, we've fixed lots of bugs also!</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:e34fc8d5-02fc-40cd-af83-a699ca56282e" title="0.9.39 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/03/21/0.9.39-Release" author="zzz" published="2019-03-21T12:00:00Z" updated="2019-03-21T12:00:00Z"><details><summary>0.9.39 with performance improvements</summary></details><p>0.9.39 includes extensive changes for the new network database types (proposal 123).
+We've bundled the i2pcontrol plugin as a webapp to support development of RPC applications.
+There are numerous performance improvements and bug fixes.</p>
+<p>We've removed the midnight and classic themes to reduce the maintenance burden;
+previous users of those themes will now see the dark or light theme.
+There's also new home page icons, a first step in updating the console.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:6c580177-a55b-400b-bb61-dc8a14d40219" title="0.9.38 Released" href="http://i2p-projekt.i2p/en/blog/post/2019/01/22/0.9.38-Release" author="zzz" published="2019-01-22T12:00:00Z" updated="2019-01-22T12:00:00Z"><details><summary>0.9.38 with new setup wizard</summary></details><p>0.9.38 includes a new first-install wizard with a bandwidth tester.
+We've added support for the latest GeoIP database format.
+There's a new Firefox profile installer and a new, native Mac OSX installer on our website.
+Work continues on supporting the new "LS2" netdb format.</p>
+<p>This release also contains plenty of bug fixes, including several issues with susimail attachments, and a fix for IPv6-only routers.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:dfeb655e-d305-42ba-88d4-0579550e5f8a" title="35C3 Trip Report" href="http://i2p-projekt.i2p/en/get-involved/roadmap" author="sadie" published="2019-01-21T12:00:00Z" updated="2019-01-21T12:00:00Z"><details><summary>I2P at 35C3</summary></details><p>The I2P team was mostly all in attendance at 35C3 in Leipzig.
+Daily meetings were held to review the past year and cover our development and design goals for 2019.</p>
+<p>The Project Vision and new Roadmap can be <a href="http://i2p-projekt.i2p/en/get-involved/roadmap">reviewed here</a>.</p>
+<p>Work will continue on LS2, the Testnet, and usability improvements to our website and console.
+A plan is in place to be in Tails, Debian and Ubuntu Disco. We still need people to work on Android and I2P_Bote fixes.</p>
+</article><article id="urn:uuid:b02623a0-5936-4fb6-aaa8-2a3d81c2f01e" title="0.9.37 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/10/04/0.9.37-Release" author="zzz" published="2018-10-04T12:00:00Z" updated="2018-10-04T12:00:00Z"><details><summary>0.9.37 with NTCP2 enabled</summary></details><p>0.9.37 enables a faster, more secure transport protocol called NTCP2.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:678f9d11-a129-40ea-b68a-0b3d4c433774" title="0.9.36 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/08/23/0.9.36-Release" author="zzz" published="2018-08-23T12:00:00Z" updated="2018-08-23T12:00:00Z"><details><summary>0.9.36 with NTCP2 and bug fixes</summary></details><p>0.9.36 contains a new, more secure transport protocol called NTCP2.
+It is disabled by default, but you may enable it for testing by adding the <a href="/configadvanced">advanced configuration</a> <tt>i2np.ntcp2.enable=true</tt> and restarting.
+NTCP2 will be enabled in the next release.</p>
+<p>This release also contains several performance improvements and bug fixes.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:32750025-4fc9-4858-a6bb-4ad9c28657c4" title="0.9.35 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/06/26/0.9.35-Release" author="zzz" published="2018-06-26T12:00:00Z" updated="2018-06-26T12:00:00Z"><details><summary>0.9.35 with SusiMail folders and SSL Wizard</summary></details><p>0.9.35 adds support for folders in SusiMail, and a new SSL Wizard for setting up HTTPS on your Hidden Service website.
+We also have the usual collection of bug fixes, especially in SusiMail.</p>
+<p>We're hard at work on several things for 0.9.36, including a new OSX installer and a faster, more secure transport protocol called NTCP2.</p>
+<p>I2P will be at HOPE in New York City, July 20-22. Find us and say hello!</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:40eaa552-2afb-4485-ab68-426f3f2aa17a" title="0.9.34 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/04/10/0.9.34-Release" author="zzz" published="2018-04-10T12:00:00Z" updated="2018-04-10T12:00:00Z"><details><summary>0.9.34 with bug fixes</summary></details><p>0.9.34 contains a lot of bug fixes!
+It also has improvements in SusiMail, IPv6 handling, and tunnel peer selection.
+We add support for IGD2 schemas in UPnP.
+There's also preparation for more improvements you will see in future releases.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:344db535-fa7b-429a-8e7e-417c2772270c" title="0.9.33 Released" href="http://i2p-projekt.i2p/en/blog/post/2018/01/30/0.9.33-Release" author="zzz" published="2018-01-30T12:00:00Z" updated="2018-01-30T12:00:00Z"><details><summary>0.9.33 with bug fixes</summary></details><p>0.9.33 contains a large number of bug fixes, including i2psnark, i2ptunnel, streaming, and SusiMail.
+For those who cannot access the reseed sites directly, we now support several types of proxies for reseeding.
+We now set rate limits by default in the hidden services manager.
+For those that run high-traffic servers, please review and adjust the limits as necessary.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:dc95b7d9-0c55-472e-8cd9-cf485a495c2c" title="KAISER, Meltdown and Spectre" href="https://gruss.cc/files/kaiser.pdf" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>Security issues found in nearly every system</summary></details><p>A very serious issue has been found in modern CPUs which are found in nearly all sold computers worldwide, including mobiles. Those security issues are named "Kaiser", "Meltdown", and "Spectre".</p>
+<p>The whitepaper for KAISER/KPTI can be found under <a href="https://gruss.cc/files/kaiser.pdf" target="_blank">KAISER.pdf</a>, Meltdown under <a href="https://meltdownattack.com/meltdown.pdf" target="_blank">Meltdown.pdf</a>, and SPECTRE under <a href="https://spectreattack.com/spectre.pdf" target="_blank">Spectre.pdf</a>. Intels first response is listed under <a href="https://newsroom.intel.com/news/intel-responds-to-security-research-findings/" target="_blank">Intels response</a>.</p>
+<p>It is important for our I2P users to update your system, as long as updates are available. Windows 10 patches are availble from now on, Windows 7 and 8 will follow soon. MacOS patches are already available, to. Lots of Linux systems have a newer Kernel with a included fix available, too. Same applies to Android, which security fix of 2nd Jan 2018 includes a patch for this issues.
+Please update your systems as soon as available and possible.</p>
+</article><article id="urn:uuid:a6fc490b-2877-4cbf-afa8-d6e7d4637440" title="Happy new year! - 34C3" href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" author="echelon" published="2018-01-04T12:00:00Z" updated="2018-01-04T12:00:00Z"><details><summary>New year and I2P at 34C3</summary></details><p>Happy new year from the I2P team to everyone!</p>
+<p>No less than 7 I2P team members did meet at the 34C3 in Leipzig from 27th til 30th december 2017. Beside the <a href="http://zzz.i2p/topics/2437-meetings-dec-27-30-at-34c3" target="_blank">meetings</a> at our table we did meet lots of friends of I2P all over the place. 
+Results of the meetings are posted on <a href="http://zzz.i2p" target="_blank">zzz.i2p</a> already.</p>
+<p>Also we did hand out lots of stickers and gave information about our project to anyone asking. 
+Our annual I2P dinner was a full success as a thank you to all attendees for ongoing support of I2P.</p>
+</article><article id="urn:uuid:062c316b-2148-4aae-a0d3-81faeb715345" title="0.9.32 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/11/07/0.9.32-Release" author="zzz" published="2017-11-07T12:00:00Z" updated="2017-11-07T12:00:00Z"><details><summary>0.9.32 with console updates</summary></details><p>0.9.32 contains a number of fixes in the router console and associated webapps (addressbook, i2psnark, and susimail).
+We have also changed the way we handle configured hostnames for published router infos, to eliminate some network enumeration attacks via DNS.
+We have added some checks in the console to resist rebinding attacks.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:48298a7a-e365-4719-a6ac-cb335cf0a4ce" title="0.9.31 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/08/07/0.9.31-Release" author="zzz" published="2017-08-07T12:00:00Z" updated="2017-08-07T12:00:00Z"><details><summary>0.9.31 with console updates</summary></details><p>The changes in this release are much more noticeable than usual!
+We have refreshed the router console to make it easier to understand,
+improved accessibility and cross-browser support,
+and generally tidied things up.
+This is the first step in a longer-term plan to make the router console more user-friendly.
+We have also added torrent ratings and comments support to i2psnark.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:2ce9a846-4d7e-11e7-b788-00163e5e6c1b" title="Call for Translators" href="https://www.transifex.com/otf/I2P/announcements/7243/" author="str4d" published="2017-06-10T12:00:00Z" updated="2017-06-10T12:00:00Z"><details><summary>The upcoming 0.9.31 release has more untranslated strings than usual</summary></details><p>In preparation for the 0.9.31 release, which brings with it significant updates
+to the user interface, we have a larger than normal collection of untranslated
+strings that need attention. If you're a translator, we would greatly appreciate
+it if you could set aside a little more time than usual during this release cycle
+in order to bring the translations up to speed. We have pushed the strings early
+to give you three weeks to work on them.</p>
+<p>If you're not currently an I2P translator, now would be a great time to get
+involved! Please see the
+<a href="http://i2p-projekt.i2p/en/get-involved/guides/new-translators" target="_blank">New Translator's Guide</a>
+for information on how to get started.</p>
+</article><article id="urn:uuid:3b9b01cf-23ec-4aeb-ab20-2f79e8396c4f" title="0.9.30 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/05/03/0.9.30-Release" author="zzz" published="2017-05-03T12:00:00Z" updated="2017-05-03T12:00:00Z"><details><summary>0.9.30 updates to Jetty 9</summary></details><p>0.9.30 contains an upgrade to Jetty 9 and Tomcat 8.
+The previous versions are no longer supported, and are not available in the upcoming Debian Stretch and Ubuntu Zesty releases.
+The router will migrate the jetty.xml configuration file for each Jetty website to the new Jetty 9 setup.
+This should work for recent, unmodified configurations but may not work for modified or very old setups.
+Verify that your Jetty website works after upgrading, and contact us on IRC if you need assistance.</p>
+<p>Several plugins are not compatible with Jetty 9 and must be updated.
+The following plugins have been updated to work with 0.9.30, and your router should update them after restart:
+i2pbote 0.4.6; zzzot 0.15.0.
+The following plugins (with current versions listed) will not work with 0.9.30.
+Contact the appropriate plugin developer for the status of new versions:
+BwSchedule 0.0.36; i2pcontrol 0.11.</p>
+<p>This release also supports migration of old (2014 and earlier) DSA-SHA1 hidden services to the more-secure EdDSA signature type.
+See <a href="http://zzz.i2p/topics/2271">zzz.i2p</a> for further information, including a guide and FAQ.</p>
+<p>Note: On non-Android ARM platforms such as the Raspberry Pi, the blockfile database will upgrade on restart, which may take several minutes.
+Please be patient.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:5f5166f0-a1c3-4ca9-9db0-32a157eb6ca7" title="0.9.29 Released" href="http://i2p-projekt.i2p/en/blog/post/2017/02/27/0.9.29-Release" author="zzz" published="2017-02-27T12:00:00Z" updated="2017-02-27T12:00:00Z"><details><summary>0.9.29 contains bug fixes</summary></details><p>0.9.29 contains fixes for numerous Trac tickets, including workarounds for corrupt compressed messages.
+We now support NTP over IPv6.
+We've added preliminary Docker support.
+We now have translated man pages.
+We now pass same-origin Referer headers through the HTTP proxy.
+There are more fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
+<p>As usual, we recommend that all users update to this release.
+The best way to help the network and stay secure is to run the latest release.</p>
+</article><article id="urn:uuid:cb742cac-df38-11e6-aed3-00163e5e6c1b" title="I2P-Bote Security Vulnerability" href="http://bote.i2p/news/0.4.5/" author="str4d" published="2017-01-20T12:00:00Z" updated="2017-01-20T12:00:00Z"><details><summary>I2P-Bote Security Vulnerability</summary></details><p>I2P-Bote 0.4.5 fixes a security vulnerability present in all earlier versions of the
+I2P-Bote plugin. The Android app was not affected.</p>
+<p>When showing emails to the user, most fields were being escaped. However, the filenames
+of attachments were not escaped, and could be used to execute malicious code in a browser
+with JavaScript enabled. These are now escaped, and additionally a Content Security Policy
+has been implemented for all pages.</p>
+<p>All I2P-Bote users will be upgraded automatically the first time they restart their router
+after I2P 0.9.29 is released in mid-February. However, for safety we recommend that you
+<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
+upgrade manually if you plan on using I2P or I2P-Bote in the intervening time.</p>
+</article><article id="urn:uuid:91ad7d6c-a1e1-4e3c-b9bc-0b3b2742153c" title="0.9.28 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/12/12/0.9.28-Release" author="zzz" published="2016-12-12T12:00:00Z" updated="2016-12-12T12:00:00Z"><details><summary>0.9.28 contains bug fixes</summary></details><p>0.9.28 contains fixes for over 25 Trac tickets, and updates for a number of bundled software packages including Jetty.
+There are fixes for the IPv6 peer testing feature introduced last release.
+We continue improvements to detect and block peers that are potentially malicious.
+There are preliminary fixes for Java 9, although we do not yet recommend Java 9 for general use.</p>
+<p>I2P will be at 33C3, please stop by our table and give us your ideas on how to improve the network.
+We will review our 2017 roadmap and priorities 2017 at the Congress.</p>
+<p>As usual, we recommend that all users update to this release.
+The best way to help the network and stay secure is to run the latest release.</p>
+</article><article id="urn:uuid:00015ff6-b556-11e6-adb4-00163e5e6c1a" title="I2P-Bote Security Vulnerability" href="http://bote.i2p/news/0.4.4/" author="str4d" published="2016-11-28T12:00:00Z" updated="2016-11-28T12:00:00Z"><details><summary>I2P-Bote Security Vulnerability</summary></details><p>I2P-Bote 0.4.4 fixes a security vulnerability present in all earlier versions of the
+I2P-Bote plugin. The Android app was not affected.</p>
+<p>A lack of CSRF protection meant that if a user was running I2P-Bote and then loaded a
+malicious site in a browser with JavaScript enabled, the adversary could trigger actions
+in I2P-Bote on behalf of the user, such as sending messages. This might also have enabled
+extraction of private keys for I2P-Bote addresses, however no proof-of-exploit was tested
+for this.</p>
+<p>All I2P-Bote users will be upgraded automatically the first time they restart their router
+after I2P 0.9.28 is released in mid-December. However, for safety we recommend that you
+<a href="http://bote.i2p/install/">follow the instructions on the installation page</a> to
+upgrade manually if you plan on using I2P or I2P-Bote in the intervening time. You should
+also consider generating new I2P-Bote addresses if you regularly browse sites with
+JavaScript enabled while running I2P-Bote.</p>
+</article><article id="urn:uuid:c1d01ac3-81e7-4acd-bacd-d9178089e8c3" title="0.9.27 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/10/17/0.9.27-Release" author="zzz" published="2016-10-17T12:00:00Z" updated="2016-10-17T12:00:00Z"><details><summary>0.9.27 contains bug fixes</summary></details><p>0.9.27 contains a number of bug fixes.
+The updated GMP library for crypto acceleration, which was bundled in the 0.9.26 release for new installs and Debian builds only, is now included in the in-network update for 0.9.27.
+There are improvements in IPv6 transports, SSU peer testing, and hidden mode.</p>
+<p>We updated a number of plugins during <a href="http://i2p-projekt.i2p/en/blog/post/2016/06/01/I2P-Summer-Dev">I2P Summer</a> and your router will automatically update them after restart.</p>
+<p>As usual, we recommend that all users update to this release.
+The best way to help the network and stay secure is to run the latest release.</p>
+</article><article id="urn:uuid:7e818120-88f8-401a-88fe-8db4ba20ad4d" title="I2P Stack Exchange proposal" href="https://area51.stackexchange.com/proposals/99297/i2p" author="zzz" published="2016-06-07T13:00:00Z" updated="2016-06-07T13:00:00Z"><details><summary>I2P is now a proposed site on Stack Exchange!</summary></details><p>I2P is now a proposed site on Stack Exchange!
+Please <a href="https://area51.stackexchange.com/proposals/99297/i2p">commit to using it</a> so the beta phase can begin.</p>
+</article><article id="urn:uuid:5b1ccc70-2160-44cd-ad1e-2f0be6beb621" title="0.9.26 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/06/07/0.9.26-Release" author="zzz" published="2016-06-07T12:00:00Z" updated="2016-06-07T12:00:00Z"><details><summary>0.9.26 contains crypto updates, Debian packaging improvements, and bug fixes</summary></details><p>0.9.26 contains a major upgrade to our native crypto library,
+a new addressbook subscription protocol with signatures,
+and major improvements to the Debian/Ubuntu packaging.</p>
+<p>For crypto, we have upgraded to GMP 6.0.0, and added support for newer processors,
+which will speed up crypto operations considerably.
+Also, we are now using constant-time GMP functions to prevent side-channel attacks.
+For caution, the GMP changes are enabled for new installs and Debian/Ubuntu builds only;
+we will include them for in-net updates in the 0.9.27 release.</p>
+<p>For Debian/Ubuntu builds, we have added dependencies on several packages,
+including Jetty 8 and geoip, and removed the equivalent bundled code.</p>
+<p>There's a collection of bug fixes also, including a fix for a timer bug
+that caused instability and performance degradations over time.
+As usual, we recommend that all users update to this release.
+The best way to help the network and stay secure is to run the latest release.</p>
+</article><article id="urn:uuid:c6f7228d-3330-4422-a651-ef9d8ca3484b" title="0.9.25 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/03/22/0.9.25-Release" author="zzz" published="2016-03-22T12:00:00Z" updated="2016-03-22T12:00:00Z"><details><summary>0.9.25 contains SAM 3.3, QR codes, and bug fixes</summary></details><p>0.9.25 contains a major new version of SAM, v3.3, to support sophisticated multiprotocol applications.
+It adds QR codes for sharing hidden service addresses with others,
+and "identicon" images for visually distinguishing addresses.</p>
+<p>We've added a new "router family" configuration page in the console,
+to make it easier to declare that your group of routers is run by a single person.
+There are several changes to increase the capacity of the network and hopefully improve tunnel build success.</p>
+<p>As usual, we recommend that all users update to this release.
+The best way to help the network and stay secure is to run the latest release.</p>
+</article><article id="urn:uuid:8390114d-8e50-45fd-8b4d-3e613bdd034e" title="0.9.24 Released" href="http://i2p-projekt.i2p/en/blog/post/2016/01/27/0.9.24-Release" author="zzz" published="2016-01-27T18:00:00Z" updated="2016-01-27T18:00:00Z"><details><summary>0.9.24 contains several bug fixes and speedups</summary></details><p>0.9.24 contains a new version of SAM (v3.2) and numerous bug fixes and efficiency improvements.
+Note that this release is the first to require Java 7.
+Please update to Java 7 or 8 as soon as possible.
+Your router will not automatically update if you are using Java 6.</p>
+<p>To prevent the problems caused by the ancient commons-logging library, we have removed it.
+This will cause very old I2P-Bote plugins (0.2.10 and below, signed by HungryHobo) to crash if they have IMAP enabled.
+The recommended fix is to replace your old I2P-Bote plugin with the current one signed by str4d.
+For more details, see <a href="http://bote.i2p/news/0.4.3">this post</a>.</p>
+<p>We had a great <a href="http://i2p-projekt.i2p/en/blog/post/2016/01/23/32C3">32C3 Congress</a> and are making good progress on our 2016 project plans.
+Echelon gave a talk on I2P's history and current status, and his slides are <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/ccc/2015/I2P_Still_alive.pdf">here</a> (pdf).
+Str4d attended <a href="http://www.realworldcrypto.com/rwc2016/program">Real World Crypto</a> and gave a talk on our crypto migration, 
+his slides are <a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/media/rwc/2016/rwc2016-str4d-slides.pdf">here</a> (pdf).</p>
+<p>As usual, we recommend that all users update to this release.
+The best way to help the network and stay secure is to run the latest release.</p>
+</article><article id="urn:uuid:91d19b26-0d7c-4e4a-aa7b-c22d4f400668" title="0.9.23 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/11/19/0.9.23-Release" author="str4d" published="2015-11-19T18:00:00Z" updated="2015-11-19T18:00:00Z"><details><summary>0.9.23 contains a variety of bug fixes, and some minor improvements in I2PSnark</summary></details><p>Hello I2P! This is the first release signed by me (str4d), after 49 releases
+signed by zzz. This is an important test of our redundancy for all things,
+including people.</p>
+<p><b>Housekeeping</b></p>
+<p>My signing key has been in router updates for over two years (since 0.9.9), so
+if you are on a recent version of I2P this update should be just as easy as
+every other update. However, if you are running an older version than 0.9.9, you
+will first need to manually update to a recent version. Update files for recent
+versions can be downloaded
+<a href="http://whnxvjwjhzsske5yevyokhskllvtisv5ueokw6yvh6t7zqrpra2q.b32.i2p/releases/">here</a>,
+and instructions on how to manually update are provided
+<a href="http://i2p-projekt.i2p/en/download#update">here</a>. Once you have manually
+updated, your router will then find and download the 0.9.23 update as usual.</p>
+<p>If you installed I2P via a package manager, you are not affected by the change,
+and can update as usual.</p>
+<p><b>Update details</b></p>
+<p>The migration of RouterInfos to new, stronger Ed25519 signatures is going well,
+with at least half of the network already estimated to have rekeyed. This
+release accelerates the rekeying process. To reduce network churn, your router
+will have a small probability of converting to Ed25519 at each restart. When it
+does rekey, expect to see lower bandwidth usage for a couple of days as it
+reintegrates into the network with its new identity.</p>
+<p>Note that this will be the last release to support Java 6. Please update to
+Java 7 or 8 as soon as possible. We are already working to make I2P compatible
+with the upcoming Java 9, and some of that work is in this release.</p>
+<p>We have also made some minor improvements in I2PSnark, and added a new page in
+the routerconsole for viewing older news items.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="0.9.22 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 with bug fixes and starts Ed25519 migration</summary></details><p>0.9.22 contains fixes for i2psnark getting stuck before completion, and begins the migration of router infos to new, stronger Ed25519 signatures.
+To reduce network churn, your router will have only a small probability of converting to Ed25519 at each restart.
+When it does rekey, expect to see lower bandwidth usage for a couple of days as it reintegrates into the network with its new identity.
+If all goes well, we will accelerate the rekeying process in the next release.</p>
+<p>I2PCon Toronto was a big success!
+All the presentations and videos are listed on the <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">I2PCon page</a>.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="0.9.21 Released" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>0.9.21 released with performance improvements and bug fixes.</summary></details><p>0.9.21 contains several changes to add capacity to the network, increase the efficiency of the floodfills,
+and use bandwidth more effectively.
+We have migrated the shared clients tunnels to ECDSA signatures and added a DSA fallback
+using the new "multisession" capability for those sites that don't support ECDSA.</p>
+<p>The speakers and the schedule of the I2PCon in Toronto 2015 have been announced.
+Have a look on the <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon page</a> for details.
+Reserve your seat on <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
+<p>As usual, we recommend that you update to this release. The best way to
+maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:53ba215d-6cf2-489c-8135-10248e06a141" title="I2PCon Toronto speakers and schedule announced" href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon" author="echelon" published="2015-07-19T18:00:00Z" updated="2015-07-22T12:00:00Z"><details><summary>I2PCon Toronto 2015 speakers and schedule announced</summary></details><p>The speakers and the schedule of the I2PCon in Toronto 2015 have been announced.
+Have a look on the <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon page</a> for details.
+Reserve your seat on <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>.</p>
+</article>
+</div>

data/translations/entries.yo.html

@@ -1,5 +1,173 @@
 <div>
-<header title="Ìròyìn 12P">Gbàgede Ìròyìn, àti àfikún-un apínṣẹ̀ìsopọ̀ká</header><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
+<header title="Ìròyìn 12P">Gbàgede Ìròyìn, àti àfikún-un apínṣẹ̀ìsopọ̀ká</header><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 Release</summary></details><p>2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release.
+The bug primarily affected high-bandwidth routers.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 Release</summary></details><p>2.8.1 fixes accesses to local sites that were broken in 2.8.0.
+We have added notification bubbles to several applications in the console to highlight application messages.
+We fixed a tunnel test bug that may have been affecting tunnel reliability.
+The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions.
+There are several dark theme fixes and improvements.</p>
+<p>We fixed the installer that previously failed on Java 21 or higher.
+We also fixed installing to directory paths that contain spaces on Linux.
+For those of you that use Docker, we updated outdated Docker container and container libraries.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="Local site access fails in 2.8.0" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 Local Access Bug</summary></details><p>In 2.8.0, browsing to a local site (either by hostname or b32) will fail.
+The workaround is using localhost and the server port, usually 7658, to bypass I2P.
+For example, <a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
+We apologize for the issue and are working on a fix.</p>
+</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 Release</summary></details><p>This release improves I2P by fixing bugs, removing unused code, and improving network stability.</p>
+<p>We have improved handling of congested routers in the network.
+Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting.
+We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload.
+Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 Release" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 Release</summary></details><p>This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.</p>
+<p>Access to information from the console and applications has been improved.
+Issues have been fixed in I2PSnark and SusiMail search.
+The netDB search embedded into the router console now operates in a more intuitive and useful way.
+Minor improvements have been made to diagnostic displays in advanced mode.</p>
+<p>Bugs have also been fixed to improve compatibility within the network.
+An issue with publishing leaseSets was solved which improves reliability major hidden services.
+I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
+This prevents torrents from being unnecessarily disrupted by these changes.
+We welcomed this contribution from a new contributor.
+A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 Release</summary></details><p>I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
+This bug caused scrolling to be disabled, rendering some configuration inaccessible.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 Release</summary></details><p>This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.</p>
+<p>Newer routers will be favored when selecting floodfill routers.
+I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
+Legacy transport protocols are being removed, simplifying the code in the UDP transports.
+Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
+Additional tweaks were made to peer selection strategies.</p>
+<p>I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
+We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
+If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
+Non-exit relays and Tor clients are unaffected by this and do not need to change anything.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 with HTTP fix</summary></details><p>I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 Released" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P Release 2.5.1 released to address Denial-of-Service Attacks</summary></details><p>I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
+With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
+This should help the network return to normal operation.
+Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
+Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="Stormy Weather" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>Network Weather: Stormy. I2P is under attack.</summary></details><p>The I2P network is currently under a Denial-of-Service attack.
+This attack affects I2P and i2pd but in different ways and is having a serious effect on network health.
+Reachability of I2P sites is badly degraded.</p>
+<p>If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability.
+Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.</p>
+</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="New Release I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>More Application Improvements, Audit of NetDB Isolation strategy</summary></details><p>This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.</p>
+<p>New features have been added to I2PSnark like the ability to search through torrents.
+Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
+We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
+New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
+Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.</p>
+<p>During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
+This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
+This investigation uncovered one minor isolation-piercing event which we repaired.
+This issue was discovered and fixed internally by the I2P team.</p>
+<p>During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
+This should result in improved delivery and availability for these downstream products.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 Release with Congestion and NetDB Security improvements" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 Release with Congestion and NetDB Security improvements</summary></details><p>This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
+It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.</p>
+<p>The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
+This will help the network limit the effect of tunnel spam.
+It will also help the network heal during and after DDOS attacks.</p>
+<p>The NetDb changes also help secure individual routers and the applications that use them. 
+Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
+This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.</p>
+<p>Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:" title="New Release I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - Security Fixes, Tweakable blocklists, DTG API</summary></details><p>This release contains fixes for CVE-2023-36325.
+CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter.
+An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client.
+The message, after passing through the bloom filter, is not allowed to be re-used in a second message.
+The attacker then sends the same message directly to the router.
+The router passes the message to the bloom filter, and is dropped.
+This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client.
+This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly.
+Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives.
+Users of Java I2P are recommended to update immediately to avoid the attack.</p>
+<p>In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks.
+This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.</p>
+<p>This release adds not_bob as a second default hosts provider, and adds <a href="http://notbob.i2p">notbob.i2p</a> and <a href="http://ramble.i2p">ramble.i2p</a> to the console homepage.</p>
+<p>This release also contains a tweakable blocklist.
+Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted.
+Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval.
+This feature is off-by-default and is only recommended for advanced users at this time.</p>
+<p>This release also includes an API for plugins to modify with the Desktop GUI(DTG).
+It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="New Release 2.2.1, Packaging fixes for Docker, Ubuntu Lunar and Debian Sid" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - maintenance release for 2.2.0</summary></details><p>After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages.
+This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package.
+Docker packages were not reading arguments correctly, resulting in inaccessible configuration files.
+This issue has also been resolved.
+The docker container is now also compatible with Podman.</p>
+<p>This release syncs translations with transifex and updates the GeoIP database.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="New Release 2.2.0, Mitigations to DDOS attacks and tweaks to the Streaming subsystem" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>Mitigations to DDOS attacks and tweaks to the Streaming subsystem</summary></details><p>We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023.
+This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks.
+The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.</p>
+<p>This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients.
+This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers.
+This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks.
+We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.</p>
+<p>As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz.
+zzz has chosen to step away from the project and his responsibilities are being taken on by other team members.
+As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p.
+We thank zzz for providing these services for such a long time.</p>
+<p>As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.</p>
+</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS Update" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS Update</summary></details><p>We have confirmed that the attacker controls a large number of routers.
+Our investigations and mitigations continue.</p>
+<p>This is a good time to remind people that even after 20 years, the I2P network is relatively small.
+We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service.
+However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require.
+The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.</p>
+<p>We will provide additional information here in the news feed and on <a href="http://zzz.i2p">zzz.i2p</a> as necessary.
+We ask for your patience as we work to improve I2P.</p>
+</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="About the recent Denial of Service attacks" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P remains intact with impaired performance</summary></details><p>The I2P network is currently being affected by a Denial of Service attack.
+  The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping.
+  Participants in the network have experienced difficulties connecting to I2P sites and using I2P services.
+  Mitigation strategies are being investigated and implemented gradually.</p>
+<p>While the attack has degraded performance, the network remains intact and usable.
+  Java I2P routers appear to be handling the issues better than i2pd routers for now.
+  Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.</p>
+</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 with numerous SSU2 fixes</summary></details><p>We have learned several things since our 2.0.0 release in November.
+As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol.
+First, we have confirmed that SSU2 is a solid, well designed, and secure protocol.
+Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol.
+Cumulatively, the effects of these bugs have reduced the performance of the network.</p>
+<p>Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network,
+possibly triggered by Bitcoin's new I2P transient address feature,
+but made worse by our SSU2 bugs and other congestion control problems.
+We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands.
+We have improved our algorithms to reduce network load during times of congestion.
+We are also collaborating with i2pd to develop common congestion control strategies.</p>
+<p>Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody.
+i2pd released their version 2.45.0 last week and the early results are encouraging.
+New protocols, and distributed networks, are difficult to develop.
+Congestion can arrive with little warning and with little clue of the cause.
+Thank you for your patience as we have diagnosed and hopefully fixed the problems.</p>
+<p>Bíi ìṣe, a gbà ó níyànjú kí o s'àfikún sí àgbéjáde yìí. Ọ̀nà ìdáààbòbò tó dáa jù àti ìrànwọ́ fún ẹ̀rọ-ayélukára ni lílo àgbéjáde tuntun. </p>
+</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 Released" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 Transport Enabled</summary></details><p>I2P release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.</p>
 <p>We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.</p>
 <p>Bíi ìṣe, a gbà ó níyànjú kí o s'àfikún sí àgbéjáde yìí. Ọ̀nà ìdáààbòbò tó dáa jù àti ìrànwọ́ fún ẹ̀rọ-ayélukára ni lílo àgbéjáde tuntun. </p>
 </article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="Recent Blog Posts" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>A few recent blog posts</summary></details><p>Here's links to several recent blog posts on our website:</p>

data/translations/entries.zh.html

@@ -1,10 +1,163 @@
 <div>
-<header title="I2P 新闻">新闻订阅和软件更新</header><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 全面启用</summary></details><p>I2P 2.0.0版本在完成了小特性开发、测试和若干错误修复以后还为所有用户启用了我们新的SSU2协议。</p>
+<header title="I2P 新闻">新闻订阅和软件更新</header><article id="urn:uuid:f2a6aabd-ee29-4f45-a8dd-7378e907016a" title="2.9.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2025/06/02/2.9.0_released" author="idk" published="2025-06-02T19:00:00Z" updated="2025-06-02T19:00:00Z"><details><summary>I2P 2.9.0 版本</summary></details><p>I2P 2.9.0 是一个维护版本，包括错误修复和新功能开发。</p>
+<p>改进了线程使用以提高 i2ptunnel 系统的性能。改进了 NTCP2 以抵御探测攻击。通知系统已集成到更多应用程序中，以便从 I2PSnark 和其他应用程序向用户提供更好的反馈。自动播种的注册问题已被修复。用户在参与播种时可能会观察到更多的资源使用情况。如果不希望出现这种情况，可在 /config 页面上禁用播种模式。</p>
+<p>控制台中新增了全局地图功能，可在网络数据库视图中显示路由器位置。这些都是帮助路由器建立隧道和匿名提供服务的对等节点。</p>
+<p>关于隧道的自动带宽管理、数据报 2 协议和后量子密码学的实现工作仍在继续。在两个版本后，即 2.11.0，I2P 将需要 Java 17。</p>
+<p>如往常一样，我们建议您更新到此版本。维护安全和帮助网络的最佳方式是运行最新版本。</p>
+</article><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 发布" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 版本</summary></details><p>2.8.2 修复了 2.8.1 版本中引入的导致 SHA256 失败的错误。该错误主要影响高带宽路由器。</p>
+<p>如往常一样，我们建议您更新到此版本。维护安全和帮助网络的最佳方式是运行最新版本。</p>
+</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 发布" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 版本</summary></details><p>2.8.1 修复了 2.8.0 中本地站点访问问题。我们在控制台中为多个应用程序添加了通知气泡，以突出显示应用程序消息。我们修复了可能影响隧道可靠性的隧道测试错误。地址簿现在新增了“最新”标签页，用于显示您订阅中添加的最新主机名。此外，我们还修复了多项深色主题问题并进行了改进。</p>
+<p>我们修复了之前在 Java 21 或更高版本上失败的安装程序。 我们还修复了在 Linux 上安装到包含空格的目录路径的问题。 对于使用 Docker 的用户，我们更新了过时的 Docker 容器和容器库。</p>
+<p>如往常一样，我们建议您更新到此版本。维护安全和帮助网络的最佳方式是运行最新版本。</p>
+</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="2.8.0 访问本地站点失败" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 本地访问错误</summary></details><p>在 2.8.0 中，浏览本地站点（通过主机名或 b32）将失败。
+解决方法是使用 localhost 和服务器端口（通常为 7658）来绕过 I2P。
+例如，<a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>。
+我们对此问题深表歉意并努力修复中。</p>
+</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 版本" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 版本</summary></details><p>此版本通过修复错误、删除未使用的代码以及提高网络稳定性以改进 I2P。</p>
+<p>我们改进了网络中拥堵的路由器的处理。
+UPnP 和 NAT 遍历的问题已解决，以改善连接性和错误回报。
+我们现在有一个更激进的策略来从 NetDb 中删除赁集，以提高路由器性能并减轻过载。
+另外有一些降低事件可观察性的更改，如路由器重启或关闭等。</p>
+<p>如往常一样，我们建议您更新到此版本。维护安全和帮助网络的最佳方式是运行最新版本。</p>
+</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 已发布</summary></details><p>本次发布，I2P 2.7.0 继续修复错误，提高性能以及添加功能。</p>
+<p>从控制台和应用程序的信息访问已得到改进。
+I2PSnark 和 SusiMail 搜索中的问题已得到修复。
+路由器控制台中嵌入的 netDB 搜索的使用方式现在更直观、更实用。
+高级模式下的诊断显示亦有少量改进。</p>
+<p>另外修复了一些错误以提高网络内的兼容性。
+一个赁集发布的问题已解决，提高了主要隐藏服务的可靠性。
+当用户仅更改现有种子上的跟踪器时，I2PSnark 不再更改信息哈希。
+这可以防止种子因这些更改而受到不必要的干扰。
+我们欢迎这份来自新贡献者的工作。
+在处理流媒体库选项时的冲突已被解决以提高与其他 I2P 实现的兼容性。</p>
+<p>如往常一样，我们建议您更新到此版本。维护安全和帮助网络的最佳方式是运行最新版本。</p>
+</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 已发布" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 版本</summary></details><p>I2P 2.6.1 的发布是为了修复隐藏服务管理器应用程序中的用户界面错误。
+此错误导致滚动被禁用，从而使某些配置无法访问。</p>
+<p>如往常一样，我们建议您更新到此版本。维护安全和帮助网络的最佳方式是运行最新版本。</p>
+</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 已发布" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 版本</summary></details><p>本次发布的 I2P 2.6.0 版本继续致力于修复漏洞、添加新功能并提升网络的可靠性。</p>
+<p>当选择洪泛路由时，较新的路由将受到青睐。
+I2PSnark 除了修复漏洞之外，还获得了一些功能，这些功能可以提高PeX（对等节点交换）的性能。
+遗留的旧传输协议正在被移除，因此简化了UDP传输代码。
+本地主机上的目标节点将可以直接被本地客户端访问，而不需要请求它们的赁集，这可以提高性能和可测试性。
+另外对对等节点的选择策略进行了一些额外的调整。</p>
+<p>I2P 不再允许通过 Tor 建立 I2P 连接，从 Tor 出口IP地址建立的连接现在已被阻止。
+我们不鼓励这样做，因为它会降低I2P的性能，并浪费Tor出口节点的资源而无任何益处。
+如果您既运行Tor出口路由又运行I2P，我们鼓励您继续这样做，为两者使用不同的IP地址。
+非出口节点和Tor客户端不受此影响，无需任何更改。</p>
+<p>如往常一样，我们建议您更新到此版本。维护安全和帮助网络的最佳方式是运行最新版本。</p>
+</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 发布" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 包含 HTTP 修复</summary></details><p>I2P 2.5.2 版本是为了修复在 2.5.0 中引入的导致某些 HTTP 内容被截断的错误。</p>
+<p>如往常一样，我们建议您更新到此版本。维护安全和帮助网络的最佳方式是运行最新版本。</p>
+</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 已发布" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P 版本 2.5.1 已发布以解决拒绝服务攻击</summary></details><p>I2P 2.5.1 的发布是为了解决影响 I2P 网络和服务的拒绝服务攻击。
+在此版本中，我们禁用了 Sybil 攻击检测工具的基于 IP 的部分，这些部分旨在放大攻击的影响和持续时间。
+这应该有助于网络恢复正常运行。
+那些已禁用 Sybil 攻击检测工具的人可以安全地重新启用它。
+其他子系统也进行了调整，以改进路由信息验证和对等节点选择。</p>
+<p>如往常一样，我们建议您更新到此版本。维护安全和帮助网络的最佳方式是运行最新版本。</p>
+</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="暴风雨天气" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>网络天气：暴风雨。 I2P 正在遭受攻击。</summary></details><p>I2P 网络目前正遭受拒绝服务攻击。
+此攻击以不同的方式影响 I2P 和 i2pd，并对网络健康状况造成严重影响。
+I2P 站点可达性严重下降。</p>
+<p>如果您在 I2P 内部托管服务，并且该服务托管在洪泛路由上，则应考虑在禁用 Floodfill 的路由器上对该服务采用多宿主形式，以提高可达性。
+其他缓解措施正在讨论中，但长期的、可向后兼容的解决方案仍需进一步研究。</p>
+</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="新版本 I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>更多应用改善，NetDB隔离策略审计</summary></details><p>该版本 I2P 2.5.0 比 2.4.0 版本提供了更多面向用户的改进，后者侧重于实施 NetDB 隔离策略。</p>
+<p>I2PSnark增加了一些新功能，比如搜索种子。
+若干错误已经修复，以提高与其他I2P种子客户端如 BiglyBT 和 qBittorrent 的兼容性。
+我们要感谢所有与libtorrent和qBittorrent合作的开发人员，他们支持并改进了I2P支持。
+SusiMail还增加了一些新功能，包括支持邮件中的Markdown格式和将附件拖放到邮件中的功能。
+使用隐藏服务管理器创建的隧道现在支持“Keepalive”，这提高了性能和与网络技术的兼容性，使更复杂的I2P站点成为可能。</p>
+<p>在此版本中，我们还对 NetDB 进行了一些调整，以增强其对垃圾信息的韧性，并提高路由器阻挡可疑消息的能力。
+这是“审计” 2.4.0 版本中“子数据库隔离”防御实现的一部分。
+此次调查发现了一个小的隔离穿透事件并修复之。
+这个问题是 I2P 团队在内部发现并修复的。</p>
+<p>在这个版本中，我们对发布Android和Windows下游发行版的过程进行了一些改进。
+这将改善这些下游产品的交付和可用性。</p>
+<p>如往常一样，我们建议您更新到此版本。维护安全和帮助网络的最佳方式是运行最新版本。</p>
+</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 发布包含 Congestion 和 NetDB 安全提升" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 发布包含 Congestion 和 NetDB 安全提升</summary></details><p>此版本 I2P 2.4.0 持续努力提高 I2P 网络的安全性和稳定性。
+其中包含对网络数据库的大幅改进，网络数据库是 I2P 网络中用于发现对等节点的基本结构。</p>
+<p>拥塞控制的改进将使路由器能够通过避开拥堵的对等节点从而提高网络稳定性。
+这将有助于网络限制隧道垃圾信息造成的影响。
+它还将有助于在 DDOS 攻击期间和之后修复网络。</p>
+<p>NetDb 的更改还有助于保护各个路由器以及使用它们的应用程序的安全。
+路由器现在可以通过将 NetDB 分成多个“子DB”来防御攻击者，我们使用这些“子DB”来防止应用程序和路由器之间的信息泄漏。
+这同时改进了 Java 路由器可用的有关其 NetDB 活动的信息，并简化了我们对多宿主应用程序的支持。</p>
+<p>还包括 I2PSnark 和 SusiMail 应用程序中的许多错误修复和功能增强。</p>
+<p>如往常一样，我们建议您更新到此版本。维护安全和帮助网络的最佳方式是运行最新版本。</p>
+</article><article id="urn:uuid:" title="I2P 2.3.0 新版本 - 安全修复，可调的黑名单，DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - 安全修复，可调的黑名单，DTG API</summary></details><p>此版本包含 CVE-2023-36325 的修复。
+CVE-2023-36325 是一个发生在布隆过滤器中的上下文混淆错误。
+攻击者制作包含唯一 messageID 的 I2NP 消息，并将该 messageID 发送给客户端。
+该消息在通过布隆过滤器后，不允许在第二条消息中重复使用。
+随后，攻击者将相同的消息直接发送给路由。
+路由器将消息传递给布隆过滤器并被丢弃。
+这泄露了之前已经看到的 messageID 信息，使攻击者有充分的理由相信路由器承载了客户端。
+这个问题已经通过将布隆过滤器的功能分离到不同的上下文中得到了解决，这些上下文中是基于消息是通过客户端隧道，还是探测隧道直接发送到路由的。
+在正常情况下，这种攻击需要数天才能成功执行，并且可能受到攻击期间路由重启和对误报的灵敏度等若干因素的干扰。
+建议使用 Java I2P 的用户立即更新以免受攻击。</p>
+<p>在修复这个上下文混淆错误的过程中，我们修改了一些策略来防御这类型的泄漏。
+这包括对 netDb 的调整、速率限制机制和洪泛路由的行为。</p>
+<p>此版本添加了 not_bob 作为第二个默认hosts来源，并把<a href="http://notbob.i2p">notbob.i2p</a>和<a href="http://ramble.i2p">ramble.i2p</a>添加到控制台主页。</p>
+<p>这个版本还包含一个可调整的黑名单。
+黑名单是半永久性的，每个被封禁的IP地址会被一直屏蔽，直到路由器重新启动。
+在 sybil 攻击期间观察到黑名单爆炸性增长的用户可以通过将黑名单配置为按一定时间段使条目过期来缩短超时间隔。
+此功能在默认情况下是关闭的，目前仅建议高级用户使用。</p>
+<p>该版本还包括一个API，用于使用桌面GUI(DTG)修改插件。
+现在可以将菜单项添加到系统托盘中，从而更直观地启动使用本地应用接口的插件。</p>
+<p>如往常一样，我们建议您更新到此版本。维护安全和帮助网络的最佳方式是运行最新版本。</p>
+</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="新版本 2.2.1，包含Docker，Ubuntu Lunar和Debian Sid的打包修复" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - 2.2.0 的维护修复</summary></details><p>I2P 2.2.0 版本向前推进以加快缓解 DDOS 攻击后，我们了解到一些开发问题，因此有必要构建和发布新包。
+此发布修复了 Ubuntu Lunar 和 Debian Sid 中的一个问题，即使用更新后的版本的 jakarta 包无法访问路由器控制台。
+Docker 包未正确读取参数，导致无法访问配置文件。
+此问题也已解决。
+docker 容器现在也与 Podman 兼容。</p>
+<p>本发布与 transifex 同步翻译并更新 GeoIP 数据库。</p>
+<p>如往常一样，我们建议您更新到此版本。维护安全和帮助网络的最佳方式是运行最新版本。</p>
+</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="新版本 2.2.0，包含DDOS攻击的缓解措施和 Streaming 子系统的调整" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>DDOS攻击的缓解措施和 Streaming 子系统的调整</summary></details><p>我们已选择将 2.2.0 的发布日期提前到今天，即 2023 年 3 月 13 日。
+此版本包括对网络数据库、洪泛和节点选择组件的修改，提高了路由器抵御 DDOS 攻击的能力。
+攻击可能会持续进行，但对这些系统的改进将通过帮助路由识别和降低路由评分来帮助减轻 DDOS 攻击的风险。</p>
+<p>此版本还为 Streaming 子系统添加了重放保护，以防止可以捕获加密数据包的攻击者通过将其发送给意外的接收者来重新使用它。
+这是一个向后兼容的更改，因此旧路由器仍然能够使用新路由器的流媒体功能。
+此问题由 I2P 开发团队在内部发现并修复，与 DDOS 攻击无关。
+我们从未在实际环境遇到过重放流数据包，并且不相信此时针对 I2P 网络发生过流重放攻击。</p>
+<p>您可能已经注意到，这些发行说明和发行版本身已由 idk 而非 zzz 签署。
+zzz 已选择退出该项目，他的职责由其他团队成员承担。
+因此，该项目正致力于更换网络统计基础设施并将开发论坛移至 i2pforum.i2p。
+我们感谢 zzz 长期以来提供这些服务。</p>
+<p>如往常一样，我们建议您更新到此版本。维护安全和帮助网络的最佳方式是运行最新版本。</p>
+</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS 消息进展" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS 消息进展</summary></details><p>我们已经确认攻击者控制了大量的路由器。
+我们的调查和缓解措施仍在继续当中。</p>
+<p>这是提醒人们即使在 20 年后，I2P 网络规模仍然相对较小的好时候。
+我们没有证据表明攻击者正试图对任何特定用户或隐藏服务进行去匿名化。
+但是，如果您有高风险威胁模型，您应该仔细考虑 I2P 目前是否提供了您需要的保护。
+从长远来看，最好的解决方案是宣传并发展 I2P 网络以提高我们用户的安全性。</p>
+<p>我们将在有必要时在新闻推送和<a href="http://zzz.i2p">zzz.i2p</a>提供更多信息。
+在我们努力改进 I2P 的过程中，请您耐心等待。</p>
+</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="关于最近的拒绝服务攻击" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P 保持完好，但性能受损</summary></details><p>I2P 网络目前正受到拒绝服务攻击的影响。
+网络的洪泛功能受到影响，导致响应中断，隧道构建成功率下降。
+网络参与者在连接到 I2P 站点和使用 I2P 服务时遇到困难。
+我们在正在逐步调查和实施缓解策略。</p>
+<p>虽然攻击降低了性能，但网络仍然完好无损且可用。
+目前，Java I2P 路由器似乎比 i2pd 路由器能更好地处理这些问题。
+下周，各种缓解措施应该会开始出现在 Java 和 C++ 路由器的开发版本中。</p>
+</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 包含大量 SSU2 修复</summary></details><p>自 11 月发布 2.0.0 以来，我们获知了一些情况。
+随着路由器更新到该版本，网络对我们新的 SSU2 传输协议的支持率从大约 1% 提高到 60% 以上。
+首先，我们已经确认 SSU2 是一个可靠、设计良好且安全的协议。
+其次，我们发现并修复了协议推行中的许多小错误或很少触发的错误。
+这些错误累积起来的影响降低了网络的性能。</p>
+<p>此外，我们还注意到网络中隧道数量的增加和隧道构建成功率的下降，
+可能是由比特币新的 I2P 临时地址功能触发的，
+但由于我们的 SSU2 错误和其他拥塞控制问题而变得更差。
+我们正在与比特币和其他非比特币项目合作，以减少 I2P 网络需求。
+我们改进了算法以减少拥塞期间的网络负载。
+我们还与 i2pd 合作开发通用的拥塞控制策略。</p>
+<p>因此，我们将此版本的发布时间加快了大约六周，以便向所有人发布修复程序。
+i2pd 上周发布了他们的 2.45.0 版，早期的结果令人鼓舞。
+新协议和分布式网络的开发很困难。
+拥塞可能会在没有任何警告和原因的情况下出现。
+感谢您的耐心等待，因为我们已经诊断并希望解决问题。</p>
+<p>如往常一样，我们建议您升级到这个版本。维护安全并帮助网络的最佳方式就是运行最新版本。</p>
+</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 全面启用</summary></details><p>I2P 2.0.0版本在完成了小特性开发、测试和若干错误修复以后还为所有用户启用了我们新的SSU2协议。</p>
 <p>我们也修复了各种问题，包括安装包、网络数据库、私有地址簿添加，Windows浏览器启动程序，和IPv6 UPnP。</p>
 <p>如往常一样，我们建议您升级到这个版本。维护安全并帮助网络的最佳方式就是运行最新版本。</p>
 </article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="最近的博客文章" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>部分最近的博客文章</summary></details><p>这是我们网站部分最近的博客文章的链接：</p>
 <ul>
-<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">有关我们新的SSU2 协议的概述</a></li>
+<li><a href="http://i2p-projekt.i2p/en/blog/post/2022/10/11/SSU2-Transport">有关我们新的 SSU2 协议的概述</a></li>
 <li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/i2p-safety-reminder">有关I2P币及其他骗局的警告</a></li>
 <li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/26/meet-your-maintainer-divaexchange">与divs.exchange的Konrad的访谈</a></li>
 <li><a href="http://i2p-projekt.i2p/en/blog/post/2022/09/07/Meet_your_Maintainer_StormyCloud">与StormyCloud的Dustin的访谈</a></li>
@@ -30,7 +183,7 @@
  <a href="http://i2p-projekt.i2p/en/blog/post/2022/8/4/Enable-StormyCloud">在我们的博客文章上查看截图</a>。
 你可以在 <a href="http://notbob.i2p/cgi-bin/blog.cgi?page=116">notbob的博客</a>上查看Android版的说明和截图。</p>
 <p>路由器更新不会更新你的配置，你必须手动修改。
-非常感谢StormyCloud的支持。如果可能的话，请考虑<a href="http://stormycloud.i2p/donate.html">给他们捐赠</a>。</p>
+非常感谢 StormyCloud 的支持。如果可能的话，请考虑<a href="http://stormycloud.i2p/donate.html">给他们捐赠</a>。</p>
 </article><article id="urn:uuid:ad7c438d-01c6-435b-b290-855190d73b73" title="1.8.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2022/05/23/1.8.0-Release" author="zzz" published="2022-05-23T12:00:00Z" updated="2022-05-23T12:00:00Z"><details><summary>1.8.0 包含错误修复</summary></details><p>本发布包含i2psnark，
 路由器，I2CP和UPnP的错误修复。
 修复了路由器软重启、IPv6、SSU 对等节点测试、网络数据库存储和隧道构建中的地址错误。
@@ -42,7 +195,7 @@ SSU2将带来实质性的性能和安全性改进。
 本发布包含一个默认关闭的初步发行。
 如果你想参与测试，请关注zzz.i2p的当前消息。</p>
 <p>如往常一样，我们建议您升级到这个版本。维护安全并帮助网络的最佳方式就是运行最新版本。</p>
-</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="安装必要的Java/Jpackage升级" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>最近Java的“Psychic Signatures”漏洞影响到I2P。当前Linux的I2P用户，或任何正在使用非捆绑JVM的I2P用户应当更新
+</article><article id="urn:uuid:0b18adce-f766-45bf-bf12-dc0b32951a71" title="安装必要的 Java/Jpackage 升级" href="http://i2p-projekt.i2p/en/blog/post/2022/4/21/Easy-Install-Updates" author="idk" published="2022-04-22T11:00:00Z" updated="2022-04-22T11:00:00Z"><details><summary></summary></details><p>最近Java的“Psychic Signatures”漏洞影响到I2P。当前Linux的I2P用户，或任何正在使用非捆绑JVM的I2P用户应当更新
 他们的JVM或切换到 Java 15 以下
 不包含该漏洞的版本。</p>
 <p>新的I2P一键安装包已使用
@@ -54,7 +207,7 @@ i2psnark 现在有一个新的种子编辑器。
 还大大降低了 NTCP2 的CPU占用。</p>
 <p>在新安装中，长期不受支持的 BOB 接口已被移除。
 除了 Debian 包以外，现有的安装将继续使用之。
-其余任何 BOB 应用的用户都应该要求开发人员切换到SAMv3协议。</p>
+其余任何 BOB 应用的用户都应该要求开发人员切换到 SAMv3 协议。</p>
 <p>我们得知自 1.6.1 发布以来，网络可靠性不断恶化。
 我们在发布以后很快就意识到了这个问题，然而我们花了近两个月才找到原因。
 我们最终确认为 i2pd 2.40.0 中的一个bug，
@@ -75,10 +228,10 @@ SSU2 将带来实质上的性能和安全提升。
 为路由迁移至 X25519 加密的步伐加快了，我们预计绝大部分路由在今年年底能完成切换。
 短隧道构建信息已启用以减少带宽使用。</p>
 <p>我们为新安装向导增添了一个主题选择面板。
-我们改善了SSU表现，修复了一个SSU对等节点测试信息的问题。
-调整了隧道构建Bloom过滤器以降低内存使用。
+我们改善了 SSU 表现，修复了一个 SSU 对等节点测试信息的问题。
+调整了隧道构建布隆过滤器以降低内存使用。
 我们改善了非Java插件的支持。</p>
-<p>另外，我们在设计新的UDP传输协议SSU2方面取得了重大进展，预计明年年初开始推行。</p>
+<p>另外，我们在设计新的 UDP 传输协议 SSU2 方面取得了重大进展，预计明年年初开始推行。</p>
 <p>如往常一样，我们建议您升级到这个版本。维护安全并帮助网络的最佳方式就是运行最新版本。</p>
 </article><article id="urn:uuid:87e8a1b1-d683-4e8e-9f5a-b1ac746b3ae9" title="1.5.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2021/08/23/1.5.0-Release" author="zzz" published="2021-08-23T12:00:00Z" updated="2021-08-23T12:00:00Z"><details><summary>1.5.0 包含新的隧道搭建信息</summary></details><p>是的没错，在 0.9.x 发布9年后，我们直接从 0.9.50 跳到 1.5.0。
 这并不意味着有重大的API更改，也不意味着开发已经完成。
@@ -336,9 +489,9 @@ Str4d 出席了 <a href="http://www.realworldcrypto.com/rwc2016/program">Real Wo
 </article><article id="urn:uuid:fe93e501-255c-4558-af7e-1cd433939b43" title="0.9.22 发布" href="http://i2p-projekt.i2p/en/blog/post/2015/09/12/0.9.22-Release" author="zzz" published="2015-09-12T18:00:00Z" updated="2015-09-12T18:00:00Z"><details><summary>0.9.22 带有bug修复并且开始 Ed25519 迁移</summary></details><p>0.9.22 包含对 i2psnark 在完成前被攻陷的修复，并且开始将路由器信息向更新、更强的 Ed25519 签名迁移。 为了减少网络的流失，您的路由器将只在每次重启时有较小的概率开始转换为 Ed25519。 在转换之后，请预期到在几天内看到较低的带宽使用量，因为它需要重新将新的身份集成到网络中。 如果一切顺利，我们在下一个版本中加快密钥更新的过程。</p>
 <p>I2PCon Toronto 成功！ 所有演讲和视频资料已放在 <a href="http://i2p-projekt.i2p/en/about/i2pcon/2015">I2PCon 页面</a>。</p>
 <p>如往常一样，我们建议您升级到这个版本。维护安全并帮助网络的最佳方式就是运行最新版本。</p>
-</article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="0.9.21 发布" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>0.9.21 版本带有性能改进和缺陷修复。</summary></details><p>0.9.21&nbsp;包含几个更改，以增加网络容量、提高播种效率，并更有效率的使用带宽。我们已经迁移共享客户端隧道到 ECDSA 签名，并使用新的 "multisession"&nbsp;功能为那些不支持 ECDSA&nbsp;的站点添加一个 DSA&nbsp;后备。</p>
-<p>2015年多洛伦 I2PCon&nbsp;的报告人和时间表已经公布。查阅 <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon 页面</a>了解详细信息。在 <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>&nbsp;上预定您的座位。&lt;br&gt;</p>
+</article><article id="urn:uuid:49713025-cfb8-4ebb-aaaa-7805333efa6a" title="0.9.21 发布" href="http://i2p-projekt.i2p/en/blog/post/2015/07/31/0.9.21-Release" author="zzz" published="2015-07-31T18:00:00Z" updated="2015-07-31T18:00:00Z"><details><summary>0.9.21 版本带有性能改进和缺陷修复。</summary></details><p>0.9.21 包含几个更改，以增加网络容量、提高播种效率，并更有效率的使用带宽。我们已经迁移共享客户端隧道到 ECDSA 签名，并使用新的 "multisession" 功能为那些不支持 ECDSA 的站点添加一个 DSA 后备。</p>
+<p>2015年多洛伦 I2PCon 的报告人和时间表已经公布。查阅 <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon 页面</a>了解详细信息。在 <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a> 上预定您的座位。</p>
 <p>如往常一样，我们建议您升级到这个版本。维护安全并帮助网络的最佳方式就是运行最新版本。</p>
-</article><article id="urn:uuid:53ba215d-6cf2-489c-8135-10248e06a141" title="I2PCon&nbsp;多伦多报告人和时间表已公布" href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon" author="echelon" published="2015-07-19T18:00:00Z" updated="2015-07-22T12:00:00Z"><details><summary>2015年在多伦多的 I2PCon&nbsp;报告人和时间表已公布&lt;br&gt;</summary></details><p>2015年多洛伦 I2PCon&nbsp;的报告人和时间表已经公布。查阅 <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon 页面</a>了解详细信息。在 <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a>&nbsp;上预定您的座位。&lt;br&gt;</p>
+</article><article id="urn:uuid:53ba215d-6cf2-489c-8135-10248e06a141" title="I2PCon 多伦多报告人和时间表已公布" href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon" author="echelon" published="2015-07-19T18:00:00Z" updated="2015-07-22T12:00:00Z"><details><summary>2015年在多伦多的 I2PCon 报告人和时间表已公布</summary></details><p>2015年多洛伦 I2PCon 的报告人和时间表已经公布。查阅 <a href="http://i2p-projekt.i2p/en/blog/post/2015/07/16/I2PCon">I2PCon 页面</a>了解详细信息。在 <a href="http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466">Eventbrite I2PCon</a> 上预定您的座位。</p>
 </article>
 </div>

data/translations/entries.zh_TW.html

@@ -1,5 +1,179 @@
 <div>
-<header title="I2P 新聞">新聞提要和路由器更新</header><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 已启用</summary></details><p>I2P 2.0.0版本在完成了小特性开发、测试和若干错误修复以后为所有用户启用了我们新的SSU2 UDP传输。</p>
+<header title="I2P 新聞">新聞提要和路由器更新</header><article id="urn:uuid:f2a6aabd-ee29-4f45-a8dd-7378e907016a" title="2.9.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2025/06/02/2.9.0_released" author="idk" published="2025-06-02T19:00:00Z" updated="2025-06-02T19:00:00Z"><details><summary>I2P 2.9.0 版本</summary></details><p>I2P 2.9.0 是一个维护版本，包括错误修复和新功能开发。</p>
+<p>改进了线程使用以提高 i2ptunnel 系统的性能。改进了 NTCP2 以抵御探测攻击。通知系统已集成到更多应用程序中，以便从 I2PSnark 和其他应用程序向用户提供更好的反馈。修复了自动播种注册问题。用户在充当播种时可能会观察到更多的资源使用情况。如果不希望出现这种情况，可在 /config 页面上禁用播种模式。</p>
+<p>控制台中新增了全局地图功能，可在网络数据库视图中显示路由器位置。这些都是帮助路由器建立隧道和匿名提供服务的对等节点。</p>
+<p>关于隧道的自动带宽管理、数据报 2 协议和后量子密码学的实现工作仍在继续。在两个版本后，即 2.11.0，I2P 将需要 Java 17。</p>
+<p>如往常一样，我们建议您升级到这个版本。
+维护安全并帮助网络的最佳方式就是运行最新版本。</p>
+</article><article id="urn:uuid:50254469-02a4-4615-bf33-8002e4f935fe" title="2.8.2 发布" href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release" author="zzz" published="2025-03-29T12:00:00Z" updated="2025-03-29T12:00:00Z"><details><summary>I2P 2.8.2 版本</summary></details><p>2.8.2 修复了在 2.8.1 版本中引入的导致 SHA256 失败的错误。
+该错误主要影响高带宽路由器。</p>
+<p>如往常一样，我们建议您升级到这个版本。
+维护安全并帮助网络的最佳方式就是运行最新版本。</p>
+</article><article id="urn:uuid:34d09336-48af-44d2-954c-c5fd879bd6ce" title="2.8.1 发布" href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release" author="zzz" published="2025-03-17T14:00:00Z" updated="2025-03-17T14:00:00Z"><details><summary>I2P 2.8.1 版本</summary></details><p>2.8.1 修复了 2.8.0 中出现问题的本地站点访问问题。
+我们在控制台中为多个应用程序添加了通知气泡，以突出显示应用的消息。
+我们修复了可能影响隧道可靠性的隧道测试错误。
+地址簿现在有一个新的“最新”选项卡，显示从您的订阅中添加的最新主机名。
+对暗色主题进行了若干处修复和改进。</p>
+<p>我们修复了之前在 Java 21 或更高版本上失败的安装程序。
+我们还修复了在 Linux 上安装到包含空格的目录路径出现的问题。
+对于使用 Docker 的用户，我们更新了过时的 Docker 容器和容器库。</p>
+<p>如往常一样，我们建议您升级到这个版本。
+维护安全并帮助网络的最佳方式就是运行最新版本。</p>
+</article><article id="urn:uuid:847ddf63-9aa5-41e7-a3ac-48cb277d883e" title="2.8.0 访问本地站点失败" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="zzz" published="2025-02-08T16:00:00Z" updated="2025-02-08T16:00:00Z"><details><summary>2.8.0 本地访问错误</summary></details><p>在 2.8.0 中，浏览本地站点（通过主机名或 b32）将失败。
+解决方法是使用 localhost 和服务器端口（通常为 7658）来绕过 I2P。
+例如，<a href="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>。
+我们对此问题深表歉意并努力修复中。</p>
+</article><article id="urn:uuid:06f15e55-4cdb-4d17-9d55-a0b289017994" title="I2P 2.8.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release" author="idk" published="2025-02-03T13:00:00Z" updated="2025-02-03T13:00:00Z"><details><summary>I2P 2.8.0 发布</summary></details><p>此版本通过修复错误、删除未使用的代码以及提高网络稳定性以改进 I2P。</p>
+<p>我们改进了网络中拥堵的路由器的处理。
+UPnP 和 NAT 遍历中的问题已解决，以改善连接性和错误回报。
+我们现在有一个更激进的策略来从 NetDb 中删除赁集，以提高路由器性能并减轻过载。
+另外有一些降低事件可观察性的更改，如路由器重启或关闭等。</p>
+<p>如往常一样，我们建议您升级到这个版本。
+维护安全并帮助网络的最佳方式就是运行最新版本。</p>
+</article><article id="urn:uuid:f6a17bb2-0c3c-4028-9e1e-bf1b9a9439c0" title="I2P 2.7.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release" author="idk" published="2024-10-08T10:00:00Z" updated="2024-10-08T10:00:00Z"><details><summary>I2P 2.7.0 发布</summary></details><p>本次发布，I2P 2.7.0 继续修复错误，提高性能以及添加功能。</p>
+<p>从控制台和应用程序的信息访问已得到改进。
+I2PSnark 和 SusiMail 搜索中的问题已得到修复。
+路由器控制台中嵌入的 netDB 搜索的使用方式现在更直观、更实用。
+高级模式下的诊断显示亦有少量改进。</p>
+<p>另外修复了一些错误以提高网络内的兼容性。
+一个赁集发布的问题已解决，提高了主要隐藏服务的可靠性。
+当用户仅更改现有种子上的跟踪器时，I2PSnark 不再更改信息哈希。
+这可以防止种子因这些更改而受到不必要的干扰。
+我们欢迎这份来自新贡献者的工作。
+在处理流媒体库选项时的冲突已被解决以提高与其他 I2P 实现的兼容性。</p>
+<p>如往常一样，我们建议您升级到这个版本。
+维护安全并帮助网络的最佳方式就是运行最新版本。</p>
+</article><article id="urn:uuid:818bda0d-22a4-48a9-9745-503db1d2f632" title="I2P 2.6.1 已发布" href="http://i2p-projekt.i2p/en/blog/post/2024/08/06/i2p_2.6.1_released" author="idk" published="2024-08-06T13:00:00Z" updated="2024-08-06T13:00:00Z"><details><summary>I2P 2.6.1 版本</summary></details><p>I2P 2.6.1 的发布是为了修复隐藏服务管理器应用程序中的用户界面错误。
+此错误导致滚动被禁用，从而使某些配置无法访问。</p>
+<p>如往常一样，我们建议您升级到这个版本。
+维护安全并帮助网络的最佳方式就是运行最新版本。</p>
+</article><article id="urn:uuid:7a55a68d-d01e-4538-ab87-216550a4e40e" title="I2P 2.6.0 已发布" href="http://i2p-projekt.i2p/en/blog/post/2024/07/19/i2p_2.6.0_released" author="idk" published="2024-07-19T22:00:00Z" updated="2024-07-19T22:00:00Z"><details><summary>I2P 2.6.0 版本</summary></details><p>本次发布的I2P 2.6.0版本继续致力于修复漏洞、添加新功能并提升网络的可靠性。</p>
+<p>当选择洪泛路由时，较新的路由将受到青睐。
+I2PSnark 除了修复漏洞之外，还获得了一些功能，这些功能可以提高PeX（对等节点交换）的性能。
+遗留的旧传输协议正在被移除，因此简化了UDP传输代码。
+本地主机上的目标节点将可以直接被本地客户端访问，而不需要请求它们的赁集，这可以提高性能和可测试性。
+另外对对等节点的选择策略进行了一些额外的调整。</p>
+<p>I2P 不再允许通过 Tor 建立 I2P 连接，从 Tor 出口IP地址建立的连接现在已被阻止。
+我们不鼓励这样做，因为它会降低I2P的性能，并浪费Tor出口节点的资源而无任何益处。
+如果您既运行Tor出口路由又运行I2P，我们鼓励您继续这样做，为两者使用不同的IP地址。
+非出口节点和Tor客户端不受此影响，无需任何更改。</p>
+<p>如往常一样，我们建议您升级到这个版本。
+维护安全并帮助网络的最佳方式就是运行最新版本。</p>
+</article><article id="urn:uuid:2afb1b0a-0ba3-466b-a665-ccdd5ede9ccf" title="2.5.2 发布" href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release" author="zzz" published="2024-05-15T12:00:00Z" updated="2024-05-15T12:00:00Z"><details><summary>2.5.2 包含 http 修复</summary></details><p>I2P 2.5.2 版本是为了修复 2.5.0 中引入的导致某些 HTTP 内容被截断的错误。</p>
+<p>如往常一样，我们建议您升级到这个版本。
+维护安全并帮助网络的最佳方式就是运行最新版本。</p>
+</article><article id="urn:uuid:f6735a6b-8405-4ee0-835b-b2826c4f254a" title="I2P 2.5.1 已发布" href="http://i2p-projekt.i2p/en/blog/post/2024/05/06/i2p_2.5.1_released" author="idk" published="2024-05-06T10:00:00Z" updated="2024-05-06T10:00:00Z"><details><summary>I2P 版本 2.5.1 已发布以解决拒绝服务攻击</summary></details><p>I2P 2.5.1 的发布是为了解决影响 I2P 网络和服务的拒绝服务攻击。
+在此版本中，我们禁用了 Sybil 攻击检测工具的基于 IP 的部分，这些部分旨在放大攻击的影响和持续时间。
+这应该有助于网络恢复正常运行。
+那些已禁用 Sybil 攻击检测工具的人可以安全地重新启用它。
+其他子系统也进行了调整，以改进路由信息验证和节点选择。</p>
+<p>如往常一样，我们建议您升级到这个版本。
+维护安全并帮助网络的最佳方式就是运行最新版本。</p>
+</article><article id="urn:uuid:1dfa95f0-faed-4bb3-900a-c532b9ae5c9d" title="暴风雨天气" href="http://i2p-projekt.i2p/en/blog/post/2024/04/25/stormy_weather" author="idk" published="2024-04-25T22:00:00Z" updated="2024-04-25T22:00:00Z"><details><summary>网络天气：暴风雨。 I2P 正在遭受攻击。</summary></details><p>I2P 网络目前正遭受拒绝服务攻击。
+此攻击以不同的方式影响 I2P 和 i2pd，并对网络健康状况造成严重影响。
+I2P 站点可达性严重下降。</p>
+<p>如果您在 I2P 内部托管服务，并且该服务托管在洪泛路由上，则应考虑在禁用 Floodfill 的路由器上对该服务采用多宿主形式，以提高可达性。
+其他缓解措施正在讨论中，但长期的、可向后兼容的解决方案仍需进一步研究。</p>
+</article><article id="urn:uuid:d0b633da-0f36-409e-9b2a-9a3b03b033c3" title="新版本 I2P 2.5.0" href="http://i2p-projekt.i2p/en/blog/post/2024/04/08/new_release_i2p_2.5.0" author="idk" published="2024-04-08T10:00:00Z" updated="2024-04-08T10:00:00Z"><details><summary>更多应用改善，NetDB隔离策略审计</summary></details><p>该版本 I2P 2.5.0 比 2.4.0 版本提供了更多面向用户的改进，后者侧重于实施 NetDB 隔离策略。</p>
+<p>I2PSnark增加了一些新功能，比如搜索种子。
+若干错误已经修复，以提高与其他I2P种子客户端(如 BiglyBT 和 qBittorrent)的兼容性。
+我们要感谢所有与libtorrent和qBittorrent合作的开发人员，他们支持并改进了I2P支持。
+SusiMail还增加了一些新功能，包括支持邮件中的Markdown格式和将附件拖放到邮件中的功能。
+使用隐藏服务管理器创建的隧道现在支持“Keepalive”，这提高了性能和与网络技术的兼容性，使更复杂的I2P站点成为可能。</p>
+<p>在此版本中，我们还对 NetDB 进行了一些调整，以提高其对垃圾邮件的韧性，并提高路由器阻挡可疑消息的能力。
+这是“审计” 2.4.0 版本中“子数据库隔离”防御实现的一部分。
+此次调查发现了一个小的隔离穿透事件并修复之。
+这个问题是 I2P 团队在内部发现并修复的。</p>
+<p>在这个版本中，我们对发布Android和Windows下游发行版的过程进行了一些改进。
+这将改善这些下游产品的交付和可用性。</p>
+<p>如往常一样，我们建议您升级到这个版本。
+维护安全并帮助网络的最佳方式就是运行最新版本。</p>
+</article><article id="urn:uuid:6be01098-562b-48f9-b205-455c0d9665a7" title="I2P 2.4.0 发布包含 Congestion 和 NetDB 安全提升" href="http://i2p-projekt.i2p/en/blog/post/2023/12/18/i2p-release-2.4.0" author="idk" published="2023-12-18T20:00:00Z" updated="2023-12-18T20:00:00Z"><details><summary>I2P 2.4.0 发布包含 Congestion 和 NetDB 安全提升</summary></details><p>此版本 I2P 2.4.0 持续努力提高 I2P 网络的安全性和稳定性。
+其中包含对网络数据库的大幅改进，网络数据库是 I2P 网络中用于发现对等节点的基本结构。</p>
+<p>拥塞控制的改进将使路由器能够通过避开拥堵的对等节点从而提高网络稳定性。
+这将有助于网络限制隧道垃圾信息造成的影响。
+它还将有助于在 DDOS 攻击期间和之后修复网络。</p>
+<p>NetDb 的更改还有助于保护各个路由器以及使用它们的应用程序的安全。
+路由器现在可以通过将 NetDB 分成多个“子DB”来防御攻击者，我们使用这些“子DB”来防止应用程序和路由器之间的信息泄漏。
+这同时改进了 Java 路由器可用的有关其 NetDB 活动的信息，并简化了我们对多宿主应用程序的支持。</p>
+<p>还包括 I2PSnark 和 SusiMail 应用程序中的许多错误修复和功能增强。</p>
+<p>如往常一样，我们建议您升级到这个版本。
+维护安全并帮助网络的最佳方式就是运行最新版本。</p>
+</article><article id="urn:uuid:" title="I2P 2.3.0 新版本 - 安全修复，可调的黑名单，DTG API" href="http://i2p-projekt.i2p/en/blog/post/2023/06/25/new_release_2.3.0" author="idk" published="2023-06-25T12:00:00Z" updated="2023-06-25T12:00:00Z"><details><summary>I2P 2.3.0 - 安全修复，可调的黑名单，DTG API</summary></details><p>此版本包含 CVE-2023-36325 的修复。
+CVE-2023-36325 是一个发生在布隆过滤器中的上下文混淆错误。
+攻击者制作包含唯一 messageID 的 I2NP 消息，并将该 messageID 发送给客户端。
+该消息在通过布隆过滤器后，不允许在第二条消息中重复使用。
+随后，攻击者将相同的消息直接发送给路由。
+路由器将消息传递给布隆过滤器并被丢弃。
+这泄露了之前已经看到的 messageID 信息，使攻击者有充分的理由相信路由器承载了客户端。
+这个问题已经通过将布隆过滤器的功能分离到不同的上下文中得到了解决，这些上下文中是基于消息是通过客户端隧道，还是探测隧道直接发送到路由的。
+在正常情况下，这种攻击需要数天才能成功执行，并且可能受到攻击期间路由重启和对误报的灵敏度等若干因素的干扰。
+建议使用 Java I2P 的用户立即更新以免受攻击。</p>
+<p>在修复这个上下文混淆错误的过程中，我们修改了一些策略来防御这类型的泄漏。
+这包括对 netDb 的调整、速率限制机制和洪泛路由的行为。</p>
+<p>此版本添加了 not_bob 作为第二个默认hosts来源，并把<a href="http://notbob.i2p">notbob.i2p</a>和<a href="http://ramble.i2p">ramble.i2p</a>添加到控制台主页。</p>
+<p>这个版本还包含一个可调整的黑名单。
+黑名单是半永久性的，每个被封禁的IP地址会被一直屏蔽，直到路由器重新启动。
+在 sybil 攻击期间观察到黑名单爆炸性增长的用户可以通过将黑名单配置为按一定时间间隔使条目过期来选择更短的超时时间。
+此功能在默认情况下是关闭的，目前仅建议高级用户使用。</p>
+<p>该版本还包括一个API，用于使用桌面GUI(DTG)修改插件。
+现在可以将菜单项添加到系统托盘中，从而更直观地启动使用本地应用程序接口的插件。</p>
+<p>如往常一样，我们建议您升级到这个版本。
+维护安全并帮助网络的最佳方式就是运行最新版本。</p>
+</article><article id="urn:uuid:d960054d-6e03-4638-b808-cd3dadae40d5" title="新发布 2.2.1，包含Docker，Ubuntu Lunar和Debian Sid的打包修复" href="http://i2p-projekt.i2p/en/blog/post/2023/4/12/new_release_2.2.1" author="idk" published="2023-04-12T03:00:00Z" updated="2023-04-12T03:00:00Z"><details><summary>I2P 2.2.1 - 2.2.0 的维护修复</summary></details><p>I2P 2.2.0 版本向前推进以加快缓解 DDOS 攻击后，我们了解到一些开发问题，因此有必要构建和发布新包。
+此发布修复了 Ubuntu Lunar 和 Debian Sid 中的一个问题，即使用更新后的版本的 jakarta 包无法访问路由器控制台。
+Docker 包未正确读取参数，导致无法访问配置文件。
+此问题也已解决。
+docker 容器现在也与 Podman 兼容。</p>
+<p>本发布与 transifex 同步翻译并更新 GeoIP 数据库。</p>
+<p>如往常一样，我们建议您升级到这个版本。
+维护安全并帮助网络的最佳方式就是运行最新版本。</p>
+</article><article id="urn:uuid:3b44ff84-d820-4976-bb4a-9c6e4dd3e362" title="新版本 2.2.0，包含DDOS攻击的缓解措施和流传输子系统的调整" href="http://i2p-projekt.i2p/en/blog/post/2023/3/13/new_release_2.2.0" author="idk" published="2023-03-13T17:00:00Z" updated="2023-03-13T17:00:00Z"><details><summary>DDOS攻击的缓解措施和流传输子系统的调整</summary></details><p>我们已选择将 2.2.0 的发布日期提前到今天，即 2023 年 3 月 13 日。
+此版本包括对网络数据库、洪泛和节点选择组件的修改，提高了路由器抵御 DDOS 攻击的能力。
+攻击可能会持续进行，但对这些系统的改进将通过帮助路由识别和降低路由评分来帮助减轻 DDOS 攻击的风险。</p>
+<p>此版本还为 Streaming 子系统添加了重放保护，以防止可以捕获加密数据包的攻击者通过将其发送给意外的接收者来重新使用它。
+这是一个向后兼容的更改，因此旧路由器仍然能够使用新路由器的流媒体功能。
+此问题由 I2P 开发团队在内部发现并修复，与 DDOS 攻击无关。
+我们从未在实际环境遇到过重放流数据包，并且不相信此时针对 I2P 网络发生过流式重放攻击。</p>
+<p>您可能已经注意到，这些发行说明和发行版本身已由 idk 而非 zzz 签署。
+zzz 已选择退出该项目，他的职责由其他团队成员承担。
+因此，该项目正致力于更换网络统计基础设施并将开发论坛移至 i2pforum.i2p。
+我们感谢 zzz 长期以来提供这些服务。</p>
+<p>如往常一样，我们建议您升级到这个版本。
+维护安全并帮助网络的最佳方式就是运行最新版本。</p>
+</article><article id="urn:uuid:1a4d272b-8f28-4bb0-bab7-59953c1013f7" title="DDoS 消息进展" href="http://zzz.i2p/topics/3593" author="zzz" published="2023-02-14T19:00:00Z" updated="2023-02-14T19:00:00Z"><details><summary>DDoS 消息进展</summary></details><p>我们已经确认攻击者控制了大量的路由器。
+我们的调查和缓解措施仍在继续。</p>
+<p>这是提醒人们即使在 20 年后，I2P 网络规模仍然相对较小的好时候。
+我们没有证据表明攻击者正试图对任何特定用户或隐藏服务进行去匿名化。
+但是，如果您有高风险威胁模型，您应该仔细考虑 I2P 目前是否提供了您需要的保护。
+从长远来看，最好的解决方案是宣传并发展 I2P 网络以提高我们用户的安全性。</p>
+<p>我们将在有必要时在新闻推送和<a href="http://zzz.i2p">zzz.i2p</a>提供更多信息。
+在我们努力改进 I2P 的过程中，请您耐心等待。</p>
+</article><article id="urn:uuid:6558c015-7767-45f1-b80a-07def923a88d" title="关于最近的拒绝服务攻击" href="http://i2p-projekt.i2p/en/blog/post/2023/2/9/about_the_recent_denial_of_service_attacks" author="sadie,idk" published="2023-02-09T23:00:00Z" updated="2023-02-09T23:00:00Z"><details><summary>I2P 保持完好，但性能受损</summary></details><p>I2P 网络目前正受到拒绝服务攻击的影响。
+网络的洪泛功能受到影响，导致响应中断，隧道构建成功率下降。
+网络参与者在连接到 I2P 站点和使用 I2P 服务时遇到困难。
+我们在正在逐步调查和实施缓解策略。</p>
+<p>虽然攻击降低了性能，但网络仍然完好无损且可用。
+目前，Java I2P 路由器似乎比 i2pd 路由器能更好地处理这些问题。
+下周，各种缓解措施应该会开始出现在 Java 和 C++ 路由器的开发版本中。</p>
+</article><article id="urn:uuid:68f9a58c-de7f-493e-8cb7-c0ceeda78007" title="2.1.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2023/01/09/2.1.0-Release" author="zzz" published="2023-01-09T12:00:00Z" updated="2023-01-09T12:00:00Z"><details><summary>2.1.0 包含大量 SSU2 修复</summary></details><p>自 11 月发布 2.0.0 以来，我们获知了一些情况。
+随着路由器更新到该版本，网络对我们新的 SSU2 传输协议的支持率从大约 1% 提高到 60% 以上。
+首先，我们已经确认 SSU2 是一个可靠、设计良好且安全的协议。
+其次，我们发现并修复了协议推行中的许多小错误或很少触发的错误。
+这些累积错误的影响降低了网络的性能。</p>
+<p>此外，我们还注意到网络中隧道数量的增加和隧道构建成功率的下降，
+可能是由比特币新的 I2P 临时地址功能触发的，
+但由于我们的 SSU2 错误和其他拥塞控制问题而变得更差。
+我们正在与比特币和其他非比特币项目合作，以减少 I2P 网络需求。
+我们改进了算法以减少拥塞期间的网络负载。
+我们还与 i2pd 合作开发通用的拥塞控制策略。</p>
+<p>因此，我们将此版本的发布时间加快了大约六周，以便向所有人发布修复程序。
+i2pd 上周发布了他们的 2.45.0 版，早期的结果令人鼓舞。
+新协议和分布式网络很难开发。
+拥堵可能会在没有任何警告和原因的情况下出现。
+感谢您的耐心等待，因为我们已经诊断并希望解决问题。</p>
+<p>一如往常一般，我們建議您更新到這個版本，要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
+</article><article id="urn:uuid:adf95235-a183-4870-b5fa-99752e3657d2" title="2.0.0 发布" href="http://i2p-projekt.i2p/en/blog/post/2022/11/21/2.0.0-Release" author="zzz" published="2022-11-21T12:00:00Z" updated="2022-11-21T12:00:00Z"><details><summary>SSU2 已启用</summary></details><p>I2P 2.0.0版本在完成了小特性开发、测试和若干错误修复以后为所有用户启用了我们新的SSU2 UDP传输。</p>
 <p>我们也修复了所有部分，包括安装包、网络数据库、私有地址簿添加，Windows浏览器启动程序，和IPv6 UPnP。</p>
 <p>一如往常一般，我們建議您更新到這個版本，要確保安全性以及協助貢獻此互連網路的最好方式就是保持使用最新的版本。</p>
 </article><article id="urn:uuid:65da828c-43de-49a4-98e7-b8bfeed8d341" title="最近的部落格文章" href="http://i2p-projekt.i2p/en/blog/" author="zzz" published="2022-10-12T12:00:00Z" updated="2022-10-12T12:00:00Z"><details><summary>最近的博客文章</summary></details><p>这是我们网站部分最近的博客文章的链接：</p>

data/win/beta/entries.html

@@ -1,5 +1,352 @@
 <div>
     <header title="I2P News">News feed, and router updates</header>
+<article
+  id="urn:uuid:1d530419-42fd-4ab6-979c-644872a2a8b9"
+  title="I2P Easy-Install 2.9.0"
+  href="http://i2p-projekt.i2p/en/blog/post/2025/06/07/i2p_easy-install_2.9.0_release"
+  author="idk"
+  published="2025-06-07T17:00:00Z"
+  updated="2025-06-07T17:00:00Z">
+<details>
+<summary>I2P Easy-Install 2.9.0</summary>
+</details>
+<p>
+This release updates the embedded I2P router to I2P 2.9.0.
+It also updates the embedded I2P Firefox profile to 2.9.0.
+</p>
+</article>
+
+
+
+<article
+  id="urn:uuid:598e5703-364e-4806-9083-d1bdfc430d2e"
+  title="I2P Easy-Install 2.8.2"
+  href="http://i2p-projekt.i2p/en/blog/post/2025/03/29/2.8.2-Release"
+  author="idk"
+  published="2025-04-02T14:00:00Z"
+  updated="2025-04-02T14:00:00Z">
+<details>
+<summary>I2P Easy-Install 2.8.2</summary>
+</details>
+<p>
+This release updates the embedded I2P router to I2P 2.8.2.
+It also updates the embedded I2P Firefox profile to 2.8.2.
+Due to the point release of I2P, 2.8.2 has become the final release to support Chrome and Chromium browsers due to the adoption of ManifestV3.
+Previously, this had been announced as 2.8.1.
+</p>
+</article>
+
+
+
+<article
+  id="urn:uuid:dc6880db-d329-4693-9c1c-ed02fa361864"
+  title="I2P Easy-Install 2.8.1"
+  href="http://i2p-projekt.i2p/en/blog/post/2025/03/17/2.8.1-Release"
+  author="idk"
+  published="2025-03-21T13:00:00Z"
+  updated="2025-03-21T13:00:00Z">
+<details>
+<summary>I2P Easy-Install 2.8.1</summary>
+</details>
+<p>
+This release updates the embedded I2P router to I2P 2.8.1.
+It also updates the embedded I2P Firefox profile to 2.8.1.
+Chrome extension configuration has been removed from the profile manager.
+Chrome-specific proxy management has been retained for now.
+This will be the final release to support Chrome and Chromium browsers due to the adoption of ManifestV3.
+</p>
+</article>
+
+
+
+<article
+  id="urn:uuid:1d9a0eaf-148c-4c97-9c27-f8f15be29ef6"
+  title="Easy-Install for Windows Release 2.8.0"
+  href="http://i2p-projekt.i2p/en/blog/post/2025/02/03/i2p_2.8.0_release"
+  author="idk"
+  published="2024-10-12T16:00:00Z"
+  updated="2024-10-12T16:00:00Z">
+<details>
+<summary>I2P Easy-Install 2.8.0</summary>
+</details>
+<p>
+This release updates the embedded I2P router to I2P 2.8.0.
+It also updates the embedded I2P Firefox profile to 2.8.0.
+</p>
+</article>
+
+<div>
+    <header title="I2P News">News feed, and router updates</header>
+<article
+  id="urn:uuid:1d9a0eaf-148c-4c97-9c27-f8f15be29ef6"
+  title="Easy-Install for Windows Release 2.7.0"
+  href="http://i2p-projekt.i2p/en/blog/post/2024/10/08/i2p_2.7.0_release"
+  author="idk"
+  published="2024-10-20T16:00:00Z"
+  updated="2024-10-20T16:00:00Z">
+<details>
+<summary>I2P Easy-Install 2.7.0</summary>
+</details>
+<p>
+This release updates the embedded I2P router to I2P 2.7.0.
+It also updates the embedded I2P Firefox profile to 2.7.0.
+</p>
+</article>
+
+
+
+<article
+  id="urn:uuid:eda5b6e0-8d11-4410-9088-f892e9ea4d5f"
+  title="Easy-Install for Windows Release 2.6.1"
+  href="http://i2p-projekt.i2p/en/blog/post/2024/08/26/easy-install_for_windows_release_2.6.1"
+  author="idk"
+  published="2024-08-26T18:00:00Z"
+  updated="2024-08-26T18:00:00Z">
+<details>
+<summary>I2P Easy-Install 2.6.1</summary>
+</details>
+<p>
+This release updates the embedded I2P router to I2P 2.6.1.
+It also updates the embedded I2P Firefox profile to 2.6.2.
+</p>
+</article>
+
+
+
+<article
+  id="urn:uuid:a58ced07-3a33-4294-9bb5-e344feb84754"
+  title="Easy-Install for Windows Release 2.6.0"
+  href="http://i2p-projekt.i2p/en/blog/post/2024/07/20/easy-install_for_windows_release_2.6.0"
+  author="idk"
+  published="2024-07-20T23:00:00Z"
+  updated="2024-07-20T23:00:00Z">
+<details>
+<summary>I2P Easy-Install 2.6.0</summary>
+</details>
+<p>
+This release of the I2P Easy-Install bundle updates the embedded I2P router to I2P 2.6.0.
+It also includes an updated I2P Firefox Profile, an updated version of I2P in Private Browsing, and updated browser plugins.
+Discovery of browser configuration has been improved on some platforms.
+</p>
+</article>
+
+
+
+<article
+  id="urn:uuid:0a728047-f126-4ce2-91a1-c09dd11a9a8b"
+  title="Easy-Install for Windows Release 2.5.2"
+  href="http://i2p-projekt.i2p/en/blog/post/2024/05/15/2.5.2-Release"
+  author="idk"
+  published="2024-05-15T23:00:00Z"
+  updated="2024-05-15T23:00:00Z">
+<details>
+<summary>2.5.2 with HTTP fix</summary>
+</details>
+<p>
+I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.
+</p>
+<p>
+As usual, we recommend that you update to this release.
+The best way to maintain security and help the network is to run the latest release.
+</p>
+</article>
+
+
+
+<article
+  id="urn:uuid:bf83d82a-0849-474f-b883-73cf8e779bde"
+  title="Easy-Install for Windows Release 2.5.0"
+  href="http://i2p-projekt.i2p/en/blog/post/2024/4/8/easy-install_for_windows_release_2.5.0"
+  author="idk"
+  published="2024-04-08T22:00:00Z"
+  updated="2024-04-08T22:00:00Z">
+<details>
+<summary>I2P Easy-Install Bundle for Windows 2.5.0</summary>
+</details>
+<p>
+This latest release of the I2P Easy-Install Bundle for Windows revises the packaging of the bundle to be self-contained and portable.
+The profile manager is moved to an I2P plugin and un-bundled from the router launcher itself, enabling it to be updated without a router update or even a router restart.
+Many of these changes were previewed in the recent pre-releases.
+During testing we chose to disable Chromium-wrapping capabilities, meaning the bundle still depends on an existing Firefox installation.
+The profile manager has also been integrated with the desktop UI.
+</p>
+</article>
+
+
+
+<article
+  id="urn:uuid:94cffa29-35bd-41d6-adc8-f5cb407f8012"
+  title="Easy-Install for Windows Release 2.4.9"
+  href="http://i2p-projekt.i2p/en/blog/post/2024/3/20/easy-install_for_windows_release_2.4.9"
+  author="idk"
+  published="2024-03-20T15:00:00Z"
+  updated="2024-03-20T15:00:00Z">
+<details>
+<summary>I2P Easy-Install Bundle for Windows 2.4.9</summary>
+</details>
+<p>
+    <p>This is a pre-release of the I2P Easy-Install Bundle for Windows.
+        This changes how the I2P bundle and browser profile manager are installed and integrated with the host system.
+        The Easy-Install bundle is now a "portable" system that can be moved to different locations within or between Windows file-systems while retaining all built-in functionality.
+        A shortcut for starting the I2P router is still provided by the installer for convenience, but the shortcuts for starting the I2P Browser are now integrated with the I2P desktop UI.</p>
+        
+        <p>The browser profile manager itself has been split away from the monolithic I2P router+Java/jpackage, and moved into an I2P plugin managed by the router.
+        While this was done primarily to reduce how complex the existing code was, this also results in behavior which is closer to the main distribution of I2P for Windows and will lead to a more flexible installer, which can bundle additional default plugins and may be suitable for installation as a Windows service.
+        I2P Plugins can also be updated independently of the router that hosts them, so it will be possible to update the browser profile manager independently of the router itself.
+        It also means that the browser profile manager can be un-installed by uninstalling the plugin, and much more importantly that the browser profile manager is now compatible with all Java I2P distributions.</p>
+        
+        <p><strong>Why a dev build 3 weeks before the release?</strong></p>
+        
+        <p>By further delineating the components of the bundle, these changes also affected how the release process happens.
+        In particular the build process of each component has been encapsulated in a CI description which can be reproduced on a local PC.
+        This simplifies and automates the build process by ensuring that up-to-date build tools are installed in a brand-new container for every build.
+        In effect this should speed up the release process for I2P Easy-Install for Windows considerably.
+        This release is a test-run of the new process, so I can document what is going on.
+        It breaks down roughly like this:</p>
+        
+        <ul>
+        <li>It takes ~22 minutes to compile all the targets for the <code>i2p.plugins.firefox</code> and make the resulting artifacts available. During this process, I must insert 1 HSM and enter 1 password. (This part used to be about 30 steps, now it takes 1)</li>
+        <li>It takes ~22 minutes to compile all the targets for the <code>i2p.firefox</code> project and make the resulting artifacts available. This process produces only unsigned artifacts identified by their hashes, and is non-interactive. (This part used to be around 60 steps the first time, and 40 steps each additional time)</li>
+        <li><code>i2p.firefox</code> updates are signed in their <code>.su3</code> form. The <code>NSIS</code>-powered <code>.exe</code> installer is the current updater. The next step is to sign <em>just this installer</em> and generate a torrent of the result. (This process used to depend on the previous build process and couldn't be done independently. Now it takes about 30 seconds)</li>
+        <li>Generate and sign a newsfeed to notify the users of an update. This process is the only process that is <strong>slower</strong> when containerized, because there are dozens of feeds to be signed in their respective containers. It takes about an hour.</li>
+        </ul>
+        
+        <p>For you the end user, nothing much should change.
+        You'll get your updates a lot faster, and have more options available for testing.
+        The same installer is used for the updater, and the process is handled the same way.
+        However for developers, testers, and maintainers, this release will result in big changes for the better.</p>
+        
+        <p>This release still embeds a <code>2.4.0</code> Java I2P router. No changes have been made to update the embedded router.
+        Network behavior will be unchanged until the official <code>2.5.0</code> release.</p>
+        
+</p>
+</article>
+
+
+
+<article
+  id="urn:uuid:dba13cd7-443c-450d-a888-3ad8880f8a2d"
+  title="Easy-Install for Windows Release 2.3.0"
+  href="http://i2p-projekt.i2p/en/blog/post/2023/7/10/easy-install_for_windows_release_2.3.0"
+  author="idk"
+  published="2023-07-10T23:00:00Z"
+  updated="2023-07-10T23:00:00Z">
+<details>
+<summary>I2P Easy-Install for Windows 2.3.0 Release</summary>
+</details>
+<p>
+    The I2P Easy-Install bundle for Windows version 2.3.0 has now been released.
+    As usual, this release includes an updated version of the I2P router.
+    This extends to security issues which affect people hosting services on the network.
+</p>
+<p>
+    This will be the last release of the Easy-Install bundle which will be incompatible with the I2P Desktop GUI.
+    It has been updated to include new versions of all included webextensions.
+    A longstanding bug in I2P in Private Browsing which makes it incompatible with custom themes has been fixed.
+    Users are still advised to *not* install custom themes.
+    Snark tabs are not automatically pinned to the top of the tab order in Firefox.
+    Except for using alternate cookieStores, Snark tabs now behave as normal browser tabs.
+</p>
+<p>
+    <b>Unfortunately, this release is still an unsigned <code>.exe</code> installer.</b>
+    Please verify the checksum of the installer before using it.
+    <b>The updates, on the other hand</b> are signed by my I2P signing keys and therefore safe.
+</p>
+<p>
+    This release was compiled with OpenJDK 20.
+    It uses i2p.plugins.firefox version 1.1.0 as a library for launching the browser.
+    It uses i2p.i2p version 2.3.0 as an I2P router, and to provide applications.
+    As always it is recommended that you update to the latest version of the I2P router at your earliest convenient opportunity.
+</p>
+<ul>
+    <li><a href="http://git.idk.i2p/i2p-hackers/i2p.firefox/-/tree/i2p-firefox-2.3.0">Easy-Install Bundle Source</a></li>
+    <li><a href="http://git.idk.i2p/i2p-hackers/i2p.i2p/-/tree/i2p-2.3.0">Router Source</a></li>
+    <li><a href="http://git.idk.i2p/i2p-hackers/i2p.plugins.firefox/-/tree/1.1.0">Profile Manager Source</a></li>
+</ul>
+</article>
+
+
+
+<article
+  id="urn:uuid:dd6a31af-009b-4eed-be23-041f8440a641"
+  title="I2P Easy-Install 2.2.0 for Windows release"
+  href="http://i2p-projekt.i2p/en/blog/post/2023/3/20/i2p_easy-install_2.2.0_for_windows_release"
+  author="idk"
+  published="2023-03-20T18:00:00Z"
+  updated="2023-03-20T18:00:00Z">
+<details>
+<summary>SUMMARY_HERE</summary>
+</details>
+<p>
+    The I2P Easy-Install bundle for Windows version 2.2.0 has been released.
+    As usual, this release includes an updated version of the I2P Router.
+    This release of I2P provides improved strategies for dealing with network congestion.
+    These should improve performance, connectivity, and secure the long-term health of the I2P network.
+    It also includes several minor bugfixes and stability improvements when managing the router updates.
+    It is now better at co-existing with other I2P routers on the same device.
+</p>
+<p>
+    <b>Unfortunately, this release is still an unsigned <code>.exe</code> installer.</b>
+    Please verify the checksum of the installer before using it.
+    <b>The updates, on the other hand</b> are signed by my I2P signing keys and therefore safe.
+</p>
+<p>
+    This release was compiled with OpenJDK 19.
+    It uses i2p.plugins.firefox version 1.0.9 as a library for launching the browser.
+    It uses i2p.i2p version 2.2.0 as an I2P router, and to provide applications.
+    As always it is recommended that you update to the latest version of the I2P router at your earliest convenient opportunity.
+</p>
+<ul>
+    <li><a href="http://git.idk.i2p/i2p-hackers/i2p.firefox/-/tree/i2p-firefox-2.2.0">Easy-Install Bundle Source</a></li>
+    <li><a href="http://git.idk.i2p/i2p-hackers/i2p.i2p/-/tree/i2p-2.2.0">Router Source</a></li>
+    <li><a href="http://git.idk.i2p/i2p-hackers/i2p.plugins.firefox/-/tree/1.0.9">Profile Manager Source</a></li>
+</ul>
+</article>
+
+
+
+<article
+  id="urn:uuid:0e16492e-a30d-4cbc-80bf-503b3837e283"
+  title="I2P Easy Install for Windows 2.1.0"
+  href="http://i2p-projekt.i2p/en/blog/post/2023/01/13/i2p_easy_install_for_windows_2.1.0"
+  author="idk"
+  published="2023-01-13T01:00:00Z"
+  updated="2023-01-13T01:00:00Z">
+<details>
+<summary>Windows Easy-Install Bundle 2.1.0 released to improve stability, performance.</summary>
+</details>
+<p>
+    The I2P Easy-Install bundle for Windows version 2.1.0 has been released.
+    As usual, this release includes an updated version of the I2P Router.
+    This release of I2P provides improved strategies for dealing with network congestion.
+    These should improve performance, connectivity, and secure the long-term health of the I2P network.
+</p>
+<p>
+    This release features mostly under-the-hood improvements to the browser profile launcher.
+    Compatibility with Tor Browser Bundle has been improved by enabling TBB configuration through environment variables.
+    The Firefox profile has been updated, an the base versions of the extensions have been updated.
+    Improvements have been made throughout the codebase and the deployment process.
+</p>
+<p>
+    <b>Unfortunately, this release is still an unsigned <code>.exe</code> installer.</b>
+    Please verify the checksum of the installer before using it.
+    <b>The updates, on the other hand</b> are signed by my I2P signing keys and therefore safe.
+</p>
+<p>
+    This release was compiled with OpenJDK 19.
+    It uses i2p.plugins.firefox version 1.0.7 as a library for launching the browser.
+    It uses i2p.i2p version 2.1.0 as an I2P router, and to provide applications.
+    As always it is recommended that you update to the latest version of the I2P router at your earliest convenient opportunity.
+</p>
+<ul>
+    <li><a href="http://git.idk.i2p/i2p-hackers/i2p.firefox/-/tree/i2p-firefox-2.1.0">Easy-Install Bundle Source</a></li>
+    <li><a href="http://git.idk.i2p/i2p-hackers/i2p.i2p/-/tree/i2p-2.1.0">Router Source</a></li>
+    <li><a href="http://git.idk.i2p/i2p-hackers/i2p.plugins.firefox/-/tree/1.0.7">Profile Manager Source</a></li>
+</ul>
+</article>
+
+
+
 <article
   id="urn:uuid:df1ead45-ee60-410b-a776-0c608116ee30"
   title="I2P Easy-Install for Windows 2.0.0 Update, Unsigned EXE"
@@ -8,25 +355,20 @@
   published="2022-11-23T01:00:00Z"
   updated="2022-11-23T01:00:00Z">
 <details>
-<summary>
-    <p>
-The I2P Easy-Install bundle for Windows has been released.
-In this release, support has been added for most major browsers, including all major Firefox(Gecko) and Chromium forks.
-Compatibility with external I2P Service installs and un-bundled I2P user installs has been improved.
-The Easy-Install bundle can now detect other I2P routers and prompt the user to launch them instead, if they already have I2P.
-The browser extensions have been updated to the latest versions.
-The Easy-Install now has access to `i2p.plugins.firefox`'s usability mode via the `-usability` command-line flag.
-The default mode is the "Strict" mode where Javascript is disabled by NoScript.
-In usability mode, Javascript is restricted by JShelter.
-For more details, see the profile manager repository at i2pgit.org.
-    </p>
-    <p>
-It is recommended that you update to this release for the best security, privacy, and performance, and to help the network.
-    </p>
-</summary>
+<summary>The I2P Easy-Install bundle for Windows has been released.</summary>
 </details>
 <p>
-
+    In this release, support has been added for most major browsers, including all major Firefox(Gecko) and Chromium forks.
+    Compatibility with external I2P Service installs and un-bundled I2P user installs has been improved.
+    The Easy-Install bundle can now detect other I2P routers and prompt the user to launch them instead, if they already have I2P.
+    The browser extensions have been updated to the latest versions.
+    The Easy-Install now has access to `i2p.plugins.firefox`'s usability mode via the `-usability` command-line flag.
+    The default mode is the "Strict" mode where Javascript is disabled by NoScript.
+    In usability mode, Javascript is restricted by JShelter.
+    For more details, see the profile manager repository at i2pgit.org.
+</p>
+<p>
+    It is recommended that you update to this release for the best security, privacy, and performance, and to help the network.
 </p>
 </article>
 

data/win/beta/releases.json

@@ -1,12 +1,12 @@
 [
   {
-    "date": "2022-11-23",
-    "version": "2.0.0",
+    "date": "2025-04-02",
+    "version": "2.9.0",
     "minVersion": "1.5.0",
     "minJavaVersion": "1.8",
     "updates": {
       "su3": {
-        "torrent": "magnet:?xt=urn:btih:6afc1ef251ab0b8462bee137a33d98fc797a4d26&dn=i2pwinupdate.su3&tr=http://tracker2.postman.i2p/announce.php&tr=http://w7tpbzncbcocrqtwwm3nezhnnsw4ozadvi2hmvzdhrqzfxfum7wa.b32.i2p/a&tr=http://mb5ir7klpc2tj6ha3xhmrs3mseqvanauciuoiamx2mmzujvg67uq.b32.i2p/a",
+        "torrent": "magnet:?xt=urn:btih:88bfdbc25eeef113ba3105f9a47eb74734e79396&dn=i2pwinupdate.su3&tr=http%3A%2F%2Ftracker2.postman.i2p%2Fannounce.php",
         "url": [
           "http://ekm3fu6fr5pxudhwjmdiea5dovc3jdi66hjgop4c7z7dfaw7spca.b32.i2p/i2pwinupdate.su3"
         ]

data/win/testing/releases.json

@@ -1,16 +0,0 @@
-[
-  {
-    "date": "2022-02-09",
-    "version": "1.6.1",
-    "minVersion": "1.5.0",
-    "minJavaVersion": "1.8",
-    "updates": {
-      "su3": {
-        "torrent": "magnet:?xt=urn:btih:239e24b612e737ca69bfea29bf539633eb07ba7a&dn=i2pwinupdate.su3&tr=http://tracker2.postman.i2p/announce.php&tr=http://w7tpbzncbcocrqtwwm3nezhnnsw4ozadvi2hmvzdhrqzfxfum7wa.b32.i2p/a&tr=http://mb5ir7klpc2tj6ha3xhmrs3mseqvanauciuoiamx2mmzujvg67uq.b32.i2p/a",
-        "url": [
-          "http://ekm3fu6fr5pxudhwjmdiea5dovc3jdi66hjgop4c7z7dfaw7spca.b32.i2p/i2pwinupdate.su3"
-        ]
-      }
-    }
-  }
-]

etc/project.vars

@@ -1,3 +1,2 @@
 export venv_dir="env"
-export venv="`which virtualenv`" 
-#virtualenv-2.7 || which virtualenv`"
+export venv="`which virtualenv-2.7 || which virtualenv`"

feedgen/ext/i2p.py

@@ -69,7 +69,7 @@ class Release(object):
         if self.__release_min_java_version is not None:
             release.attrib['minJavaVersion'] = self.__release_min_java_version
 
-        for update_type, update in list(self.__release_updates.items()):
+        for update_type, update in self.__release_updates.items():
             update_node = etree.SubElement(release, '{%s}update' % I2P_NS)
             update_node.attrib['type'] = update_type
 
@@ -159,7 +159,7 @@ class Revocations(object):
 
         revocations = etree.Element('{%s}revocations' % I2P_NS)
 
-        for crl_id, crl in list(self.__revocations_crls.items()):
+        for crl_id, crl in self.__revocations_crls.items():
             crl_node = etree.SubElement(revocations, '{%s}crl' % I2P_NS)
             crl_node.attrib['id'] = crl_id
             crl_node.attrib['updated'] = crl.updated().isoformat()

generate_news.py

@@ -35,7 +35,7 @@ def load_entries(fg, entries_file, platform_entries_file=None):
     metadatas = {}
     finalentries = {}
 
-    print(('Loading entries from %s' % entries_file))
+    print('Loading entries from %s' % entries_file)
     entries = prepare_entries_file(fg, entries_file)
     
     # split() creates a junk final element with trailing </div>
@@ -46,7 +46,7 @@ def load_entries(fg, entries_file, platform_entries_file=None):
         finalentries[md['id']] = entry_parts[1]
 
     if os.path.exists(platform_entries_file) and platform_entries_file != entries_file and platform_entries_file is not None and platform_entries_file != "data/entries.html":
-        print(('Loading platform entries from %s' % platform_entries_file))
+        print('Loading platform entries from %s' % platform_entries_file)
         entries = prepare_entries_file(fg, platform_entries_file)
         for entry_str in entries[:-1]:
             entry_parts = entry_str.split('</details>', 1)
@@ -56,7 +56,7 @@ def load_entries(fg, entries_file, platform_entries_file=None):
 
     sorted_metadata = collections.OrderedDict(sorted(metadatas.items()))
 
-    for metadata in list(sorted_metadata.values()):
+    for metadata in sorted_metadata.values():
         fe = fg.add_entry()
         fe.id(metadata['id'])
         fe.title(metadata['title'])
@@ -73,7 +73,7 @@ def prepare_entries_file(fg, entries_file=None):
     with open(entries_file) as f:
         entries_data = f.read().strip('\n')
         # Replace HTML non-breaking space with unicode
-        entries_data = entries_data.replace('&nbsp;', '\\u00a0')
+        entries_data = entries_data.replace('&nbsp;', '\u00a0')
         # Strip the leading <div> from translations
         if entries_data.startswith('<div>'):
             entries_data = entries_data[5:]
@@ -88,7 +88,9 @@ def prepare_entries_file(fg, entries_file=None):
 
 def extract_entry_metadata(s):
     m = {k:v.strip('"') for k,v in re.findall(r'(\S+)=(".*?"|\S+)', s)}
-    m['summary'] = re.findall(r'<summary>(.*)</summary>', s)[0]
+    summary = re.findall(r'<summary>(.*)</summary>', s, re.DOTALL)
+    if len(summary) > 0:
+        m['summary'] = summary[0]
     return m
 
 def load_releases(fg):
@@ -103,7 +105,7 @@ def load_releases(fg):
             if 'minJavaVersion' in release:
                 r.min_java_version(release['minJavaVersion'])
 
-            for update_type, update in list(release['updates'].items()):
+            for update_type, update in release['updates'].items():
                 u = r.add_update(update_type)
                 if 'clearnet' in update:
                     for url in update['clearnet']:

stats.py

@@ -1,259 +0,0 @@
-#
-# -*- coding: utf-8 -*-
-#
-import datetime
-import json
-import logging
-import operator
-import os
-import time
-
-# try importing redis redis
-try:
-    import redis
-except ImportError:
-    print("redis not available, fall back to volatile stats backend")
-    redis = None
-    
-# try importing pygal
-try:
-    import pygal
-except ImportError:
-    print("pygal not available, fall back to text based stats")
-    pygal = None
-pygal =None
-    
-__doc__ = """
-statistics backend optionally using redis
-"""
-
-
-class RedisDB:
-    """
-    redis based backend for storing stats
-    """
-    def __init__(self):
-        self._redis = redis.Redis()
-        self.exists = self._redis.exists
-        self.get = self._redis.get
-        self.set = self._redis.set
-
-class DictDB:
-    """
-    volatile dictionary based database backend for storing stats in memory
-    """
-    def __init__(self):
-        self._d = dict()
-
-    def get(self, k):
-        if self.exists(k):
-            return self._d[k]
-        
-    def set(self, k, v):
-        self._d[k] = v
-
-    def exists(self, k):
-        return k in self._d
-
-    
-class Grapher:
-    """
-    generic grapher that does nothing
-    """
-
-    def collect(self, data_sorted, multiplier, calc_netsize):
-        """
-        do the magic calculations
-        yields (x, netsize_y, rph_y)
-        """
-        total = 0
-        hours = 0
-        req_s = []
-        netsize_s = []
-        window = []
-        for hour, val in data_sorted:
-            years = hour / ( 365 * 24 )
-            days = ( hour - years * 365 * 24 ) / 24
-            hours = hour - ( ( years * 365 * 24 ) + ( days * 24 ) )
-            hour = datetime.datetime.strptime('%0.4d_%0.3d_%0.2d' % (years, days, hours), '%Y_%j_%H')
-            if val > 0:
-                total += val
-                hours += 1
-                per_hour = float(total) / hours
-                window.append(val)
-                while len(window) > window_len:
-                    window.pop(0)
-                mean = sum(window) / len(window)
-                netsize = int(calc_netsize(mean, multiplier))
-                yield (hour, netsize, val)
-                
-    def generate(self, data_sorted, multiplier, calc_netsize):
-        """
-        :param data_sorted: sorted list of (hour, hitcount) tuple
-        :param multiplier: multiplier to use on graph Y axis
-        :param calc_netsize: function that calculates the network size given a mean value and multiplier
-        :return (netsize, requests) graph tuple:
-        """
-
-class SVGText:
-    """
-    svg hold text
-    """
-    def __init__(self, data='undefined'):
-        self.data = data
-    
-    def render(self):
-        return """<?xml version="1.0" standalone="no"?>
-<svg viewBox="0 0 80 40" xmlns="http://www.w3.org/2000/svg">
-    <desc>fallback svg</desc>
-    <rect x="0" y="0" width="80" height="40" stroke="red" fill="None">
-    </rect>
-    <text x="30" y="20">{}</text>
-</svg>
-        """.format(self.data)
-    
-class TextGrapher(Grapher):
-    """
-    generates svg manually that look like ass
-    """
-
-    def generate(self, data_sorted, multiplier, calc_netsize):
-        nsize = 0
-        rph = 0
-        t = 0
-        for hour, netsize, reqs in self.collect(data_sorted, multiplier, calc_netsize):
-            t += 1
-            nsize += netsize
-            rpy += reqs
-        if t:
-            nsize /= t
-            rph /= t
-        return SVGText("MEAN NETSIZE: {} routers".format(nsize)), SVGText("MEAN REQUETS: {} req/hour".format(rph))
-        
-class PygalGrapher(Grapher):
-    """
-    generates svg graphs using pygal
-    """
-    
-    def generate(self, data_sorted, multiplier, calc_netsize):
-
-        _netsize_graph = pygal.DateY(show_dots=False,x_label_rotation=20)
-        _requests_graph = pygal.DateY(show_dots=False,x_label_rotation=20)
-        
-        _netsize_graph.title = 'Est. Network Size (multiplier: %d)' % multiplier
-        _requests_graph.title = 'Requests Per Hour'
-
-        netsize_s, req_s = list(), list()
-        for hour, netsize, reqs in self.collect(data_sorted, multiplier, calc_netsize):
-            netsize_s.append((hour, netsize))
-            req_s.append((hour, reqs))
-            
-        _netsize_graph.add('Routers', netsize_s)
-        _requests_graph.add('news.xml Requests', req_s)
-        return _netsize_graph, _requests_graph
-
-        
-class StatsEngine:
-    """
-    Stats engine for news.xml
-    """
-
-    _log = logging.getLogger('StatsEngine')
-
-    def __init__(self):
-        self._cfg_fname = 'settings.json'
-        if redis:
-            self._db = RedisDB()
-            try:
-                self._db.exists('nothing')
-            except:
-                self._log.warn("failed to connect to redis, falling back to volatile stats backend")
-                self._db = DictDB()
-        else:
-            self._db = DictDB()
-        if pygal:
-            self._graphs = PygalGrapher()
-        else:
-            self._graphs = TextGrapher()
-        
-        self._last_hour = self.get_hour()
-        
-    def _config_str(self, name):
-        with open(self._cfg_fname) as f:
-            return str(json.load(f)[name])
-        
-    def _config_int(self, name):
-        with open(self._cfg_fname) as f:
-            return int(json.load(f)[name])
-
-    def multiplier(self):
-        return self._config_int('mult')	
-
-    def tslice(self):
-        return self._config_int('slice')
-
-    def window_len(self):
-        return self._config_int('winlen')
-
-    @staticmethod
-    def get_hour():
-        """
-        get the current our as an int
-        """
-        dt = datetime.datetime.utcnow()
-        return dt.hour + (int(dt.strftime('%j')) * 24 ) + ( dt.year * 24 * 365 )
-
-    def calc_netsize(self, per_hour, mult):
-        return float(per_hour) * 24 / 1.5 * mult
-
-    @staticmethod
-    def _hour_key(hour):
-        return 'newsxml.hit.{}'.format(hour)
-        
-    def hit(self, lang=None):
-        """
-        record a request
-        """
-        hour = self.get_hour()
-        keyname = self._hour_key(hour)
-        if not self._db.exists(keyname):
-            self._db.set(keyname, '0')
-        val = self._db.get(keyname)
-        self._db.set(keyname, str(int(val) + 1))
-        
-    def _load_data(self, hours):
-        """
-        load hit data 
-        """
-        hour = self.get_hour() 
-        data = list()
-        while hours > 0:
-            keyname = self._hour_key(hour)
-            val = self._db.get(keyname)
-            if val:
-                data.append((hour, int(val)))
-            hour -= 1
-            hours -= 1
-        return data
-            
-    def regen_graphs(self, tslice, window_len, mult):
-        data = self._load_data(tslice)
-        data_sorted = sorted(data, key=operator.itemgetter(0))
-        if len(data_sorted) > tslice:
-            data_sorted = data_sorted[-tslice:]
-        self._netsize_graph, self._requests_graph = self._graphs.generate(data_sorted, self.multiplier(), self.calc_netsize)
-        
-
-
-    def netsize(self, tslice, window, mult):
-        #if not hasattr(self,'_netsize_graph'):
-        self.regen_graphs(tslice, window, mult)
-        return self._netsize_graph.render()
-
-    def requests(self, tslice, window, mult):
-        #if not hasattr(self,'_requests_graph'):
-        self.regen_graphs(tslice, window, mult)
-        return self._requests_graph.render()
-
-
-engine = StatsEngine()

test.sh

@@ -0,0 +1,14 @@
+#! /usr/bin/env sh
+# This script is used to download and extract the latest news from I2P
+# and display it on a terminal. I use it to test when I check in the news.
+i2p() {
+    java -jar ~/i2p/lib/i2p.jar "$@"
+}
+
+if [ ! -f news.su3 ]; then
+    echo "Downloading news.su3..."
+    eepget http://tc73n4kivdroccekirco7rhgxdg5f3cjvbaapabupeyzrqwv5guq.b32.i2p/news.su3
+fi
+i2p su3file extract -x news.su3
+gunzip news.xml.gz
+less news.xml 

validate_html.sh

@@ -0,0 +1,10 @@
+#
+# check that all the html files are valid xml
+# sudo apt install libxml2-utils
+# no output = pass
+# zzz 1/23
+#
+for i in `find -name *.html`
+do
+	xmllint $i > /dev/null || echo "FAIL $i"
+done