-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Include key in stream URL in livestream modal #3568
Comments
I don't think the UX problem stems from us here, but rather from Jitsi’s reliance on YouTube as a default and thus hiding what should be another field: the live stream URL. Covering that special case by adding it in our documentation examples should be enough IMHO. |
ok. the documentation seems to be updated to jitsi meet but we need to either tell the users to put url/key when there is just one box like in the case of android streamers or provide that ourselves in the information box. |
I agree with @rigelk. It seems to be an UX issue from these software, because the URL is public whereas the stream key must be private. We could add another field that merges the base RTMP URL and stream key, but it would be just more confusing for users. |
Describe the current behavior
currently the live stream live information modal displays rtmp url and stream key in two separate boxes because services like OBS expect them in separate boxes.
the issue is services like jitsi meet and even android rtmp servers show a single input box where the user is expected to input rtmp url followed by "/" and then stream key.
this ui quirk is not explained by the live information modal in peertube and this leads to people only putting rtmp url in the box without the key.
Describe the expected behavior
my suggestion is to add the following to the live information modal,
If your live streaming software has only one input box, you must put your Live RTMP Url and Live stream key in the following manner:
Live RTMP Url/Live stream key
jitsi/jitsi-meet#8283 (comment)
this comment is the example of this ux quirk.
The text was updated successfully, but these errors were encountered: