Maybe create a new channel for reporting issues. I...
# ideas-and-suggestions
c
Maybe create a new channel for reporting issues. I know that, in general, bugs should be reported in GitHub and unexpected downtime or blockers can be reported via the dashboard, but since people also use Discord for such problems anyway, a dedicated channel might be worth it
j
open to hear ideas on this. we are currently trying to figure out an internal process for collecting these kind of things - discord is just 1 of many channels of communication we have with users/customers/developers and so on. a dedicated channel in discord might be helpful for the supabase team, since we can import any messages from it into our main feedback system. this channel is already helpful (#867348150741237790), so piping every main message/thread into our feedback system will be something I'm keen to do anyway.
c
to be honest, my main concern is that the uptime Supabase website (https://status.supabase.com/) doesn't seem to reflect issues reported on Discord (unless they are super major). For example, multiple people have reported issues with the dashboard since yesterday evening, and yet the uptime dashboard shows now sign of issues.
I think downtime problems are important enough, that using the regular GitHub issues/discussions flow is just too slow. And while reporting directly the Supabase team via the feedback button is something that, in my opinion, should be the first thing to do, it does NOT allow for people to get a sense of whether the problem is ONLY related to their project or a more wide-spread issue (which is important to know)