Apple has proposed a standardized format for delivering one-time code over SMS.
Since there is no current standard text format for SMS delivery of one-time codes, systems rely on heuristics to locate the code in the message and associate it with a relevant origin.
WebKit engineer Theresa O'Connor proposes this lightweight text format:
-----
747723 is your FooBar authentication code.
@foobar.com #747723
-----
In this example, "747723 is your FooBar authentication code." is the human-readable explanatory text, "@foobar.com" identifies the origin (https://foobar.com) for which the code is to be used, and "#747723" identifies the one-time code (747723). "@" and "#" are sigils used to identify the text that follows them. Any origin which is schemelessly same site as https://foobar.com/ is an origin on which this code may be used.
Both Apple and Google are onboard with the proposed format but Mozilla's stance is unknown.
More details at the link below...
Read More [via Alfred]
Since there is no current standard text format for SMS delivery of one-time codes, systems rely on heuristics to locate the code in the message and associate it with a relevant origin.
WebKit engineer Theresa O'Connor proposes this lightweight text format:
-----
747723 is your FooBar authentication code.
@foobar.com #747723
-----
In this example, "747723 is your FooBar authentication code." is the human-readable explanatory text, "@foobar.com" identifies the origin (https://foobar.com) for which the code is to be used, and "#747723" identifies the one-time code (747723). "@" and "#" are sigils used to identify the text that follows them. Any origin which is schemelessly same site as https://foobar.com/ is an origin on which this code may be used.
Both Apple and Google are onboard with the proposed format but Mozilla's stance is unknown.
More details at the link below...
Read More [via Alfred]