Solved improvements: Allowing members to indicate they're experiencing a reported issue

I think the “Me too” idea is great.

This is something that has been needed for years. That said, the way I would ideally like to see it implemented may not dovetail with how I understand the current design.

My understanding is that this feature is scoped to the world of Discourse topics. On the OpenAI forum, for example, there is often a broader need for a “Me too” signal when users are affected by outages or service issues, such as OpenAI servers being down, a specific API endpoint not responding, or a Codex regression affecting multiple users.

However, those cases are often tied to systems outside Discourse, such as:

From what I understand, this update does not interact with those external systems. It helps members indicate that they are experiencing the same issue in a Discourse topic and opt in to receive a notification when that topic is solved, but it does not appear to connect that signal to an external status page, GitHub issue, or incident tracker.

A recent OpenAI forum example is this topic:

https://community.openai.com/t/realtime-api-sip-inbound-calls-failing-again-before-webhook-dispatch/1380763

That topic collected multiple user reports and was later linked to this OpenAI Status incident:

https://status.openai.com/incidents/01KRG0AZKH41DV4D9SNJSXM33Q

So, is my understanding correct that the current “Me too” feature is limited to Discourse topics themselves, and does not currently provide a way to connect or synchronize that signal with external systems such as status pages or GitHub issues?

1 Like