So for a little more clarification, the website https://i.mjh.nz has the .m3u8 and .xml for:
PlutoTV
Stirr
Plex
Samsung TV+
PBS (a handful of channels, not what it used to be)
However, due to those links being used millions of times, and still being used, using them will leave you susceptible to interruptions in playback when someone else accesses the channel you are watching. So. What this means is that you should only use links from that site as a last resort. For example, I use them for SamsungTV+, Plex, and PBS because I'm aware of no other way / place / etc to find / create those links.
PlutoTV and Stirr:
You have 2 different ways to avoid using the links at https://i.mjh.nz
The docker route (advanced, requires maintenance)
The non-docker route using links from https://nocords.xyz/
This is kind of a no brainer if you don't want to or cant use docker. @HankLloydRight has done a fantastic job adapting the docker scripts to run on his enterprise grade equipment with his own resources so that we don't have to.
I think the SamsungTV now has a docker option (I'm using docker on my Linux server). Pretty sure there is a thread on here if anyone is interested. I don't use it that much, so may drop it soon.
I linked to the non-docker method by @HankLloydRight which is the https://nocords.xyz/ method.
FYI, the creator of that Samsung TV+ docker solution explained that he created it merely as a learning exercise and all itās doing is passing along the exact same mhj.nz links. No metadata massaging at all. So thereās really no benefit to incorporating those channels that way.
I like my little Docker container. Why not work together instead of pushing for a single preferred solution? Collaboration is so much more fun.
Sounds like you're pushing for a single preferred solution?
Besides, they're collaborating already, the code on nocords.xyz leverages maddox's code on github. They are just different methods of incorporating the results into our Channels DVRs.
That would explain why I don't go to those channels frequently.
I am advocating for a alternative deployment. When they come up with a Docker solution, I will consider it. I will also consider contributing to their attempt to monetize the solution.
Yessir you did, but she responded to my older post with the old links before any newer methods, so just wanted to make sure she isn't using the old links.
thanks! I switched it. It did freeze on me a couple of times. Thank you all for your help!
Iām sorry, I donāt understand, If you want to use Docker, use Docker. Thatās what maddoxās code on GitHub is for, Nocords.xyz is for people who donāt want to use Docker. But the end result is the same, So what are advocating a change to?
I was referring to the discussion of SamsungTV Plus above.
Oh, in that case, using the Docker that @matthuisman created (as a test) passes along the exact same data you'd get, if you just subscribed directly to the URLs themselves: Index of /SamsungTVPlus/
So do whatever you want, both solutions co-exist, and work fine. I'm still not understanding what you're advocating a change to.
I misinterpreted your comment about the Docker solution. For whatever reason, I thought you were saying one provided better data than the other. My mistake.
i.mjh.nz is me 
(mjh is my initials)
others playing the same channels shouldn't affect your playback.
It more is probably due to x-discontinuity (ad breaks) in the playlist themselves.
As far as I know - ffmpeg player doesn't really support them
https://trac.ffmpeg.org/ticket/5419
(unless channels has integrated that patch into the ffmpeg they use?)
but if you confirm the other Docker or xcords doesn't have the same issue, then maybe I can look into it some more.
Hi Matt,
I think the core of the problem is that in your all.m3u8 file for PlutoTV, you have:
deviceId=%7BPSID%7D or translated:
deviceId={BPSID}
The problem I believe (I'm definitely no expert on this) is that BPSID has to be unique for each user that accesses the file. When PlutoTV sees the identical deviceId across multiple users when using your file, it blocks them.
https://nocords.xyz gives each user who accesses the file a unique deviceId to prevent the blocks/interruptions. At least that's how I think it works with PlutoTV.
oh right - of course. in my kodi add-on (where most my users are) I replace those with unique ids
thanks for the reply
PS: Are you generating the m3u8 on every call to replace the ids?
Or using something like Cloudflare Workers?
Yup. I could use CF workers, but it's easier this way to do it on the server. The impact on bandwidth for the m3u files is minimal since they're only updated once per day at most. It's the program guide that really sucks up the bandwidth, but I have those edge cached and refreshed once every 30 minutes.
I've updated our DVR to replace the deviceId= with a unique value as well. Will be in the next build.