No, there's no way for a specific user to filter these out on the front page. There are some site settings that can be adjusted to adjust how frequently the bot bumps posts and how often a specific post can be bumped. Before I get to those, though, I'm going to say that I understand the frustration but y'all have the power to address the situation in a way that most askers do not.
I've explained this in depth on several sites - here's a link to the one on Meta Stack Overflow. Please understand, while you may believe there's nothing you can do, there are, in fact, many things you (or someone else on the site) could do. To quote my MSO answer:
The first thing worth considering is whether you have the domain expertise to judge the questions and answers - if not, then it's probably best to leave it for someone else to review. Let's assume you do have that expertise:
- Look at the question first - is it a good question and not a duplicate?
- Yes! (go to 2)
- No! You have two options, you can do one or both of them:
- Close - closed questions will not be bumped. (requires more than one person)
- Downvote - negatively-scoring questions will not be bumped. (most effective if post has a score of 0)
- Look at the zero-score answers one at a time and repeat as necessary.
- If you can confirm the answer is good and correct, upvote - if at least one answer has a score of >= 1, the question will not be bumped.
- If you can confirm the answer is low quality or incorrect, downvote - if all answers have a score <0, the question will not be bumped.
- If you are unsure, skip. Best not to vote if you can't adequately judge the answer.
The steps above apply to the degree you have the privileges to act, of course.
Yes, askers can accept answers but that assumes they are capable of determining whether an answer works - and that they'll ever re-visited the site since asking in the first place. Notifying someone like that is kinda pointless.
Not getting any feedback on the answers is also problematic because you end up with a site full of unverified Q&A just sitting around getting stale. Most of the time, if a site has a lot of questions being bumped, that's an indication of poor community engagement/health. Hiding the content by never getting eyes on it exacerbates the issue.
If a site is attracting a lot of questions that aren't getting closed when they should be, that indicates issues with too few close voters. If answers typically considered not an answer (comments, "me too", etc) aren't being deleted, that's a concern, too; as is having insufficient voting on answers, good or bad.
What was that thing you were saying about site settings?
The most applicable site setting that can be adjusted is the one that prevents the Community bot from bumping a post if there's one already visible in the most recent n posts. There's a list of sites with this settings changed here on MSE.
I would refer sites interested in considering this to the discussions on Android Meta and Arts & Crafts Meta for situations where the request was approved and rejected, respectively. These give some insight into what a site should address in a question if they believe this setting should be enabled. In the Android request, you'll also find some recommendations on how to address very old questions in this state, particularly about tech that may no longer be supported.
What's unlikely is that this would be changed on a network-wide basis, so if someone thinks Community bumping is too onerous on a specific site, they need to start a discussion on the child meta of the site where they feel it needs adjusting. In the near term, though - try to reduce the volume of eligible questions as best you can through other means.
Newestand notActive- except for here.