archive
/
matrix-spec-proposals
mirror of https://github.com/matrix-org/matrix-spec-proposals
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Make clear images should be included in clients, and discuss future changes

Browse Source
andybalaam/emoji-verification-images
Andy Balaam 1 month ago
parent ae6a9f30b8
commit cbaf8a9997
1 changed files with 16 additions and 3 deletions
Show Stats Download Patch File Download Diff File

19
proposals/4347-emoji-verification-images.md
Unescape Escape View File

@ -31,7 +31,7 @@ same or different.
I propose providing a fixed set of images to use for emoji verification, and I propose providing a fixed set of images to use for emoji verification, and
recommending a fixed layout for display on screen. recommending a fixed layout for display on screen.
### Changes to the emoji table ### Including URLs in the Emoji table
Currently the spec provides Unicode code points of emoji for each Currently the spec provides Unicode code points of emoji for each
number 0-63 along with translated names. It also provides this information as number 0-63 along with translated names. It also provides this information as
@ -80,6 +80,13 @@ I also propose that graphical clients SHOULD display these images in two rows,
centred vertically, with 4 images on the first row and 3 images on the second, centred vertically, with 4 images on the first row and 3 images on the second,
with the local translation of the corresponding word below each image. with the local translation of the corresponding word below each image.
Unless absolutely necessary, the images will not change, so clients are not
expected to update them in future, and will probably not bother to automate
downloads of the images as part of their build process.
There is no uptime guarantee for the supplied URLs, so clients SHOULD NOT depend
on them being available when a user needs to use them.
### Non-graphical clients ### Non-graphical clients
Non-graphical clients or other clients that are unable to use the supplied Non-graphical clients or other clients that are unable to use the supplied
@ -89,8 +96,7 @@ images may continue to use Unicode code points as before.
I propose taking a snapshot of the relevant images from I propose taking a snapshot of the relevant images from
[twemoji](https://github.com/twitter/twemoji) at the time of incorporating this proposal [twemoji](https://github.com/twitter/twemoji) at the time of incorporating this proposal
into the spec, and freezing the set of images at that time. (Until/unless some into the spec, and freezing the set of images at that time.
other MSC requires them to be changed.)
These images are attractive and clear. These images are attractive and clear.
@ -98,6 +104,13 @@ These images are provided under the CC BY 4.0 license so may be used with
proper attribution, which should be added to the spec text and client proper attribution, which should be added to the spec text and client
applications. applications.
### Future changes
If at all possible, these images will not change. In future, if they need to
change in an incompatible way, I expect that the verification process will be
extended to include information allowing clients to negotiate which image set to
use, but this is out of scope for this proposal.
## Potential issues ## Potential issues
* If existing clients use Unicode characters to aid accessibility (e.g. for * If existing clients use Unicode characters to aid accessibility (e.g. for

Write Preview
Loading…
Cancel
Save