SMF·VISTA-SOCIAL
Can a prompt replace Vista Social?
Social media — social scheduling and content repurposing
Exhibit tracking slip
Verdict
Scheduling is the part of this category everybody builds. Vista Social's harder half is the inbox: pulling comments, mentions and replies off your published posts into a triage queue where none of them gets missed. Building that for one network is a weekend of polling, deduplication and read-state tracking. Building it for the six a real account uses means six developer approvals, and comment-read permissions are exactly what platforms are most reluctant to grant.
Exhibit A — The prompt
Received on31.07.2026Build a social engagement inbox for one network. Publishing is secondary here; the queue is the product.
Connection: register a developer application and request the permissions needed to read comments and mentions on your own content — note in the README that this is a stricter permission set than posting, and that some platforms refuse it for personal applications. Run the documented OAuth flow, store tokens encrypted, and surface a reconnect flow on expiry.
Collection: on a schedule, for each of your published posts within a recency window, fetch comments and replies. Separately fetch mentions of your account where the API exposes them. Store each item with its platform id, author handle, text, timestamp, parent post, and thread position. Deduplicate on platform id — polling overlaps and a queue full of duplicates is a queue nobody uses.
The queue, which is the point of this build:
- Items in one list, oldest first by default, with a state: new, read, replied, or dismissed with a reason.
- Threading: an item's replies grouped under it, so a conversation is handled as a conversation.
- Filters: unhandled only, by post, by author, by date, and a text search.
- Keyboard operation throughout — j and k to move, r to reply, e to dismiss — because a queue is worked through, not browsed.
- A saved-replies library with placeholders for the author's handle, since most replies in practice are variations on five answers.
Replying: post the reply through the official API, store the returned id, and mark the item replied with the text sent. Never scrape and never automate a reply — a queue that answers on your behalf is a bot, and it is the thing that gets accounts restricted.
Rate limits and backfill: respect the platform's limits with a token bucket, and on first connection backfill only a bounded window (defaulting to 30 days) rather than the whole history, with progress shown. An unbounded first sync is how a new integration exhausts its quota on day one.
Health: show when each poll last ran and succeeded, and warn when collection has been failing, because a silently broken inbox looks exactly like a quiet week.
Also build: a minimal scheduler — compose, queue, publish through a background worker with idempotency — since the inbox needs posts to attach to, but keep it deliberately thin.
Out of scope: additional networks, review management on business listings, social listening beyond your own posts and mentions, analytics dashboards, and any automated or AI-generated reply.Opening prefills the prompt — press enter to run it.
Exhibit B — What you lose
- B.1 every network beyond the one whose comment permissions you were granted
- B.2 the review management across Google and Facebook business listings
- B.3 social listening for mentions that do not touch your own posts
- B.4 the analytics and reporting suite alongside
Prior art
Exhibit C — Why people still pay: API access, connector upkeep, and collaboration
Because an inbox that covers one network is not an inbox. The value is that nothing anywhere goes unanswered, and that means permissions on every platform at once.
Questions
Can I import my Vista Social data?
Scheduled and published posts export as CSV. The inbox history — which comments were handled and how — does not export, so the queue starts from your backfill window on the day you connect.
How hard is getting comment-read permission?
Harder than posting permission, and this is the practical gate on the whole build. Platforms treat reading other people's comments as a higher-risk permission and several will not grant it to a personal application at all. Check the specific network's current policy before starting.
What does it cost to run?
A small VPS with PostgreSQL, five to ten dollars a month. The APIs are free at personal volumes, though comment polling consumes rate limit faster than scheduling does, which is why the bounded backfill and the token bucket are in the prompt.
What is the one thing that does not survive the rebuild?
Coverage. The point of an engagement inbox is that nothing is missed anywhere, and a queue covering one network out of five means four places where a customer question sits unanswered. That is not a partial version of the feature — it is the absence of it.
Related tools
Receipt