-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Inaccuracy in README.md #303
Comments
The create_secret_chat will return the name of the secret chat. Normally this is !_firstname_lastname for the first secret chat, and after that it will be !_firstname_lastname#1 and so on. So you have to look for the answer of the create_secret_chat to know which username to use. ANSWER 50 |
Yes, you explained the same like me. Thus I suggest to rewrite the text and make clear where the chat name for secure chat comes from and that the syntax is !_firstname_lastname (reads exclamation mark underscore first underscore lastname) |
Can README.md be updated to reflect the actual way of sending a message through a secure chat correctly? |
|
I think the following sentence is not accurate:
"Peer refers to the name of the contact or dialog and can be accessed by TAB completion. For user contacts peer name is Name Lastname with all spaces changed to underscores. For chats it is it's title with all spaces changed to underscores For encrypted chats it is Name Lastname with all spaces changed to underscores."
Shouldn't it mean "For encrypted chats it is !_Name_Lastname with exclamation mark and underscore as prefix followed by Name and Lastname and all spaces changed to underscores."
Or let me explain differently:
I try to start a new secure chat for a user who is not on my contact list.
add_contact +12345 firstname lastname
create_secret_chat firstname_lastname
After this step, I accept the new secret chat on the recipient's side and now try to send a message:
msg firstname_lastname test
So how do I call msg here correctly? Something like "msg !_firstname_lastname"?
The text was updated successfully, but these errors were encountered: