Nostr Web Client

I have just launched a new Nostr Live Streaming Server with recordings and VOD playback of your live streams, so that people can view you live, or come back and watch your replay whenever they like.

I'm looking for testers and am interested in your feedback.

The server uses Cloud Flare live stream as the backend and serves your recordings from there, so should be (I hope!) highly available and responsive.

It also solves the issue we had for Shosho users on iPhone where the server would disconnect mid-stream.

Would you like to try it?

If you are on Shosho and want to test it IRL, click Add Server > Nostr Streaming Server > and then enter: "https://api.shosho.live/api/v1" and the app will connect.

For other systems, the API is based-on and interchangeable-with ZS, so swap "api-core.zap.stream" with "api.shosho.live" and it should "just work".

For those technical folks who can use the above, this is all available for you now. For everyone else I look forward to making this more accessible in the new year!

As always thanks for your help and advice everyone nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 nostr:npub1c7k2hu076gq62vv9unw9urrt4c4utkce6uatlpq9xhestk8s2xqql8qh4c nostr:npub1de6l09erjl9r990q7n9ql0rwh8x8n059ht7a267n0q3qe28wua8q20q0sd nostr:npub1q6ps7m94jfdastx2tx76sj8sq4nxdhlsgmzns2tr4xt6ydx6grzspm0kxr nostr:npub1qe3e5wrvnsgpggtkytxteaqfprz0rgxr8c3l34kk3a9t7e2l3acslezefe nostr:npub1zl3g38a6qypp6py2z07shggg45cu8qex992xpss7d8zrl28mu52s4cjajh nostr:npub1826v365he5ty69lk3xgvzqrwy8587vdfrxnsz0k09khzustf8r7s6j7t95 nostr:npub1j42rxzt0eg3r72ddl4f2psk7q73u2t4ksrumfk0td3rdjxtv2s8qk2u4jf et al

Thank you and looking forward to your feedback!

mar 2w ago 💬 3

Hey, I tested the new Shosho backend today. First off: it’s impressively fast, no buffering at all on my end, noticeably smoother than the other backends.

I did notice a few things while testing though:

The stream stopped after ~30 minutes on the Shosho side, even though OBS was still streaming and the stream continued to show normally on my LFL site. Not sure what triggered the stop, but it might be a timeout or session limit.

In Zap Stream, the streamer name showed up as Shosho (overseer/host) instead of my pubkey, which looks like the same p-tag / overseer issue I’ve seen on my own backend as well. I'll have to ask the ZS dev about this issue.

I couldn’t find any recording or VOD link published back to Nostr (no recording/url tag in the kind:30311 event), since recording is a core feature you mentioned, so I may be missing where that’s exposed.

Overall though, performance-wise it’s excellent, and I’m happy to keep testing

Reply to this note

Please Login to reply.

Discussion

Rod 2w ago

Hi Mar, thanks, great feedback! I found the 30311 event for your stream and you're right. What should have happened was that the recording URL gets added to the Nostr event as a "recording" tag, but that tag is absent. That's a bug. I didn't test extensively with longer streams and so perhaps it relates to a) that disconnection you experienced after 30 minutes, or b) perhaps that longer recordings take more time to process and I need to expand some tolerances. I'll look into it!

Meanwhile here's a link to your recording. https://customer-51tzzrmdygiq19h7.cloudflarestream.com/8e7d68bda62d52a74bcb9d16405835d4/manifest/video.m3u8

Rod 2w ago

Hi Mar, the issue with "Sho Bot" showing instead of your username may be fixed now. Kieran has made a change to Zap Stream. Would you be interested to test it again?

mar 2w ago

I steamed this morning, and yes the problem is fixed. Didn't have any issues on your backend. It was fast as usual.

I don't stream from zap stream, so I noticed I can't accept your TOS but I can still stream. I'll have to look into how to add a TOS button, but the TOS links to zap steam and not the backends website with their own TOS, because I didn't accept my own backend TOS. I'll have to put in a ticket in for backends administrators to have their own TOS.

Another thing I have to test on yours as well, is the stream sats because I've noticed that in 2 backends my steaming sats went down faster then the time I steamed. Started off with 60 sats and by 20 minutes I was out of sats. The price was 1 sat per minute so I should've got 60 minutes. I'm trying to track that down if it's all the backends. The main zap stream backends are 0.01 per minute so hard to notice if that is happening there too. I'll have to put in a ticket for that too. Yours is free so can't test that yet.

but other then that, my stream went well. I'll keep using it and others to see if I can find more bugs.