Better remix detection

Techno-CAT

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?

Last edited by Techno-CAT (April 18, 2016 07:25:05)

NanoRook

Way to exploit the system, unnamed scratcher.

Support, we don't want stolen material all over the website.

SkyShine

Support and why would you want to steal someone's material anyway unknown scratcher?

Zro716

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.

Techno-CAT

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.

If it's alright, I've added it into the main post

DaSpudLord

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.

I support for this idea. I don't support for the original idea because with nearly 15 million projects, it would take a really long time to compare each project to a newly uploaded one.

Scratcher1002

DaSpudLord wrote:
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.
I support for this idea. I don't support for the original idea because with nearly 15 million projects, it would take a really long time to compare each project to a newly uploaded one.

helloandgoodbye9

DaSpudLord wrote:
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.
I support for this idea. I don't support for the original idea because with nearly 15 million projects, it would take a really long time to compare each project to a newly uploaded one.

Support. Also, how about a stolen project url in the report button? Then, it will see if it is very similar.

NanoRook

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.

No support for the original idea, but support for this.

Thelnvoker

I have nothing against remixes, but I don't like, if not hate, when people don't give credit. I think that this could be a good solution.

I support this.

Abstract-

Support. This will help people get credit. It might be hard to implement though…

MathlyCat

Support! This would honestly help with the loss of credit, etc.

Techno-CAT

bump

-ShadowOfTheFuture-

Support! Stolen material is a serious problem that needs to be fixed.

muellly

I support this. However what if someone made a new account and moved all of their projects to the new account by importing/exporting projects because the remix thing made the instructions and notes to small. I feel like the owner of the original project it is detected of a remix for should be able to remove the this project is a remix of thing if it is marked as a remix from this.

python_megapixel

I can see this working well, but you could just edit the JSON. Also, it would remove the one way that people can switch usernames without losing their stuff.

Techno-CAT

python_megapixel wrote:
“..you could just edit the JSON..”

hence the need for the hash to verify legitimacy

Wahsp

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

python_megapixel

Techno-CAT wrote:
python_megapixel wrote:
“..you could just edit the JSON..”
hence the need for the hash to verify legitimacy

OK, but that still doesn't answer my question about changing usernames.

Also, what would it do if the hash wasn't legit?

Last edited by python_megapixel (April 27, 2018 12:21:38)

Botcho_Otkho

Support, it is really annoying because other people may think the project is theirs and not yours and those users think nobody will see that it's a remix.

Last edited by Botcho_Otkho (April 27, 2018 20:11:32)

Discuss Scratch