Hootsuite

Promptfree, for everyone, and the only version there is

Copy the prompt for Claude CodeCopy the prompt for CodexCopy the prompt for Cursor

Copy

Do not build this. The obstacle is not code and it has got worse.

**Publishing permission is granted by the networks, and several no longer grant it** to independent developers, or grant it only at a tier that costs more than this subscription. Reading comments and messages across networks needs the same permissions again. That access is the product now.

WHAT TO DO FIRST
- Check today, for the one network that actually matters to you, whether an independent developer can still get publishing access and what it costs. Write the answer down with the date
- If the answer is no, no amount of good software fixes it, and that settles the question

WHEN TO KEEP PAYING
- Several networks, several people, and an approval step before anything goes out
- A shared inbox for comments and messages, which needs the same permissions and is the half people forget

WHAT YOU CAN BUILD REGARDLESS
- **The composer and the calendar.** Writing well is the hard part, and copying a finished post out to publish by hand costs ten seconds. That half works whatever the networks decide
- Per-network validation as data: character counts and how they are counted, media limits, aspect ratios, whether threads or a first comment are supported. Checked at scheduling time, not at publish time
- A preview per network at the size it will actually appear
- **Link clicks through your own short domain**, which is the one number nobody can take away and often the most meaningful one you have
- Your own archive of everything you posted, with metrics collected on a schedule afterwards and appended rather than overwritten. When a network changes what it reports, your history survives

IF YOU DO GET ACCESS
- One row per network per post, and idempotent publishing: a timeout may still have published, so check before retrying. A duplicate post is a public embarrassment
- Tokens refreshed under a lock, because two workers refreshing at once invalidate each other

THE ONE-LINE VERSION
Check the access before writing anything. Build the composer and your own short domain either way.