Nostr Web Client

I’m in

Love it! Let me know what help you need if any.

I see you nostr:npub1c7k2hu076gq62vv9unw9urrt4c4utkce6uatlpq9xhestk8s2xqql8qh4c

mar 2w ago

😂😅 I got curious and excited and wanted to see if I was capable of adding it. I'll be streaming on it tomorrow to test it out for you.

Well something worked! Need to accept TOC otherwise looks GTG

Im shocked you havnt talked to nostr:nprofile1qqsglv2qkn5dmmuhee9cy8fywfu2rfp4xd3xy0myqg2gfvmjl9yqqrqppemhxue69uhkummn9ekx7mp0qythwumn8ghj7un9d3shjtnwdaehgu3wvfskuep0qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0crg0k2 to join your experiment 🤓.

DJ Valerie B LOVE🩷 2w ago

✅ sure

Sebastix 2w ago

Nice work Rod?

Is there an iOS which I can test? For now I was only using the Android version of the app.

Great! Thanks! Yes should work well on both Android and iOS. Both apps have full store releases.

If users like the new server, I can add it automatically in future versions, for now press servers > add server to add it manually.

Here is iOS https://apps.apple.com/au/app/shosho-live-stream-on-nostr/id6747323179

I just did a quick test stream. It post to zap stream under shosho bot? I dont see it under my own npub?

The server tags you as the host, and shosho and other clients should then show it as your stream (even though the "author" npub is the bot that lives on my server). Did ZS website do something different? It looks great here - Short but I see it! https://shosho.live/live/naddr1qvzqqqrkvupzppwlsg4gvkvll05pg0d3u8sm7tgk97nql359ce23t937vl8awjvlqqjrgc3jx9jkxenp95ursvf4956xyvps94skvdm995urzdnpvccrxd3hvvcnwz74uu3

I viewed it on zap.stream and I saw the stream but it was under a shosho bot. Not under my npub. I also didn't see it pop up on amethyst

Its hard to explain. It showed it under a different npub lol. It also had like a group chat that wasn't mine if that makes sense?

Well that sounds like a bug! The Nostr event looks good and it tags you as host, and the replay/thumb etc all work. I even sent you a message on Shosho. Maybe I broke Zap Stream? I will have to check this out. Thanks for the feedback!

Thank you for the amazing app. Cant wait for you to add more features. I have a list of features I can already see I wanting in a app like this 😆. I gotta sleep if I am going to go to work tomorrow 😆. Thank you again for building and working on this. I believe in you 🫡

This may be fixed now. Kieran has made a change to Zap Stream to show your name (as host) rather than Sho Bot's name (the server). Would you be interested to test it again?

I will give it a quick test tonight when im home!

_ 2w ago

just woke up to this. going to test it out lator. good stuff RB

_ 2w ago 💬 1

API Shosho server disconnects after a few minutes of streaming. 👀 👀 .

For me it’s requiring an api URL. What’s next Rod. That link you embedded isn’t loading for me

I made a little demo video, maybe this will help. Please give it a go and let me know how you get on. I hope to make this easier in the new year! nostr:nevent1qqs97x5yh2dpuzwcq6yx63e6z4y2zpd6stj6fsvw3wsgc726esulx4spzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtczyqda5lslwwttmgk3a7vsx0dgl5kuxc5pq7gdlxlx9av3qw9mjlzdjqcyqqqqqqg4fktya

mar 2w ago

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

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

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.

Followed exact instructions and still getting this

Do you see how at the end of the URL there you have some sort of extra characters, like "%22". It''s hard to make out exactly, but it looks like a mistake. Try to copy and paste only the exact URL itself which ends in /api/v1