I tried again and same issues. I didn't see any new network errors. This time tho, I did time it, I started my OBS, using my rtmp and key, and after 5 minutes it disconnects by itself. I'm not sure if that's normal since it didn't play on my player and I tired that website but just a black screen. if I disable the API and stream forward to twitch it works right away. I wanted to try API & twitch but I don't have a NWC wallet to try both at the moment

I couldn't even get a lightning address on primal, they blacklisted me. Primal sucks. I use Amethyst

I started a stream from OBS and kept it running. The HLS URL https:// simulcast . me/hls/8e4551823a23f584/index . m3u8?apiKey=... loads in the Akamai hls .js player, but it only shows a black screen and stops after ~8 seconds even though OBS remains connected and streaming. No errors, just a short black clip. Your client can reach his HLS. The problem is the content/encoding, not your player.

did you check your username in the settings icon, account settings, profile information, shaketag it will show example: @ username you would then put that in your amethyst client in your profile edit section, as: [email protected]

I’m trying to play my stream from my domain using hls .js. Your status endpoint returns: { "isLive": true, "hlsUrl": "https://simulcast.me/hls/8e4551823a23f584/index.m3u8?apiKey=-zlqHdG0KoqskMKLfnCfsH9zfKZ8oOe-", "streamKeyLabel": "test", "playbackToken": "8e4551823a23f584", ... } But when my browser (or hls.js) requests that URL, I get: Status: 404 Not Found Content-Type: application/json; charset=utf-8 Body: JSON error (not an .m3u8 playlist) Hls . js reports: type: "networkError" details: "manifestLoadError" fatal: true url: "https://simulcast.me/hls/8e4551823a23f584/index.m3u8?apiKey=..." So your API says isLive: true with that hlsUrl, but the manifest URL returns 404. Can you check why that HLS path doesn’t exist or why it’s returning JSON instead of the .m3u8 file

no problem, I've been testing all other stream services, happy to help, I tested the hls stream again after your change. The good news, my web player can now request the manifest, so cors is definitely working. However, I’m seeing a few new issues when streaming from OBS, The stream comes online, then drops offline Sometimes it appears in the player for a moment, then the player reports the stream as offline again. A few seconds later it may come back, then drop again. hls buffer append error & Autoplay failed: DOMException: The fetching process for the media resource was aborted hls buffer append error It looks like the manifest loads correctly, but some of the .ts segments might be failing intermittently, which triggers hls . js to treat the stream as broken and drop back to “offline.” summary OBS to Simulcast detects “stream online” Player starts loading segments Buffer append fails intermittently hls . js recovers - fails - recovers - fails (stream flickers online/offline)

ShakePay a Canadian Bitcoin company enabled lightning payments today. I tested their lighting addresses on nostr and it worked. I used the following format: [email protected] They give you free sats for shaking your phone once a day. About 21 sats or so. #shakepay

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.

Catoshi keeps warning me about the glow in the blue closet. I keep ignoring it.. but somehow.. I'm more productive than ever. #marandcatoshi

derek helped me understand how to use ai to learn coding, he's a good guy

Yeah, one thing that would be cool in the future is some kind of public playback URL or HLS endpoint for each live stream. Something simple like /stream/{id}.m3u8 that apps or websites could embed. Not urgent, but it would open up a lot of integrations because Im also building a small streaming project for my own site, and having a simple public playback URL would make it easier to integrate external sources like yours. Nothing complex, just something that tools can read when a stream is live.

jin invited his friend to eat chicken together

so I figured out why everytime I clicked on a livestream shosho link from mobile Firefox browser it wouldn't play, it was because I always use ad blockers, I use unblock orgin and I didn't realize to turn it off because on mobile it's hidden in the settings, once turned off it plays, I never had that issue on desktop browser, just thought I'd let you know

ya paying for X is dumb, don't support fake propaganda apps. Use that money somewhere else.

that's why I suggested an option in Amethyst so everyone can willingly pay a subscription every month to the app, either using NWC or at the end of the month you can a notification for renewal, they could give you an optional badge to display on your profile saying you are a subscriber and nothing more,

mar is.. looking forward to playing this game, unlike starfox.. that means this game is good Let's Fo live at: 🔴 https://mar101xy.com/live 🟣 Nostr: #livestream #gaming #letsfo-live-global

blogs are dead, blogging is dead,