Open Fire- opened 11 years ago
+1. I'd really want to avoid doing this through scraping.
We've kicked this around a bit internally and haven't settled on a position. Not least because there is a lot of client side logic that would need to move server side. We ended up going the route that we did because we couldn't think of a realistic reason why people would want access to panels - can you guys provide a few cases where it makes sense so that when we come back to this discussion we have something to work with?
On Fri, Dec 21, 2012 at 10:44 AM, Kim Knudsen notifications@github.comwrote:
+1. I'd really want to avoid doing this through scraping.
— Reply to this email directly or view it on GitHubhttps://github.com/justintv/Twitch-API/issues/37#issuecomment-11622970.
The simplest and most obvious problem this would help solve is the complete lack of dynamic content in panels. Updating panels on the fly via script would alleviate that issue because, for instance, you could have an image panel that updates periodically or a text panel that updates with the contents of a Twitter feed every few minutes.
Side: I'm not sure if github emails edits, I fleshed out the resource as I imagined it after creating the issue.
We have plans for dynamic content in panels, we just built the most requested panels first. Twitter panels are definitely going to be next up. Any other examples?
On Fri, Dec 21, 2012 at 11:11 AM, Devon Adkisson notifications@github.comwrote:
The simplest and most obvious problem this would help solve is the complete lack of dynamic content in panels. Updating panels on the fly via script would alleviate that issue because, for instance you could have an image panel that updates periodically or a text panel that updates with the contents of a Twitter feed every few minutes.
— Reply to this email directly or view it on GitHubhttps://github.com/justintv/Twitch-API/issues/37#issuecomment-11623876.
The ability to dynamically create and update panels lends itself to several different things, next thing that comes to mind would be a user with a panel that their Blog dynamically updates with their newest post. Dynamically updated Image panels would allow users to get some of the same functionality as the old style cross-site embedding, but without the inherent exploitability of the latter. A panel that your website updates with the newest joined user, or some such information like that. Interop with other APIs would also come to mind ( Newest friends on Steam, Most recently purchased games, etc ). A dynamically updating donators list, basically any information a website would normally be able to grab fresh on the fly that a user would have to manually update on their panels ( Which they can't do during a cast or while away ).
There's more, but that just what I had on the top of my head.
For myself they're all custom, meaning they can't be just a widget from a well known site. I'd personally use it for a list of donors, custom statistics and statuses in the panels. I'd like to have this in the panels so users can avoid going to an external site for this info.
I run a marketplace website where a lot of our sellers utilize twitch. The reason we'd love to have this feature is to have dynamic panels that display the users current market place items for sale. We were planning on promoting streams for our sellers who link their twitch accounts. In which case we would create a panel for their listed items. And when items sell, we would automatically remove the item from their marketplace panel.
Yesterday I found out about this post, and it was a questioning that the team was looking for about 3 months when we started changing more frequently the panels because we've multiple streamers that produce in our channel. We'd like to delegate the job of Updating the Channel Panels, the thing is that we can't yield the credentials of our channel, since we represent a Company and we can't take risks of inappropriate usage of the Channel. Providing this, would allow to our admins of the app, editing panels even more frequently with more information, and helping us to control this editing activity from our web. Improving this will give the streamers the ability to advertise more accurately.
bump
What now after changing to GraphQL? As I see only the raw data is submitted to the GraphQL-Server
Would be nice to have it implemented! :)
We still need this! Even with twitch panel extensions.
I'd like this for backup and easier editing capabilities. With an API one could make a script that backs up the content of the panels to some file or ideally even a github repo. It could also do the reverse: Change text in gitlab -> script updates content. Would be super handy to have!
It would be a very good addition to Channels to be able to list, add, edit, remove, and reorder panels in the new design. I realize the new design is in beta, but that's the best time to start asking for additions of this type.
GET /channels/:channel/panels/ GET /channels/:channel/panel/:id/ GET /panel/:id/ ( ?.. Maybe not? )
Authenticated: POST /channels/:channel/panels/ ( Content, Type, Position | More than one panel at once? ) PUT /channels/:channel/panel/:id/ ( For updating a specific panel )
Position should probably work like it does on the site, popping it out at that point, placing it at whatever position and incrementing the position of all other panels.