Feature/validate usernames - Unverifiable usernames

[friedger]

This PR

• accepts models that contain unverifiable usernames and adds an attribute usernameUnverified
• builds on top of #42

[pradel]

@friedger, with this approach the username will need to be verified at some point right? Could it be done via a cron job or something like this?

[friedger]

They should be resubmitted by the app maybe?

Léo Pradel [email protected] schrieb am Sa., 29. Feb. 2020, 09:03:

@friedger https://github.com/friedger, with this approach the username will need to be verified at some point right? Could it be done via a cron job or something like this?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/blockstack/radiks-server/pull/43?email_source=notifications&email_token=AALBYWJP4BONGEDGM3USIQTRFDAL5A5CNFSM4KZ4JL62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENLTJKI#issuecomment-592917673, or unsubscribe https://github.com/notifications/unsubscribe-auth/AALBYWNJW2HSQMEEMFNHFPLRFDAL5ANCNFSM4KZ4JL6Q .

[pradel]

@friedger it's a solution but it might decrease the user experience if the user have to resubmit all the data prior to the username invalidation..

[friedger]

It should be just a call to crawl for the gaia bucket. But I haven't tried it yet

Léo Pradel [email protected] schrieb am Sa., 29. Feb. 2020, 11:21:

@friedger https://github.com/friedger it's a solution but it might decrease the user experience if the user have to resubmit all the data prior to the username invalidation..

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/blockstack/radiks-server/pull/43?email_source=notifications&email_token=AALBYWKPLP3SSUPHP7C5EK3RFDQUHA5CNFSM4KZ4JL62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENLWH5Y#issuecomment-592929783, or unsubscribe https://github.com/notifications/unsubscribe-auth/AALBYWMRPZKSG7EWJZRNQJLRFDQUHANCNFSM4KZ4JL6Q .