Another Topic Of Mine

°°°°
So, you know how some people remix, and dont change anything? Thats like stealing, sort of.

My idea to stop that is that when you remix, a change detector is activated. When you share / try to share the remix, if nothing had changed in the coding or costumes, it would pop up saying “Sorry, it appears that your remix doesn't have any difference from the original project. Please make some changes before sharing.”

It also bugs me when people dont remove the instructions, or change them? Especially if they are a message from me to other people (not meant to be copied). Maybe there could also be a feature where something in the description has to change. Just an idea tho.

Also, for both of these, i think you should be able to turn these off or on for your project, for example, if it was a project that other people remix and sign if they eant to help something, but didnt need to change the desc.

Thats all

note: these ideas above have not been edited after further discussion….below is a more recent list


Ideas
- Pop Up ‘Suggestion’
- Change Detector
- Undeletable Credit Comment
- If a file is uploaded, check it for similarity to shared projects, then proceed with the system for Remixed Projects, listed above.
- Project Type Tag
- Same Description Detector

Cons
- Remix + Sign projects might not be allowed. ~ can be fixed with tag idea
- Support-By-Remixing projects might be taken down ~ can be fixed with tag idea
- Some people may avoid crediting still

Pros
- Stops exact-copy remixes
- Credit will be rightfully given
- We will have influenced Scratch, will would feel pretty cool!

Notes
- When people download a file then upload it they can evade the detector (idea: if a file is uploaded, check it for similarity to shared projects)
- At least a quarter of the project (if tag is not sign/remix/support) must be changed, including costumes, coding, and sounds

XxxxxxxxxxxxX

Snip Quotes Before Posting

I may be wrong but I'm pretty sure this is rejected

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.

I think this would be great! The Scratch Team has talked about it over the years and it would be a good feature to help stop exact copy remixes. The difficult issues might be deciding how much of a change would be required to allow the remix to be shared - and coming up with good messaging to let the person know why sharing wasn't happening - and what they have to do to satisfy the difference detector.

musicROCKS013 wrote:

I may be wrong but I'm pretty sure this is rejected

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.

…. I think that what im suggesting is an automatic version, as well as one that checks the description

Paddle2See wrote:

I think this would be great! The Scratch Team has talked about it over the years and it would be a good feature to help stop exact copy remixes. The difficult issues might be deciding how much of a change would be required to allow the remix to be shared - and coming up with good messaging to let the person know why sharing wasn't happening - and what they have to do to satisfy the difference detector.

Thanks for replying!
I think that it would be hard, but worth it…..
Like, i write a message that is finished with “from kattcrazy” and the remix (by another person) says the exact same, which would be incorrect.

Paddle2See wrote:

The difficult issues might be deciding how much of a change would be required to allow the remix to be shared

The only way this would really be possible is if you could detect if the project was EXACTLY the same. Like, changing one costume a little bit would suffice it, but at this point it is pretty much useless. The problem with this is about same problem with how the filter can't detect context.

Paddle2See wrote:

coming up with good messaging to let the person know why sharing wasn't happening

How about the “share” button is saturated or gray, indicating you can't press it, and on the project page instead of saying, “This project is not shared — so only you can see it. Click share to let everyone see it!” it could say something else, like "Try making more changes to the project before sharing it —Make your own unique creation!

musicROCKS013 wrote:

Paddle2See wrote:

The difficult issues might be deciding how much of a change would be required to allow the remix to be shared

The only way this would really be possible is if you could detect if the project was EXACTLY the same. Like, changing one costume a little bit would suffice it, but at this point it is pretty much useless. The problem with this is about same problem with how the filter can't detect context.

Paddle2See wrote:

coming up with good messaging to let the person know why sharing wasn't happening

How about the “share” button is saturated or gray, indicating you can't press it, and on the project page instead of saying, “This project is not shared — so only you can see it. Click share to let everyone see it!” it could say something else, like "Try making more changes to the project before sharing it —Make your own unique creation!

Maybe the message could be "Sorry, your remix of 's project ( ), appears to not have any changes, making it exactly the same as the project you remixed. This is highly dicouraged, and before you share the project, you must make a few small (or big ) changes, such as colouring, functions, or coding“

Or


”Sorry, your remix of 's project ( ), description appears to not have any changes, making it exactly the same as the project you remixed's descrption. This is highly dicouraged, and before you share the project, you must change the description. This could be by removing sections, personalizing, or maybe even correcting errors.

Paddle2See wrote:

. The difficult issues might be deciding how much of a change would be required to allow the remix to be shared

Well, i think that even just colour change would be a good start, but maybe 10+ coding blocks too?

Idk how it would detect that, but….

If this was implemented, should the ST be SUPER clear about remixing requirements, or make them kind of vague, such as the requirements on how to become a scratcher?

musicROCKS013 wrote:

If this was implemented, should the ST be SUPER clear about remixing requirements, or make them kind of vague, such as the requirements on how to become a scratcher?

I'm not sure…. I'll think about that

This is a duplicate so you should book the rest of the discussion there for organization!

Sliverus wrote:

This is a duplicate so you should book the rest of the discussion there for organization!

Sorry, what do you mean?

kattcrazy wrote:

Sliverus wrote:

This is a duplicate so you should book the rest of the discussion there for organization!

Sorry, what do you mean?

It means someone made the suggestion before so to keep the conversation organized let's continue talking there.

Sliverus wrote:

kattcrazy wrote:

Sliverus wrote:

This is a duplicate so you should book the rest of the discussion there for organization!

Sorry, what do you mean?

It means someone made the suggestion before so to keep the conversation organized let's continue talking there.

Im not planning to leave this thread… You go chat there if you want, this is different to that thread

kattcrazy wrote:

Im not planning to leave this thread… You go chat there if you want, this is different to that thread

It's good to keep the discussion in one place. You can post these ideas in that post.

musicROCKS013 wrote:

kattcrazy wrote:

Im not planning to leave this thread… You go chat there if you want, this is different to that thread

It's good to keep the discussion in one place. You can post these ideas in that post.

I'm still staying. They are different approaches

Sliverus wrote:

This is a duplicate so you should book the rest of the discussion there for organization!

musicROCKS013 wrote:

It's good to keep the discussion in one place. You can post these ideas in that post.

This doesn't really seem like the same idea to me - it's a rather different approach to the problem. Both could complement each other, though.

Harakou wrote:

Sliverus wrote:

This is a duplicate so you should book the rest of the discussion there for organization!

This doesn't really seem like the same idea to me - it's a rather different approach to the problem. Both could complement each other, though.

I agree! thanks for replying, i hope this feature will be considered

musicROCKS013 wrote:

If this was implemented, should the ST be SUPER clear about remixing requirements, or make them kind of vague, such as the requirements on how to become a scratcher?

kattcrazy wrote:

musicROCKS013 wrote:

If this was implemented, should the ST be SUPER clear about remixing requirements, or make them kind of vague, such as the requirements on how to become a scratcher?

I'm not sure…. I'll think about that

I think it should be clear so someone doesn’t get confused if it doesn’t let them share or get reported but they don’t understand
Because people under 8 use scratch or they just don’t get it.

Prince_Wolf1 wrote:

I think it should be clear so someone doesn’t get confused if it doesn’t let them share or get reported but they don’t understand
Because people under 8 use scratch or they just don’t get it.

Yeah. On one hand, a troll could make a bot to fulfill these requirements if they were too clear, but on the other hand innocent users could have trouble changing a project.
-
Plus, what is stopping someone from, after sharing the project, just reverting everything back to its original state?