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 nexus market url carried across a device travels on a transfer medium chosen by the reader. Cloud sync, a qr scan, a chat with self or a piece of paper each have their own losses.
What it is
A nexus market url carried across a device is a string that was written down on one machine and used on another. The move might be phone to laptop for pasting into a browser that is only run on the laptop, or laptop to phone if the reader is opening the mirror on a phone this time. The medium between the two devices is the whole path here.
The path is defined by the medium of the transfer, not by the two devices. The same laptop and the same phone can share a string over cloud sync, over a scanned qr code, over a chat with yourself, over a self email or over a piece of paper. Each medium has its own losses and its own risks. A reader who uses several mediums for the same purpose is really using several different paths.
The common transfer mediums
- Cloud sync
- A notes app that syncs across the reader's devices carries the string as text. The move is invisible and fast, and the string sits on servers the reader does not run in the middle.
- Qr code
- A qr scanned by the second device off the first. The image encodes the string as bytes, and the scan reads the bytes back. Scale, focus and screen glare are all failure modes.
- Chat with self
- A message the reader sends to themselves on any messenger that supports it. Same losses as any other chat, plus one round trip through the messenger servers.
- Email to self
- A short email the reader sends from one account to the same account. Passes through both the sending and the receiving mail servers, and can be scanned by either.
- Removable media
- A file on a usb stick or an sd card. The string is on disk in plain text, and the drive is a physical object that can be lost or copied.
What tends to slip in transit
- A newline injected by the notes app on line wrap, which the paste picks up on the receiving device only.
- A font substitution on the receiving device that renders a base32 run in a way that reads differently from the source device, without changing the underlying bytes.
- A qr code scanned at a poor angle, decoded by the phone into a slightly different string, and pasted without a byte for byte check.
- A chat client on the receiving device that autolinkifies the string in a way the sending device did not, so the paste picks up markup that was never in the source.
Lifeline
- Held on the source device
- Being moved across the medium
- Held on the destination device, on top of a stale copy
What the path drops
The path drops the guarantee that the string is the same on both ends. Even a transfer that succeeds byte for byte can end up displayed differently on the receiving device because of the fonts or the render behaviour of the app that shows it. That is only a display problem, but a reader who checks by eye and not by paste can still be caught by it.
The path also drops the reader's ownership of the middle. Any cloud service in the path, any chat server, any mail relay, has the string in the clear on their infrastructure for as long as they keep the message. This does not mean the string is secret to begin with, but the path is not the reader's alone the moment it uses any of these mediums.
What to check after the move
- The string on the destination device is the same length as the string on the source device, character for character. A qr round trip changes lengths more often than any other medium.
- The prefix reads the same on both devices, without relying on the font. Both devices should show the same run when the reader compares them side by side.
- The medium was cleared after the move if it does not need to keep the string. A cloud note, a self email or a chat with self all sit around after the transfer unless the reader removes them.
- The reader knows which device is the source and which is the destination. When the same medium is used both ways over time, older copies of the string can end up mistaken for newer ones.