Say if you wanted to make a Scratch username, but then realized someone had it already and hadn't used it in awhile, Scratch can email the user to ask if they would like to hand over the username. If there is no response within a day, the new user gets the username, and the old username gets archived. For example, if you saw a project from the old user, instead of saying the regular username, it would say this: user[ARCHIVED]. That way, all of the old user's projects are moved into an archived account, and the new user gets the username.
Of course, the old user can respond at any time saying that he wants his username back and he shall get it, while the new user will get a new username.
What do you think? Comment with tips and suggestions, or add it to Scratch Suggestions!
Offline
-1
I don't like the idea either. Everyone can mistaken this user as the old person. Lets say it was a popular user. I would hate to be mistakened for an old user. Also it may be hard for the scratch team to program this and also how would they find out your email?
-.-
Offline
I don't agree.
Offline
It would only work for users who haven't been on for like 3 years.
There's no way a million people would take over SpriteMaster's account
Offline
undefeatedgames wrote:
It would only work for users who haven't been on for like 3 years.
There's no way a million people would take over SpriteMaster's account![]()
What if SpriteMaster went to college for 3 years without any computers or phones you can surf the web with?
Offline
I don't agree because people might think that you're the person whose name you're taking. That would cause a lot of trouble.
Offline
Nah. To avoid confusion, the new person would need to be labelled as [new] for a while, and that kinda defeats the whole point.
Offline
You guys are right. Let's close the topic.
Offline
undefeatedgames wrote:
You guys are right. Let's close the topic.
That's where the close suggestion comes in...
Offline
I don't support.
LS97 wrote:
undefeatedgames wrote:
You guys are right. Let's close the topic.
That's where the close suggestion comes in...
![]()
Offline
undefeatedgames wrote:
You guys are right. Let's close the topic.
Closed by request of owner.
Offline