Back in January I started a tiny project called daFeed. It has become my central hub for posting all sorts of updates and syndicating them elsewhere—POSSE in essence. While the idea was simple, the implementation got a bit... messy. I bet on EchoFeed to handle most of the heavy lifting, but as it's now being sunset, I'm gonna have to revise the entire setup. Until now, this is how it looked:

  • Ordinary posts landing on this blog -> RSS Feed -> Tootly. The last part runs as an hourly cronjob in my local k8s setup. I wrote a bit more about the tool here: Tooting toots with Tootly.
  • GhostFeedMe (my own internal tool) took a different approach. It uses Ghost directly as a source of truth by comparing what it wants to publish with what's already out there. It also relies on webhooks instead of polling on a cron, though it can still poll JSON Feeds on an interval (a built-in job instead of a cronjob).
  • Content landing on daFeed comes from all sorts of places: page updates (like Now or Changelog), PPA updates, Micro.blog posts etc. On top of that, some of the content lands directly there and is then syndicated further down the pipe via EchoFeed.
  • Nothing fancy was happening there:
    • New posts tagged Micro.blog on daFeed (my 365 project) -> EchoFeed -> Mastodon
    • New posts tagged Changelog, Links and Status -> EchoFeed -> Mastodon & Micro.blog

Now that EchoFeed is closing, I'm gonna end up extending GhostFeedMe's capabilities, potentially merging it with Tootly to have a single tool handling all the cases.