Gardens suck. It's easily the worst part about the Web, New or Olde. Worse than UI dark patterns. Worse than user tracking. It's no contest.<p>Stop "updating" content destructively. Nobody raids my bookshelf when an author or publisher decides to put out a new edition of their best-selling work.<p>Stop lying about the identity of your resources. Previously:<p>> <i>I wish SE followed closer to the print tradition instead of the modern Web millieu and clearly identified its microeditions as exactly that: distinct editions of the same text. (Yes, that means there are possibly dozens [or hundreds—maybe even thousands] of different editions [...] No, that's not a problem.)</i><p><<a href="https://news.ycombinator.com/item?id=38835224">https://news.ycombinator.com/item?id=38835224</a>><p>(Assigning the same identifier to multiple resources <i>is</i> a problem.)
> <i>That in turn means that the existing feed specifications serve reasonably well to publish new items but very poorly to notify subscribers about changes to existing items.</i><p>That's a jaw-dropping misunderstanding. RSS items are not the content; they are notifications for something else. The content is elsewhere. When you have some content-object that changes, those changes appear as a train of RSS items. The RSS item is not the thing that it's about.<p>Your expectations and mental model are wrong, not the feed semantics.
The article specifically says it prefers not to be featured on HN at this time:<p>> Given its preliminary, work-in-progress status, I would appreciate it very much if you do not share this to social media, Hacker News, etc.—call it part of the contract for “working with the garage door open”. Thanks!