From 3b537524d8ab11e9e989e462d5ff4fdb72ff1150 Mon Sep 17 00:00:00 2001 From: zzz Date: Mon, 26 Apr 2021 11:09:03 -0400 Subject: [PATCH] Update note about i2pd support of b32 addresses in SAM --- i2p2www/pages/site/docs/api/samv3.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/i2p2www/pages/site/docs/api/samv3.html b/i2p2www/pages/site/docs/api/samv3.html index 17477bce..af5f2034 100644 --- a/i2p2www/pages/site/docs/api/samv3.html +++ b/i2p2www/pages/site/docs/api/samv3.html @@ -1,7 +1,7 @@ {% extends "global/layout.html" %} {% block title %}SAM V3{% endblock %} -{% block lastupdated %}2021-03{% endblock %} -{% block accuratefor %}0.9.49{% endblock %} +{% block lastupdated %}2021-04{% endblock %} +{% block accuratefor %}0.9.50{% endblock %} {% block content %}

SAM is a simple client protocol for interacting with I2P. SAM is the recommended protocol for non-Java applications to connect to the I2P network, @@ -671,7 +671,7 @@ depending on signature type. NOTE: Since about 2014 (SAM v3.1), Java I2P has also supported hostnames and b32 addresses for the $destination, but this was previously undocumented. Hostnames and b32 addresses are now officially supported by Java I2P as of release 0.9.48. -The i2pd router does not currently support hostnames and b32 addresses; support may be added in a future release. +The i2pd router has always supported hostnames. I2pd supports b32 addresses as of release 2.38.0 (0.9.50).

Connect Response