Yep, that is indeed intended. It’s mostly a compromise of a few different problems. A common occurrence is that someone accidentally publishes a post for a few seconds and then unpublishes it, in those cases I wouldn’t want to force the author to copy their whole post into a new document if they want to actually publish it a few day layer. Sometimes we’ve also seen people publish major new revisions of posts after a while that deserve another round of attention.
The current solution isn’t perfect, but I tend to manually adjust the date if I notice that a post was accidentally republished, if I notice, which tends to catch a good chunk of the false positives of this policy. In the long-run I would probably want there to be better UI around unpublishing, and maybe some kind of system where you get a limited number of republishings of a post, with UI that makes it clear what is happening.
Yep, that is indeed intended. It’s mostly a compromise of a few different problems. A common occurrence is that someone accidentally publishes a post for a few seconds and then unpublishes it, in those cases I wouldn’t want to force the author to copy their whole post into a new document if they want to actually publish it a few day layer. Sometimes we’ve also seen people publish major new revisions of posts after a while that deserve another round of attention.
The current solution isn’t perfect, but I tend to manually adjust the date if I notice that a post was accidentally republished, if I notice, which tends to catch a good chunk of the false positives of this policy. In the long-run I would probably want there to be better UI around unpublishing, and maybe some kind of system where you get a limited number of republishings of a post, with UI that makes it clear what is happening.