@jagrim I just wanted to follow up on this because I did some digging.
So, I completely reverse engineered the Android TV authentication flow and built it into Fast Channels just for some fun. And while doing that, I was able to figure out how they count the number of streams. We're currently appearing to be outside of the house, even though we aren't. And essentially, what they do is they like reserve a ticket and it keeps reminting every couple of minutes to confirm that it's still active. And we reserve the ticket and immediately die, essentially. So it never remints, it never looks like it's an active stream, which is almost better in some ways because it just looks like we're on a device that has perhaps crashed or the network has gone down suddenly, which happens, I'm sure, thousands of times a day for them. And it's just a needle in a haystack.
The side effect of this is you should have as many streams as you want, and it should not bark at you about IP address or location or anything like that. This was all my quest to get their digital ad insertion working so I would get ads like local to my market rather than the national feed because it was just bugging my OCD. At the same time, as I got that working, I built the Android TV authentication flow instead of the current one that impersonates a web browser. And while doing that, I figured out exactly how they handle counting streams. Counting them would actually look much worse for us and would probably raise more alarms than just doing it the way it's being done now and just letting the tickets sort of die. I just thought I'd mention that with your grandfathered package, you should be able to stream a couple of sticks and not have a problem, honestly. At the same time, I was also able to build profile support so you can choose what profile Fast Channels runs as so the request looks a little bit more legitimate, and that also helps with the ad insertion functionality I worked out.
I have a feeling, you know, we should be fine because they want our money. They don't care about a bunch of nerds on a forum watching TV on some other app. They care about IPTV farms rebroadcasting.
I will make a suggestion though, just for our own safety and security while doing this. Kinetic Man may want to consider putting the player source in a separate repo, making it private, and keeping it closed source from now on just to make it harder for bad actors to take advantage of this tool. Obviously, you can't protect everything, but there should be something in place to make it really hard to, you know, find this reverse engineering work and then, you know, take it and use it for rebroadcasting or something like that that.