Suppose I created a project with 'accounts' and passwords, and the passwords are stored in a cloud list. If someone saw inside the project, they would have access to all the passwords. What I propose is an option for 'locked' cloud variables. The values of these would not be accessible to anyone but the creator of the project. However, this would not change Scratch's core values; because if someone tried to view or change these, a notification box would appear with 'The creator of this project has locked these variables. To change the values, you must erase the(or create a new) cloud variable/list.'
Please note that locking/unlocking data would be an option. If the creator chose to use unlocked data, the values could be changed by anyone. Also, the values may be changed by the original program. Also, mods could see locked data (yes, the magical fix for any suggestion. ).
Supporters:
RedRocker227
joefarebrother
jcpopp
TorbyFork234
SJRCS_011
zippynk
stevetheipad
G0D_M0D3
pi3
James07
CheeseMunchy
Mokat
joletole
Markyparky
3DSfan12345
jontmy00
meowscratchcat
benjamin2
Lellowsfuzz
Last edited by technoboy10 (2012-05-19 13:40:57)
Offline
You could always encode the passwords using an encoder/decoder script...
Offline
joefarebrother wrote:
You could always encode the passwords using an encoder/decoder script...
Then they'd just check the script to see the method of encrypting though.
I support.
Offline
RedRocker227 wrote:
joefarebrother wrote:
You could always encode the passwords using an encoder/decoder script...
Then they'd just check the script to see the method of encrypting though.
I support.
Thanks!
Offline
OK, I support!
Offline
joefarebrother wrote:
OK, I support!
Great, thanks!
WHY, 60 SECOND RULE?!?!?!?
[/rant]
Offline
This is a great idea! I support!
Offline
jcpopp wrote:
This is a great idea! I support!
Thanks!
Offline
I support! This is exactly what I need to make the big project I wanted to make.
Offline
Not sure if I'm fully supporting this...yet.
One thing lightnin told me was that there will most likely be a Boolean sensing block for the player's scratch username. So you could make an "If username=stevetheipad, show" script. However, a person could download, change the = value to their username and see the sprite.
Offline
stevetheipad wrote:
Not sure if I'm fully supporting this...yet.
One thing lightnin told me was that there will most likely be a Boolean sensing block for the player's scratch username. So you could make an "If username=stevetheipad, show" script. However, a person could download, change the = value to their username and see the sprite.
It wouldn't be able to report your username offline, since, well, it's offline. Unless you for some reason have to log in offline, but that defeats the whole point of having it offline.
Though they could just tick the box which determines whether it's showing or hiding...
And it's a reporter you're thinking of, not a boolean.
Offline
stevetheipad wrote:
Not sure if I'm fully supporting this...yet.
One thing lightnin told me was that there will most likely be a Boolean sensing block for the player's scratch username. So you could make an "If username=stevetheipad, show" script. However, a person could download, change the = value to their username and see the sprite.
Exactly. I couldn't think of any way to prevent the problems I presented while still encouraging remixes. Oh, and where did lightnin tell you about the username thing?
Last edited by technoboy10 (2012-05-12 09:44:55)
Offline
SJRCS_011 wrote:
I'm already 99.999999999% sure this will already have been thought of by the ST.
But if it hasn't been, I support
TorbyFork234 wrote:
I support! This is exactly what I need to make the big project I wanted to make.
Thanks!
Last edited by technoboy10 (2012-05-12 09:46:39)
Offline
technoboy10 wrote:
SJRCS_011 wrote:
I'm already 99.999999999% sure this will already have been thought of by the ST.
But if it hasn't been, I supportTorbyFork234 wrote:
I support! This is exactly what I need to make the big project I wanted to make.
Thanks!
Thou hath misspelled my username
Offline
SJRCS_011 wrote:
technoboy10 wrote:
SJRCS_011 wrote:
I'm already 99.999999999% sure this will already have been thought of by the ST.
But if it hasn't been, I supportTorbyFork234 wrote:
I support! This is exactly what I need to make the big project I wanted to make.
Thanks!
Thou hath misspelled my username
Nooooooooooooo
I'll change it.
Offline
Hey y'all! Check out the Scratch Suggestions page here: http://suggest.scratch.mit.edu/forums/6 … cloud-data
Please vote for it!
Offline
I'm pretty sure the st is making them locked, but if not, then I support!
Offline
ya i support i can make a mmo with this
Offline
This probably won't happen. It's still keeping information secret, and could be abused.
Also, the user could just get around it with
say (☁ passwords)You just have to hash them.
Offline
RedRocker227 wrote:
joefarebrother wrote:
You could always encode the passwords using an encoder/decoder script...
Then they'd just check the script to see the method of encrypting though.
I support.
But if it were hashing, it wouldn't be crackable.
Offline
http://en.wikipedia.org/wiki/SHA-1#SHA-1_pseudocode
when 2.0 comes out somebody in AT surely will make a script
Offline
veggieman001 wrote:
RedRocker227 wrote:
joefarebrother wrote:
You could always encode the passwords using an encoder/decoder script...
Then they'd just check the script to see the method of encrypting though.
I support.But if it were hashing, it wouldn't be crackable.
How do you 'hash' info in Scratch? The only reason I suggested this was because of a project I want to make that uses accounts.
Offline