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
at the moment, the only way to identify a peer in the store is via a hash string of the public key (peerId), but this is not very user friendly. A great idea from @gideonairex is to extract the userId from the public key and set that at the top of each PeerInfo to be browsed by the user or even add in the ability to set a local alias for a particular peer.
This might be accomplished through the use of an extra map in PeerManager. If we wan't to keep the alias local, then it shouldn't be added to the PeerInfo as that might be shared to others.
So our aliasStore might be a mapping of peerIds to alias strings.
The text was updated successfully, but these errors were encountered:
Fix: UDP direct hole punching, high CPU usage and misc.
Closes#135, #134, #133, #132, #129, #127, #126, #123, #121, and #120
See merge request MatrixAI/Engineering/Polykey/js-polykey!130
at the moment, the only way to identify a peer in the store is via a hash string of the public key (peerId), but this is not very user friendly. A great idea from @gideonairex is to extract the userId from the public key and set that at the top of each PeerInfo to be browsed by the user or even add in the ability to set a local alias for a particular peer.
This might be accomplished through the use of an extra map in PeerManager. If we wan't to keep the alias local, then it shouldn't be added to the PeerInfo as that might be shared to others.
So our
aliasStore
might be a mapping of peerIds to alias strings.The text was updated successfully, but these errors were encountered: