#Bunny Stream - VAST
1 messages · Page 1 of 1 (latest)
Hey, I've opened a internal feature request and I'll see what I can do internally. Would a query string parameter to manage this be okay? @rose sierra I was thinking maybe ?ads=false
Would be awesome 👏 , so that premium users could see no ads
What would stop your non-premium users from adding the query string and not receiving ads?
I mean, it is hard to implement a way to disable it for users and keep it enabled without the above being an issue. Generally I would tie it to a cookie or use two libraries and dynamically render the URL depending on what's happening.
Or use a custom player and do it that way.
Would be good to have the new parameter in the Embed view token config perhaps, to prevent users modifying it?
Was debating this internally since currently you can modify query string parameters since we don't include that in the hash itself. Will see what I can do.
You know, if we're dreaming, it would be good to have any of the parameters in the hash and then have a new parameter for the permitted bitrates. Would allow a "if free user then include ads and limit to 720p, but if premium user then disable ads and allow 1080/4k playback" kind of scenario, without the user being able to edit the parameters and/or needing two different stream libraries.
@leaden marsh hey sunil any update for this?
I don't have any to provide yet, the query string idea is the easiest way to implement it I suppose, but advanced users could make a plugin to rewrite embed urls to include this query string.