-
Notifications
You must be signed in to change notification settings - Fork 309
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[UX] Account ownership verification process consolidation [draft] #23
Comments
----- My suggestion: |
|
I see. The "editable" appeared in the second option box in Automatic Mode. I may adjust the wording. |
Automatic mode may not be accepted by users since it will create a post without the user's permission |
👍Let's keep this design for now |
Fix linter errors
…trace-powered feat: update dialog title
Background
It can be hard to ensure that the automatic verification posting mechanism can work, so we need some saturation measures to ensure that the public key is posted, in bio or in post.
Some basic change on setup
Measure 1: Just-in-time Self-checking
As soon as the setup is completed (proof(s) automatically added), the extension shall immediately check if the proof is really added to bio and really posted on timeline. If no proof is online, the user will receive alert message like "automatic proof failed, please add manually", and will be guided to post the public key.
Error handling: User bio may have no enough space for the public key. This will lead to failure of bio update and the other method of proof is the only possible way. In the best case, we can detect the available space in user bio so we can ban the option when it is not possible.
Measure 2: Continued Self-checking
The extension shall periodically check the proofs of claimed accounts of the user to see if they are validly connected.
If the proof is no longer available, the user will receive alert message like "proof broken, please re-add". This alert should appear only when the user is logged in as the Facebook account.
The text was updated successfully, but these errors were encountered: