Thanks everyone for the great conversation so far!
@Marenthyu As @xzion pointed out – we’re definitely envisioning a future where extensions can do more with chat than just send messages. In the future, it will hopefully only make sense to build a chatbot as an extension. That, of course, won’t be the case once this RFC lands but this is just a stepping stone to get us there.
@moocat The main issue we’re trying to solve with this addition is the one of “channel page presence” for extensions. Right now, it’s really hard for an Extension to let a viewer know they should be paying attention. We’re hoping by adding these features extension developers will be able to provide some sort of “call to action” to the viewer informing them they should be looking at the extension. As I mentioned just above, we’re working towards a future with many more features and integrations with chat and this is the first step which we plan to grow and learn from. Regarding multiple extensions: we will be queuing up these messages on the front-end so 6 different extensions send a pinned message at the same time, they will appear one after each other in the order received.
@ehgoodenough For this version, we will only be supporting the main, Stream Chat.