SMF·PUBLER
Can a prompt replace Publer?
Social media — social scheduling and content repurposing
Exhibit tracking slip
Verdict
Publer's two habits worth copying are bulk import and recycling: paste a hundred posts from a spreadsheet, and let the good ones repeat on a rotation instead of dying after one impression. Both are ordinary code. The cost is the same as every scheduler in this catalogue: each network is a developer account, an app review and a set of rate limits that change without notice, and recycling in particular runs straight into platform rules about duplicate content.
Exhibit A — The prompt
Received on31.07.2026Build a personal social scheduler built around bulk import and evergreen recycling.
Connect exactly one network through its documented OAuth flow, with encrypted token storage and a visible reconnect flow on expiry.
Bulk import: accept a CSV with columns for text, media path, tags and an optional explicit publish time. Validate every row before importing anything — character count against the network's real limit, media file existence, dimensions and size — and show a per-row report so the user fixes the file rather than discovering failures three days later. Importing 200 rows must be one transaction that either lands entirely or not at all.
Time grid: instead of scheduling each post individually, define slots (for example weekdays at 09:00, 13:00 and 18:00, weekends at 11:00). Queued posts fill the next free slots in order. Dragging a post reorders the queue rather than setting a timestamp, which is what makes bulk work tolerable.
Recycling: any post can be marked evergreen with a minimum interval, defaulting to 90 days. Evergreen posts return to the queue after their interval, but only into slots not already filled by fresh content. Track how many times each has run and its per-run engagement if the network exposes it, and automatically retire one whose engagement has fallen below a threshold across three runs.
Duplicate-content guard: before re-publishing an evergreen post, compare it against the last N published posts and refuse if the text is identical to something published within a configurable window. Warn in the interface that most networks discourage or penalise identical repeated posts, and require the user to vary the text themselves. Do not generate variations automatically.
Publishing: a background worker with idempotency keys, exponential backoff on rate limits, and failures surfaced with the platform's own error text rather than a generic message.
Out of scope: additional networks, scraping or unofficial API use, a browser extension, analytics dashboards, and team accounts.Opening prefills the prompt — press enter to run it.
Exhibit B — What you lose
- B.1 every network beyond the one you got API approval for
- B.2 the browser extension that schedules from any page
- B.3 AI-generated variations of an evergreen post to avoid duplicate-content flags
- B.4 team workspaces and per-client separation
Prior art
Exhibit C — Why people still pay: API access, connector upkeep, and collaboration
Because twelve dollars a month for someone else to keep six platform integrations alive is less than the cost of the first weekend you spend repairing one of them.
Questions
Can I import my Publer queue?
Yes, and this is the one migration in the category that works well. Publer exports scheduled posts as CSV, which is exactly the format the bulk importer expects. Media has to be downloaded separately and re-pathed, and recycling history does not come across.
Is recycling actually safe to do?
With care. Networks vary from indifferent to actively penalising identical repeated posts, which is why the prompt blocks exact duplicates within a window and refuses to auto-generate variations. The intended workflow is that you rewrite an evergreen post before it runs again.
What does it cost to run?
A small VPS with PostgreSQL, five to ten dollars a month, plus local media storage. That is roughly the price of the Professional plan, so the case for building it is control and one network, not savings.
What is the one thing that does not survive the rebuild?
Breadth. Publer's value is one queue feeding six networks at once, and this build feeds one. Every additional network is a separate developer account and app review, and some networks will simply refuse a personal application.
Related tools
Receipt