Allow us to embed the clip editor.

I have a personal site that I used to list and view all of my clips that I make during a stream. I also have functions for tagging my clips for easier searching, and other implementations.

Currently, I have to link to the edit page, to edit the clip to the desired length and position. Then, go back to my site to embed the clip player, where I have my extra functionality. My desired work flow would be to just embed the edit page, so that I could use my page's tagging functions in a much quicker, and easier way.

You get free tools to differentiate your platform. Passionate developers try their best to make amazing products, how hard is it so difficult to make their products visible for streamers?

Multiple suggestions:

• a monthly highlight message on twitch twitter (put the spotlight on a great extension)
• improve the extension dashboard by removing the top categories based on their function. This should NOT be a standard to get the top spot.
• let developers upload videos/trailers on the extension page.
• make a simple checkbox, that allows developers to send updates (email, chat notification) to streamers that opt-in for updates. (how do developers communicate to their 2000 users that the extension received a new function??)
• Run another dev contest

Thanks for reading. <3, Jeroen

The endpoint /helix/subscriptions?broadcaster_id=USER_ID doesn't return the data from the most recent to the oldest subscriber.

We could maybe use /helix/subscriptions/events?broadcaster_id=ID but the data here apparently doesn't last more than 5 days or so. This doesn't work for small streamers who don't have a lot of subscribers coming on a daily basis, for example.

Suggestions:

1. Create an "order" parameter to the first endpoint, so we could use like /helix/subscriptions?broadcaster_id=USER_ID&order=desc&limit=1
2. Make the second endpoint return the latest "forever".

The first endpoint seems buggy, the data being returned comes in random order and the pagination cursor is always present, even if I clearly don't have more results or that's the last page. According to the docs, the pagination cursor should don't return anything in that case.

Even If I use the pagination cursor to fetch ALL subscribers, with 100 results per page, it wouldn't be worth doing 10 calls if a streamer has 1000+ subscribers just to get the latest, for example, this would take A LOT of time to go through all those pages.

It would be very easy to build and design for if there were official typing for all data endpoints. The data between all the different API's for the same data isn't consistent, and with event sub, since it no longer relies on the underlying Helix endpoint, that data can now be different too. This will also mitigate typos on the docs which causes huge headaches when trying to code for API responses and the data not working, or missing fields. The typing can specify which fields are required and which are optional, so when designing your app, you can easily make those checks.

An example is the Extension transaction data. On the ext helper, you get a signed receipt, but on the API end point, you don't. So depending on where you get the data, you need to code for 2 different scenarios for the same exact data.

Currently, when a non-Englisch Character is entered into the "Name" Field of the Application Settings (https://dev.twitch.tv/console/apps/<CLIENTID>), it is denied with the Error Message saying that the word "Twitch" is not allowed, even if that is not entered.

1) This Error Message is confusing as it is incorrectly describing the situation.
2) For some usecases, Non-English Characters would help for Names - such as German Companies with umlauts (öäü) in their name.

I acknowledge that allowing the entire Unicde / UTF-8 subset can pose issues, but It makes it so an Application Name may not be 100% identifying of the Name of the actual Application / Third Party and thus potentially create doubt.