this isn’t a misleading praise post, like my last one
, because
- Discourse supports a bypass_bump flag when revising a post; it prevents the topic’s bump date from changing even if you edit the last (or first-and-only) post. This is explicitly listed in the PostRevisor options (“- bypass_bump: do not bump the topic, even if last post”).
- This praise topic exists and states exactly that use case.
- Historically people used the /t/{id}/reset-bump-date workaround because this option wasn’t widely known/documented in API docs, but it’s still available if needed.
Practical note: when you PUT /posts/{post_id}.json with the new raw and include bypass_bump=true, the edit won’t surface the topic in /latest. (Official docs don’t spell out this param, but it’s wired up server-side via PostRevisor.)