From changelog to social posts: RSS automation that keeps a human in the loop
· OragleGPT
Shipping notes are some of the most useful posts a technical team can make, and also the most often forgotten. Most teams already publish a changelog or blog with an RSS feed. The question is how to turn it into social posts without spamming every network with raw titles.
Why fully automatic posting goes wrong
- Feed titles are written for the blog, not for a 300-character Bluesky post.
- Some entries (a typo fix, an internal note) should not be announced at all.
- Communities like Lemmy and many Mastodon servers dislike automated promotional posts.
A better loop
- Fetch the feed on a schedule and create one draft per new entry.
- Skip anything already seen, using the item's GUID or link.
- A person picks which drafts to post and writes a short version per network.
- The approved posts are scheduled into your normal posting slots.
How GPTpost does it
In GPTpost an RSS feed with a repeat rule is fetched on that schedule, never more than every 15 minutes, with a back-off when the feed is unreachable. Each new item becomes a draft and nothing is published from a feed by itself: the draft goes through the same composer, approval and scheduling as any other post. That keeps the speed of automation and the judgement of a person.