Opened at 2012-11-09T05:38:50Z
Last modified at 2021-03-30T18:40:46Z
#1850 new defect
Design new caps to be resilient against human transcription errors.
| Reported by: | nejucomo | Owned by: | davidsarah |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | code-encoding | Version: | 1.9.2 |
| Keywords: | newurls usability standards uri | Cc: | |
| Launchpad Bug: |
Description
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.
Change History (5)
comment:1 Changed at 2012-11-09T05:40:28Z by nejucomo
comment:2 Changed at 2012-11-09T13:48:58Z by PRabahy
https://en.bitcoin.it/wiki/Base58Check_encoding and https://en.bitcoin.it/wiki/Protocol_specification#Addresses have some information on Bitcoin handled this.
comment:3 Changed at 2012-11-20T01:29:23Z by davidsarah
- Component changed from unknown to code-encoding
- Keywords newurls added; newcaps removed
- Milestone changed from undecided to 2.0.0
This is strictly speaking a design issue for new URLs, rather than new caps.
comment:4 Changed at 2012-11-20T01:30:07Z by davidsarah
- Keywords usability standards uri added
comment:5 Changed at 2021-03-30T18:40:46Z by meejah
- Milestone 2.0.0 deleted
Ticket retargeted after milestone closed (editing milestones)
Note: See
TracTickets for help on using
tickets.
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. ;-)