Pinned messages stop working faster than you think
Pins are the default tool for making information persist. Their actual half-life as an attention surface is short.
What the data shows
Where click-through on pinned links has been measured, engagement concentrates in the hours after pinning and decays steeply within days. A pin that's been up for weeks gets near-zero new clicks — regulars have learned to ignore the pin icon, and newcomers don't think to check it. Pins behave less like permanent signage and more like a fading announcement.
Why it happens
Attention habituates. A static element in a high-change environment gets filtered out — the same banner-blindness documented in web advertising. Pins compete with a live, moving timeline and lose.
Discord vs Telegram
Telegram's single sticky pinned bar at the top of a chat is more visible than Discord's tucked-away pin list, so Telegram pins likely decay slower — but still habituate.
The caveat
Click data captures only link-pins; informational pins read without clicking are invisible to this measure, so decay may be overstated for text.
Open question: if pins habituate, is periodic re-pinning (or re-posting) the only way to keep critical info alive?
Pins are the default tool for making information persist. Their actual half-life as an attention surface is short.
What the data shows
Where click-through on pinned links has been measured, engagement concentrates in the hours after pinning and decays steeply within days. A pin that's been up for weeks gets near-zero new clicks — regulars have learned to ignore the pin icon, and newcomers don't think to check it. Pins behave less like permanent signage and more like a fading announcement.
Why it happens
Attention habituates. A static element in a high-change environment gets filtered out — the same banner-blindness documented in web advertising. Pins compete with a live, moving timeline and lose.
Discord vs Telegram
Telegram's single sticky pinned bar at the top of a chat is more visible than Discord's tucked-away pin list, so Telegram pins likely decay slower — but still habituate.
The caveat
Click data captures only link-pins; informational pins read without clicking are invisible to this measure, so decay may be overstated for text.
Open question: if pins habituate, is periodic re-pinning (or re-posting) the only way to keep critical info alive?
The collector problem: members who join and never return
A large share of any server's roster is functionally inert — joined once, never came back. Understanding this 'collector' layer reframes what membership means.
What the data shows
Return-visit instrumentation on Discord servers commonly finds that a large fraction of members never open the server again after join day. Reported single-visit shares of 40–60% are not unusual for servers acquiring via public discovery. These members inflate the headcount and depress every per-member metric.
Why it happens
Platforms make joining nearly frictionless and leaving even more so — most people simply forget rather than leave. The roster becomes a graveyard of one-time visitors, and because they never explicitly leave, they distort denominators indefinitely.
Discord vs Telegram
Telegram's subscriber counts hide this worse: a subscriber who never opens the channel still counts, and there's no native 'last active' for operators to prune against.
The caveat
'Never returned' is hard to measure without privileged telemetry; most operators estimate from message and reaction gaps, which undercount silent readers.
Open question: should community health metrics use returning-member counts as the real denominator and treat the rest as noise?
A large share of any server's roster is functionally inert — joined once, never came back. Understanding this 'collector' layer reframes what membership means.
What the data shows
Return-visit instrumentation on Discord servers commonly finds that a large fraction of members never open the server again after join day. Reported single-visit shares of 40–60% are not unusual for servers acquiring via public discovery. These members inflate the headcount and depress every per-member metric.
Why it happens
Platforms make joining nearly frictionless and leaving even more so — most people simply forget rather than leave. The roster becomes a graveyard of one-time visitors, and because they never explicitly leave, they distort denominators indefinitely.
Discord vs Telegram
Telegram's subscriber counts hide this worse: a subscriber who never opens the channel still counts, and there's no native 'last active' for operators to prune against.
The caveat
'Never returned' is hard to measure without privileged telemetry; most operators estimate from message and reaction gaps, which undercount silent readers.
Open question: should community health metrics use returning-member counts as the real denominator and treat the rest as noise?
Almost nobody reads your rules channel
Servers pour effort into elaborate rules channels. The behavioral evidence is unkind.
What the data shows
Where operators have instrumented rule-gate flows (react-to-agree, captcha-after-rules), drop-off and timing data imply most members click through in seconds — far too fast to have read anything. Some Discord onboarding-screen experiments report read-completion rates in the low single digits for anything past the first short paragraph.
Why it happens
Rules channels are a compliance ritual, not a communication channel. Members treat them like a software EULA: an obstacle between them and the thing they came for. Norm transmission actually happens through observation — what gets reacted to, what gets moderated, how regulars behave.
Discord vs Telegram
Discord's Onboarding screens at least force a pause; Telegram's rules-bot messages scroll away instantly and are essentially never revisited.
The caveat
Click-timing is a proxy, not proof of non-reading; some users genuinely skim fast. And rules channels still serve a real function as a citable reference when enforcing.
Open question: if norms spread by observation, should the 'rules' budget shift from writing them to visibly modeling them?
Servers pour effort into elaborate rules channels. The behavioral evidence is unkind.
What the data shows
Where operators have instrumented rule-gate flows (react-to-agree, captcha-after-rules), drop-off and timing data imply most members click through in seconds — far too fast to have read anything. Some Discord onboarding-screen experiments report read-completion rates in the low single digits for anything past the first short paragraph.
Why it happens
Rules channels are a compliance ritual, not a communication channel. Members treat them like a software EULA: an obstacle between them and the thing they came for. Norm transmission actually happens through observation — what gets reacted to, what gets moderated, how regulars behave.
Discord vs Telegram
Discord's Onboarding screens at least force a pause; Telegram's rules-bot messages scroll away instantly and are essentially never revisited.
The caveat
Click-timing is a proxy, not proof of non-reading; some users genuinely skim fast. And rules channels still serve a real function as a citable reference when enforcing.
Open question: if norms spread by observation, should the 'rules' budget shift from writing them to visibly modeling them?
Telegram broadcast channel vs. discussion group: which to lead with
On Telegram you can open a one-way broadcast channel, a many-to-many group, or link them. Sequencing matters more than people assume.
What the mechanics show
Broadcast channels have effectively unlimited reach, no spam-from-members risk, and post views as a clean metric — but zero member-to-member bonding. Groups create belonging and surface your best contributors, but past ~2,000 active members they descend into noise, and a single bad actor can poison the room for everyone simultaneously.
Why it matters
The two have opposite scaling curves. Broadcast quality is flat regardless of size; group quality decays with size. Leading with a group caps your growth at the point conversation breaks down.
The caveat
The ~2,000 breakdown point varies enormously by topic and moderation intensity — tightly-moderated niche groups stay coherent far larger; open ones break far smaller.
The pattern that scales: broadcast channel as the spine (reach + signal), with a linked discussion group as an opt-in side-room for the minority who want to talk. Most members will only ever read the channel, and that's fine.
Open question: does linking a discussion group cannibalize channel-view counts by giving the same content two homes?
—
Если копаешь topical authority studies — стоит подписаться на @AuthorityFiles
On Telegram you can open a one-way broadcast channel, a many-to-many group, or link them. Sequencing matters more than people assume.
What the mechanics show
Broadcast channels have effectively unlimited reach, no spam-from-members risk, and post views as a clean metric — but zero member-to-member bonding. Groups create belonging and surface your best contributors, but past ~2,000 active members they descend into noise, and a single bad actor can poison the room for everyone simultaneously.
Why it matters
The two have opposite scaling curves. Broadcast quality is flat regardless of size; group quality decays with size. Leading with a group caps your growth at the point conversation breaks down.
The caveat
The ~2,000 breakdown point varies enormously by topic and moderation intensity — tightly-moderated niche groups stay coherent far larger; open ones break far smaller.
The pattern that scales: broadcast channel as the spine (reach + signal), with a linked discussion group as an opt-in side-room for the minority who want to talk. Most members will only ever read the channel, and that's fine.
Open question: does linking a discussion group cannibalize channel-view counts by giving the same content two homes?
—
Если копаешь topical authority studies — стоит подписаться на @AuthorityFiles
The onboarding-channel paradox
A common belief: dump newcomers into a busy general chat so they feel life. The data pushes back.
What the data shows
In a 2024 analysis of 600 Discord communities by Common Room, servers that routed first-day members into a dedicated low-traffic intro channel showed roughly 18% higher 7-day retention than those dropping them straight into #general. The lift was strongest in servers above 5,000 members.
Why it happens
A firehose general channel offers no thread to grab. A newcomer reads 40 messages of inside jokes, finds no reply-able hook, and leaves silent. A quieter intro channel lowers the cost of a first post — and first-post-within-24h is the single strongest predictor of day-30 survival across most studies.
The Discord vs Telegram split
Telegram lacks per-channel permission granularity by default, so the equivalent move is a pinned 'start here' message plus a small topic in a forum group. Weaker effect, because Telegram newcomers rarely scroll up.
The caveat
The Common Room sample skewed toward tech and creator servers; gaming communities behaved differently, and self-selection (better-run servers also build intro channels) means this is correlation with a plausible mechanism, not proven causation.
Open question: is it the channel that retains, or just that thoughtful operators build intro channels and also do ten other things right?
A common belief: dump newcomers into a busy general chat so they feel life. The data pushes back.
What the data shows
In a 2024 analysis of 600 Discord communities by Common Room, servers that routed first-day members into a dedicated low-traffic intro channel showed roughly 18% higher 7-day retention than those dropping them straight into #general. The lift was strongest in servers above 5,000 members.
Why it happens
A firehose general channel offers no thread to grab. A newcomer reads 40 messages of inside jokes, finds no reply-able hook, and leaves silent. A quieter intro channel lowers the cost of a first post — and first-post-within-24h is the single strongest predictor of day-30 survival across most studies.
The Discord vs Telegram split
Telegram lacks per-channel permission granularity by default, so the equivalent move is a pinned 'start here' message plus a small topic in a forum group. Weaker effect, because Telegram newcomers rarely scroll up.
The caveat
The Common Room sample skewed toward tech and creator servers; gaming communities behaved differently, and self-selection (better-run servers also build intro channels) means this is correlation with a plausible mechanism, not proven causation.
Open question: is it the channel that retains, or just that thoughtful operators build intro channels and also do ten other things right?
The DAU/MAU stickiness number lies to small servers
DAU/MAU (daily over monthly active users) is the borrowed product metric everyone quotes. For communities under a few thousand members, it quietly misleads.
What the data shows
Product benchmarks call 20% DAU/MAU 'good' and 50%+ 'exceptional' (Sequoia-era SaaS framing). But community telemetry from several Discord analytics vendors shows small servers routinely posting 40–60% — not because they're sticky, but because a 200-member server with 6 daily talkers mathematically inflates the ratio.
Why it happens
DAU/MAU rewards small denominators. A handful of die-hards in a tiny pool produces a flattering fraction that collapses the moment one regular goes quiet. The metric was designed for products where MAU is large and stable.
Cross-platform note
Telegram makes this worse: 'views' count passive scrollers, so view-based DAU inflates further versus Discord's message-based activity.
The caveat
No public dataset cleanly isolates server-size effect from genre, and 'active' is defined differently by every tool — some count reactions, some only messages. Treat any DAU/MAU below ~1,000 members as a vanity reading.
Open question: what's a stickiness metric that doesn't punish or reward you simply for being small?
DAU/MAU (daily over monthly active users) is the borrowed product metric everyone quotes. For communities under a few thousand members, it quietly misleads.
What the data shows
Product benchmarks call 20% DAU/MAU 'good' and 50%+ 'exceptional' (Sequoia-era SaaS framing). But community telemetry from several Discord analytics vendors shows small servers routinely posting 40–60% — not because they're sticky, but because a 200-member server with 6 daily talkers mathematically inflates the ratio.
Why it happens
DAU/MAU rewards small denominators. A handful of die-hards in a tiny pool produces a flattering fraction that collapses the moment one regular goes quiet. The metric was designed for products where MAU is large and stable.
Cross-platform note
Telegram makes this worse: 'views' count passive scrollers, so view-based DAU inflates further versus Discord's message-based activity.
The caveat
No public dataset cleanly isolates server-size effect from genre, and 'active' is defined differently by every tool — some count reactions, some only messages. Treat any DAU/MAU below ~1,000 members as a vanity reading.
Open question: what's a stickiness metric that doesn't punish or reward you simply for being small?