A conversation is easier to become part of the web when you can point at it.
That sounds trivial until the discussion lives inside an app.
A traditional forum thread or blog comment page has an address that can be copied into another document, indexed by a search engine, cited years later, or opened by somebody who was not present when the discussion happened. The URL becomes part of the memory of the conversation.
Modern chat systems can provide message links too, but those links often depend on access to the original container.
Discord, for example, lets users copy a direct link to an individual message. Its own documentation explains that a message link can jump somebody into the conversation if that person has access to the channel. See Discord’s guide to message links and IDs.
That is an address.
It is not the same thing as a public permalink.
The link inherits the walls around the conversation
A Discord message URL contains identifiers for the server, channel, and message. If the recipient belongs to the server and can read the channel, the link is extremely useful.
If they do not have access, the URL does not magically make the conversation public.
Private Slack channels work similarly at the access level. Slack says messages and files in private channels appear in search results only for people who belong to that channel. The information may be perfectly searchable inside the authorized group while remaining invisible to everybody else. See Slack’s explanation of public and private channels.
This changes how knowledge travels.
Someone solving an obscure technical problem in a public forum can send the thread to a stranger five years later. Someone solving the same problem in a private channel may only be able to send a link that works for members of the same space.
The discussion exists. The address exists. The address is not independently useful.
Stable public URLs create reusable context
A durable public permalink gives later readers more than a sentence.
They can see the original question, replies, corrections, timestamps, related links, usernames, and arguments that produced the answer. Other websites can reference that discussion without copying the whole thing.
App-bound conversation often keeps those benefits for participants while weakening them for outsiders.
That is not necessarily a design failure. Private groups are private for reasons. People may want access controls, moderation, limited audiences, or conversations that are not permanently exposed to the entire internet.
The Dead Internet Theory mistake would be to interpret the shrinking supply of public discussion URLs as proof that discussion stopped.
Sometimes the humans are talking constantly.
The conversation simply no longer has a front door that the rest of the web can use.