Łukasz Zaroda

> > In case of alpine container following steps helped me. Patch version [(2.7.6)](https://pkgs.alpinelinux.org/package/edge/main/x86/patch) have an option `--no-backup-if-mismatch`. > > ``` > > echo '@em http://dl-cdn.alpinelinux.org/alpine/edge/main' >> /etc/apk/repositories > >...

This theme is amazing. I moved to Arc for a time being, but I cannot wait when Ceti-2 will be updated. I feel like I lost my home ;) .

@al404 Do any streams on http://shoutcast.com/ work for you on Sierra?

I'm also trying to solve this problem. I think [this](https://trac.webkit.org/changeset/201895/trunk/Source) killed Shoutcast, and possibly some other streaming servers. From what I researched, the shoutcast's stream doesn't have proper HTTP headers,...

I think this is a browser's interpretation of headers. I did wget on the stream and raw data shows what I wrote. Browser is simply interpreting it as HTTP/0.9 .

Yep, everything is as expected. "No header, i presume HTTP/0.9" so HTTP/0.9 is presumed when there are no headers (or if headers cannot be understood). I guess that's the convention....

If you want to see the same headers I gave example of, just run wget, close it shortly, and edit the file it downloaded. Those are not technically HTTP headers,...

I reported it to the Webkit team, and reportedly Apple is aware of the problem, and is looking into it, so there is a hope we will get this sorted...

I don't think it will be fixed soon enough, with Chrome damage is already too great. We moved to Shoutcast 2. The workaround to this currently would be to have...

It's already perfectly usable in browser with Webpack 5. You just need [node-polyfill-webpack-plugin](https://www.npmjs.com/package/node-polyfill-webpack-plugin) and additionally in your webpack's configuration: ``` resolve: { fallback: { fs: false, net: false, tls: false,...