Nexus Panel BoardPanels of numbers this site works out for itself
Orders

When it goes to dispute

A dispute turns on what can be shown, and what can be shown was fixed long before the dispute started.

Words on this panel
804
words on this panel
Headed sections here
7
headed sections on this panel
Every panel length, in order
883
longest panel, with every panel plotted in order
Share of the whole board
1.64%
of the board is this panel

Nexus market addresses in this board

copy, do not retype
nexusb2l73qzjn4slhyfxa3jvpolw7fomiz5sgyyefnsdhikaqgborqd.onion
nexusma2iekjhhyenua3u4zlyfsj2ubwxr2nt6gdte5rvwukzze63fyd.onion
nexusabcdbnjw6or46y3hh6uicsl4xvu5cncfp27hkggznvtxhxlngad.onion

Printed as supplied, in no order, with nothing marked best or main. This board never opens an address, so nothing on this page says one of them is reachable for you now.

The gap between what happened and what can be shown

A dispute is not resolved by what took place. It is resolved by what somebody can put in front of whoever decides, and those two are only related if a record was kept.

That is an uncomfortable thing to read and it is the useful thing to know, because it moves the decisive moment much earlier. The record is either made as things happen or it does not exist, and no amount of being right afterwards produces one retroactively.

What makes a record useful

  • Made at the time, not reconstructed. Reconstructions are shaped by how you feel now.
  • Specific about what and when, in terms that will still make sense to somebody who was not there.
  • Kept somewhere you will still have access to, which is not the system the dispute is in.
  • Boring. A record that argues a case is weaker than one that states what happened.

The timing problem

Records get made when somebody suspects a problem, which is usually after the moment that turns out to matter. By then the early details are gone, and the early details are frequently the decisive ones.

The remedy is a small habit rather than vigilance: note what you did and when, at each stage, as a matter of course. The panel on waiting recommends the same thing for a different reason, which is a hint that it is worth doing generally.

How to write during one

Briefly, factually, once per point, without heat. A dispute is read by somebody with no context and limited patience, and the version that reads as a clear account of events lands better than the version that reads as an argument.

This is not about being nice. It is that a clear account is easier to act on, and whoever is deciding is looking for something they can act on rather than something they have to adjudicate.

What this board does not know

It has no idea how any dispute process works anywhere, who decides, what the criteria are, or what outcomes are typical. It has never seen one and holds no data of any kind about them.

What it can say applies to disputes generally, in any setting: the record decides, the record has to be contemporaneous, and the tone of the writing affects how easy it is to act on. Those are structural rather than specific, which is why they are the only things here.

The tiles, and the pattern by now

This panel word count, its headed section count, the line of every panel length on the site, and its share of the whole board. Every panel in the orders and money sections has ended up here, and the reason is worth stating once more.

These are the subjects where readers most want figures, and they are exactly the subjects where a board with two narrow data sources has none. A site that filled that gap would be more satisfying to read and would be making things up, and the whole design of this one is a bet that the first is not worth the second.

What a record is not

A record made at the time is useful and it is not proof of anything. It is your account, written by you, and whoever reads it knows that.

The value is not that it convinces. It is that it is specific, contemporaneous and consistent, and those three properties are visible in writing in a way that a reconstruction is not. A reconstruction reads differently even when it is accurate, because it has been shaped by knowing how things turned out.

So the reason to keep one is not that it wins arguments. It is that it stops you being wrong about your own case, which happens more often than people expect and is the fastest way to lose the sympathy of whoever is deciding.

Questions that come up on this panel

What should I keep a record of?

What you did and when, at each stage, in plain terms. Made at the time, kept somewhere outside the system in question.

Does this board know how disputes are handled?

No. It has never seen one, holds no data about any, and everything here is general rather than specific.

Reading this panel wrong

3 ways it happens
  1. Assuming being right is enough.It is decided on what can be shown. Those coincide only when a record exists.
  2. Starting a record when trouble appears.The early details usually matter and are already gone by then.
  3. Expecting specifics about any dispute system.There are none here. Everything on this panel is structural and applies to disputes anywhere.

What this panel is not: a description of any dispute process. It has never observed one and says only what holds generally.

Nearby panels

Every panel on the board

68 pages
Strings
How long each address is The symbols an address can contain The opening all three share Where the three part company Digits, and where they fall What repeats inside an address How far apart the three are The character they all end on
Reading
Symbols the eye trades What a front and back check proves The part nobody reads Reading an address in blocks Copying rather than typing The stretches you cannot say Reading an address out loud What a check cannot reach
Route
What the browser is doing The first load of the session When a page loads slowly Why the path keeps changing What each step can see The screens that mean failure Where the address lives between visits Where the address came from
Session
The name you choose The login screen How long a session lasts What stays behind Two tabs, one account Ending a session on purpose Losing access Encrypted text in a session
Money
The deposit address Waiting for confirmations What escrow holds Where the cost sits Rounding and leftovers Taking a balance back out The waiting, laid out The steps you cannot take back
Orders
Before the order exists Placing the order The delivery details Between placing and dispatch What tracking does not say Finalising When it goes to dispute The feedback you leave
Corpus
How much is on this board How the panels are distributed How long a panel is The tiles, counted Which phrases the board uses What is deliberately left out How the panels connect The tiles that come back empty
Reference
All panelsHow the numbers are madeThe addressesWhat this board covers