RFC 0010 - Extension Management Improvements

[BarryCarlyon]

@bribrobot

Only manually “whitelisted viewers” can access extensions that haven’t been reviewed. (An empty list no longer means anyone can access.)

it’s always been this way as far as I can remember.

@bribrobot

Especially given that there is now a clear viewer disclosure UI, why require a manually restricted whitelist of viewers to test a Hosted Test extension with? It requires a click-through either way.

Because I don’t want EVERYONE to poke about in broken code just my white listed users. But it is annoying to have the extra click.

@bribrobot

The only remaining workflow for quickly iterating on extensions with multiple viewers right now is to manually:

1. Move the extension into Local Test (since you now can’t edit the viewer whitelist while in Hosted Test)

You don’t need to be in Hosted Test to test with a large group.

• Hosted test means “test on the Twitch CDN”
• Local Test means “not on the Twitch CDN but on a base URI you define which could be a real domain/website with the code on it and not always localhost”, there is actually no reason to jump into/back from Local/Hosted test if you need/want to rapidly change the whitelist.

Just leave it in local test and throw your code on a real website URL to test leaving you to easily update the whitelist no need to mode jump