I've noticed that a few Scratchers don't want their projects to be remixed. Of course, the entire thing with Scratch is that you may share ideas and others may remix. But here's the thing: PEOPLE DON'T GIVE CREDIT. That is a big reason why some people don't like their projects being remixed, the original project took a long time to make, and somebody remixes without changing anything or giving any sort of credit to the creator of the original project. So, I believe that there should be an option to turn off remixing. You may turn remixing back on whenever you wish, but if remixing is turned off, nobody can remix your project. Should this be an update?

Firstly, all remixes already give automatic credit to the project remix.

Secondly, the sticky of rejected suggestions has a few words about restricting remixes:

jvvg wrote:

3. Disabling “See inside”, restricting sharing, etc.
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).

Restricting sharing (i.e. sharing a project so only some people can see it) is also not going to be implemented.

Paddle2See wrote:

We depend very heavily on our community to help us keep an eye on things and make sure that the Community Guidelines are being followed. Reducing the number of people that can see a project increases the likelihood that inappropriate content could be shared without being reported. That's a risk that we are not willing to take. Keeping everything out in the open is the best way we have found to help keep Scratch friendly and safe.
(source)

14. Banning minor remixes
Remixes are allowed as long as at least something is changed, even if it's minor.

Sheep_maker wrote:

Firstly, all remixes already give automatic credit to the project remix.

Secondly, the sticky of rejected suggestions has a few words about restricting remixes:

jvvg wrote:

3. Disabling “See inside”, restricting sharing, etc.
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).

Restricting sharing (i.e. sharing a project so only some people can see it) is also not going to be implemented.

Paddle2See wrote:

We depend very heavily on our community to help us keep an eye on things and make sure that the Community Guidelines are being followed. Reducing the number of people that can see a project increases the likelihood that inappropriate content could be shared without being reported. That's a risk that we are not willing to take. Keeping everything out in the open is the best way we have found to help keep Scratch friendly and safe.
(source)

14. Banning minor remixes
Remixes are allowed as long as at least something is changed, even if it's minor.

Stop pointing out everything wrong in my forums and just chill. 1- I'm not perfect. 2- I don't normally read other forums. 3- We're different people with different views. So stop. Please.

While this unfortunately is rejected, I agree.
And I do agree that giving credit should have stricter rules.

Dreamy_Vela wrote:

Sheep_maker wrote:

Firstly, all remixes already give automatic credit to the project remix.

Secondly, the sticky of rejected suggestions has a few words about restricting remixes:

jvvg wrote:

3. Disabling “See inside”, restricting sharing, etc.
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).

Restricting sharing (i.e. sharing a project so only some people can see it) is also not going to be implemented.

Paddle2See wrote:

We depend very heavily on our community to help us keep an eye on things and make sure that the Community Guidelines are being followed. Reducing the number of people that can see a project increases the likelihood that inappropriate content could be shared without being reported. That's a risk that we are not willing to take. Keeping everything out in the open is the best way we have found to help keep Scratch friendly and safe.
(source)

14. Banning minor remixes
Remixes are allowed as long as at least something is changed, even if it's minor.

Stop pointing out everything wrong in my forums and just chill. 1- I'm not perfect. 2- I don't normally read other forums. 3- We're different people with different views. So stop. Please.

that's kind of the point of the suggestions forum

Dreamy_Vela wrote:

I've noticed that a few Scratchers don't want their projects to be remixed. Of course, the entire thing with Scratch is that you may share ideas and others may remix. But here's the thing: PEOPLE DON'T GIVE CREDIT. That is a big reason why some people don't like their projects being remixed, the original project took a long time to make, and somebody remixes without changing anything or giving any sort of credit to the creator of the original project. So, I believe that there should be an option to turn off remixing. You may turn remixing back on whenever you wish, but if remixing is turned off, nobody can remix your project. Should this be an update?

-* Feedback *-

If these Scratchers didn't want their project remixed, they shouldn't share it! People are allowed to remix. Yes, it is wrong to steal someone else's work, but we have “Original Project: …” in the bottom of the Notes and Credits! Being able to toggle the remix button restricts the freedoms on here, say if someone finds a lag error or bug, and the owner locks it. They won't be able to remix it correctly for the owner, and explaining the bug will be hard and long.

Dreamy_Vela wrote:

Sheep_maker wrote:

Firstly, all remixes already give automatic credit to the project remix.

Secondly, the sticky of rejected suggestions has a few words about restricting remixes:

jvvg wrote:

3. Disabling “See inside”, restricting sharing, etc.
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).

Restricting sharing (i.e. sharing a project so only some people can see it) is also not going to be implemented.

Paddle2See wrote:

We depend very heavily on our community to help us keep an eye on things and make sure that the Community Guidelines are being followed. Reducing the number of people that can see a project increases the likelihood that inappropriate content could be shared without being reported. That's a risk that we are not willing to take. Keeping everything out in the open is the best way we have found to help keep Scratch friendly and safe.
(source)

14. Banning minor remixes
Remixes are allowed as long as at least something is changed, even if it's minor.

Stop pointing out everything wrong in my forums and just chill. 1- I'm not perfect. 2- I don't normally read other forums. 3- We're different people with different views. So stop. Please.

Oh come on. Just because a person helpfully posts some good arguments about the topic from a sticky, means they are being offensive to you? No.

BTW the sticky he/she is quoting is a sticky from the same forum as we are on now.

I agree that its very annoying if someone remixes your project and doesn't give credit but normally (and I say normally cause maybe there are cases where this doesn't happen) the original project will still get nearly all the views and loves so it doesn't really matter. It really doesn't matter if people remix your project without credit as they go relatively unnoticed anyway if they didn't change anything major. Besides, I think many new scratchers remix projects just as a way to keep them somewhere so they can play them again later. (mabye)

Remixing is a big part of Scratch - I don't see it becoming optional. We feel that remixing is a great way for beginning coders to learn to program. Or, new artists to experiment with new styles. Remixing let's them tinker with any project on the site.. When you share stuff on Scratch, you are giving permission to all Scratchers to reuse any parts of your project in any way they want, as long as they add their own ideas and give you credit. In exchange, you get to reuse any parts of their projects. That's how Scratch is set up — sharing is a big part of it.

If no credit is being given, please use the Report button to let the Scratch Team moderators know about it.