Skip to content
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

Open
electricimp123 opened this issue Jul 23, 2020 · 3 comments
Open

only chatroom identify DEADCAFE works #43

electricimp123 opened this issue Jul 23, 2020 · 3 comments
Labels
question Further information is requested

Comments

@electricimp123
Copy link

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)

@gridhead
Copy link
Member

gridhead commented Jul 24, 2020

Hi @electricimp123, DEADCAFE is the standard identity of the chatroom generated when the page is loaded or refreshed. If you wish to join a chatroom with different identity - simply generate a random room identity or enter an 8-character lowercase hexadecimal number of your choice.

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 DEADCAFE is generated back.

@gridhead gridhead added the question Further information is requested label Jul 24, 2020
@electricimp123
Copy link
Author

electricimp123 commented Jul 24, 2020

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.

@gridhead
Copy link
Member

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.

DEADCAFE is the start point. Every client loads it up by default as a common identity so if you simply enter that - which you did - you would be able to conversate easily.

Another way to say it perhaps is that newly generated identities are NOT working, but the standard identity is.

Just share the newly generated identity with others and ask them to join. It should work as expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants