-
Notifications
You must be signed in to change notification settings - Fork 11
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
only chatroom identify DEADCAFE works #43
Comments
Hi @electricimp123, Then share this chatroom identity with someone else who you would like to add here and begin your conversations. As one of the features of the chatroom is transience - no message is kept back once the client leaves or refreshes the page so a default identity of |
Thank you for your reply. What I am saying is that, in my case, though I was able to connect multiple clients to a generated chatroom identity, I was not able to see the various connections actually chat with each other (ie, whatever each client typed was not reflected in the other connections). I tried this multiple times so it was not just a typo in the chatroom identity. The only time it worked as expected was when I happened to notice "DEADCAFE" and just used that as the identity. Another way to say it perhaps is that newly generated identities are NOT working, but the standard identity is. |
I understood your question properly now I guess. All the clients are expected to have the same identity if they wish to be in the same chatroom. Even a slight change in the identity means it's a new chatroom and any conversation that you make with the older identity would not be reflected in the newer one.
Just share the newly generated identity with others and ask them to join. It should work as expected. |
On Raspberry Pi 3 Model B Rev 1.2, following instructions verbatim, I am not able to connect local network clients to any chatroom identity EXCEPT for "DEADCAFE" (no idea where this identify was generated from but it showed up when I hit the reload icon at the top of the client)
The text was updated successfully, but these errors were encountered: