A tiny tweak to cloud variables - 10 Supporters!

LoopyS

Hi Scratch Team!

My suggestion is a tiny tweak to cloud variable blocks.

At the moment, New Scratchers and Non Scratchers can't make cloud variables.
That's okay, it's preventing spam.
But, at the moment, New Scratch and Non Scratchers can't change cloud variables.
My suggestion comes in here.

Change the cloud variable blocks so New Scratchers and Non Scratchers can't code
or edit cloud variables, but they can change cloud variables. This is okay because
cloud variables are just numbers, and what harm could changing a number do?

Of course New and Non Scratchers still won't be able to code cloud variables
like this:

forever
change [☁ Cloud Variable v] by (99999999)
wait (0.001) secs
end

and crash the server.

Changing cloud variables in this way means
Anyone can get a highscore in a game project, not just Scratchers.
Anyone can participate in a poll run through Scratch, not just Scratchers.

This further opens Scratch projects to everyone, not just Scratchers.

Also, AonymousGuy pointed out that spam accounts could crash the server.
So, New Scratchers (or non Scratchers) should have a 60 second rule on data changed, as the
New Scratcher stage is designed to filter out spammers.

SUPPORTERS

Only AWESOME Scratchers support this idea.
Scratchers like, CodeLegend, jontmy00,
AonymousGuy, gregory9, DerAxeEffekt,
Centrifugal, Chainmanner, 1234abcdcba4321,
Blaze349, and Zambonifofex.

Are you AWESOME?

MEANINGS

For this Suggestion, change and code mean this
Change: Change a cloud variable in Presentation Mode (e.g. Get a highscore in a game)
Code: Edit the cloud variable in “See Inside” Mode (e.g. Edit a cloud variable block)

Last edited by LoopyS (Jan. 18, 2014 11:06:53)

CodeLegend

I support this! New Scratchers should be able to change cloud variables.

And, by the way, this would ‘crash the server’ even more because there wouldn't be a need for calculations.

forever
set [☁ Cloud Variable v] to (0)
wait (0.001) secs
end

AonymousGuy

LoopyS wrote:
This is okay because cloud
variables are just numbers, and what harm could changing a number do?

This is the problem. Changing a number could potentially be harmful. For example, a spam account could be created that used the following procedure:

a) Find scratch projects with highscores
b) Send a copy to the owner to write a bot
c) Use the bot to get an infinitely big highscore (potentially lagging out the server)
d) Repeat

If the person had to create an account and USE it to be able to change cloud data, this could result in a crash (not likely, but possible).

This would be difficult to stop until the server crashed, because the bot would constantly be running, even if the cloud variable was reset.

The only way to stop this would be to unshare the project or ban the spam account.

Although, I do wish that New Scratchers could use cloud data.

LoopyS

CodeLegend wrote:
I support this! New Scratchers should be able to change cloud variables.

And, by the way, this would ‘crash the server’ even more because there wouldn't be a need for calculations.
forever
set [☁ Cloud Variable v] to (0)
wait (0.001) secs
end

Thanks for supporting this, CodeLegend!

AonymousGuy wrote:
LoopyS wrote:
This is okay because cloud
variables are just numbers, and what harm could changing a number do?

This is the problem. Changing a number could potentially be harmful. For example, a spam account could be created that used the following procedure:

a) Find scratch projects with highscores
b) Send a copy to the owner to write a bot
c) Use the bot to get an infinitely big highscore (potentially lagging out the server)
d) Repeat

If the person had to create an account and USE it to be able to change cloud data, this could result in a crash (not likely, but possible).
This would be difficult to stop until the server crashed, because the bot would constantly be running, even if the cloud variable was reset.
The only way to stop this would be to unshare the project or ban the spam account.
Although, I do wish that New Scratchers could use cloud data.

I see your point.

I think this is an important change, so maybe a compromise could be found?
Maybe a 60 second rule could be introduced for data change from New Scratchers, like the forum post rule???

AonymousGuy

LoopyS wrote:
I see your point.
I think this is an important change, so maybe a compromise could be found?
Maybe a 60 second rule could be introduced for data change from New Scratchers, like the forum post rule???

Yeah, a 60 second rule could work. Or maybe the scratcher could be logged out automatically if it seemed to be a spam account (like changed a cloud variable 300 times in a minute)

Also, my “point” is a bit strange, because who bothers writing a bot just to crash the scratch server?

seanbobe

AonymousGuy wrote:
LoopyS wrote:
I see your point.
I think this is an important change, so maybe a compromise could be found?
Maybe a 60 second rule could be introduced for data change from New Scratchers, like the forum post rule???

Yeah, a 60 second rule could work. Or maybe the scratcher could be logged out automatically if it seemed to be a spam account (like changed a cloud variable 300 times in a minute)

Also, my “point” is a bit strange, because who bothers writing a bot just to crash the scratch server?

people without lives

LoopyS

Thanks for your input AonymousGuy and seanbobe!

Spread the word! This is a simple change that could
open up lots of opportunites!

LoopyS

bump

jontmy00

LoopyS wrote:
Change the cloud variable blocks so New Scratchers and Non Scratchers can make
cloud variables, but they can change cloud variables.

Re-read that sentence; New Scratchers should not be able to make CVs. Typo?

Last edited by jontmy00 (Nov. 21, 2013 09:16:03)

LoopyS

jontmy00 wrote:
LoopyS wrote:
Change the cloud variable blocks so New Scratchers and Non Scratchers can make
cloud variables, but they can change cloud variables.

Re-read that sentence; New Scratchers should not be able to make CVs. Typo?

Whoops!

jontmy00

LoopyS wrote:
jontmy00 wrote:
LoopyS wrote:
Change the cloud variable blocks so New Scratchers and Non Scratchers can make
cloud variables, but they can change cloud variables.

Re-read that sentence; New Scratchers should not be able to make CVs. Typo?

Whoops!

I support this suggestion.

LoopyS

Thanks for Supporting, jonmy00!

Gravitation

As AonymousGuy pointed out, people changing these could effect the functionality of the project. Imagine, you use a cloud list system and have a variable that looks like this:

98765872947878578374899..,

Some new scratcher comes along and changes it to see what it does, and you've just lost all your cloud data. Complex projects (which are the most likely victims of this) use variables for functionality.

Cloud variables are a part of the project's code. Letting people modify this is essentially the equivalent of letting people edit your project and publishing it back to your account. It deems cloud variables as an insecure method of data sharing and therefore not viable, rendering them useless. And what are the pros? You can easily make an alternative system yourself within Scratch.

1234abcdcba4321

^^
Yet, any full scratcher can do that, too.

LoopyS

Edits to the suggestion to make it more Spam-Proof,

I wrote:
Also, AonymousGuy pointed out that spam accounts could crash the server.
So, New Scratchers (or non Scratchers) should have a 60 second rule on data changed, as the
New Scratcher stage is designed to filter out spammers.

Do you support this???

gregory9

Support

forever
    say [Support]
end

Last edited by gregory9 (Nov. 24, 2013 12:19:47)

AonymousGuy

Wait, I said I support as well!

I just pointed out that someone who was bored and somewhat malicious could crash the Scratch servers.

LoopyS

Thanks for supporting AonymousGuy and gregory9

Supporter Count: 4
Will you Support too?

LoopyS

bump

DerAxeEffekt

Support!

Discuss Scratch