I2P Address: [http://git.idk.i2p]

Skip to content
Snippets Groups Projects
Commit 0aca327b authored by zzz's avatar zzz
Browse files

minor doc fix

parent 0c6c35bd
No related branches found
No related tags found
No related merge requests found
{% 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>
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment