-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow people to set their own name #10
Comments
Maybe it's a silly question, but reading the issue I wondered if we need storage for that or if we should do a thing like ARP that basically works like this:
At this point everybody has all information. WDYT? |
While that would work I'm worried that the amount of meta-information we want to persist into the network is only going to grow over time. We probably want to use something like hypercore https://github.com/mafintosh/hypercore to append data into the network. If we have data about a specific person and we want to privilege that person writing it we can have them sign it with their public key since every peer is identified by a public key. |
Gonna ping @mafintosh to see what he thinks. |
@mikeal if you only wanna sync a simple name simply broadcasting it + a signature to everyone when you connect is pretty simple. if you wanna add more state using hypercore is def the way to go. |
The storage of your name locally is now in and working, so part of this is done. |
Need to add this back in the new version. |
Right now the names are content-editable for each person, so every person on the call can say whatever they like about each person's name and it is only viewable to that person.
It would be nice if when I set my own name it shared that with the swarm and no longer made it content-editable.
The tricky part is have a storage system for this kind of data that gets shared with new participants as well as people who are already on the call.
The text was updated successfully, but these errors were encountered: