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 note to self chat is a thread with one participant. Readers use it as a scratch surface for the string because it syncs across devices, timestamps by the app clock, and searches by keyword. It also comes with a preview engine and a link renderer.
What it is
A chat app on a phone almost always offers a channel called saved messages, favourites, or a thread the reader creates with only themselves in it. A message posted there sits inside the app database, syncs to every device the account is on, and appears in search across the app.
The reader posts the string, the app receives it, the app renders it. The rendering is where a chat surface stops being neutral. Some apps recognise .onion and offer a tap to open. Some apps do not and treat the message as text. Some apps insert a link preview and try to fetch it.
Lifeline
- Not in the thread
- Pinned or scrolled in view
- Buried under new messages
What the chat keeps
- The exact text of the message, in the sense that the string arrives at the app server as the reader typed it.
- A timestamp on the message that the app renders every time the thread is opened, which is useful only if the reader trusts the app clock.
- The sync across the devices the account is on, so the string appears on the phone, the tablet and the desktop with no further action.
- The searchability of the thread, so typing part of the vanity prefix into the app search returns the message.
What the chat loses
- The privacy of a string that never left the device, because the message went through the app server on the way to the other devices.
- The exact rendering, because the app link renderer may cut the .onion suffix, may hide part of the string under an ellipsis, or may fold long lines.
- The clean paste, because a copy from a chat bubble may include the timestamp label above the bubble or the sender label if the reader copied by long press.
- The invisibility, because a link preview fetch is a request the app made from an app server the reader did not choose.
The preview problem
A chat app that recognises a link tries to preview it. A preview means a server the app runs fetches the page and reports back what is on it. For an onion address this either does nothing because the app does not speak tor, or does something because a service in the middle does. Either way the address the reader typed is now known to a system the reader did not pick.
Most apps let a reader disable link previews. That setting is usually one toggle deep in the app settings and applies to future messages, not to past ones. A message already sent has already been previewed by whatever the app was going to preview it with.
Pinning the message
A saved messages thread that is used for anything else scrolls. A string typed into it three hundred messages ago is not visible until the reader scrolls or searches. The countermeasure most apps offer is a pin on a message that keeps it at the top of the thread. A pinned message is one tap to copy, and the pin is per thread.
A second countermeasure is to reply to the pinned message from a fresh line, so a chain of replies keeps the string in the reply header of every following message. That works until the reader breaks the chain by starting a new message without a reply, at which point the string is again only in the pinned bubble.