The fact that something doesn’t happen anymore isn’t either. Is there any data on how many administrators have noticed that Discourse’s behavior has changed? I understand your argument that there were repeated requests on how to prevent bumps. It’s obvious admins notice a bump they don’t want. But if a topic isn’t bumped, you don’t even notice that it hasn’t been bumped, even though you would have liked it to be. So it seems less likely that people ask for that.
For example, I would have liked to have noticed the edits to this post that changed “I will try” into a follow-up question. Just like it would have been nice to see the edit on other posts like Localization of posts on topics with more than 20 posts - #7 by nat
Also, recently the fact that spam is more easily noticed if the topic is bumped came up again. I wonder why this is relevant in the now rather limited case where a post should be bumped during editing. But it didn’t matter when changing the default for most of the posts. Why does a first post that is a wiki need more spam protection that a last post in a topic that is a wiki?
As I have said many times before, I understand the advantages, but there doesn’t seem to be much interest in finding solutions to the disadvantages. It’s no use if there’s a replacement for the current workflows after a year or so. I’ll have to find a new solution now because there is not much time left where there is a supported version of Discourse where an edit of the last post moves the topic to the top.