kytv/I2P_Website
1
0
Fork 0
forked from I2P_Developers/i2p.www
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

minor doc fix

Browse Source
This commit is contained in:
zzz
2017-01-19 13:45:15 +00:00
parent 0c6c35bd48
commit 0aca327b70
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
i2p2www/pages/site/docs/applications/bittorrent.html
View File

@@ -1,7 +1,7 @@
{% extends "global/layout.html" %}
{% block title %}{% trans %}Bittorrent over I2P{% endtrans %}{% endblock %}
{% block lastupdated %}{% trans %}May 2014{% endtrans %}{% endblock %}
{% block accuratefor %}0.9.13{% endblock %}
{% block lastupdated %}{% trans %}January 2017{% endtrans %}{% endblock %}
{% block accuratefor %}0.9.28{% endblock %}
{% block content %}
<p>{% trans -%}
@@ -44,8 +44,8 @@ Other parameters are the same as in standard bittorrent.
{%- endtrans %}</p>
<p>{% trans -%}
While all current Destinations for clients are exactly 387 bytes, a tracker should not
presume that will always be so. A reasonable maximum to assume, for now, is 475 bytes.
Current Destinations for clients are 387 or more bytes (516 or more in Base 64 encoding).
A reasonable maximum to assume, for now, is 475 bytes.
As the tracker must decode the Base64 to deliver compact responses (see below),
the tracker should probably decode and reject bad Base64 when announced.
{%- endtrans %}</p>