nostr:nprofile1qqs2vrneurk665gq6a2rke572y7mc8ppwr5wnd60mw8fwxharc8xsycpzemhxue69uhkzat5dqhxummnw3erztnrdakj7qgwwaehxw309ahx7uewd3hkctc82ymh5 nostr:nprofile1qqstyu3d68snl7dc9le0gvscvqvsghlw8xg364jj666zvdtzqcd0jzqpz4mhxue69uhk2er9dchxummnw3ezumrpdejqzrthwden5te0dehhxtnvdakq5f4vlp I've tried other livestreams. They worked fine. Tried different ones. No problems.
Any ideas guys?
Login to reply
Replies (4)
I couldn’t see your comments so can you give me more context on what you did and didn’t try?
Seems the mobile apps were sketchy yesterday morning. Both iOS and GrapheneOS for some reason. I used Primal Web for the Friday live stream and it worked without a hitch.
Any explanations what could be the cause?
Do they provide different servers for different platforms❓
Different streams/codecs for different platforms❓
Other livestreams on nostr I've tested immediately on mobile have worked fine.
nostr:nprofile1qqs2vrneurk665gq6a2rke572y7mc8ppwr5wnd60mw8fwxharc8xsycpzemhxue69uhkzat5dqhxummnw3erztnrdakj7qgwwaehxw309ahx7uewd3hkctc82ymh5
Not sure, we only have one Nostr output pointed to zap.stream and everything else should just pick it up. That’s how it’s worked in previous weeks.