Social media platform playbook: what works on every Cadencz channel

LinkedIn: teach from work, then invite a professional point of view

LinkedIn's own sharing guide emphasizes fresh perspectives, concrete expertise, questions, conversation, consistent participation, and rich media. For a founder, the strongest raw material is usually a decision with consequences: what changed, why you chose it, and what another operator can learn.

• Best for: business lessons, decisions, customer insight, hiring and launch context.
• Opening: state the change or tension before the company introduction.
• Body: provide enough context for the lesson to stand alone.
• Interaction goal: ask for an example or judgment, then respond to comments.
• Avoid: a vague inspirational hook followed by a product pitch.

X: make one claim easy to understand and easy to answer

A standard X post gives you 280 characters; threads exist when an idea needs connected context. That constraint rewards choosing one observation rather than compressing a whole article into fragments. Use a thread only when each part advances the argument.

• Best for: sharp observations, live commentary, concise build notes, threads with a clear sequence.
• Opening: lead with the claim, result, or disagreement.
• Body: one proof point beats four generic claims.
• Interaction goal: a reply, quote, or useful continuation of the idea.
• Avoid: a long preamble, unexplained link, or thread that repeats the first post.

Threads: write for replies and original conversation

Meta has reported that replies account for almost half of views on Threads and recommends conversation-driving, original posts. Its published creator guidance also suggests adding context to media and testing a consistent rhythm. Treat those figures as platform-reported direction, not a guarantee for any account.

• Best for: conversational opinions, cultural or industry observations, questions, personality.
• Opening: sound like a person entering a conversation, not a brand opening a campaign.
• Body: keep enough context in the post; do not make the image explain everything.
• Interaction goal: replies and follow-up discussion.
• Avoid: mechanically importing an X post without adapting tone or context.

Reddit: earn relevance inside one community

Reddit is not a distribution list. Its spam guidance tells people to contribute authentically in communities they care about, be thoughtful when most contributions link to their own business, and check each community's rules. A useful Reddit post begins with the community's problem, not the marketer's campaign calendar.

• Best for: detailed walkthroughs, honest postmortems, questions, technical or niche discussion.
• Opening: state the problem and why this community is the right place to discuss it.
• Body: include the useful detail in the post instead of forcing a click.
• Interaction goal: informed discussion and direct answers.
• Avoid: identical posts across subreddits, disguised promotion, or automated mass engagement.

Bluesky: join a topic, feed, or live moment

Bluesky does not revolve around one universal feed. Custom feeds can organize around keywords, communities, and live events, while the Discover feed continues to evolve. Write with a specific conversation in mind and learn which feeds or topic conventions your audience actually follows.

• Best for: live commentary, open-web topics, science and tech discussion, community discovery.
• Opening: connect the observation to the topic already in motion.
• Body: one clear idea with language relevant feeds can recognize.
• Interaction goal: replies, follows, and participation in a recurring topic.
• Avoid: assuming one growth hack reaches every custom feed.

Mastodon: optimize for clarity, hashtags, and community norms

Mastodon documentation highlights hashtags as a discovery mechanism and supports per-post visibility, alt text, and content warnings. Server and community norms matter. Use clear hashtags intentionally, write useful alt text, and choose visibility rather than treating every post as a universal broadcast.

• Best for: open-web communities, focused topics, accessible media, thoughtful discussion.
• Opening: a clear subject line-like first sentence works well.
• Body: use descriptive hashtags and full links; link shorteners are discouraged.
• Interaction goal: discussion inside a community and discoverability through followed tags.
• Avoid: copying commercial language that ignores server culture.

Facebook: give the post a reason to matter to a real group of people

Facebook can hold more context than a short-form feed, but length is not the objective. Use a complete update, customer story, local or interest-based relevance, and media that clarifies the point. When a group is the destination, read its rules and write for the group's shared interest rather than treating it as reach inventory.

• Best for: community updates, visual stories, events, customer education, longer product context.
• Interaction goal: comments, shares to relevant people, or a clear next step.
• Avoid: context-free links and the same promotional caption posted into unrelated groups.

Telegram: write like an owned publication

A Telegram channel is closer to an opt-in publication than an open discovery feed. The reader has already chosen the channel, so reward that attention with a clear update, useful detail, and predictable formatting. Use a short headline, the news, why it matters, and one next action.

• Best for: release notes, alerts, curated resources, community briefings.
• Interaction goal: reading, forwarding, reacting, or following one link.
• Avoid: sending several small messages when one edited update would be easier to scan.

Discord: separate announcements from conversation

Discord announcement channels are built to broadcast important updates and can be followed by other servers. Discord suggests uses such as patch notes, daily tips, giveaways, and going-live updates. Keep the announcement complete, then point discussion to the appropriate channel.

• Best for: patch notes, community events, releases, status updates, recurring tips.
• Interaction goal: informed members and discussion in the correct channel.
• Avoid: overusing broad mentions or mixing a long debate into the announcement itself.

Slack: make the message operational

Slack is a workspace, not a public feed. A useful scheduled message helps a team make a decision or take an action. Name the update, summarize what changed, identify the owner or deadline when relevant, and move detailed discussion into a thread.

• Best for: internal launches, customer-community updates, event reminders, decisions.
• Interaction goal: acknowledgment, action, or a focused thread.
• Avoid: marketing hooks that hide the actual update from colleagues or members.

dev.to: teach the complete technical job

DEV is an article community for software practitioners. Tutorials, discussion prompts, technical stories, and series fit the environment better than a social caption. If you cross-post from your own site, use the canonical URL field; if AI assisted the article, follow DEV's disclosure guidance.

• Best for: tutorials, implementation notes, engineering lessons, technical series.
• Opening: make the problem and reader outcome explicit.
• Body: include prerequisites, code or evidence, tradeoffs, and a usable conclusion.
• Interaction goal: help a developer complete or understand something.
• Avoid: expanding a promotional social post into a thin article.

The adaptation checklist

• What is the reader doing on this channel?
• What is the smallest useful idea from the source?
• How much context does this audience need before the lesson?
• Should the desired response be a reply, discussion, click, action, or simply understanding?
• Which platform or community rule could make this post unwelcome?
• Can the post be useful without the product mention?