You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the note module is instantiated it can specify a connection and port to pair with, if none is provided, the first voice module to connect with it will become the pair. After pairing, the note module will refuse to connect to any other voice modules, even ones on the same chain, and even in the face of channel closure.
There are two reasons for this behavior:
It improves the UX of sending messages, as there is only one route for them.
It simplifies state in the note module.
We should test (instantiate with pair, pair with first connection) x (won't accept other pairs, reconnects after the channel closes).
The text was updated successfully, but these errors were encountered:
When the note module is instantiated it can specify a connection and port to pair with, if none is provided, the first voice module to connect with it will become the pair. After pairing, the note module will refuse to connect to any other voice modules, even ones on the same chain, and even in the face of channel closure.
There are two reasons for this behavior:
We should test (instantiate with pair, pair with first connection) x (won't accept other pairs, reconnects after the channel closes).
The text was updated successfully, but these errors were encountered: