status-im
/
specs
mirror of https://github.com/status-im/specs.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

mentions (#105)

This commit is contained in:
yenda 2020-06-15 14:43:21 +02:00 committed by GitHub
parent 073cf26949
commit 046f865eb6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/stable/6-payloads.md
View File

@ -161,6 +161,15 @@ There are other content types that MAY be implemented by the client:
* `EMOJI` * `EMOJI`
* `TRANSACTION_COMMAND` * `TRANSACTION_COMMAND`
##### Mentions
A mention MUST be represented as a string with the `@0xpk` format, where `pk` is the public key of the [user account](https://specs.status.im/spec/2) to be mentioned, within the `text` field of a message with content_type `TEXT_PLAIN`.
A message MAY contain more than one mention.
This specification RECOMMENDs that the application does not require the user to enter the entire pk.
This specification RECOMMENDs that the application allows the user to create a mention by typing @ followed by the related ENS or 3-word pseudonym.
This specification RECOMMENDs that the application provides the user auto-completion functionality to create a mention.
For better user experience, the client SHOULD display a known [ens name or the 3-word pseudonym corresponding to the key](https://specs.status.im/spec/2#contact-verification) instead of the `pk`.
##### Sticker content type ##### Sticker content type
A `ChatMessage` with `STICKER` `Content/Type` MUST also specify the ID of the `Pack` and A `ChatMessage` with `STICKER` `Content/Type` MUST also specify the ID of the `Pack` and

1
wordlist.txt
View File

@ -169,6 +169,7 @@ pubkey
publicKey publicKey
puk puk
pyspelling pyspelling
RECOMMENDs
relayers relayers
requestMessages requestMessages
RLP RLP