Hide contents of lists and variables from view

Tbtemplex97

How about the ability for project creators to hide the data inside of lists and variables to stop people from gaining possibly sensitive information from clicking see inside?

Wes64

Tbtemplex97 wrote:
How about the ability for project creators to hide the data inside of lists and variables to stop people from gaining possibly sensitive information from clicking see inside?

You could always encrypt the information somehow. I doubt anyone is determined enough to crack even a basic cypher, so that might work.

Tbtemplex97

Yes but it would save alot of effort if one could simply have this:

Zro716

no support. the way you say “sensitive information” implies you are trying to gather personal information from other users or that you are trying to create a blacklist of sorts, both of which are not acceptable here. so could you clarify what you mean by “sensitive”?

theonlygusti

How on earth could you gather sensitive information about someone?

gcenac

This bassicly fits under this…
To quote @jvvg

3. Disabling “See inside” (formerly locking downloads)
Several people want to be able to lock their projects so that they are read-only, and other people can't see the code to copy their scripts, sounds, or artwork. However, the motto of Scratch is “Imagine - Program - Share”. By putting a project on the site, you give anyone who sees it the right to see your code, all data in it, and potentially copy it. Part of the whole goal of Scratch is remixing. If you do not wish to allow this, then you are welcome to publish the project on your own site (once the downloadable Scratch 2.0 comes out).

And as it sais, "Imagine, Program, Share"

OmnipotentPotato

gcenac wrote:
This bassicly fits under this…
To quote @jvvg
3. Disabling “See inside” (formerly locking downloads)
Several people want to be able to lock their projects so that they are read-only, and other people can't see the code to copy their scripts, sounds, or artwork. However, the motto of Scratch is “Imagine - Program - Share”. By putting a project on the site, you give anyone who sees it the right to see your code, all data in it, and potentially copy it. Part of the whole goal of Scratch is remixing. If you do not wish to allow this, then you are welcome to publish the project on your own site (once the downloadable Scratch 2.0 comes out).
And as it sais, "Imagine, Program, Share"

No support as per the sticky.

I recommend encryption

RandomPerson1789

no support

Centrifugal

gcenac wrote:
This bassicly fits under this…
To quote @jvvg
3. Disabling “See inside” (formerly locking downloads)
Several people want to be able to lock their projects so that they are read-only, and other people can't see the code to copy their scripts, sounds, or artwork. However, the motto of Scratch is “Imagine - Program - Share”. By putting a project on the site, you give anyone who sees it the right to see your code, all data in it, and potentially copy it. Part of the whole goal of Scratch is remixing. If you do not wish to allow this, then you are welcome to publish the project on your own site (once the downloadable Scratch 2.0 comes out).
And as it sais, "Imagine, Program, Share"

TheHockeyist

OmnipotentPotato wrote:
gcenac wrote:
This bassicly fits under this…
To quote @jvvg
3. Disabling “See inside” (formerly locking downloads)
Several people want to be able to lock their projects so that they are read-only, and other people can't see the code to copy their scripts, sounds, or artwork. However, the motto of Scratch is “Imagine - Program - Share”. By putting a project on the site, you give anyone who sees it the right to see your code, all data in it, and potentially copy it. Part of the whole goal of Scratch is remixing. If you do not wish to allow this, then you are welcome to publish the project on your own site (once the downloadable Scratch 2.0 comes out).
And as it sais, "Imagine, Program, Share"
No support as per the sticky.

I recommend encryption

As per OmnipotentPotato.

DemCupcakesYo

TheHockeyist wrote:
OmnipotentPotato wrote:
gcenac wrote:
This bassicly fits under this…
To quote @jvvg
3. Disabling “See inside” (formerly locking downloads)
Several people want to be able to lock their projects so that they are read-only, and other people can't see the code to copy their scripts, sounds, or artwork. However, the motto of Scratch is “Imagine - Program - Share”. By putting a project on the site, you give anyone who sees it the right to see your code, all data in it, and potentially copy it. Part of the whole goal of Scratch is remixing. If you do not wish to allow this, then you are welcome to publish the project on your own site (once the downloadable Scratch 2.0 comes out).
And as it sais, "Imagine, Program, Share"
No support as per the sticky.

I recommend encryption
As per OmnipotentPotato.

I agree, no support. I can't think of any “sensitive info” other than a user's password.

danielhal

No support. What would happen in remixes? They would be harder to make properly.

Discuss Scratch