Interesting. Since yesterday, Twitch streams do not load anymore on FreeBSD/OpenBSD with Firefox. With Konqueror, it works without problems.
@grubernaut @Iketani Fortunately it's the new default! 
https://bsd.network/web/statuses/101943552500281701
If on 6.4/6.5, or I guess FreeBSD, you can start chrome with '--js-flags=--noexpose_wasm'
@grubernaut @Iketani Oh my brain filtered out Firefox, landry@ has a solution for that.. besides cranking ulimit -d datasize to absurdity (16G!)
@brynet @grubernaut I had a look at it the website, then deactivated javascript.options.wasm (it was activated). Unfortunately, no success. The weird thing is that the streams worked fine till yesterday on the systems, they suddenly stopped working when I switched to a different stream. As it is late here, I will have to check this tomorrow more thoroughly. Thanks for the help though, it is much appreciated :)
@Iketani @grubernaut Oh this is actually something more-- it seems Twitch is playing favourites and checking for the User-Agent.. specifically, it does not like the operating system.
Mozilla/5.0 (X11; OpenBSD amd64; rv:66.0) Gecko/20100101 Firefox/66.0
If you change the User-Agent to be on Linux, Mac or Windows it works.
Mozilla/5.0 (Windows NT 10.0; WOW64; rv:66.0) Gecko/20100101 Firefox/66.0
@brynet @grubernaut Awesome, that solved it for me :)
I have a support ticket already open with Twitch, will ask them about this.
A question out of curiosity: Is there a reason why companies do that?
@Iketani @grubernaut Not any legitimate ones.. there's many ways to do feature detection in browsers without resorting to UA filtering. 
@brynet @grubernaut Well, I am looking forward to the answer from their support then 
@Iketani @grubernaut The reason I didn't notice this before on OpenBSD, because robert@, the chrome port maintainer made the decision awhile ago to include Linux in the UA string by default:
https://marc.info/?l=openbsd-ports-cvs&m=151264513213832&w=2