Scratch

SJRCS_011 wrote:

Though with 2.0 coming up, i have an idea.
Maybe there is some way that the editor can check to see if the new project file is the exact same as the old one, minus the section about what the project is based on.  True, there would be many ways to cheat this, but at least it would prevent about 90% of direct copies (my estimate), so it may be worth putting into place.
TL,DR: Machine check each file to see if it's a duplicate
TL,DR:TL,DR: Machine check thing for double 

The development team is actually exploring ideas very similar to this in Scratch 2.0!  Better ways of stopping direct copies and better ways to show credit.  We know this is a problem area.

I suggest some kind of auto-credit feature for 2.0. Simply a list with names (links) of creators to previous iterations of the project. A user should perhaps be able to add names to this list, but not subtract names he himself did not add to it. (Or maybe what I just said should be links to the referenced projects instead of the creators.)

Also, fellow scratchers visiting a project should perhaps be able to "suggest" names that should be referenced.

My son who just turned 8 today is happily learning Scratch. It is so much fun and I would not be surprised if he is a great contributor to the coding community one day. As for now, though, it is SIMPLY too much to expect him to credit stuff properly. He can't even remember to put on his t-shirt. And it CANNOT fairly be compared to "theft" because code is a lot more abstract than "a candy" or whatever, especially when you are *supposed* to download other peoples code and learn/experiment/manipulate it. As for my soon 10 yr old daughter, she might better grasp the "theft" aspect but the greater concern, for me, is to keep her interest up in Scratch all together. Anything that is boring would just, well, you get it. The way to do it is to have the *system* do it automatically. If properly designed, it'll set a good role model for kids to learn from. And one day they will experience someone else using their work and begin to *understand* the concern.

Also if the system deals with this, it should be simple to keep track of whose work is used/copied etc - which is something that the original creator should get credit for! I suggest a "Top Inspirator List" or some such, showcasing the most "copied" projects to give them the honor they deserve. Copying IS after all a definite sign for appreciation, much more than a "like" vote.

Thank you!

northmeister wrote:

Lots of my projects are remixed without the remixer changing anything. I reported them, and it said remixing is allowed and you have to try to support it or something. I agree when they change stuff, but not if they don't change anything. In my minecraft series, someone copied Minecraft Cool Stuff Part 7, kept the title exactly the same (they didn't even change it to part 1 as they hadn't made any before), they kept the notes the same with my upcoming projects and such, and it got quite a few views from people who didn't see the based on sign and thought that they had made it. I've seen quite a few copied projects without a based on link, when the copiers import the project into a new project, and it's completely unacceptable.

First, ask nicely about credit or deleting the project, if the comments are not locked. If the comments are not locked, type in that you made it in the tag. If it still does not work, tell the remixer that you will flag it. If that still does not work, flag the project.
When you flag a copied project, you will need to describe how it is inappropiate. So, you need to say that it was a copied version. That way, the ST will listen more. I once flagged a copied project, told them it was a copied one, and in a few days, when I looked at the remix, there was only a scratch cat in the screen, which meant that it was removed.
I hope this helps. 

TorbyFork234 wrote:

I don't support.

Many new scratchers are trying to see how the scratch program works. They look at the front page and say, "Hey, these projects are so good they're on the front page. What is it?"
Then they see it, and sometimes are amazed enough to download it to see how it works. Then they start experimenting by changing a number here and there, changing the color effect by somewhat. It helps them learn about the scratch program.

But, I also flag outright copies, or ones with the exact same project notes with almost no changes. But I think they have the right to upload a tinkered with project.

You are talking about remixing projects, but here, we are talking about copied projects. Project copying is NOT allowed and should be dealt with. Remixing helps, but scratchers can't copy projects.

Last edited by joshuaho (2013-03-21 16:27:04)

boardsmm wrote:

I suggest some kind of auto-credit feature for 2.0. Simply a list with names (links) of creators to previous iterations of the project. A user should perhaps be able to add names to this list, but not subtract names he himself did not add to it. (Or maybe what I just said should be links to the referenced projects instead of the creators.)

Also, fellow scratchers visiting a project should perhaps be able to "suggest" names that should be referenced.

My son who just turned 8 today is happily learning Scratch. It is so much fun and I would not be surprised if he is a great contributor to the coding community one day. As for now, though, it is SIMPLY too much to expect him to credit stuff properly. He can't even remember to put on his t-shirt. And it CANNOT fairly be compared to "theft" because code is a lot more abstract than "a candy" or whatever, especially when you are *supposed* to download other peoples code and learn/experiment/manipulate it. As for my soon 10 yr old daughter, she might better grasp the "theft" aspect but the greater concern, for me, is to keep her interest up in Scratch all together. Anything that is boring would just, well, you get it. The way to do it is to have the *system* do it automatically. If properly designed, it'll set a good role model for kids to learn from. And one day they will experience someone else using their work and begin to *understand* the concern.

Also if the system deals with this, it should be simple to keep track of whose work is used/copied etc - which is something that the original creator should get credit for! I suggest a "Top Inspirator List" or some such, showcasing the most "copied" projects to give them the honor they deserve. Copying IS after all a definite sign for appreciation, much more than a "like" vote.

Thank you!

+1
Especially the "Top Inspirator List". That was a stroke of genius. If someone copies, they're just helping the victim! Although the only problem with this is that someone could create multiple accounts and remix one project to get it to top inspirator.