WTN Mirror Studies

Study 4 of 8 in Switching

Switching while a message is half typed

A message you have not sent is not in an inbox. It is on a page.

The question

What happens to an unsent message if the route it was being written on is left behind?

The three WTN mirror addresses

  • hn2paw7zfvndw3dovycegeqmvvnf4pl67b3g2p7pohjlzavloosh73id.onion
  • hn2paw7zrgujyhnt6mgxlt2q6uhgbke4itpqitxhyfbumq3wtnckbuyd.onion
  • hn2paw7zadwkcra3qzv5e4q547i7e5lvxm62cfxqftuqdu7moiu2ceyd.onion

Set out flat, in the arrangement they were handed over, with nothing added. Nothing on this page marks one of them as the main one, because on this site that would be the one claim the studies are all arguing against. This reference opens none of them and measures nothing about them.

Why this is the common case

Orders are placed occasionally. Messages get written constantly, often at length, and often while a reader is already half distracted by whatever prompted them to write.

It is also the case where readers are least likely to have thought about it in advance, because a message feels lightweight compared with an order and therefore feels safe.

Where an unsent message lives

On the page, in the box, and nowhere else. It is not a draft, nothing has stored it, and the market has not been told about it.

Leaving the page ends it. That includes moving to another route, and it includes the route becoming unavailable while you were typing.

The two ways it goes

You switch deliberately
You chose to leave, usually because the route was slow. The text goes with the page and there is no way back to it.
The route goes quiet while you type
Nobody chose anything. The text is still visible in front of you and can no longer be sent anywhere, which is worse because it looks recoverable.

Why the second is worse than it looks

Text you can still see feels like text you still have. A reader will often try to send it repeatedly, then try to reload, and lose the text in the reload rather than in the failure.

The move that saves it is to copy the text out before doing anything else. That is a plain and unglamorous instruction and it is the entire content of this study.

Writing long things elsewhere

For anything you would mind losing, writing it in a place you control and pasting it in removes this whole problem. It also has a second effect worth noting: it means switching route mid conversation costs nothing at all, which makes the other two addresses genuinely usable at any moment.

That is the connection to the rest of the site. A reader whose work is never trapped in a form can use the set freely, and a reader whose work often is will avoid moving even when moving is the right thing to do.

A note on urgency

The times a message is being written in a hurry are the times a route failing is most likely to prompt a switch. Those two things arriving together is the ordinary case rather than the unlucky one, and it is closely related to choosing in a hurry.

What is not affected

Everything already sent, and everything already received. The message history is part of the account and is reachable from any of the three routes, as set out in the inbox being one object.

The loss here is narrow. It is confined entirely to text that has never left your screen.

The rule

Copy before you move. Copy before you reload. Anything long, write elsewhere first. Three short habits, and between them they close the only gap in this section that has real contents.

Why the advice is so unglamorous

Copy the text before you do anything. There is no cleverer version and no tool that improves on it, and it is the kind of instruction that gets skipped precisely because it sounds too simple to be the answer.

It is the answer. Everything else in this study is an explanation of why an unsent message is more fragile than it looks, and the explanation exists only to make the dull instruction feel worth following.

If there were only one address

Unsent text would still be lost when a page was left or a route failed, but never as the price of a decision to go somewhere else. The distinctive loss here is voluntary and avoidable, and it exists because a reader has an alternative address available and does not think of the box in front of them as containing anything.

What this study is not. It is not about message privacy or encryption, which do not change with the number of published addresses.

Every page on this site

How this site thinksThe addressesPluralityThree addresses can describe one marketWhat a second address actually buys youWhat a second address costs the readerA second mirror is not a backup of the firstThe head all three addresses shareWhy the set is three and not fiftyPlurality is not a promise that one will answerNobody on this side decides what the set containsChoosingThere is no correct address to open firstOpening the first address you seeAfter a while, habit picks for youReading order is not a rankingChoosing badly happens when you are in a hurryRotating between the three on purposeLoad time as a tiebreak, and where it failsThe choice you only make once per visitEquivalenceOne account, reachable from any of the threeThe inbox is one object, seen from three routesAn order does not belong to the address it came fromA balance is not held per addressThe circuit is yours, not the address'sA session does not follow you across addressesChecks at the front door are per routeWhere the sameness stopsDivergenceWhen two addresses seem to disagreeA stale page is not a stale marketYour own browser can manufacture a differenceTwo front pages that do not matchOne route slow, one quick, one marketSomething on one route and not the otherThe kind of difference that mattersTelling a real difference from an apparent oneSwitchingWhat carries when you switch mid visitWhat is dropped the moment you switchSwitching while an order is half writtenSwitching while a message is half typedProblems switching will not fixTwo routes open in two tabsThe moments where switching is the right moveThe cost of switching, counted honestlyAbsenceOne route quiet, two answeringTwo quiet, one answeringAll three quiet at onceWhat silence cannot tell youThe quiet that is on your sideRoutes that go quiet and come backNothing announces that a route went quietWhy there is no uptime number hereListsA list is a copy, not the thingHow a list goes staleTwo honest lists can differA list longer than the setWhat a list can and cannot proveThe list you keep yourselfReading the age of a listA list that ranks its entriesMistakesMixing characters from two addressesAssuming the set has an orderTreating one address as the real siteKeeping one and not the setJudging the market by one routeRetyping an address from memoryExpecting one route to point at anotherBlaming the market for a route level problemAll studiesThe words people type