Lowercase l against I in a nexus market address

This is the dossier for one specific nexus market address trap. A lowercase l is written or read as an uppercase I, or the reverse, and the paste that follows opens something that is not the market at all.

What it is

A nexus market address is a lowercase string. Every character on the visible run before the .onion label is a letter from a to z or a digit from 2 to 7. Uppercase letters are not part of that alphabet, and an uppercase I is not a valid character on any v3 onion. The trap does not need the uppercase I to reach the onion itself. It only needs the uppercase I to sit in a copy that a reader trusts, so that the copy is read out, retyped or shared with the wrong shape kept in place.

The confusion runs both ways. A reader sees a lowercase l on a screen in a proportional font and reads it as capital I from the letters around it. A reader sees an uppercase I in a hand-written note and reads it as lowercase l because the note lives next to a run of lowercase letters. In many fonts the two glyphs are a single upright stroke with no serif, and the eye completes the letter from its neighbours rather than from its own shape.

Where the shape hides

A screenshot of an onion in an article, a slide, a receipt or a support ticket is where the shape hides most often. The font on the article page is proportional, the lowercase l has no lower foot and the uppercase I has no serifs, and the two look the same at the resolution the article prints. A reader who retypes from that screenshot has no way to tell which one the author meant.

Hand-written notes are the second surface. A capital I written in a hurry without serifs is a straight vertical stroke. A lowercase l written without a curl at the top is a straight vertical stroke. The two survive on the page as the same mark, and the reader who wrote it does not always remember which one they meant a few days later.

Lifeline

How to catch it

A monospace font is the fastest catch. In a monospace font the lowercase l has a slight curl or a foot the uppercase I lacks, and the column of pixels for the two letters is not the same shape. Pasting the string into a plain text field set to a monospace font shows the difference straight away. The address bar on tor browser is monospace, which is why a wrong address of this class often reveals itself the moment it lands there and refuses to resolve.

On screen

Copy the string into a monospace field. If the letter changes shape between the source and the paste, the source is the surface that carried the trap.

On paper

Look for a lowercase l sitting among lowercase letters, and a capital I standing on its own. The eye tends to correct a lone letter to match its neighbours.

In a message

The character can be checked by counting. An onion has fifty six characters before the .onion label, all lowercase, and no uppercase letter is allowed.

What this card does not claim

• It does not print a wrong address in full. The shape of the trap is described in words on purpose.
• It does not say which fonts fail worst. Any proportional font without a serif on the capital I fails.
• It does not name a publication that has printed this class of typo.
• It does not treat the trap as more common than any other on this rubric.

What a caught trap teaches

A trap caught on this shape is a small argument for keeping every nexus market address on this site in a monospace font. Every onion on the panel above rides in a monospace face for that reason. The lowercase l on the panel above has a bottom foot the capital I would not have, and a reader who has read this dossier can look up at the panel now and see it.

The tor browser bar as the last reader

The tor browser address bar is the last surface a nexus market address passes through before it opens. The bar is monospace by design, so the same paste that read as ambiguous in a proportional article font resolves into two different columns for the letter l and the letter I once the paste lands in the bar. A reader who has trained the habit of looking at the address bar before pressing return gets a second chance at catching this shape, one column at a time.

A paste that reaches the address bar with an uppercase letter in it refuses to resolve. The refusal is not a warning message the reader might miss. It is a page that simply does not load, and the address bar keeps the paste where the reader can read it. Reading the bar at that point is what turns a failed load into a caught trap rather than a mystery.

A reader who leaves the bar unread and clicks reload a second time is a reader who has not benefited from the refusal. The lesson of this trap is that the bar is a source of information, not a status field. Reading the bar is a habit that pays off on every trap in this rubric, not only on this one.

Engagement

Discover more