Skip to content

MSC4405: Deprecate the emoji method for SAS verification#4405

Open
uhoreg wants to merge 4 commits intomatrix-org:mainfrom
uhoreg:deprecate_emoji_verification
Open

MSC4405: Deprecate the emoji method for SAS verification#4405
uhoreg wants to merge 4 commits intomatrix-org:mainfrom
uhoreg:deprecate_emoji_verification

Conversation

@uhoreg
Copy link
Copy Markdown
Member

@uhoreg uhoreg commented Jan 20, 2026

Rendered

Disclosure: I am a member of the Spec Core Team, and the Element crypto team. This proposal was written with my Spec Core Team hat on.

@uhoreg uhoreg added e2e proposal A matrix spec change proposal client-server Client-Server API kind:maintenance MSC which clarifies/updates existing spec labels Jan 20, 2026
@uhoreg uhoreg changed the title MSCxxxx: Deprecate the emoji method for SAS verification MSC4405: Deprecate the emoji method for SAS verification Jan 20, 2026
@uhoreg uhoreg marked this pull request as ready for review January 20, 2026 21:27
@turt2live turt2live moved this to Ready for general review in Spec Core Team Workflow Jan 20, 2026
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Implementation requirements:

  • Some notion of approval from product-focused teams

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As a data point, Nico says that Famedly is already only using decimal verification, due to requests from customers.

@turt2live turt2live added the needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. label Jan 20, 2026
Co-authored-by: Johannes Marbach <n0-0ne+github@mailbox.org>
@@ -0,0 +1,141 @@
# MSC4405: Deprecate the emoji method for SAS verification
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I struggle really badly at handling numbers (to the point where 2FA is a nightmare and I have quit doing 2FA on a separate device, or taking 5-10 minutes to type over a bank account number).

This also would be majorly problematic for anyone with dyscalculia or otherwise poor/bad vision.

I would prefer if Emoji verification remained, because it's very visual and intuitive, even if the rendering can be inconsistent between apps, devices and platforms.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I struggle really badly at handling numbers (to the point where 2FA is a nightmare and I have quit doing 2FA on a separate device, or taking 5-10 minutes to type over a bank account number).

I'm not sure how much of a practical difference it makes but bank account numbers in Europe are almost double the length of the verification decimals (20 vs. 12 symbols) and you shouldn't have to type them during verification.

This also would be majorly problematic for anyone with dyscalculia or otherwise poor/bad vision.

This is true. Though I suppose a dyslexic person would have similar issues when having to also read emoji names and possibly translations. I wonder if voiceover / screenreaders could assist in both of these cases?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ara4n suggested:

  • change the font/layout in EW to make it more dyslexia-friendly.
  • Allow users to click "compare emoji instead".

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Providing the text descriptions of emojis may be a fair solution to avoid the confusion problem, as it can be ignored outright if the emojis match up.

As for the 20 vs. 12 symbols thing, I mentioned 2FA as another annoying case specifically because it's 6 symbols - it still takes a considerable amount of time and effort to verify, whereas with the 8 emojis you can rely on visual memory at a glance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

client-server Client-Server API e2e kind:maintenance MSC which clarifies/updates existing spec needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal

Projects

Status: Ready for general review

Development

Successfully merging this pull request may close these issues.

9 participants