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
Since peers are unique the name should be shared in the database
📝 Detailed Description
Hello,
Since every peer ID is unique once the name has been set on any network for a certain peer the name should cross to any other network .
This is because in a lot of cases a similar equipment FE a laptop from a manager can be allowed access to different networks but in all the networks the filed to set the name is empty so the idea is to have a unique name for the seme peer on any network.
🎯 Use Case
The same peer will be all ready named on any network if it exists on the system and it has a name
The peer name will be shared between networks
💡 Willing to Contribute
Yes, I could help with testing
The text was updated successfully, but these errors were encountered:
🚀 Feature Summary
Since peers are unique the name should be shared in the database
📝 Detailed Description
Hello,
Since every peer ID is unique once the name has been set on any network for a certain peer the name should cross to any other network .
This is because in a lot of cases a similar equipment FE a laptop from a manager can be allowed access to different networks but in all the networks the filed to set the name is empty so the idea is to have a unique name for the seme peer on any network.
🎯 Use Case
The same peer will be all ready named on any network if it exists on the system and it has a name
The peer name will be shared between networks
💡 Willing to Contribute
Yes, I could help with testing
The text was updated successfully, but these errors were encountered: