As I understand nostr:nprofile1qqsv73dxhgfk8tt76gf6q788zrfyz9dwwgwfk3aar6l5gk82a76v9fgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszxthwden5te0wfjkccte9eekummjwsh8xmmrd9skctcppemhxue69uhkummn9ekx7mp0dutak6 the app is for viewers of the stream, not for the streamer themselves.

To start a stream I add zap.stream rtmp and streamkey to my broadcast app, and it makes that part easy.

And I can use any broadcast app, like prism or larix or whatever, so long as it can push to rtmp.

BUT, if you as a viewer message me on zap.stream (or zap me, or whatever), my broadcast app doesn't show me this. To see it, I will have to run and watch a second completey separate device in order to see my audience chat.

Big gap

Reply to this note

Please Login to reply.

Discussion

That's not exclusively a zap stream problem mind you.

Was chatting with a guy who uses whatnot to break baseball cards on live stream. He says the key to being a good streamer is to provide good entertainment and audience engagement.

Pushing the video is just the start, seeing and responding to chat etc are all critical for him.

Oh, I see now. That’s definitely something that should be looked into. I guess this will be easily fixable when we have Nostr-native broadcast apps.

Do you know is someone already working on Nostr-native broadcast apps?

To be honest I didn’t know this was a thing 😅 I thought it was just a feature in every streaming app type of thing.

I might hack on this tomorrow. I think I know where to start