The "trick" to stop following this blog post does not work if you ever commented on it yourself. Tina Vega and I are still getting spammed every time someone "marks it as helpful" even though we have both stopped following the post. Time to turn off "Inbox" notifications in my community profile "Preferences". I've had enough!

the "curating good replies" is native in the platform. When seeing a question that received many replies, the UX provides quick links to:

the Correct Answer (if there is any)

all the Helpful Answers

That concept is entirely undermined if almost every answer in a thread if marked as "helpful"...this feature is unnecessary, especially when it sits alongside the far more positive 'Like' button. The very fact that someone can also mark a comment as 'Unhelpful' points to why it shouldn't be there, such negative interactions on any social platform are bad practice.

...its also quite ironic (and appropriate) that these 'Marked as helpful' notifications have just today started to now arrive in quarantine, as spam:

Very informal, illustrating that you're taking things easy, and are here to have a good time with everybody

Where was it taken? UK? France?

Kept the previous avatar too, since it was still appearing on a browser tab:

Checked again with tech team.

"we have no short-term way to hack this feature" (thanks Puja Kumari for checking with BMC Engineers, and looped in platform vendor)

Since the problem seems to be too many Email notifications when people mass-click on Helpful, who can come up with an Outlook rule that gets rid of these Emails, and post a screenshot of this rule here?

That would be a great way for the Community to work around something, and create a better Experience for people using Email notifs

Wouldn't it make more sense to limit the "Mark as Helpful" options to those community posts that are marked as "Questions?" The only time I use the "Mark as Helpful" option is when it provides some code or process information that I can (re)use or a link to such information.

Not possible... or not feasible given current priorities and workload? Regardless, it's unfortunate that it can't/won't be able to be done. It could have added a simple, almost invisible change that could have eased the pain for a number of communities members who have become disheartened with the system and how it "communicates" to us.