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
Currently, peers are identified by count, and they are counted simply in the order in which the CreatePeerMessages are processed. This leads to a certain degree of uncertainty as to what peer will have what ID. One idea for a solution would be to give the peers a user-supplied string identifier.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Currently, peers are identified by count, and they are counted simply in the order in which the
CreatePeerMessage
s are processed. This leads to a certain degree of uncertainty as to what peer will have what ID. One idea for a solution would be to give the peers a user-supplied string identifier.The text was updated successfully, but these errors were encountered: