I can totally understand that it's nice to know whether a feature request is considered or not. I myself am a user of software and have proposed features (even for this forum software). Staying in the dark about whether our idea will eventually be implemented or not is not what our minds like.
However, over the years of being a software developer (especially as a Freeware software developer) I've noticed that I'm not able to comment on every feature request. This has two main reasons. First, often my resources are bound to a totally different feature that I'm implementing right now, or issue that needs to be fixed, or DevOps task that needs urgent attention or — tax declarations. So in such situations it would set a false tone to react quickly on the proposal and — because resources are bound elsewhere — in the worst case, brush it off and simply move on. Second, I often don't need this feature personally. This doesn't mean that it's not useful. And using myself only as a source for decision whether a feature makes sense or not would be not beneficial.
It also would be fatal for the software if I'd jump in and implement most of the requested features right away. Mp3tag would be a funny creature if I did so. I've made some of these mistakes early in the beginning and had to clean up some of the mess I've created. But I'm still carrying the burden of features which I cannot remove easily.
I'm also refraining from posting a template response to every feature request. I think something like "Thanks for your suggestion. We might consider it for a future release." would be not respectful.
What I do instead is to read most of the posts here and see them as a source of potential ideas for improvement. It takes time. It's a slow process. I notice the likes that are given by means of hearts to a feature request (this one is doing pretty good by the way).
Then I see topics that get crowded with links to other possible improvements and feature requests that might be somehow related to the initial requests. This makes it harder to follow the original idea (this one is doing pretty good, also in this regard).
I'm keeping a private internal wish list where I put ideas that make sense. I also see many ways of improving the Filter, and I like the idea of an easy way to edit the filter history.
But I don't have a public ETA for where I put my attention to.