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
{{ message }}
This repository has been archived by the owner on Feb 8, 2018. It is now read-only.
Stub participants created before 2012-09-13 have as their username the username that they have on GitHub. When we added Twitter support we changed to using randomized usernames for stub participants. We should switch to randomized usernames for the old stub participants, to release the usernames in question back into the pool and come into line with our current behavior.
But! Note that if the username starts with deactivated- then they did join but then were deactivated (manually, see #54 (comment)). If the username starts with deactivated- it shouldn't be scrambled. (Edit by @Changaco: deactivated accounts have been renamed in #2507)
Also note that we need to update username_lower along with username. Do we have a neat Python function we can use for this? We should at least use our usual random username algorithm.
Stub participants created before 2012-09-13 have as their username the username that they have on GitHub. When we added Twitter support we changed to using randomized usernames for stub participants. We should switch to randomized usernames for the old stub participants, to release the usernames in question back into the pool and come into line with our current behavior.
But! Note that if the username starts with(Edit by @Changaco: deactivated accounts have been renamed in #2507)deactivated-
then they did join but then were deactivated (manually, see #54 (comment)). If the username starts withdeactivated-
it shouldn't be scrambled.Also note that we need to update
username_lower
along withusername
. Do we have a neat Python function we can use for this? We should at least use our usual random username algorithm.Reticketed from #2362.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: