Blowphie wrote:

I saw someone comment this (i forget who:
“We should have a button to prevent remixing, so if you don't want your project to be remixed” (this is what I'm saying now->) and you can just turn it on and off, like for closed maps, cc's, artwork, ect. I doubt it will happen, but it's just a little suggestion

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).

1004587 wrote:

Blowphie wrote:

I saw someone comment this (i forget who:
“We should have a button to prevent remixing, so if you don't want your project to be remixed” (this is what I'm saying now->) and you can just turn it on and off, like for closed maps, cc's, artwork, ect. I doubt it will happen, but it's just a little suggestion

Rejected by stickies:

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).

cs156175 wrote:

1004587 wrote:

Blowphie wrote:

I saw someone comment this (i forget who:
“We should have a button to prevent remixing, so if you don't want your project to be remixed” (this is what I'm saying now->) and you can just turn it on and off, like for closed maps, cc's, artwork, ect. I doubt it will happen, but it's just a little suggestion

Rejected by stickies:

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).

not necessarily. disabling remixes is not the same as disabling see inside. people could still look inside, just not save it as their own. support, though there should be a way to turn it off and on.

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.

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..

1004587 wrote:

cs156175 wrote:

1004587 wrote:

Blowphie wrote:

I saw someone comment this (i forget who:
“We should have a button to prevent remixing, so if you don't want your project to be remixed” (this is what I'm saying now->) and you can just turn it on and off, like for closed maps, cc's, artwork, ect. I doubt it will happen, but it's just a little suggestion

Rejected by stickies:

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).

not necessarily. disabling remixes is not the same as disabling see inside. people could still look inside, just not save it as their own. support, though there should be a way to turn it off and on.

You even read?
sry
But it also says:

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.

I'll zoom in:

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..

ok, i read that. i actually misunderstood the post. i thought it was against the “turn off remix identity” hack people use to hide their project being remixed. i didn't realize it was that. i understand.

therealpsy wrote:

No support.
If you turn off remixes, you might not get to see how funny the remixes could have been.

1004587 wrote:

Blowphie wrote:

I saw someone comment this (i forget who:
“We should have a button to prevent remixing, so if you don't want your project to be remixed” (this is what I'm saying now->) and you can just turn it on and off, like for closed maps, cc's, artwork, ect. I doubt it will happen, but it's just a little suggestion

Rejected by stickies:

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).