DeepLinks: ESPN+

[bnhf]

@turtletank

This would work. Thanks!

And here are the steps to set it up:

ESPN+ with Custom Channels via ADBTuner

Using recent features added by @turtletank to ADBTuner and @KineticMan to ESPN4cc4c. it's now possible to implement a hybrid of both projects! What you'll get, with the set of steps below, are 40 custom channels with ESPN+ events on them (for ESPN+ subscribers only of course). First, spin up @KineticMan's project, which you can either build locally with his instructions -- or use this Docker Compose to pull it off of Docker Hub: services: eplustv4cc: image: bnhf/eplustv4cc container…

[tonywagner]

@tonywagner

Could Channels implement an additional Stream Link protocol instead, say "redirect://", where it expects to fetch the final Stream Link? So our M3U could contain a generic line like "redirect://localhost:8000/channels/12", Channels would first hit "http://localhost:8000/channels/12", and our app's web server would simply respond with a specific active deep link "sportscenter://x-callback-url/showWatchStream?playID=" for Channels to load.

@tmm1

Hm yea that's interesting. I guess if we know the M3U type is set to STRMLNK, then http could also work. But since some apps use https urls, a new redirect:// like you suggest makes more sense.

@tmm1 do you still think a new "redirect://" STRMLNK protocol might be possible? This would allow programs like this and FruitDeepLinks — Universal Sports Aggregator for Channels DVR to more easily deliver changing content on virtual channels.