Messages, comments, and small signals without the attention machine
Social software should help people talk, respond, and stay in touch without turning every interaction into a growth loop. Messages, comments, and small signals can be useful. They do not need to become an attention machine.
TouchGrass is built around real friends, circles, posts, profiles, and intentional audiences. Conversation belongs in that context. A comment can add something. A message can continue a conversation. A small signal can say “I saw this” without becoming a public popularity count.
Why we chose this
Most social platforms do not only host conversation. They shape it.
A comment can become a performance. A like can become a scoreboard. A notification can become a habit loop. A direct message can become one more surface for pressure, interruption, and expectation.
The problem is not that people respond to each other. The problem is when the product treats every response as fuel for more engagement.
Healthy social software should make conversation possible without making interruption the business model. It should let people reply, ask, acknowledge, and follow up without pushing them into public metrics, infinite feed checks, or algorithmic ranking.
TouchGrass approaches conversation as part of a wider social home. Friends and circles matter. Audience matters. The profile and post context matter. The question is not “how do we maximize interaction?” It is “how do we support useful contact without turning people into engagement targets?”
How this works on TouchGrass
Today, TouchGrass supports social interaction around friends, circles, profiles, and posts. that includes messages, comments, and smaller signals for acknowledging or responding.
The design direction is to keep these interactions human-sized. Comments should support conversation around a post. Messages should support direct communication. Small signals should help people acknowledge something without turning the entire product into a public like-count race.
TouchGrass also supports visibility choices: public, friends, and circles. That affects conversation because the audience of a post shapes the audience of the response. A comment under a public post is different from a response in a friends-only or circle context.
TouchGrass is also moving in an open-web direction. Federation, portability, ATProto/Atmosphere, Solid, ActivityPods, and private sharing are important directions, but conversation features are especially sensitive.
Worth knowing
Messages and private sharing need careful language.
If someone receives something, they may copy it, photograph it, forward it, or describe it elsewhere.
Comments and small signals also have social limits. Removing public like-count races can reduce pressure, but it cannot make every interaction kind, accurate, or welcome. Moderation, safety tools, and social norms still matter.
Open-web work should also be described carefully. Federation and portability can improve exits and reduce lock-in, but they can also introduce remote-server behavior and protocol limits.
FAQ
What are small signals?
Small signals are lightweight ways to acknowledge or respond without turning everything into a public score. The exact set of signals depends on the current product state.
Are private messages or private posts completely private?
No product should promise that. Private sharing can limit intended visibility, but it cannot protect against screenshots, recipient misuse, remote-server behavior, compromised devices, or every future integration.
How is this different from engagement-first platforms?
TouchGrass does not center the product on algorithmic feed ranking, public like-count races, infinite scroll, or videos as the main social object. Conversation exists to support real social contact, not to maximize interruption.
See what you can do
Friends and circles
TouchGrass is built around real friends, circles, posts, profiles, and intentional audiences. Conversation belongs in that context. A comment can add something. A message can continue a conversation. A small signal can say “I saw this” without becoming a public popularity count.
Why we chose this
Most social platforms do not only host conversation. They shape it.
A comment can become a performance. A like can become a scoreboard. A notification can become a habit loop. A direct message can become one more surface for pressure, interruption, and expectation.
The problem is not that people respond to each other. The problem is when the product treats every response as fuel for more engagement.
Healthy social software should make conversation possible without making interruption the business model. It should let people reply, ask, acknowledge, and follow up without pushing them into public metrics, infinite feed checks, or algorithmic ranking.
TouchGrass approaches conversation as part of a wider social home. Friends and circles matter. Audience matters. The profile and post context matter. The question is not “how do we maximize interaction?” It is “how do we support useful contact without turning people into engagement targets?”
How this works on TouchGrass
Today, TouchGrass supports social interaction around friends, circles, profiles, and posts. that includes messages, comments, and smaller signals for acknowledging or responding.
The design direction is to keep these interactions human-sized. Comments should support conversation around a post. Messages should support direct communication. Small signals should help people acknowledge something without turning the entire product into a public like-count race.
TouchGrass also supports visibility choices: public, friends, and circles. That affects conversation because the audience of a post shapes the audience of the response. A comment under a public post is different from a response in a friends-only or circle context.
TouchGrass is also moving in an open-web direction. Federation, portability, ATProto/Atmosphere, Solid, ActivityPods, and private sharing are important directions, but conversation features are especially sensitive.
Worth knowing
Messages and private sharing need careful language.
If someone receives something, they may copy it, photograph it, forward it, or describe it elsewhere.
Comments and small signals also have social limits. Removing public like-count races can reduce pressure, but it cannot make every interaction kind, accurate, or welcome. Moderation, safety tools, and social norms still matter.
Open-web work should also be described carefully. Federation and portability can improve exits and reduce lock-in, but they can also introduce remote-server behavior and protocol limits.
FAQ
What are small signals?
Small signals are lightweight ways to acknowledge or respond without turning everything into a public score. The exact set of signals depends on the current product state.
Are private messages or private posts completely private?
No product should promise that. Private sharing can limit intended visibility, but it cannot protect against screenshots, recipient misuse, remote-server behavior, compromised devices, or every future integration.
How is this different from engagement-first platforms?
TouchGrass does not center the product on algorithmic feed ranking, public like-count races, infinite scroll, or videos as the main social object. Conversation exists to support real social contact, not to maximize interruption.
See what you can do
Friends and circles