Opened 8 years ago

Last modified 6 years ago

#888 new enhancement

accept b32 as well as b64 for hostnames

Reported by: DISABLED Owned by:
Priority: minor Milestone:
Component: apps/addressbook Version: 0.9.4
Keywords: usability error Cc:
Parent Tickets: Sensitive: no


says it all. To save manually looking up the b32.


#1182: Address book should support adding entries by .b32.i2p addressclosedzzz
#1683: allow adding b32 to addressbooknew

Change History (7)

comment:1 Changed 8 years ago by zzz

Milestone: 0.9.5

Not the first time it's been proposed, but I don't think anybody's ever researched how to do it either…

How could we do it?

1) easy way

Just a UI thing. If user enters a b32 in the form, ask the router to resolve it to a full dest (which it can only do if the dest is up). If success, store the full dest. If can't be resolved, fail and tell the user.

2) hard way

Actually store the b32, and defer lookup until the addressbook is queried. This requires API changes, file/database storage enhancements, interchange (hosts.txt) format enhancements, and adds unpredictable multi-second delay to lookups.

Please elaborate on your use case and what solution might meet it.

comment:2 Changed 8 years ago by zzz

One very common use case - person has set up example.i2p. He incorrectly has absolute links or redirects in his eepsite. He hands out the b32 address to people. They view first page, or not even get that far, just a redirect, and hit the host not found page in i2ptunnel.

Another possible solution is:

3) i2ptunnel
Handle it in the i2ptunnel error page somehow, perhaps even with a 'use referring b32 as the dest' button

comment:3 Changed 8 years ago by str4d

Status: newinfoneeded_new

comment:4 Changed 7 years ago by zzz

Add a subticket #1182.

comment:5 Changed 6 years ago by str4d

Keywords: usability error added

comment:6 Changed 6 years ago by zzz

Add a subticket #1683.

comment:7 Changed 6 years ago by zzz

Status: infoneeded_newnew

Note that b32 is allowed in addresshelpers (added to i2ptunnel HTTP client in July 2011, in 0.8.8), but this is not widely used, and may not even be documented.

Note: See TracTickets for help on using tickets.