The machine and the network under you
The first decision of the session is made by default in almost every case. Whatever machine you happen to be holding becomes the machine. It is worth three minutes to make that a choice instead.
Back to minute 0Crown market addresses
crownm5jmtbhqnoxhexx7nyiygqgqofp3wnjyyfl74gziohqqy6oq5id.onioncrownrywlm7mnohkzntlir2tlhafq6tzphgqyag5cw5en7nprchfklad.onioncrownwpaimgizxylrvrh4u6acpvk4l757cfla7xs6zjki7tdjqbnv6qd.onionPublished exactly as supplied. Nothing on this site is monitored, tested or checked, so no address here is claimed to be working. What a copied address does and does not settle.
What actually happens here
You pick up something and start. That is the whole event, and it is over before you notice it happened. The machine you were already using becomes the machine the whole session runs on, and everything that follows inherits its properties.
Three properties matter and they are not the ones people expect. Who else touches this machine. Whether the account you are logged into on it is one that syncs things elsewhere. And whether the network it is on belongs to someone who has a reason to look at it.
Who else touches it
A shared family laptop is the common bad case, and the risk on it is not exotic. It is somebody opening the browser and seeing a tab, or a download folder, or a saved password prompt. None of that requires anyone to be technical or curious. It only requires them to use the machine normally after you did.
A machine nobody else touches removes an entire category of problem for free. If that is not available, at minimum use a separate account on the machine rather than the shared one.
What the machine syncs
Modern setups copy things upward without asking. Clipboard history, screenshots, downloads, browser sessions, and in some cases the contents of a folder that looked local. A phone that mirrors notes to an account is a bad place to write down anything from minute 35.
You do not need to disable all of it. You need to know which parts are on, so you do not later put a recovery phrase somewhere that quietly ships it to a server run by a company that will hand it over on request.
Whose network it is
A work network, a school network or a corporate laptop on a company connection is a different situation from a home line, because somebody there has both the ability and often the standing instruction to look at what passes through. Using the browser from minute 5 hides what you are doing on that network, but the fact that you are running it is itself visible, and on a managed machine the software may not run at all.
Public wifi is a weaker version of the same thing. The traffic is protected, the pattern is not, and the bigger practical risk on public wifi is the person behind you rather than the network in front of you.
- The largest category of first session mistakes involves other people using the same machine afterwards. Choosing removes it outright.
- It fixes where recovery material can safely go, which is the decision at minute 35 that people make in a hurry.
- It is the only cost free decision in the run. It takes minutes and no money.
- The good option is not always available. Plenty of people have one machine and it is shared.
- It invites the trap of solving it perfectly. A dedicated setup is a project, and a project is a way of never starting.
- It does nothing about anything after arrival. A clean machine does not improve a bad decision at minute 75.
The stall here is not indecision, it is escalation. Someone reads that a shared laptop is a bad idea, goes looking for what a good idea would be, and finds an entire world of dedicated operating systems and separate hardware. Two hours later they have not opened anything.
The other stall is the opposite and quieter. The question never gets asked, the session runs on the household machine, and the consequence turns up a week later when somebody else opens the browser.
If the answer takes more than five minutes you have started a different project. Note it, use what you have today, and change the setup on a day when you are not also doing everything else in this run.
A workable answer for most people
- Use a machine only you use, or a separate user account on the one you have.
- Know which of your clipboard, screenshots, notes and downloads are syncing to somewhere else, and treat those as unsafe for anything written down later.
- Use a home connection rather than a work or school one. Not because the home line is private, but because nobody on it has a job that involves reading it.
- Leave the exotic options alone for a first session. They are real and they are not a first session decision.
Choose the machine rather than inheriting it, know what it copies elsewhere, and do not turn a three minute decision into a weekend of setup.