Channel Rules

How to post on X, Telegram, and the blog. Different channels, different rules.

All docs

Channel Rules

X (Twitter)

Account: @HusherExchange

Cadence (during house-cleaning phase)

  • 3–5 posts per week
  • Avoid weekends until we have a real audience there
  • No posting between 22:00 and 07:00 AEST (Telegram-region timing skew)

Cadence (post-house-cleaning, when taps turn on)

  • 1–2 posts per day, weekdays
  • 1 thread per week minimum
  • Reactive posts (delisting news, etc.) ship same day, opportunity-driven

Three-pillar mix per week

  • 2 product proof
  • 1 privacy as principle
  • 1 ecosystem / partnership (when there's something real)
  • 1 narrative-arc continuation

Thread rules

  • 5–9 tweets is the sweet spot, hard cap at 12
  • First tweet must stand alone — many readers stop there
  • One sentence per tweet, max 280 chars (use the composer's char counter)
  • End with a link, not a CTA. The CTA is the content.

Reply etiquette

  • Reply to Tier 1 KOL threads only when we have substance to add
  • Never reply to our own posts unless threading
  • No "this!" replies, no engagement-bait, no reply-guying

Do not post

  • Price talk
  • "GM"
  • Engagement bait
  • Generic memes
  • Competitor takedowns
  • "Excited to announce…" copy

Telegram

Bot: @HusherOfficialBot (transactional, not a content channel)

Future: t.me/HusherCommunity (community group) — open this once the house is clean. Light moderation, technical-friendly, ops team checks in daily.

Format for community posts

  • One tight paragraph (max 60 words), then a link
  • No images for product updates (Telegram compresses them poorly)
  • For partnership announcements: 2-3 paragraphs, image acceptable
  • Pin only major announcements (audit, big partnership, security incident response)

Do not post

  • Live rate quotes
  • Anything we wouldn't say on X
  • Anything that wouldn't pass the "screenshot to r/Monero" test

Blog (husher.io/blog)

Cadence: 1–2 posts per month maximum. Long-form is expensive to write well.

Formats we publish

  • Husher Privacy Roundup (monthly) — MiCA, FATF, XMR delistings, new wallet integrations
  • Product launch posts (rare, only for major features like widget, bridge, audit)
  • Incident response posts (only if there's an incident)
  • Technical explainers (route architecture, ESP transparency, refund flow)

Formats we do not publish

  • Generic "10 reasons to use Husher" listicles
  • Comparison shoot-outs with named competitors
  • Token / price commentary
  • Anything an intern could write

Length and structure

  • 800–1500 words
  • Lead with the fact, not the framing
  • One clear thesis per post
  • Sources cited inline with links
  • Australian English, no em dashes, voice guide applies

SEO note

  • We are not in a content-SEO arms race with SwapSpace and Swapzone
  • We do want top placement for "Husher review", "Husher safety", "Husher [coin pair]"
  • We do want to be cited in monero.observer and kycnot.me writeups
  • Blog posts should be linkable and quotable, not keyword-stuffed