Yet if it's a decent/good idea, my go to answer is "not yet" and not "no". If it's really a great idea, eventually I'll get to it. By keeping the issue around open, it's still peripherally in my vision and I may have a plan to take care of it that depends on something else. Extra information is never wasted and may inform your decisions on what you are working on now. Plus you know, it's kind of the polite thing to do.
I feel it's the same for the original Steve quote, Apple was/is pretty famous for saying "no" to a good idea and revisiting them later. I think "not yet" is closer to the originally meant intent.
Effort is just a strong signal and redoing something you already did that didn’t go anywhere signals a willingness to expend energy on a request that historically went nowhere which is a pretty good signal that it’s important to somebody.
A related truism is people who care about something will email you more than once about it.
May be a good idea if you want people to go away or treat all issues as garbage, nonetheless it is infuriating and nowadays I check for it before making any bug report.
You have Stalebot? I am not going to bother with spending time on bug report.
To be clear, I support aggressive issue triage and closing them.