Scratch

This has already been declined by sdg1.
Reason:

 
if <(user) = [Wes64]>
be mean
else
be normal
end

Last edited by technoboy10 (2012-06-03 19:05:31)

Lightnin wrote:

Still thinking about that- but probably.

Tbtemplex97 wrote:

This has already Been suggested + Click Here

Go to possible features, theres a username block.

A reporter that reports the username of the person viewing a project.

Possible, but as said above, not likely.
(Don't add a slash to the end of the URL. Use the link here in this post; i fixed it.)

Pecola1 wrote:

i would agree, but seeing that it could be used to ban someone from playing a game, this could be used for cyber bullying. 

look inside button.
why not put in a window whenever this block is used!
it would ask "this project would like to use the (username) block will you allow it?"

LEGOengineer261 wrote:

I think a 'Username' block would be better.

(Username)

That is what they were suggesting.

Bklecka wrote:

Pecola1 wrote:

i would agree, but seeing that it could be used to ban someone from playing a game, this could be used for cyber bullying. 

look inside button.
why not put in a window whenever this block is used!
it would ask "this project would like to use the (username) block will you allow it?"

that would be good... but someone can still make it so if the username is '' then it will not play the game and say you must allow the block. 

TorbyFork234 wrote:

technoboy10 wrote:

This has already been declined by sdg1.
Reason:

 
if <(user) = [Wes64]>
be mean
else
be normal
end

But then whoever it's being mean to can click flag as inappropriate and then say,
"Inside the project it says that if the username is mine to be mean to me!"
And then the Scratch Team can deal with it easily by clicking see Inside.

That's a good point. I'll bring this up to them.

ManaUser wrote:

Another solution, if that's really a big concern, would be to use anonymized account numbers. So instead of "ManaUser" it would say "2346217318", and I suppose "0" would mean guest. That way you can't easily set up a trap for a specific user, but you can still consistently identify people in order to create accounts inside the project.

Yes, but if you have a trustworthy program, and you trick the user into enter their username, you could create a table for decoding these cryptographically unique numbers.

Pecola1 wrote:

i would agree, but seeing that it could be used to ban someone from playing a game, this could be used for cyber bullying. 

That is true. What if we prevented the (username) block from being used in an operator? This would totally stop any locking-out.

Wes64 wrote:

Pecola1 wrote:

i would agree, but seeing that it could be used to ban someone from playing a game, this could be used for cyber bullying. 

That is true. What if we prevented the (username) block from being used in an operator? This would totally stop any locking-out.

You could just set a regular variable to the value of the (username) block, and then use the variable in operators, though.

TorbyFork234 wrote:

Pecola1 wrote:

i would agree, but seeing that it could be used to ban someone from playing a game, this could be used for cyber bullying. 

But in some cases it would be good to be able to ban.
Let's say you have a chatroom project. You can change it whenever you want and you see someone posting many inappropriate things on it. In the project notes, you put that if someone is being mean that you will disallow them to use your project. You add in his name to a list of banned people and script it so that s/he can't use it anymore. The only way to do that would be to have the username block.

There wouldn't be a problem with that, but if you ban people for nothing, which would inevitably happen, then there's a problem.

I still don't trust people to not troll in 2.0. I really think that on each project that uses cloud variables there'll be at least one occurance of trolling.

Last edited by RedRocker227 (2012-06-11 11:17:05)

scimonster wrote:

TorbyFork234 wrote:

technoboy10 wrote:

This has already been declined by sdg1.
Reason:

 
if <(user) = [Wes64]>
be mean
else
be normal
end

But then whoever it's being mean to can click flag as inappropriate and then say,
"Inside the project it says that if the username is mine to be mean to me!"
And then the Scratch Team can deal with it easily by clicking see Inside.

That's a good point. I'll bring this up to them.

+1

I've made a list of all the pros and cons for this:

PROS:
Trolls could be banned
Limits spamming, spammers are identified

CONS:
Guests cannot be banned
Cyberbullying