Design new caps to be resilient against human transcription errors. #1850

New Issue

nejucomo · 2012-11-09T05:38:50Z

nejucomo commented

2012-11-09 05:38:50 +00:00

One important aspect of this ticket is to define the use cases that should be covered, for example reading over a phone or writing down on paper.

I suggest important use cases are:

cut'n'paste errors, such as:
dropping characters off the front or end
including characters outside the cap, especially whitespace
link-generation-software parsing:
For example a blog may make a link for "http://example.com?foo:bar:quz" which drops ":bar:quz"

One suggested solution is internal checksums.

One important aspect of this ticket is to define the use cases that should be covered, for example reading over a phone or writing down on paper. I suggest important use cases are: * cut'n'paste errors, such as: * dropping characters off the front or end * including characters outside the cap, especially whitespace * link-generation-software parsing: * For example a blog may make a link for "<http://example.com?foo:bar:quz>" which drops ":bar:quz" One suggested solution is internal checksums.

nejucomo added the

labels 2012-11-09 05:38:50 +00:00

nejucomo added this to the undecided milestone 2012-11-09 05:38:50 +00:00

nejucomo commented

2012-11-09 05:40:28 +00:00

Of course I'm biased in my suggestions having made some cut'n'paste errors that lead me to believe my data had been corrupted. ;-)

PRabahy commented

2012-11-09 13:48:58 +00:00

(https://en.bitcoin.it/wiki/Base58Check_encoding) and https://en.bitcoin.it/wiki/Protocol_specification#Addresses have some information on Bitcoin handled this.

(https://en.bitcoin.it/wiki/Base58Check_encoding) and <https://en.bitcoin.it/wiki/Protocol_specification#Addresses> have some information on Bitcoin handled this.

davidsarah commented

2012-11-20 01:29:23 +00:00

This is strictly speaking a design issue for new URLs, rather than new caps.

tahoe-lafs added

code-encoding

and removed

unknown

labels 2012-11-20 01:29:23 +00:00

tahoe-lafs modified the milestone from undecided to 2.0.0

2012-11-20 01:29:23 +00:00

meejah commented

2021-03-30 18:40:46 +00:00