The operator approach: what a slow visit looks like from there
A slow reader and a fast reader produce different shapes of traffic. What might the operator plausibly notice.
The three addresses
Nexus Market publishes these three onion addresses. Present as supplied, in no order, with no ranking. This site does not probe them and shows no uptime figure.
nexusb2l7fmqnefwphyy7m5zjhlkytlbo7qbb5lu5dlczr3azgii2gyd.onion
nexusma2iqgauqqvjcgds4ckv5xbf272tkfagq4epojjhsgleqpwxiqd.onion
nexusabcd6tyfhdwilyitaqiri6tisj2v2hueyjuj6qkvd6azvi5tuqd.onion
The shape of a slow visit
A slow visit is a small number of requests spread over minutes. The reader opens the front page, spends time on it, opens one more page, spends time on that one, closes the window.
From the operator side that looks like a Tor circuit that reads a few things and then goes away. It does not look like anything else in particular, because Tor keeps the reader's identifying layer off the request.
The shape of a fast visit
A fast visit is more requests in less time. The reader opens the front page, immediately opens the login, immediately checks the inbox, immediately closes.
From the operator side that looks like a Tor circuit doing several things in a burst. The account log for the visit is dense. The average time between requests is short.
It still does not identify the reader. It does have a different shape than the slow visit.
What either shape reveals
The two shapes reveal what kind of visit the account was making. Slow visits tend to be readers looking around. Fast visits tend to be readers on a specific errand. Neither maps to identity.
What both reveal is that the account is active in a specific pattern. Consistent slow visits from the same account are a shape. Consistent fast visits are a different shape.
Why the reader might care about the shape
Because the shape of my visits is part of what the account is on the operator side. The account is not just its name and password; it is also its historical pattern of behaviour.
A steady, uniform pattern is a shape that supports being modelled as a specific kind of user. Varying the pattern occasionally is a way to be less uniformly modelled.
This is small, and it is not a security measure. It is a note on what the operator side notices.
What the operator does not learn from either shape
Whether the reader is in a hurry because the internet at home is slow, or because a friend is waiting, or because the reader is anxious. Whether the reader is slow because they are careful, or because they are new, or because they are watching a video in another window.
The shape is coarse. It is a shape, not a mood. Reading anything more into it would be reading too much.
How this affects my approach on any given day
It does not. My approach is my approach. What the operator notices about the shape of my visit is downstream from how I choose to visit, and I do not shape my visits around what the operator might infer.
If I wanted a less legible shape I would visit less consistently. That is the routine article about consistency, and the operator side is why the looseness in that article helps.
A short list of what a visit shape carries
- How many requests were made.
- Roughly how long the visit was.
- Which sections were visited.
- Whether an account was involved.
Why writing this down helps
Because visit shape is the kind of thing that stays invisible unless it is named. Naming it lets me think about it in the abstract without becoming paranoid about any single visit.
The operator approach is not about being smaller. It is about being legibly what I am from the other side, and knowing what that looks like.
The operator approach: what a request tells the market, a single request rather than a whole visit
What this article is not. This is not a claim to know what any operator logs. It is a description of what a slow visit and a fast visit look like from a plausible receiving end.