-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Implement new contribution flow for unverified publishers #2836
Comments
Verified passed with
Verification PASSED on
Verification passed on
|
New logic: We never send contributions to unverified creators. However, we do allow users to take actions to tip or auto-contribute to these creators -- the difference is the user holds these tips/contributions in reserve within the browser, and the browser retries contributions once every 30 days (on the normal auto-contribute / monthly tip cycle), checking for newly verified creators. We never transmit any information about unverified creators or attention spent on their sites to any server. This information and all of the logic surrounding it is entirely client-side. Only verified creators get transmitted contributions.
Two releases: This change will be made in two releases, in order to accommodate an immediate hotfix (captured by this issue), and later, a complete fix that fully implements the retry logic. The key for the immediate hotfix is to make sure we preserve the tip/contribution data client side — and change some strings and other UX details — so that we can act upon older attention data in a future release.
The text was updated successfully, but these errors were encountered: