tahoe-lafs/trac-2024-07-25

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

New issue

Open

opened 2012-11-09 05:38:50 +00:00 by nejucomo · 4 comments

nejucomo commented

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

Owner

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.

tahoe-lafs added the

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

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

nejucomo commented

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

Author

Owner

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. ;-)

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

Author

Owner

(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

Author

Owner

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

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

tahoe-lafs added

and removed

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

Author

Owner

Ticket retargeted after milestone closed (editing milestones)

Ticket retargeted after milestone closed (editing milestones)

tahoe-lafs removed this from the 2.0.0 milestone 2021-03-30 18:40:46 +00:00

Sign in to join this conversation.

No labels

LeastAuthority.com automation

cannot reproduce

code-frontend-cli

code-frontend-ftp-sftp

code-frontend-magic-folder

code-frontend-web

code-peerselection

dev-infrastructure

somebody else's problem

was already fixed

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#1850

No description provided.