Habits from talking to people · habit 28 of 40

Pasting the link to someone

Somebody asks where you found it, and the fastest honest answer is the thing itself. Describing it takes a paragraph and some care. Pasting it takes no thought at all.

What it does everywhere else

Sharing a link is the most ordinary act on the internet. It is the unit the whole thing is built from: the object you send instead of an explanation, the move that turns a recommendation into something the other person can actually use. Every surface has a share control because the alternative is retyping, and retyping is where errors come from.

What it does on this one

Here one paste does three things at once. The service carrying the message stores the string. A preview system may go and look at whatever part of it can be reached. And a second person now holds a copy inside an account with its own settings, its own backup and its own habits.

The habit

You paste the address into a message rather than describing it, because the address is the part that is actually useful.

Why it is automatic

Link sharing is the closest thing the web has to a native gesture. It predates smartphones, it survived every platform change since, and it is taught by the interface rather than by people. Long press, share, done. There was never a moment where anybody sat down and learned it.

It is also more accurate than the alternative, which matters. A described address has to be retyped by hand at the other end, and a hand typed address is a wrong address more often than anyone likes to admit. Pasting removes an entire class of error, and removing that class of error is why the feature was built.

And it is polite. Sending the thing is doing the work for the other person instead of making them go and find it. Every norm about helping strangers online rewards exactly that, which is why it feels rude to answer a question with directions rather than with the answer.

What it actually does here

Preview generation is the part nobody pictures. When a message contains something shaped like a web address, many clients and services fetch it so they can show a title, a line of description and a small picture. That request is made by the service within seconds of sending, and neither end of the conversation asked for it.

Where the address cannot be reached from the open internet the fetch usually fails, and the attempt still took place: something read the string and tried to do its job with it. Where an ordinary web address sits in the same message, that one is fetched in the normal way.

The message itself is stored twice by construction. Your copy and theirs are separate objects and only one of them sits under settings you chose. Their client may back the thread up, their machine may be shared with a household, and their notification preview may put the first line of it on a lock screen in a room you have never been in.

After that it leaves the conversation altogether. A useful link gets forwarded, and forwarding is the same gesture again, one person further out each time. None of this needs anybody to be careless. It needs one person to find the message helpful, which is what you were hoping for when you sent it.

The request nobody typed

A pasted address is read by more than the person it was sent to. On most setups several pieces of software look at it before the recipient does, all of them for reasons that are defensible on their own terms.

The client that draws the preview card in the chat window.
The server side fetcher that goes and collects the title and picture for that card.
Spam and safety checks that examine addresses inside messages before delivery.
Any bot in a group that reads messages and expands what it finds in them.

Two archives and somebody else's backup

The thing that makes this different from every other habit on the site is that half of the result sits with a person you cannot advise. They may keep everything forever because that is the default. They may sync the thread to a machine at work. They may hand the phone to somebody to show them a photo, with the conversation list one swipe away.

This is also the one page where the phrase people arrive searching for is the exact thing worth not pasting. A mars tor link is short, it is easy to send, and sending it moves the entire question of where it came from into a second archive. The recommendation survives being spoken. The string is what needs somewhere better to live.

What to do instead

The replacement is a sentence rather than a paste, which costs more typing and nothing else. It also answers the question the person usually has, which is whether the thing is worth their evening rather than which characters to type.

Describe what it is and point the person at the list on this site, rather than at a string sitting in a chat window.
Turn link previews off in the clients you use. It stops your own copy causing a fetch and it does nothing about theirs.
Assume the person on the other end keeps everything, because most people do and almost none of them chose to.
Keep addresses out of group threads entirely. A group is a mailing list with a search box and a membership that changes without announcement.
When somebody asks you for it, answer the question underneath the question, which is usually about how to check something rather than where to click.

How to notice you did it anyway

Sent messages are searchable by the same features that made them convenient, so this is an audit you can do in a few minutes.

Search your own sent messages for the words that tend to sit next to a pasted address, such as "here" and "this one".
Look for conversations where a preview card appeared, since the card is evidence that a fetch happened.
Check the group threads you have left, because leaving removes you and not what you posted.
Open the share sheet history on the phone and the recent targets in the browser share menu.
Think about which of your contacts back their chats up, then work on the basis that the rest do too.

What readers ask about this habit

Does it matter if the address cannot be opened by the previewer anyway?

The failed fetch is not the only thing that happened. The string was still carried, stored and indexed by the service, and it still sits in two accounts. A preview that does not render is not a message that was not sent.

Is sending it as a picture better?

It avoids the preview fetch and it creates an image, which lands in the photo library at both ends and gets swept into whatever backs those up. Many setups read text out of images so search can find it. It moves the problem rather than removing it.

What about a message that deletes itself?

Disappearing messages remove the visible copy on a schedule, which is a real improvement over keeping it forever. They do not reach screenshots, notification text already delivered, or anything a fetcher did on the way. Treat it as tidying rather than as an eraser.

Someone asked me directly. What do I say?

Say what you know about how to check things and leave the string out of it. Asking in the group covers the same trade from the asker's side, and signing in covers what happens once they are past the front page.