I’d prefer letting the user actually turning off/on the extension, as it’s possible the only reason to turn it off is to put another extension in it’s place, or it’s a game specific extension and the streamer is not playing that game.
Alternatively what you and @dash describe mentions makes sense.
- Store on/off using the configuration service,
- when you update on off
- store the payload in the configuration service,
- also send the update over pubsub
This will minimise the viewer front end making requests to your EBS if your front end checks Twitch configuration service first.