What is the reason to remove useNicks?

According to https://github.com/jitsi/lib-jitsi-meet/pull/921, the reason is that Octo is incompatible with it. Can someone share the specific cases that can’t be resolved? I thought the nicks were just a prefix and it’d be (in theory) possible to have both.

We use nicks for linking a jitsi endpoint to an internal user-id (the removal will be a rather big headache), we’ve also been using Octo in the past 4 months. I did notice the Octo sessions seem to have problem with the relayed endpoint id but haven’t had enough confidence to pinpoint a cause.

Hi Jerry,

Thanks for bringing this up.

The MUC nicknames are used as endpoint IDs in jitsi-meet, jicofo and jitsi-videobridge. With Octo the ID of the originating endpoint is encoded in each bridge-to-bridge packet[0]. In the current version of the bridge this is not used substantially, which is why things work for you. But in the new version of the bridge the field is used, and Octo will not work without it.

After further discussions, we decided to remove the limitation and bring back the useNicks option. However, we are not going to block the merge of jitsi-videobridge because of it. This means that after after we merge Octo will only work with 8-hex digit endpoint IDs, and useNicks will not be available. Soon afterwards we will work on removing the limitation from the bridge and then reverting the useNicks change.



[0] https://github.com/jitsi/jitsi-videobridge/blob/master/src/main/java/org/jitsi/videobridge/octo/OctoPacket.java#L30