You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem: When the member of the public holding BrightID goes to connect their BrightID to various apps that requires and check for the Meets verification specifically, and they have not received the verification on their BrightID yet, they get this error pop-up.
Rationale: For consistency of communication and avoidance of any confusion of the public, the error pop-up should say "Meets" instead. This is specially important since the time we started having multiple verifications and their corresponding verification badges in BrightID since the launch of the Bitu verification.
It is likely applications will in mid future require or check for multiple verifications and it will be essential to distinguish one from another and clearly communicate the status of each of the verifications held by a given BrightID holding public.
The text was updated successfully, but these errors were encountered:
Problem: When the member of the public holding BrightID goes to connect their BrightID to various apps that requires and check for the Meets verification specifically, and they have not received the verification on their BrightID yet, they get this error pop-up.
Rationale: For consistency of communication and avoidance of any confusion of the public, the error pop-up should say "Meets" instead. This is specially important since the time we started having multiple verifications and their corresponding verification badges in BrightID since the launch of the Bitu verification.
It is likely applications will in mid future require or check for multiple verifications and it will be essential to distinguish one from another and clearly communicate the status of each of the verifications held by a given BrightID holding public.
The text was updated successfully, but these errors were encountered: