epninja wrote:

thirdlion wrote:

hay Epninja in support of you i think that you should comment on lighten's page the head of scratch's account and tell him about your idea

Lightnin isn't in charge of Scratch, there's not really a head, as it's a team project, but from what I've seen mres is the most respectable member.

thirdlion wrote:

wait i have a question with these blocks in function then you could hack or mess with someone's account with the right scripts

That's not really what I intend them to do.

Well, that's what hackers would intend for them to do. Just because it's not the purpose you intend doesn't mean that it won't be used in that way.

Personally, I don't want random Scratchers storing hundreds of cookies on my browser. Therefore I would not play any projects with Cached Variables in them, provided that there would be a message to tell me when projects contained them. And therefore I do not support.

Edit: If you are very concerned that people get the full experience of your games, add a note at the start of the project telling them that the game is large and that if they want to save their game, they will either have to download the project or staple the internet tab that they are on. Then you can also implement a feature where the green flag won't reset all the data, but instead, a reset button inside the project will.

Scratchifier wrote:

Well, that's what hackers would intend for them to do. Just because it's not the purpose you intend doesn't mean that it won't be used in that way.

Personally, I don't want random Scratchers storing hundreds of cookies on my browser. Therefore I would not play any projects with Cached Variables in them, provided that there would be a message to tell me when projects contained them. And therefore I do not support.

Basically this.

Firedrake969 wrote:

Scratchifier wrote:

Well, that's what hackers would intend for them to do. Just because it's not the purpose you intend doesn't mean that it won't be used in that way.

Personally, I don't want random Scratchers storing hundreds of cookies on my browser. Therefore I would not play any projects with Cached Variables in them, provided that there would be a message to tell me when projects contained them. And therefore I do not support.

Basically this.

Right, but basically every random website you visit stores cookies on your browser, and you're OK with that? Double standards?
I don't think cookie spam is that big of a problem, and even if it is, why not impose a limit in cookie variables, like for cloud data?

I mean the pros kinda outweigh the cons - it's either clunky list import/export for save games, or streamlined, transparent cookie vars. Which would you choose?

$(".box-head")[0].textContent = "committing AT crimes since $whenever"

tihis is coolish

say [HW2014 LOOOKS GOOD BRO ]

MegaApuTurkUltra wrote:

Firedrake969 wrote:

Scratchifier wrote:

Well, that's what hackers would intend for them to do. Just because it's not the purpose you intend doesn't mean that it won't be used in that way.

Personally, I don't want random Scratchers storing hundreds of cookies on my browser. Therefore I would not play any projects with Cached Variables in them, provided that there would be a message to tell me when projects contained them. And therefore I do not support.

Basically this.

Right, but basically every random website you visit stores cookies on your browser, and you're OK with that? Double standards?
I don't think cookie spam is that big of a problem, and even if it is, why not impose a limit in cookie variables, like for cloud data?

I mean the pros kinda outweigh the cons - it's either clunky list import/export for save games, or streamlined, transparent cookie vars. Which would you choose?

So true.

Scratchifier wrote:

epninja wrote:

thirdlion wrote:

hay Epninja in support of you i think that you should comment on lighten's page the head of scratch's account and tell him about your idea

Lightnin isn't in charge of Scratch, there's not really a head, as it's a team project, but from what I've seen mres is the most respectable member.

thirdlion wrote:

wait i have a question with these blocks in function then you could hack or mess with someone's account with the right scripts

That's not really what I intend them to do.

Well, that's what hackers would intend for them to do. Just because it's not the purpose you intend doesn't mean that it won't be used in that way.

Personally, I don't want random Scratchers storing hundreds of cookies on my browser. Therefore I would not play any projects with Cached Variables in them, provided that there would be a message to tell me when projects contained them. And therefore I do not support.

Edit: If you are very concerned that people get the full experience of your games, add a note at the start of the project telling them that the game is large and that if they want to save their game, they will either have to download the project or staple the internet tab that they are on. Then you can also implement a feature where the green flag won't reset all the data, but instead, a reset button inside the project will.

You've got the wrong idea. They will not be tied to your account They seriously won't contain anything that is worth hacking and nothing that can be used to attack others. If you could hack someone with the word “Chair”, then sure, hackers can use them to hack people, but you can't.

I support the idea of having a simple store variable (via cookie, so there is no risk of affecting usernames and such) until you can play again. Yes, workarounds exist, but they are far clunkier:

Cloud data can glitch up if two people try to save simultaneously.
Passwords get impractical quickly for large nonlinear games.

[ v]

The Scratch team should add this. Like now.

epninja wrote:

Scratchifier wrote:

epninja wrote:

thirdlion wrote:

hay Epninja in support of you i think that you should comment on lighten's page the head of scratch's account and tell him about your idea

Lightnin isn't in charge of Scratch, there's not really a head, as it's a team project, but from what I've seen mres is the most respectable member.

thirdlion wrote:

wait i have a question with these blocks in function then you could hack or mess with someone's account with the right scripts

That's not really what I intend them to do.

Well, that's what hackers would intend for them to do. Just because it's not the purpose you intend doesn't mean that it won't be used in that way.

Personally, I don't want random Scratchers storing hundreds of cookies on my browser. Therefore I would not play any projects with Cached Variables in them, provided that there would be a message to tell me when projects contained them. And therefore I do not support.

Edit: If you are very concerned that people get the full experience of your games, add a note at the start of the project telling them that the game is large and that if they want to save their game, they will either have to download the project or staple the internet tab that they are on. Then you can also implement a feature where the green flag won't reset all the data, but instead, a reset button inside the project will.

You've got the wrong idea. They will not be tied to your account They seriously won't contain anything that is worth hacking and nothing that can be used to attack others. If you could hack someone with the word “Chair”, then sure, hackers can use them to hack people, but you can't.

i think it is a good idea but it could maybe give private info away love it though you should get this idea out there!

thirdlion wrote:

epninja wrote:

Scratchifier wrote:

epninja wrote:

thirdlion wrote:

hay Epninja in support of you i think that you should comment on lighten's page the head of scratch's account and tell him about your idea

Lightnin isn't in charge of Scratch, there's not really a head, as it's a team project, but from what I've seen mres is the most respectable member.

thirdlion wrote:

wait i have a question with these blocks in function then you could hack or mess with someone's account with the right scripts

That's not really what I intend them to do.

Well, that's what hackers would intend for them to do. Just because it's not the purpose you intend doesn't mean that it won't be used in that way.

Personally, I don't want random Scratchers storing hundreds of cookies on my browser. Therefore I would not play any projects with Cached Variables in them, provided that there would be a message to tell me when projects contained them. And therefore I do not support.

Edit: If you are very concerned that people get the full experience of your games, add a note at the start of the project telling them that the game is large and that if they want to save their game, they will either have to download the project or staple the internet tab that they are on. Then you can also implement a feature where the green flag won't reset all the data, but instead, a reset button inside the project will.

You've got the wrong idea. They will not be tied to your account They seriously won't contain anything that is worth hacking and nothing that can be used to attack others. If you could hack someone with the word “Chair”, then sure, hackers can use them to hack people, but you can't.

i think it is a good idea but it could maybe give private info away love it though you should get this idea out there!

you can make a user saving game on scratch if you are interested about my project on that i can give you the URL.

I support, as long as the scratch team approves of it and you are notified before the cache is stored. (I think you might be notified already, but I'm not quite sure.)

thirdlion wrote:

i think it is a good idea but it could maybe give private info away love it though you should get this idea out there!

Private info? You wouldn't be able to, these local variables would only save to your own computer, no one would be able to see them except for anyone using your computer, anything you put in these variables wouldn't go to anyone else.

I support this idea.

Lotsa support, here are some [scratchblocks] for it:

store [local/project variable v] in cached [cached variable v] :: variables

store [local/project list v] in cached [cached variable v] :: list

(cached var [cached variable v] :: variables)
(cached list [cached list v] :: list)

It could be possible we'd use blocks like this, but only optional and probably not:

(cached var [cached variable v] of user [user] :: variables)
(cached list [cached list v] of user [user] :: list)

And definitely not:

store [local/project variable v] in cached [cached variable v] for user [user] :: variables

store [local/project list v] in cached [cached list v] for user [user] :: list

liam48D wrote:

Lotsa support, here are some [scratchblocks] for it:

store [local/project variable v] in cached [cached variable v] :: variables

store [local/project list v] in cached [cached variable v] :: list

(cached var [cached variable v] :: variables)
(cached list [cached list v] :: list)

It could be possible we'd use blocks like this, but only optional and probably not:

(cached var [cached variable v] of user [user] :: variables)
(cached list [cached list v] of user [user] :: list)

And definitely not:

store [local/project variable v] in cached [cached variable v] for user [user] :: variables

store [local/project list v] in cached [cached list v] for user [user] :: list

Not really what I was thinking, they could just look exactly the same as normal variables and lists, except with a symbol, like Cloud. They would just work exactly the same as normal variables, wouldn't need anything fancy. It would auto create a cookie file if the cookie file doesn't exist, then write to that.

liam48D wrote:

Lotsa support, here are some [scratchblocks] for it:

store [local/project variable v] in cached [cached variable v] :: variables

store [local/project list v] in cached [cached variable v] :: list

(cached var [cached variable v] :: variables)
(cached list [cached list v] :: list)

It could be possible we'd use blocks like this, but only optional and probably not:

(cached var [cached variable v] of user [user] :: variables)
(cached list [cached list v] of user [user] :: list)

And definitely not:

store [local/project variable v] in cached [cached variable v] for user [user] :: variables

store [local/project list v] in cached [cached list v] for user [user] :: list

I wouldn't say would work. It's stored on your computer, so it wouldn't have anything to do with your account. Unless you mean a local user (so you can save it in multiple places with different values), but there wouldn't really be much point in that.
It would be a lot simpler if they just worked like regular variables, just saved on your computer. Otherwise you'd have two versions of the variable, and if you were caching them there wouldn't be much point in having an uncached version anyway.

I have a better idea, rather than storing cached vars as cookies (which makes people complain about spam), “cached” vars should actually be stored with each Scratch user's account info on the Scratch server. That way, Scratchers can continue playing games even on other computers. To prevent spam on the Scratch servers, the same New Scratcher policy should be applied, and of course there will be a size limit on cached vars. If the vars get out of hand, Scratch should notify you

Uh oh! It looks like your account is out of cached variable space! Delete some of your old cached variables to continue:

[ ] [ Derp project 1 ]
[ X ] [ Epic game ]
[ ] [ Derp Swag ]
____________________________________________________________________
[ Delete and continue ] [ Don't delete and disable cached variables for now ]

And I also think Scratch should notify you about cloud data and cached variables just like it does for the username block

Warning: This project uses cloud data, which means it can communicate with Scratch servers. This may be useful for multiplayer games, opinion polls, and some other things. If you want this feature disabled, click the button below.
[ Dismiss ] [ Disable cloud data for this session ]

Warning: This project uses cached variables, which means it store data (such as save games) that it can access when you visit this project again. If you don't want this feature, click the button below.
[ Dismiss ] [ Disable cached variables for this session ]

Warning: This project uses the username block, which means it can see what your username is. It cannot see any other information about you, other than your your username. However, if you want this feature disabled, click the button below.
[ Dismiss ] [ Replace my username with ‘Anonymous’ for this session ]

$(".box-head")[0].textContent = "committing AT crimes since $whenever"

MegaApuTurkUltra wrote:

I have a better idea, rather than storing cached vars as cookies (which makes people complain about spam), “cached” vars should actually be stored with each Scratch user's account info on the Scratch server. That way, Scratchers can continue playing games even on other computers. To prevent spam on the Scratch servers, the same New Scratcher policy should be applied, and of course there will be a size limit on cached vars. If the vars get out of hand, Scratch should notify you

Uh oh! It looks like your account is out of cached variable space! Delete some of your old cached variables to continue:

[ ] [ Derp project 1 ]
[ X ] [ Epic game ]
[ ] [ Derp Swag ]
____________________________________________________________________
[ Delete and continue ] [ Don't delete and disable cached variables for now ]

And I also think Scratch should notify you about cloud data and cached variables just like it does for the username block

Warning: This project uses cloud data, which means it can communicate with Scratch servers. This may be useful for multiplayer games, opinion polls, and some other things. If you want this feature disabled, click the button below.
[ Dismiss ] [ Disable cloud data for this session ]

Warning: This project uses cached variables, which means it store data (such as save games) that it can access when you visit this project again. If you don't want this feature, click the button below.
[ Dismiss ] [ Disable cached variables for this session ]

Warning: This project uses the username block, which means it can see what your username is. It cannot see any other information about you, other than your your username. However, if you want this feature disabled, click the button below.
[ Dismiss ] [ Replace my username with ‘Anonymous’ for this session ]

Sounds like a good idea! I support.

when green flag clicked
wait until <I find a better signature>

epninja wrote:

liam48D wrote:

Lotsa support, here are some [scratchblocks] for it:

store [local/project variable v] in cached [cached variable v] :: variables

store [local/project list v] in cached [cached variable v] :: list

(cached var [cached variable v] :: variables)
(cached list [cached list v] :: list)

It could be possible we'd use blocks like this, but only optional and probably not:

(cached var [cached variable v] of user [user] :: variables)
(cached list [cached list v] of user [user] :: list)

And definitely not:

store [local/project variable v] in cached [cached variable v] for user [user] :: variables

store [local/project list v] in cached [cached list v] for user [user] :: list

Not really what I was thinking, they could just look exactly the same as normal variables and lists, except with a symbol, like Cloud. They would just work exactly the same as normal variables, wouldn't need anything fancy. It would auto create a cookie file if the cookie file doesn't exist, then write to that.

Yeah, something like:

(c cached var)
(c cached list :: list)
set [c cached var v] to [ ]
add [thing] to [c cached list  v]

(the “c” represents the cached symbol)

Blooper-Raptor wrote:

MegaApuTurkUltra wrote:

I have a better idea, rather than storing cached vars as cookies (which makes people complain about spam), “cached” vars should actually be stored with each Scratch user's account info on the Scratch server. That way, Scratchers can continue playing games even on other computers. To prevent spam on the Scratch servers, the same New Scratcher policy should be applied, and of course there will be a size limit on cached vars. If the vars get out of hand, Scratch should notify you

Uh oh! It looks like your account is out of cached variable space! Delete some of your old cached variables to continue:

[ ] [ Derp project 1 ]
[ X ] [ Epic game ]
[ ] [ Derp Swag ]
____________________________________________________________________
[ Delete and continue ] [ Don't delete and disable cached variables for now ]

And I also think Scratch should notify you about cloud data and cached variables just like it does for the username block

Warning: This project uses cloud data, which means it can communicate with Scratch servers. This may be useful for multiplayer games, opinion polls, and some other things. If you want this feature disabled, click the button below.
[ Dismiss ] [ Disable cloud data for this session ]

Warning: This project uses cached variables, which means it store data (such as save games) that it can access when you visit this project again. If you don't want this feature, click the button below.
[ Dismiss ] [ Disable cached variables for this session ]

Warning: This project uses the username block, which means it can see what your username is. It cannot see any other information about you, other than your your username. However, if you want this feature disabled, click the button below.
[ Dismiss ] [ Replace my username with ‘Anonymous’ for this session ]

Sounds like a good idea! I support.

support! Maybye if it was in the offline editor it could become cached!