Discuss Scratch
- Discussion Forums
- » Suggestions
- » The username block has some problems.
- tlangster
-
Scratcher
100+ posts
The username block has some problems.
I am so excited that the Scratch Team has decided to go with this block. Its possibilities are limitless. And it works great - but it has a problem.
When you get to a project that uses the username reporter, you get this:
So, if a Scratcher who doesn't know what it means sees it, they can get scared off. Or, an overly concerned parent might not want their kid using it because of concerns they may have.
Bit damaging to projects, huh?
And it is difficult to do databases, impossible without cloud data, since I can't say, set item (username) in list DATA to dfjouijhfiouid. You instead have to make a complex script to get around it.
Why not have both the username and User ID block? They both have advantages and disadvantages. User ID allows for anonymous tracking and databasing easily. The username block allows for secure tracking across projects and allows for alpha access and moderation access. Allow both!
When you get to a project that uses the username reporter, you get this:
This project can detect who is using it, through the “username” block. To hide your identity, log out before using this project.And that can cause people to think “Uh oh! There might be a problem!” since there is a warning label.
So, if a Scratcher who doesn't know what it means sees it, they can get scared off. Or, an overly concerned parent might not want their kid using it because of concerns they may have.
Bit damaging to projects, huh?
And it is difficult to do databases, impossible without cloud data, since I can't say, set item (username) in list DATA to dfjouijhfiouid. You instead have to make a complex script to get around it.
Why not have both the username and User ID block? They both have advantages and disadvantages. User ID allows for anonymous tracking and databasing easily. The username block allows for secure tracking across projects and allows for alpha access and moderation access. Allow both!
- MrFlash67
-
Scratcher
500+ posts
The username block has some problems.
It is still available as an obsolete block, look in my sig for a link.
- tlangster
-
Scratcher
100+ posts
The username block has some problems.
It is still available as an obsolete block, look in my sig for a link.
Got it.
- giratina12
-
Scratcher
100+ posts
The username block has some problems.
Ah yes that is true. I myself thought that it seemed as if they wanted you to sign out. Of course, I know nobody could do anything harmful but I do see your point about others getting worried. The Scratch Team should think about possibly changing it.
- kakfdadfdffa
-
Scratcher
43 posts
The username block has some problems.
remember the ip ban apcolpse when someone banned everyone on scratch. yeah, we all hate that guy
- spgame05
-
Scratcher
100+ posts
The username block has some problems.
Support! I think the

user id :: sensing reporterblock should be put back and the username message should be deleted.

remember the ip ban apcolpse when someone banned everyone on scratch. yeah, we all hate that guyPlease only post things related to the topic.
- gigapouch_test
-
Scratcher
54 posts
The username block has some problems.
It is still available as an obsolete block, look in my sig for a link.
But your signature links to a blog.
- GyroscopeBill
-
Scratcher
500+ posts
The username block has some problems.
I support. I think that the user message is sort of saying that if you don't log out, your computer could blow up or something. User id seems pretty cool as well 

- angrybird232
-
Scratcher
100+ posts
The username block has some problems.
Support! I think theI have both and we should keep theuser id :: sensing reporterblock should be put back and the username message should be deleted.remember the ip ban apcolpse when someone banned everyone on scratch. yeah, we all hate that guyPlease only post things related to the topic.
(username)block for other data.
- angrybird232
-
Scratcher
100+ posts
The username block has some problems.
I am so excited that the Scratch Team has decided to go with this block. Its possibilities are limitless. And it works great - but it has a problem.I agree!
When you get to a project that uses the username reporter, you get this:This project can detect who is using it, through the “username” block. To hide your identity, log out before using this project.And that can cause people to think “Uh oh! There might be a problem!” since there is a warning label.
So, if a Scratcher who doesn't know what it means sees it, they can get scared off. Or, an overly concerned parent might not want their kid using it because of concerns they may have.
Bit damaging to projects, huh?
And it is difficult to do databases, impossible without cloud data, since I can't say, set item (username) in list DATA to dfjouijhfiouid. You instead have to make a complex script to get around it.
Why not have both the username and User ID block? They both have advantages and disadvantages. User ID allows for anonymous tracking and databasing easily. The username block allows for secure tracking across projects and allows for alpha access and moderation access. Allow both!
- Charles12310
-
Scratcher
1000+ posts
The username block has some problems.
I think we should bring the “user ID” block back. There are many ways this could be useful.
- 290Scratcher
-
Scratcher
1000+ posts
The username block has some problems.
I think we should bring the “user ID” block back. There are many ways this could be useful.Necropost.
Actually that was a necropost. This is a bump.
- DaEpikDude
-
Scratcher
1000+ posts
The username block has some problems.
Necros aren't necros if you're bringing something to the conversation, and especially so in Suggestions.I think we should bring the “user ID” block back. There are many ways this could be useful.Necropost.
Actually that was a necropost. This is a bump.
- Discussion Forums
- » Suggestions
-
» The username block has some problems.














