BigNate469 wrote:

(#69)
Bumping this out of nowhere.

It seems that the ST is actually doing something like this, in an experimental stage: https://github.com/scratchfoundation/scratch-similarity-experiments

A-MARIO-PLAYER wrote:

BigNate469 wrote:

(#69)
Bumping this out of nowhere.

It seems that the ST is actually doing something like this, in an experimental stage: https://github.com/scratchfoundation/scratch-similarity-experiments

FINALLY WE WIN

when I receive [something that will never happen v]
hide
say []

TheEpikGamer211 wrote:

you can just move one singular script and go by without it going off.

1080GBA wrote:

Good idea but someone will just add a useless block and its now technically different

ThisIsTemp1 wrote:

TheEpikGamer211 wrote:

you can just move one singular script and go by without it going off.

This is not to prevent stealing. This is to tell people that exact remixing is not allowed.

ThisIsTemp1 wrote:

TheEpikGamer211 wrote:

you can just move one singular script and go by without it going off.

This is not to prevent stealing. This is to tell people that exact remixing is not allowed.

Someone wrote:
You could just do this:

when green flag clicked 
wait (0) secs

ThisIsTemp1 wrote:

TheEpikGamer211 wrote:

you can just move one singular script and go by without it going off.

This is not to prevent stealing. This is to tell people that exact remixing is not allowed.

gdfsgdfsgdfg wrote:

add a change meter that when a scratcher changes enough of their own remix of a project
the scratcher who remixed the project can be share their own remix (like 10%-20% of the project)
problem solved

-ShadowOfTheFuture- wrote:

sti_scratch wrote:

I agree.

But the blocker should block every remix except if the remix includes one or more of these criteria:

- Adds one or more blocks in a script, excluding blocks in the “Control” tab.
- Adds one more script with at least one block from the “Events” tab.

Well, yeah, but what if somebody added another script, remixed the project, and removed it?

No support, this would be way too easy to work around. Support for the concept, though, but it would be really hard to implement a foolproof copy-preventing system.

ImMaximum wrote:

Guys. Be reasonable.

If someone doesn't make any changes to a project, clearly they need to make changes.
If they have to change one thing and for it to be allowed to be posted, that still decreases the amount of copies by half and can motivate remixers to actually change things. This suggestion has way more upsides than downsides.

SUPPORT

gdfsgdfsgdfg wrote:

(#94)
add a change meter that when a scratcher changes enough of their own remix of a project
the scratcher who remixed the project can be share their own remix (like 10%-20% of the project)
problem solved

The Official List of Rejected Suggestions wrote:

3.2 Disable remixing or censor minor remixes

One of the most important ideas of Scratch is the share aspect. Scratch is a website not only for displaying your work, but also for sharing it with others, and by posting your project on the Scratch website you agree to allow others to remix your work. You are not allowed to write “Do not remix this project” in the Notes and Credits of your project; you may get alerted for this, because it discourages remixing. This suggestion extends to the ability to require permission to remix a project, as you have already given permission to others to use your creations by sharing a project on Scratch; for more information, see this post.

‎

A remix of a project is allowed on Scratch, even if the remix only contains minor changes (this includes recolors). However, when you remix a project, you should put in the Notes and Credits what you changed. If you see a project that contains no noticeable changes, please use the Report button on it so the Scratch Team can take a look at it. This suggestion extends to “extremely minor remixes,” such as a remix of a game that gives you 2 points per second instead of 1. As long as the user explains what they changed about the project and gives proper credit, this is okay.

‎

However, a feature that prevents unchanged remixes from being shared is NOT rejected. You can discuss it on this topic.

View source

The Official List of Rejected Suggestions wrote:

3.2 Disable remixing or censor minor remixes

One of the most important ideas of Scratch is the share aspect. Scratch is a website not only for displaying your work, but also for sharing it with others, and by posting your project on the Scratch website you agree to allow others to remix your work. You are not allowed to write “Do not remix this project” in the Notes and Credits of your project; you may get alerted for this, because it discourages remixing. This suggestion extends to the ability to require permission to remix a project, as you have already given permission to others to use your creations by sharing a project on Scratch; for more information, see this post.

‎

A remix of a project is allowed on Scratch, even if the remix only contains minor changes (this includes recolors). However, when you remix a project, you should put in the Notes and Credits what you changed. If you see a project that contains no noticeable changes, please use the Report button on it so the Scratch Team can take a look at it. This suggestion extends to “extremely minor remixes,” such as a remix of a game that gives you 2 points per second instead of 1. As long as the user explains what they changed about the project and gives proper credit, this is okay.

‎

However, a feature that prevents unchanged remixes from being shared is NOT rejected. You can discuss it on this topic.

View source