Browser for streamfab (becoming out of date)

Stan001

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36

Chrome:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/149.0.0.0 Safari/537.36

Mirosoft Edge:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/149.0.0.0 Safari/537.36 Edg/149.0.0.0

It seems to start causing issues on certain websites. How about StreamFab updating it?

0xFeedBeef

Stan001 I would actually go two steps further and say that the browser agent info string must match decryption used, so where SF uses playready, it must tell site it’s MS Edge, where it uses widevine, it must tell it’s Chrome. The simple reason is that it’s trivial to start detecting anomalous behaviour on the vendor site: “why would Chrome start using playready?” for example.

Secondly, one could go a step further and make per provider string customisable via registry, for example

Stan001

0xFeedBeef

Not sure SF will do that, but version of their browser 144 and latest Chrome 149.

This is causing some more issues on some websites, and as the versions increase, the problems spread; even a few are claiming issues on Amazon now about updating their browsers.
I know when we got it before, SF still downloaded, but that’s just the beginning.

The same as there are no settings in VIP for Paramount :/

Germania

0xFeedBeef where SF uses playready, it must tell site it’s MS Edge

It’s possible to use PlayReady with Chrome - but not with Win10 => info

However, I wouldn’t want to dispute that regarding compatibility (and for Win10).

0xFeedBeef

Germania yes, but your navigator.mediaCapabilities.decodingInfo(…) needs to lie that it is supported, and there’s no reason to assume that browser capabilities aren’t fed back into the provider’s backend 🤷‍♂️

MrGrackle

I generally do not update my personal browser for months and months and never see an issue. How far behind is SF?

Germania

MrGrackle How far behind is SF?

144 is only the user agent ..
.. SF use CEF 142.0.7444.135 from 11/11/2025

Current CEF Stable Build is 149.0.7827.197

Cats4U

Germania

Is there anyway to patch in CEF 149? If anyone here would have been able to do it already, it would have been you, Germania. I tried it a few times, and it seemed that something in the SF source was naming the old CEF, and I wound up with errors and failure. Probably why they are using the user agent, which would be easier to switch. Some sites are using User-Agent Client Hints to see through such changes. 0xFeedBeef referred to that above.

Germania

Cats4U Is there anyway to patch in CEF 149?

Perhaps some minor changes - but never major updates ..
.. to many dll calls fails