A tiny tweak to cloud variables - 10 Supporters!

9kiwi9

Support!

Contest101-test

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?

Sometimes there are projects that change the highscore in realtime(all points are counted) so that won't work well…

This is Contest101's test account.

My OS Automatically changes for holidays! How cool is that?

darkness3560

Thepuzzlegame

+1 Support!

hi!

Mattjod

say [I support.]

else
say [Why is there a random else?]

Hello, I don't use Scratch much anymore but I might come on at some point!

derpmeup

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 http://scratch.mit.edu/users/griffpatch]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!

hey bro that's a pretty good meme xD!

derpmeup

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!

For some reason a few days ago i could use the url tag perfectly. I just forgot how for some reason.

hey bro that's a pretty good meme xD!

Blueinkproductions

Support

Generation 2: the first time you see this copy and paste it on top of your sig in the scratch forums and increase generation by 1. Social experiment.

____                  _____  _______              
|   \  |     |     | |          |    |\    | | /
|___/  |     |     | |__        |    | \   | |/  
|   \  |     |     | |          |    |  \  | |\   
|    | |     |     | |          |    |   \ | | \  
|___/  L____  \___/  |_____  ___|___ |    \| |  \ 
               PRODUCTIONS

Here's a hint: support = support.

<shameless self promotion>follow me! follow me! follow me! love my stuff! love my stuff! love my stuff! follow me! love my stuff! remix my stuff! follow me! follow me! </shameless self promotion>

9kiwi9

Siport!

ExtremeLogic

Support.

shiguy101

Can I be awsome?

Last edited by shiguy101 (March 28, 2014 19:53:43)

Deerleg

Support. Really would help my surveys.

Last edited by Deerleg (March 29, 2014 01:01:37)

Contest101-test

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.

…that is not very likely.

This is Contest101's test account.

My OS Automatically changes for holidays! How cool is that?

Dylan5797

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 don't know how this could work. This would mean that New Scratchers would be able to remix projects that contain cloud variables and use the cloud variables. The only thing stopping New Scratchers from stealing cloud variables is their ability to edit them.

stickfiregames

Support.

If you can read this, my signature cubeupload has been eaten by an evil kumquat!

or you just used Inspect Element, you hacker

;

LoopyS

bump…because it's STILL a good idea

___________________LoopyS__________________
————| Profile | Website | A Tiny Tweak… |————

Coolmath2046

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

samq64

Bumping because someone made a duplicate recently.

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

I'm sure everyone knows this already, but it's now impossible to store more than 10^256 (2560) characters on the cloud using all 10 cloud variables in a project.

Last edited by samq64 (July 28, 2021 17:20:01)

hiPeeps124816

there already a 256-digit limit for cloud variables
but support, I'm having a feeling new scratchers are getting bullied

Generation 7: First time you see this? Copy and paste it on top of your signature in the forums and increase generation by 1.

thethethethethethethethethethethethethethethethethethethethethethethethethethethethethethethethethethethethethethethethethethethethethethethe
Specs -
OS: macOS 11.6.4
Browser: Varies, usually Safari 15.3 or Opera GX 83 or Firefox 96
Computer: Late 2013 MacBook Pro 2.4GHz Dual Core Intel Core i5
highlight and shift down arrow

;

Discuss Scratch