Tag: Online Conversation

Posted on by

Conversation without permanent, independently addressable URLs

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.

Posted on by

Undisclosed chatbot personas inside social conversations

A social conversation changes depending on who you think is in the room.

People disclose differently to friends, strangers, employees, salespeople, moderators, and machines. That makes an undisclosed chatbot more than an efficiency trick. If it speaks under a human name, uses a human-looking profile, and participates without identifying itself as automated, the other person is making decisions with the wrong model of the conversation.

Research on chatbot disclosure shows that the distinction is not always obvious. A 2024 mixed-method study of disclosed and undisclosed customer-service chatbots found that 20 percent of participants in the experiment believed they had communicated with a human, despite the study setting and participants’ general familiarity with chatbots. The paper, “Understanding users’ responses to disclosed vs. undisclosed customer service chatbots”, also found that people relied on cues such as response speed, grammar, repetition, and conversational mistakes when deciding whether the other party was human.

Those clues are getting weaker as language models improve.

Source identity changes the meaning of a reply

Suppose an account says, “I had the same problem. Here is what worked for me.”

If a human wrote that sentence, it may describe experience. If a company chatbot generated it, the same sentence is a simulation of experience. The words can be identical while the evidentiary value is completely different.

That becomes more important in social spaces than in a clearly labeled support widget. A bot in a discussion group can appear to agree with a position, recommend a product, comfort another user, or describe a personal history it never lived.

The issue is not that machines are forbidden from participating. Automated accounts can be useful, entertaining, or welcome members of a community. The problem is source confusion.

Disclosure is information, not an exorcism

Labeling a chatbot does not magically prevent people from anthropomorphizing it. The same 2024 study found that disclosure did not eliminate the sense of social presence participants experienced.

That is fine. Humans anthropomorphize cars, pets, weather, and printers that refuse to work five minutes before a deadline.

Disclosure serves a simpler purpose: it tells participants what kind of entity is producing the messages.

That distinction is increasingly relevant as companion systems and character bots move into ordinary communication platforms. The U.S. Federal Trade Commission’s 2025 inquiry into AI companion chatbots specifically asked companies how they use disclosures and representations to inform users about chatbot features and risks.

For Dead Internet Theory, undisclosed social bots are a much stronger concern than bots as such. A transparent bot increases the amount of machine participation online. An undisclosed persona can increase the apparent human population of the conversation.

Those are not the same phenomenon.