nexus-approach.shop

Front › The operator approach › The operator approach: what the inbox tells them

The operator approach: what the inbox tells them

Every message I send through the market inbox lives on the market. That is a fact I want to hold plainly in my head.

Operator approach 3 min read why no author line

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

Where the inbox physically is

On the market server. Not on my machine. Not on the vendor's machine. On the market. Messages travel from me to the market, sit there, and then travel from the market to the vendor when they open their end.

That is not a bug. That is what a market inbox is, on any market. It is a communication surface hosted by the third party.

What the operator plausibly sees

The content of any message that is not itself encrypted. Timestamps. Sender and recipient accounts. The volume of messages between two accounts. Attachments if attachments are supported.

They see the shape of the conversation as much as the content. Even if content is encrypted, the shape is legible.

What I do about it

I write my messages assuming the operator can read them. That is the honest baseline. If the message would be a problem for me if the operator read it, it is not a message I send through the inbox.

For anything that needs privacy from the operator, PGP is the answer. I encrypt to the vendor's public key and I send the ciphertext. The operator sees the ciphertext go through; the content is not readable to them.

For anything routine that does not need privacy from the operator, plain text is fine and simpler.

What encryption to a vendor key does and does not do

It hides the content from the operator. It does not hide that a message was sent, from whom, to whom, or when. Those metadata are still visible on the operator side because they are part of how the market delivers the message.

The trade off is honest. Content privacy without shape privacy. That is enough for most of what an inbox is used for.

What I never put in a plain message

A shipping address. A phone number. A payment identifier that could be tied back to a bank account or a wallet I care about. A specific request that would be a problem for me if quoted publicly.

All of that goes in an encrypted message, or does not go at all.

What I say in a plain message

Small logistics. Timing. Questions about the interface. Anything that would be no different than saying out loud in a public place. The plain inbox is a public place, in the sense that the operator can read it.

Small habits about inbox use

  • Assume the operator can read plain messages. Do not test the assumption.
  • Encrypt anything that needs to be private from the operator.
  • Do not send an address of any kind in a plain message.
  • Do not sync inbox content to my own machine in any form that outlives the session.

What this means for my approach

It means I use the inbox for the things that fit in a surface the operator can read, and I use PGP for the things that do not. That is a simple line and it is easy to hold.

The operator approach for the inbox is not about avoiding the inbox. It is about understanding what it is, so I use it correctly.

The opposite approach

The routine approach on a normal evening, the visit that treats the inbox as normal

What this article is not. This is not a claim about what any specific market does with inbox content. It is a description of what any market plausibly could.

Read another in this approach

The operator approach: what a mirror does and does not shareThree mirrors are three doors into the same house. From the operator side they are shared; from the reader side they are equivalent. The operator approach: what I cannot know and choose not to guessSome things about the operator I cannot know. Guessing about them is worse than admitting I do not. The operator approach: what a slow visit looks like from thereTwo visits of different pace produce two different shapes on the operator side. Both are legible; neither identifies me.
Every page on this site
All approaches on this siteHow to read this siteThe words people searchThe three nexus market addressesWhat this site is notThe first-time approachThe cautious approachThe impatient approachThe rebuild approachThe verify approachThe routine approachThe secondary approachThe helper approachThe journalistic approachThe operator approachThe first-time approach when a friend sent me a noteThe first-time approach out of a forum threadThe first-time approach starting on a search pageThe first-time approach after reading a news articleThe first-time approach after hearing it on a podcastThe cautious approach before I touch the keyboardThe cautious approach when the network is not mineThe cautious approach with a second machineThe cautious approach to what I copy and what I typeThe cautious approach that never signs inThe impatient approach that goes straight to the address barThe impatient approach from a tab I already had openThe impatient approach inside a five minute windowThe impatient approach when a mirror is slowThe impatient approach that skips the second checkThe rebuild approach after losing the phoneThe rebuild approach after losing every noteThe rebuild approach after losing the passwordThe rebuild approach after a clean installThe rebuild approach when one mirror has gone quietThe verify approach with two lists side by sideThe verify approach for a friends messageThe verify approach against this site aloneThe verify approach that reads the string itselfThe verify approach across two visitsThe routine approach on a normal eveningThe routine approach with one eye on a newer mirrorThe routine approach when nothing has changedThe routine approach that reads the front page firstThe routine approach with one eye on my own consistencyThe secondary approach coming from another marketThe secondary approach that keeps two markets separateThe secondary approach during a move between marketsThe secondary approach that eventually stops being secondaryThe secondary approach that reads one market and uses anotherThe helper approach at one desk with two readersThe helper approach for questions coming through a chatThe helper approach on paper, for laterThe helper approach and the things I refuse to doThe helper approach that only points at this siteThe journalistic approach for a story I am not going to nameThe journalistic approach for a story that names peopleThe journalistic approach when I interview somebodyThe journalistic approach and what not to publishThe journalistic approach in a shared CMSThe operator approach: what a request tells the marketThe operator approach: what a slow visit looks like from thereThe operator approach: what the inbox tells themThe operator approach: what a mirror does and does not shareThe operator approach: what I cannot know and choose not to guess