{
  "id": 2401071,
  "title": "★ When New DF Posts Drop in a Forest and No One Is There to Read Them",
  "url": "https://urgent.news/2026/08/21/when-new-df-posts-drop-in-a-forest-and-no-one-is-there-to-read-them",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-08-21T16:09:11.000Z",
  "source": {
    "name": "Daring Fireball",
    "slug": "daring-fireball",
    "url": "https://daringfireball.net/2026/08/df_posts_drop_in_a_forest"
  },
  "original_language": "en",
  "account": "Last night, the author noticed a decrease in feedback regarding their recent posts. They expected to hear from readers about both positive and negative reactions, but received no response. This change caught them off guard, as they typically receive feedback from EU readers when discussing Apple and the DMA.\n\nThe author also observed that the bot responsible for auto-posting new articles to DF's Mastodon account had not posted anything since Tuesday night. However, it became clear that the issue wasn't with the Mastodon bot itself, but rather with an issue in the RSS and JSON feeds update task. This task malfunctioned between Tuesday night and Wednesday morning.\n\nInterestingly, the Mastodon bot relies on the RSS feed to determine if there's new content to post. Consequently, with no new articles to post, the bot remained silent. However, the author had overlooked a crucial detail: the DF website homepage is generated from the same RSS feed. This oversight led to the widespread perception that no new articles had been published on the site since Tuesday night.\n\nIn light of this revelation, it becomes apparent why the author hasn't received any feedback from readers over the past few days. By bundling most of the week's output in a single update, the author inadvertently created a situation where readers were unaware of the website's activity. Apologizing for this oversight, the author suggests that the current situation feels akin to a weekly newsletter.\n\nInterestingly, the feed generation script malfunctioned once before, last October. However, this time, the author didn't notice the issue until several hours later. This discrepancy is attributed to a typo in the author's CMS that had previously prevented readers from noticing the issue, as the home page remained unchanged due to the feed content.",
  "summary": "https://daringfireball.net/",
  "key_points": [
    "Author noticed drop in feedback for recent posts",
    "Mastodon bot stopped posting new articles since Tuesday",
    "Website homepage generated from same RSS feed"
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}