Who Sees What
Awazon market onion addresses
awazonloedcyl2otgftfg7qm6e2klbgg2dhouyli3hdno6gdkueh6byd.onion
awazonozc4jwyrveu4473igv5ldt2hnccl2s7lerm2z27cvrc22e4uyd.onion
awazonth6ocz5cyos63czmhtsglqr7ydkdcc4lopux7nxbauoo2qmvyd.onion

Printed exactly as supplied, in the order supplied, with no labels and no ranking between them. This site runs no checks against any of them. It publishes no uptime figure, no status light and no date of last checking, because it never looks. An address that opens is not by itself evidence of anything.

The catalogue, page two

The middle of the run. These cards cover what a form receives, what a vendor receives, and the point at which the whole question stops being about networks and becomes about a physical object.

Why half of every card is a negative

A catalogue of exposure that only listed exposure would be useless, and worse than useless, because it would push a reader towards treating every observer as equally informed. They are not. The difference between what a party receives and what a party can conclude is enormous, and most bad reasoning on this subject happens in that gap.

Take the plainest example on this page. A server that renders an order form receives what was typed into it. That is not an opinion, it is how a form works. What that server does not receive is the identity of the person typing, the place they are sitting, or any assurance that the details are true. A reader who knows only the first half will conclude too much. A reader who knows only the second half will conclude too little. The card gives both halves at the same length so neither can be read alone.

The negative half is also the part that ages best. What an observer receives changes when software changes. What an observer structurally cannot receive changes only when the arrangement itself changes, which is rare. A relay in the middle of a circuit has never been in a position to see both ends of it, and no update to anything alters that.

The handover

Somewhere in this stretch of the catalogue, the subject changes. Up to a point everything is about connections, sessions and records held by machines. Then an address gets typed into a box, and from that moment there is a physical object in the world with a destination written on it.

That handover is the most important thing on this site, which is why its card is the longest and the most careful. Everything before it is reversible in the sense that a record can be deleted, an account abandoned, a circuit rebuilt. A parcel that has been posted is in a system that was built to know where things went, and no decision made afterwards reaches back into it.

The remaining cards are on page three, and they move the question inside your own house.

The marketTyping a delivery addressThe market server · Whoever runs the platform · Anyone who later obtains the serverOne field carries more than every other field on the site combined. Where it is encrypted decides everything.5 things reduce thisThe marketThe market inboxThe market server · Whoever runs the platform · Anyone who later obtains the serverA sealed envelope still shows who sent it, who received it and when it was posted. So does a message you cannot read.4 things reduce thisThe marketFunding a balanceThe market server · Whoever runs the platform · Anyone who later obtains the server · Anyone reading a public ledgerThe platform learns that an address it issued received something. A public ledger learns rather more, and shows it to everyone.4 things reduce thisThe vendorPlacing an orderThe vendor · The market serverOne account, one listing, one moment, one quantity. That is the whole of what the order itself says.5 things reduce thisThe vendorThe address you hand overThe vendor · The market server · Whoever reads the vendor's recordsThe single piece of information that has to leave your control for anything physical to arrive at all.6 things reduce thisThe vendorAsking a question firstThe vendor · The market serverA message sent before any commitment still tells the reader who they are talking to, in ways the sender rarely counts.5 things reduce thisThe vendorSending an encrypted noteThe vendor · The market server as carrierEncryption removes one reader from the conversation. It is worth being precise about which one, and what remains visible.5 things reduce thisThe vendorOpening a disputeThe vendor · A platform moderator · The market serverA dispute is the one action here that adds a reader deliberately, and the case you make is usually longer than you intended.6 things reduce thisThe vendorOrdering twiceThe vendor · The market serverTwo orders are not twice one order. Repetition connects moments to each other, which a single event cannot do.5 things reduce thisThe postA parcel entering the systemA postal operator · A courier · Whoever staffs the counterAn object is handed to a carrier. From that second a commercial system holds a file saying it exists and where it began.4 things reduce thisThe postA tracking numberA postal operator · A courier · Anyone holding the numberA short string that lets anybody holding it read part of an operator file. It is normally shared, which is the whole problem.4 things reduce thisThe postThe outside of the packetA postal operator · A courier · A customs serviceEverything the outside of an item is, as a set of recorded facts. This card describes and does not recommend.4 things reduce thisThe postSigning for deliveryA courier · A postal operator · Whoever answers the doorThe moment a delivery stops being an event at an address and becomes an event involving a person.4 things reduce thisThe postCrossing a borderA postal operator · A second operator · A customs serviceA border does not change the nature of the record. It adds observers to it, and it makes the chain considerably longer.4 things reduce thisThe postLockers and collection pointsA postal operator · A collection point operator · A camera on the wallCollecting from a locker or a counter does not remove an observer. It replaces a home address with a different set of records.4 things reduce this