LP_Play wrote:

Austinato wrote:

Digital_Gaming wrote:

But the ST has no problems keeping up with reporting projects. Implementing this will be more work than just clicking report. Even less support.

I understand your concept and reasoning for “no problems with keeping up with reporting projects,” but this could help reduce the amount of directly duplicated projects, and if any somehow makes it through this filter, then they should be legitimate or just a very minimal tweak.

My concern is, if someone just adds an useless block* to the project, i.e.:

move (0) steps

Would that allow them to bypass “CloneAlert”?

Thanks for reading,
Austinato

(Edit: *Useless block meaning a block that does not serve a purpose. The move block is useful, but entering the value of “0” will not help.)

There's still the majestic report button

shd02 wrote:

LP_Play wrote:

Austinato wrote:

Digital_Gaming wrote:

But the ST has no problems keeping up with reporting projects. Implementing this will be more work than just clicking report. Even less support.

I understand your concept and reasoning for “no problems with keeping up with reporting projects,” but this could help reduce the amount of directly duplicated projects, and if any somehow makes it through this filter, then they should be legitimate or just a very minimal tweak.

My concern is, if someone just adds an useless block* to the project, i.e.:

move (0) steps

Would that allow them to bypass “CloneAlert”?

Thanks for reading,
Austinato

(Edit: *Useless block meaning a block that does not serve a purpose. The move block is useful, but entering the value of “0” will not help.)

There's still the majestic report button

I already made a list of scripts that the CloneAlert should not allow. It's on post #47. I haven't thought of this block so I'll add it to the list.

Austinato wrote:

Digital_Gaming wrote:

But the ST has no problems keeping up with reporting projects. Implementing this will be more work than just clicking report. Even less support.

I understand your concept and reasoning for “no problems with keeping up with reporting projects,” but this could help reduce the amount of directly duplicated projects.

Thanks for reading,
Austinato

Digital_Gaming wrote:

Austinato wrote:

Digital_Gaming wrote:

But the ST has no problems keeping up with reporting projects. Implementing this will be more work than just clicking report. Even less support.

I understand your concept and reasoning for “no problems with keeping up with reporting projects,” but this could help reduce the amount of directly duplicated projects.

Thanks for reading,
Austinato

Sure. But I'm just worried that new Scratchers won't know about the remix button and will get frustrated and might even quit Scratch. But I agree with your point above.

Oh noes! You were caught by the CloneAlert filter!

______________

The CloneAlert filter prevents users from directly remixing a project without changing anything (or something, at a bare minimum.) Adding, removing, or even significantly modifying content in the remixed project won't cause this to pop up again!
______________

Thank you for reading, and Scratch on!

shd02 wrote:

• adding a repeated block that has no effect such as this:
  

  when green flag clicked
  show
  show

  adding a block that would not change anything (An example is adding a “show” block when the sprite is already shown and the sprite has no “hide” blocks anywhere.")
  
  
• adding or removing a variable or list that has no uses and is not displayed (no reporter blocks of that variable or list)
  
  
• moving a script or adding blocks that are not connected to hat blocks
  
  
• changing the stage or costumes by adding parts that cannot be seen such as adding a shape within another shape of the same color, or grouping and ungrouping the stage and costumes
  
  
• adding a backdrop or costume that is never used
  
  
• adding empty “if”, “if else”, or repeat () blocks or adding “if” or “if else” blocks with booleans that always return false, or adding “repeat” or “repeat until” blocks with booleans that always return true.
  
  
• adding a c-block that has no effect to any blocks inside(An example is a repeat (1) block).
  
  
• adding custom block definitions that do not have any uses of the actual custom block or adding broadcasts with no uses of the “when I receive” block
  
  
• adding hat blocks with no blocks under the hat block
  
  
• using a block with inputs that produce no effect such as “move 0 steps”.
  
  
• Edit: using a block with inputs that produce no effect such as “move 0 steps”.

when this sprite clicked
turn cw (15) degrees
repeat (1)
end
turn cw (15) degrees

Jonathan50 wrote:

shd02 wrote:

• adding a repeated block that has no effect such as this:
  

  when green flag clicked
  show
  show

  adding a block that would not change anything (An example is adding a “show” block when the sprite is already shown and the sprite has no “hide” blocks anywhere.")
  
  
• adding or removing a variable or list that has no uses and is not displayed (no reporter blocks of that variable or list)
  
  
• moving a script or adding blocks that are not connected to hat blocks
  
  
• changing the stage or costumes by adding parts that cannot be seen such as adding a shape within another shape of the same color, or grouping and ungrouping the stage and costumes
  
  
• adding a backdrop or costume that is never used
  
  
• adding empty “if”, “if else”, or repeat () blocks or adding “if” or “if else” blocks with booleans that always return false, or adding “repeat” or “repeat until” blocks with booleans that always return true.
  
  
• adding a c-block that has no effect to any blocks inside(An example is a repeat (1) block).
  
  
• adding custom block definitions that do not have any uses of the actual custom block or adding broadcasts with no uses of the “when I receive” block
  
  
• adding hat blocks with no blocks under the hat block
  
  
• using a block with inputs that produce no effect such as “move 0 steps”.
  
  
• Edit: using a block with inputs that produce no effect such as “move 0 steps”.

What if a New Scratcher is playing around and doesn't yet understand that these don't make a difference to the project, or they're playing with it in the editor?

If someone adds backdrops, costumes, broadcasts or custom blocks that aren't being used, they may later edit it again and add uses for them, and if there's a hat block with no blocks under it blocks may later be added under it. The number in “move 0 steps” could also be changed later.

An empty “repeat 1” causes a yield and the stage will be redrawn. See this project by tmmit, go into Sprite2 and change it to

when this sprite clicked
turn cw (15) degrees
repeat (1)
end
turn cw (15) degrees

.

Austinato wrote:

I'm not sure if that scenario would happen frequently (but don't get me wrong, that would be bad if it happens), as remixing isn't crucial to Scratch (you still have the benefit of backpacking, creating projects that are not remixed, etc.)

That does make me want to suggest something; instead of directly punishing the user, just tell them:

Oh noes! You were caught by the CloneAlert filter!

______________

The CloneAlert filter prevents users from directly remixing a project without changing anything (or something, at a bare minimum.) Adding, removing, or even significantly modifying content in the remixed project won't cause this to pop up again!
______________

Thank you for reading, and Scratch on!

Thank you for reading,
Austinato

shd02 wrote:

A problem is that someone could be working on a remix like @Jonathan50 wrote. Maybe someone just wants to click the remix button without changing the project so they can work on the project later as an unshared project. My idea would be to allow all types of unshared remixes but not allow sharing remixes that make no changes.

Oh noes! You were caught by the CloneAlert filter!

______________

The CloneAlert filter prevents users from directly remixing (and sharing) a project without changing much. Adding, removing, or even significantly modifying conntent in the remixed project won't cause this to happen again!
______________

Thank you for reading, and Scratch on!

shd02 wrote:

[What if a New Scratcher is playing around and doesn't yet understand that these don't make a difference to the project, or they're playing with it in the editor?

If someone adds backdrops, costumes, broadcasts or custom blocks that aren't being used, they may later edit it again and add uses for them, and if there's a hat block with no blocks under it blocks may later be added under it.

shd02 wrote:

I meant adding a repeat (1) block with a section of other blocks inside that were in the original project.

To solve the other problems, the CloneAlert system could just prevent the project from being shared but allow an unshared remix.

Jonathan50 wrote:

shd02 wrote:

I meant adding a repeat (1) block with a section of other blocks inside that were in the original project.

That still causes a yield, like how it is originally in tmmit's project.

when green flag clicked
repeat (1)
turn cw (15) degrees
turn cw (15) degrees
end

when green flag clicked
set [variable v] to [0]
repeat (1)
change [variable v] by (1)
end
change [variable v] by (1)

Brad-TV wrote:

Hi everyone! I had an idea that might help improve scratch. I hate copy remixes, so I thought maybe add something called a “Copy Remix Detector!” Basically, in a remix, when you click the share button and nothing's changed, it will say “Hmm… it seems you didn't change anything in your remix. Please change something.” or something like that. I think this would help improve the remixing feature on this site.

jokebookservice1 wrote:

Brad-TV wrote:

Hi everyone! I had an idea that might help improve scratch. I hate copy remixes, so I thought maybe add something called a “Copy Remix Detector!” Basically, in a remix, when you click the share button and nothing's changed, it will say “Hmm… it seems you didn't change anything in your remix. Please change something.” or something like that. I think this would help improve the remixing feature on this site.

By change something, do you mean move some scripts around, or change the order of backgrounds (which *could* help somebody who has a bug due to their costume numbers). Maybe renaming a variable?

All these things are changes, but do they count as ones that are valid for remixing?

Tyler_The_Yoshi wrote:

This Is A Fantastic Idea!

Brad-TV wrote:

Hi everyone! I had an idea that might help improve scratch. I hate copy remixes, so I thought maybe add something called a “Copy Remix Detector!” Basically, in a remix, when you click the share button and nothing's changed, it will say “Hmm… it seems you didn't change anything in your remix. Please change something.” or something like that. I think this would help improve the remixing feature on this site.

Tyler_The_Yoshi wrote:

This Is A Fantastic Idea!

KawaiiCatGirl- wrote:

Tyler_The_Yoshi wrote:

This Is A Fantastic Idea!

I second that

finnb4513 wrote:

Support! I also think it will improve Scratch.

Brad-TV wrote:

Hi everyone! I had an idea that might help improve scratch. I hate copy remixes, so I thought maybe add something called a “Copy Remix Detector!” Basically, in a remix, when you click the share button and nothing's changed, it will say “Hmm… it seems you didn't change anything in your remix. Please change something.” or something like that. I think this would help improve the remixing feature on this site.