Knowledge base
Connect Mastodon, Bluesky, Telegram, Slack, LinkedIn, Discord or a webhook, and have new content posted for you — held for approval unless you say otherwise.
Social channels lets you connect the places you post, decide what goes out, and have it written and sent for you.
Social channels → Channels → Connect a channel. We support Mastodon, Bluesky, Telegram, Slack, LinkedIn, Discord and a plain webhook for anything else you can receive on.
Each one needs its own credential — a bot token and chat id for Telegram, a webhook URL for Slack and Discord, an account authorisation for the rest. The screen asks for exactly what that channel needs and nothing more.
⛔ A newly added channel reads Not checked yet, which is neither "working" nor "broken" — it means we have not posted to it yet. Use the test post to move it to Ready before you rely on it.
The What gets posted tab is the rule: which content triggers a post, to which channels, and how the text is written. By default the AI writes a separate post per channel, because a sentence that works on LinkedIn does not work on Bluesky and a link-only post works on neither. You can switch to one text everywhere if you would rather.
Posts are held for approval unless you turn that off per rule. They queue on the Activity tab with the text we intend to send, and you release or edit them there. Turning approval off is a deliberate choice on a rule you have watched work.
Tokens expire and get revoked, and the platforms do it without telling you. A channel that starts refusing us goes to Reconnect needed and says so on the Channels tab — we do not quietly stop posting. Reconnect it and the queued posts go out.
Every attempt, its result and the text that was sent. A post that failed says which channel and why, so you are not guessing whether something went out.
What we have been writing about hosting, SEO and running sites at scale.
How hosting shapes indexing and link equity in 2026: keeping pages indexed, vetting aged domains before you build on them, link building without a footprint, and an honest line on what infrastructure can and cannot do for SEO.
Read the post →A practical checklist for fast, secure WordPress: server-level caching, a per-site object cache, the handful of plugins worth running, keeping the stack current, and the WooCommerce pages you must never cache.
Read the post →What actually separates good managed hosting from a cheap box with a control panel — migrations, backups, isolation, real caching and honest scaling — and how to judge it before you commit.
Read the post →Support is included on every plan, the desk is open 24 hours a day, and you can write to us in any of our 58 languages — we answer you in yours.
Contact support → All articles →