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?

say [I support.]

else
say [Why is there a random else?]

LoopyS wrote:

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)

derpmeup wrote:

LoopyS wrote:

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)

I definitely support this! I remember when I was a new scratcher and I couldn't play the multiplayer games by griffpatch and I wanted to play them so badly. So, right when i got the scratcher invite i accepted and went to play the cloud multiplayer platformer fun. I really like this idea!

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.

LoopyS wrote:

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)

Coolmath2046 wrote:

Changing a number wouldn't do harm since cloud variables cannot exceed 10^10240.