Nexus market mirrors, as published on this site
nexusb2l7fmqnefwphyy7m5zjhlkytlbo7qbb5lu5dlczr3azgii2gyd.onionnexusma2iqgauqqvjcgds4ckv5xbf272tkfagq4epojjhsgleqpwxiqd.onionnexusabcd6tyfhdwilyitaqiri6tisj2v2hueyjuj6qkvd6azvi5tuqd.onionPublished as supplied. This site does not probe an onion, so nothing here is a claim that a given address opens for you right now.
A tor browser tab left open is a session frozen in place. The address is in the bar, the page is in the viewport, the cookies are in memory. The tab holds all of that until the reader closes it, the browser restarts, or the machine sleeps in a way the network does not survive.
What it is
A tab in tor browser holds an address, a page loaded from that address, a scroll position, whichever cookies the site set, and a circuit through the tor network that the page rode in on. All of those live in the browser process while the tab is open. Some of them survive a tab close and some do not.
A reader who does not close the tab is using the tab as the surface. Coming back to the machine an hour later means clicking on the tab to get straight to where they were. That works when the tab is exactly what the reader left, and fails when the tab is not.
Lifeline
- Not opened
- Open and idle
- Reloaded, timed out or closed
What the tab keeps
- The address in the bar, so a reader does not type or paste again to return to it.
- The session cookies for the tab, so a login the reader already did stays valid until the site expires it or the tab is closed.
- The scroll position and any form state the page held, in the sense that the tab returns to the state the reader left when the tab wakes.
- The chance to see immediately whether the tab was disturbed, because a tab whose page reloaded shows the fresh landing state and not the state the reader left.
What the tab loses
- The steady circuit, because a machine that slept long enough loses the circuit and the next request builds a new one, which may pick a different guard.
- The freshness of the page, because a page that sat for hours may be looking at cached content while the site has already moved.
- The isolation of the address in the bar, because a background reload from the site can change the bar to a login page or an error page.
- The independence from a browser update, because a tor browser that updates in the background asks the reader to restart and the restart takes the tab with it.
What sleep does
A machine that sleeps stops the network stack. Tor loses its circuit within a short time of that. When the machine wakes, the browser tries to reach the site through a new circuit. The address in the bar is the same. The circuit is not. The site sees a fresh connection.
A site that noticed the drop may have expired the session. The tab that looked exactly like the reader left it may report a login page on the next click. That is not the tab losing the address. It is the tab losing the circuit while keeping the address, which is often more confusing than a plain timeout.
What a restart clears
A tor browser restart clears every tab, every cookie, every circuit and every form field the reader had. Some readers rely on this and restart on purpose. Some readers dread it because the tab they left open is the tab they were using as a shortcut. A tor browser update usually forces a restart. A machine reboot forces one too. Neither event asks the tab whether it was busy.
The tab left open is not the same object as the address that opened it. The address survives in the paper notebook, in the vault note, in the plain text file. The tab is a session state built on top of the address. Losing the tab does not lose the address, only the session and whatever the session held. That is worth remembering the moment the tab is gone.