yaa, that's good news. I've been working to get it going already, I’m integrating simulcast into a self-hosted web player using hls . js
The status API works correctly through my server proxy. When a stream is live, the API returns something like:
{
"isLive": true,
"hlsUrl": "https://simulcast.me/hls/.../index.m3u8?apiKey=..."
}
If I open the hlsUrl directly in a browser, I see a valid HLS manifest (#EXTM3U, segment_XXX.ts, etc.), so the HLS pipeline itself is working.
However, when hls . js inside my web player tries to load that same URL, I get:
HLS error: manifestLoadError
This usually happens when the HLS endpoint does not send CORS headers, preventing browsers from fetching the manifest via XHR/fetch.
Would it be possible to enable CORS on the HLS endpoints (for example, Access-Control-Allow-Origin: *)?
This would allow web players using hls . js to load the manifest and segments correctly.