Options for Extension

Extensions
1

So I’m essentially stuck between a rock and a hard place, I’ve built out a fully custom UI friendly website for creators and viewers, it allows creators to connect their twitch, Spotify, and effectively create their own custom branded public page for song requests at a “token price” the token is my own economy on my website, but I wanted to make it even friendlier to the Twitch experience and build an extension that essentially produces the public page on the creators panel in their page, but I can’t seem to just “mirror” or house the webpage in the panel itself so I attempted to create my own solution and instead just used a Spotify auth option, but with this solution you still need a backend configuration (Twitch currently doesn’t have this option). Is it possible to just project the broadcasters webpage into the panel (their public page from my website). The website offers solutions to separate track from VOD + other solutions to help creators not get hit with a copyright strike and it maintains sponsorship integrity as it doesn’t allow certain words, topics, etc. offers a family friend playlist filtering automatically (or non-family friendly based on the creator choices) ideally this would allow viewers to have an option to 1) spend tokens from website by authorizing a login, or 2) allows for a bits solution via server less function that tracks the on transaction complete() from twitch (in conjunction with the onBits() functionality).

In short: can I offer a solution that 1) projects the public webpage (I can build in a bits prompt / catch to use the function instead of tokens) 2) maintains integrity and compliance with twitch. So bits only when using the panel, but they have an alternative to visit the website if they’ve already purchased tokens.

2

No. Extensions are served from Twitch as all of that content has to be reviewed every Extension update before users can be released. If you could just display some arbitrary site then there’s no way for Twitch to ensure it always follows required policies/guidelines. Also if you did use any sort of Bits monetization your Extension would likely be rejected due to:

6.2 Bits may not be used within your Extension:
…
6.2.2 To allow an end user to use Bits to play a specific musical track or audio-visual work. (e.g., jukebox-like functionality).

Also if the main intent of your Extension is for a sort of jukebox that plays Spotify music on stream it might also get rejected as Spotify’s TOS explicitly prohibits broadcasting Spotify content. Doesn’t matter if the streamer has all the rights to that music, or that music is able to be distributed by all, the platform itself doesn’t allow users to redistribute music that way.

3

I’ve obtained compliance and approval from Spotify for the use of their API with monetization, the website itself wouldn’t be displayed, but a formulated version of it, I have all the logic fleshed out that would simply call an edge function to my website by obtaining the onBits, onTransactionComplete, and using twitch’s JWT as the verification of the broadcaster/viewer, so it’s not necessarily a direct website inside of the panel, but a panelized version, since their branding, and such is public on my website it pulls the URLs and builds the necessary avatar/branding for the panel.

Is this still not possible?
Since I am technically on Twitch I think you may be right in terms of the Spotify ordeal.