Support! I hate stolen material, but that scratcher that stole your project probably got an alert.

Yknow, just as a punishment, it shouldn't say remixed, it should say stolen instead.
Like when you remix a stolen project, it just says (Stolen Project) instead of (Remixed Project). It'd teach people to not steal projects

miniepicness wrote:

Yknow, just as a punishment, it shouldn't say remixed, it should say stolen instead.
Like when you remix a stolen project, it just says (Stolen Project) instead of (Remixed Project). It'd teach people to not steal projects

That is a good idea. This way the system can keep better track of what protects were detected by this so the owner can remove it if it is for
something like moving accounts the user can do that without having the remix of thing making the notes/instructions of the project smaller.

muellly wrote:

miniepicness wrote:

Yknow, just as a punishment, it shouldn't say remixed, it should say stolen instead.
Like when you remix a stolen project, it just says (Stolen Project) instead of (Remixed Project). It'd teach people to not steal projects

That is a good idea. This way the system can keep better track of what protects were detected by this so the owner can remove it if it is for
something like moving accounts the user can do that without having the remix of thing making the notes/instructions of the project smaller.

So there could be a “Mark Not Remixed or Stolen” button?

Edit: This should also happen with backpack'd scripts and sprites, they should say, in the code, “stolen from (project link)”

miniepicness wrote:

muellly wrote:

miniepicness wrote:

Yknow, just as a punishment, it shouldn't say remixed, it should say stolen instead.
Like when you remix a stolen project, it just says (Stolen Project) instead of (Remixed Project). It'd teach people to not steal projects

That is a good idea. This way the system can keep better track of what protects were detected by this so the owner can remove it if it is for
something like moving accounts the user can do that without having the remix of thing making the notes/instructions of the project smaller.

So there could be a “Mark Not Remixed or Stolen” button?

Edit: This should also happen with backpack'd scripts and sprites, they should say, in the code, “stolen from (project link)”

Yes there could be.


But I think for backpacked scripts and sprites that is overkill. Someone could have credited them in the notes/credits or in project however it would still say stolen. It could discourage people from using the backpack if they were accused of stealing every time they used something from another project. Besides I remember that there was another suggestion for auto crediting. stuff from the backpack.

Wahsp wrote:

The only problem I see with this is when a user wants to change accounts and they want all of their old projects without showing their old account.
Other than that, yeah this should be a thing

This wouldn't be a problem if they had an “export to new account” button that has been previously suggested.

Wahsp wrote:

The only problem I see with this is when a user wants to change accounts and they want all of their old projects without showing their old account.
Other than that, yeah this should be a thing

Maybe you should enter the old account's password to make sure it is your project that you're trying to move.

Wahsp wrote:

The only problem I see with this is when a user wants to change accounts and they want all of their old projects without showing their old account.
Other than that, yeah this should be a thing

The tags could be excluded if the user that created the project downloads it, fixing that problem. Otherwise, this seems like a good way to prevent any more non-remix copies.

Edit: whoops, didn't see the second page and the two posts before this with the same quote

ACE009 wrote:

Wahsp wrote:

The only problem I see with this is when a user wants to change accounts and they want all of their old projects without showing their old account.
Other than that, yeah this should be a thing

The tags could be excluded if the user that created the project downloads it, fixing that problem. Otherwise, this seems like a good way to prevent any more non-remix copies.

Edit: whoops, didn't see the second page and the two posts before this with the same quote

^^ Sounds good!

Why would you need to hack it? I don't get it. Can't you just see the remix is a remix of someone's project?

oreyelephant wrote:

Why would you need to hack it? I don't get it. Can't you just see the remix is a remix of someone's project?

It's possible to download someone else's project and reupload it, and the remix thing won't show up.

-ShadowOfTheFuture- wrote:

oreyelephant wrote:

Why would you need to hack it? I don't get it. Can't you just see the remix is a remix of someone's project?

It's possible to download someone else's project and reupload it, and the remix thing won't show up.

true but he/she could add it into the credits

Ahh

HacksonJackson wrote:

-ShadowOfTheFuture- wrote:

oreyelephant wrote:

Why would you need to hack it? I don't get it. Can't you just see the remix is a remix of someone's project?

It's possible to download someone else's project and reupload it, and the remix thing won't show up.

true but he/she could add it into the credits

Ahh, thanks.

bump

Support. If someone does this, they can take all the credit and leave you with nothing.

oreyelephant wrote:

Why would you need to hack it? I don't get it. Can't you just see the remix is a remix of someone's project?

You can download a project and then import it into a new project and claim it as your own

I definitely support the attribution part in the JSON, to link it to the original project/creator. Getting your creations stolen without permission is no fun.

Techno-CAT wrote:

Recently, I found a remix of one of my projects by another scratcher (won't say their name). However, the based on <user> box was missing. As I've discovered this exploit before, I knew they must have seen inside (editor), and downloaded to their computer (file>download to computer). Then they would create a new project (on the website) and import my project into their project.

Don't get me wrong, I have nothing against remixes.
However, I do have objections against stolen material.

As Zro716 suggested,

Zro716 wrote:

It should be really easy to embed some sort of attribution property in the JSON of a project when it is downloaded, like this:
/* … */
“attribution”:{
“owner”:“username”,
“source”:"https://scratch-mit-edu.ezproxyberklee.flo.org/projects/12345/“,
”date“:”17 Apr 2016 10:43:05 UTC-0600“,
”hash“:”deadbeef1337" // generated to verify remix is legit, not injected/hacked into JSON (don't ask me how it's made)
},
/* … */
So when it is uploaded as a new project, it automatically treats it as a direct remix of the base project. A hash check would be necessary to confirm that the content comes directly from the source so that it can be treated as a remix.

Supporters? Ideas?

I agrree with this, but what if people take scripts without credit?

Support, it's really annoying when people steal hard work.
But, like with hacked blocks, couldn't people just change the JSON?

Vercte wrote:

But, like with hacked blocks, couldn't people just change the JSON?

Yes, but a hash would be required and valid. I'm guessing that what Zro716 means by deadbeef1337 is like an md5 hash or something like that.