I’m surprised anyone at Twitch knows about my work, thank you for your kind words
This actually occurred to me earlier today and Clippy now does just that, but the one drawback is that it requires a server-side component to keep those authorization tokens safe, whereas the rest of clippy’s functionality is purely client-side. That’s not irregular for the twitch API, non-expiring refresh tokens work the same way, but it does mean it’s less accessible of an API. Regardless, this design does fix the issue for me at least, so I appreciate you taking the time to reply.
So why not simply add a setting that allows streamers to define a default behavior, and then decide separately for each clip whether it should be made available via the API or not? That way, streamers would have full control without breaking third-party tools. If no clip is available, an info message could just be shown, and if clips are available, they could be played.
@punio85@tekneil While this API doesn’t give us everything we need to fix clip players, it does give enough to implement jbulava’s suggestion, which then allows us to use this new endpoint for clip players. I’ve published my own version of this here, so that you can deploy and use it as well. If you have any questions about it, feel free to open an issue on the repo, I’m glad to help.