Known issue: Op panel problems

Summary

Issue 2: Changing the room topic through the op panel is confusing; changes do not take effect when the user hits "Apply". Instead, the user must hit the Enter key after typing the new topic.

Status

Description

Issue 2: Topic changes do not take effect as expected. This is also minor, but it is confusing.

Technical information

If the room is registered, ChanServ will immediately remove operator status from the user. This disables the operator panel. (Note that there is a race condition that was previously exploitable here: by quickly changing a nick, one could avoid the deop message and retain operator status. This was solved by requiring delays between nickname changes and adding connection-specific GUIDs.)

The operator panel does not close automatically. This leaves the first user to enter a registered room with an unusable floating window.

This problem occurs because the protocol was not originally designed for services. The data currently sent from the server to the client upon joining a room does not include its registration status (which is later set by Services). Therefore, there is no way for the server or user to know if the operator status is temporary or permanent (granted by Services). This is because the server and Services are two logically distinct entities. Issue 2: We have reported this to our software provider; the ticket is #45809.

Possible solutions

• Change the protocol to indicate registration status immediately (not shortly afterwards).
• Add a delay before displaying the operator panel to allow Services to set properties as needed.
• Disable automatic display of the operator panel unless explicitly given operator privileges.
• Add a robot to hold registered rooms open.
• Disable op on join.

Issue 2:

• Press Enter after changing the topic.
• Use the /topic command to change the topic.

Recommended action

Back to top