Closed jbrooksuk closed 7 years ago
I would vote against removing the per component subscriptions. The end users are the most important users of a status page, and they will opt-out and not use it, if they are forced to be sent notifications for components they don't care about.
Okay, so the Twitter poll concluded (closely) that we won't be removing it. This does mean that we'll need a better way of handling per-component subscriptions.
In reference to https://twitter.com/cachethq/status/814868830522667008 this is a proposal to remove the per-component subscriptions. Removing of per-component subscriptions will:
To me, 2 & 3 are the most important parts here and whilst I understand that bigger status pages will have a lot of components that their users generally aren't interested in, we need to be providing features that can be used by a wider audience.
In the future we may be able to re-implement per-component subscriptions, but first we need to nail the UX and channel integrations.