TheMonsterOfTheDeep wrote:

It actually would be possible to make a system which would automatically report projects to the ST that didn't seem to have a lot of changes.

For example, if only 3% of the pixels are changed in a single costume, it might be suspicious. If there aren't very many changes between the scripts, it may be suspicious. If the only costume / background that was changed had a name such as “logo” or “intro” then it would definitely be suspicious.

Support.

Even a small change is allowed if credit is given. that system would violate guidelines.

seanbobe wrote:

TheMonsterOfTheDeep wrote:

It actually would be possible to make a system which would automatically report projects to the ST that didn't seem to have a lot of changes.

For example, if only 3% of the pixels are changed in a single costume, it might be suspicious. If there aren't very many changes between the scripts, it may be suspicious. If the only costume / background that was changed had a name such as “logo” or “intro” then it would definitely be suspicious.

Support.

Even a small change is allowed if credit is given. that system would violate guidelines.

yeah. but support for the NO CHANGE AT ALL, or the NO CREDIT AT ALL

seanbobe wrote:

TheMonsterOfTheDeep wrote:

It actually would be possible to make a system which would automatically report projects to the ST that didn't seem to have a lot of changes.

For example, if only 3% of the pixels are changed in a single costume, it might be suspicious. If there aren't very many changes between the scripts, it may be suspicious. If the only costume / background that was changed had a name such as “logo” or “intro” then it would definitely be suspicious.

Support.

Even a small change is allowed if credit is given. that system would violate guidelines.

Actually, some changes don't count. Changing the red value of the color of 1 pixel in a 480 * 360 costume by one is not enough to constitute a valid remix. However, it is still a change and therefore cannot simply be dismissed without human confirmation that the remix is, in fact, not valid.

TheMonsterOfTheDeep wrote:

It actually would be possible to make a system which would automatically report projects to the ST that didn't seem to have a lot of changes.

For example, if only 3% of the pixels are changed in a single costume, it might be suspicious. If there aren't very many changes between the scripts, it may be suspicious. If the only costume / background that was changed had a name such as “logo” or “intro” then it would definitely be suspicious.

Support.

These are just people backed by MIT, not the next Larry Page

How about false positives? How about coloring contests? What about the moderators that already have to scour through a sea of reports?

iamunknown2 wrote:

TheMonsterOfTheDeep wrote:

It actually would be possible to make a system which would automatically report projects to the ST that didn't seem to have a lot of changes.

For example, if only 3% of the pixels are changed in a single costume, it might be suspicious. If there aren't very many changes between the scripts, it may be suspicious. If the only costume / background that was changed had a name such as “logo” or “intro” then it would definitely be suspicious.

Support.

These are just people backed by MIT, not the next Larry Page

How about false positives? How about coloring contests? What about the moderators that already have to scour through a sea of reports?

False positives are the whole reason that the thing wouldn't just be deleted in the first place. Coloring contests generally consist of way more than 3% changes, and I'm guessing if this was implemented the threshold would be even lower - probably something like 0.5%. These types of reports could be sent to a different location then the rest so that moderators could look at them when they had time because the system would alert them to quite a few projects that were in fact illegitimate.

And, it still is possible to make scripts that automatically delete the projects if there are no changes - that is rather simple to do - just compare the images and JSON file and see if they are identical or not. It's also possible to detect projects where the only change is the position of scripts.

TheMonsterOfTheDeep wrote:

iamunknown2 wrote:

TheMonsterOfTheDeep wrote:

It actually would be possible to make a system which would automatically report projects to the ST that didn't seem to have a lot of changes.

For example, if only 3% of the pixels are changed in a single costume, it might be suspicious. If there aren't very many changes between the scripts, it may be suspicious. If the only costume / background that was changed had a name such as “logo” or “intro” then it would definitely be suspicious.

Support.

These are just people backed by MIT, not the next Larry Page

How about false positives? How about coloring contests? What about the moderators that already have to scour through a sea of reports?

False positives are the whole reason that the thing wouldn't just be deleted in the first place. Coloring contests generally consist of way more than 3% changes, and I'm guessing if this was implemented the threshold would be even lower - probably something like 0.5%. These types of reports could be sent to a different location then the rest so that moderators could look at them when they had time because the system would alert them to quite a few projects that were in fact illegitimate.

And, it still is possible to make scripts that automatically delete the projects if there are no changes - that is rather simple to do - just compare the images and JSON file and see if they are identical or not. It's also possible to detect projects where the only change is the position of scripts.

They could make lots of spam stuff with dummy-scripts, which they can get from the backpack.

I find this very aggravating. Why don't the just compare the JSONs or track change the remixer makes. Both of those would be easy to implement.

TheMonsterOfTheDeep wrote:

It actually would be possible to make a system which would automatically report projects to the ST that didn't seem to have a lot of changes.

For example, if only 3% of the pixels are changed in a single costume, it might be suspicious. If there aren't very many changes between the scripts, it may be suspicious. If the only costume / background that was changed had a name such as “logo” or “intro” then it would definitely be suspicious.

Support.

That would be awesome. Maybe they could be really annoying and have it so the json has to be at least 500 characters shorter or longer.

What they could also do if when remixing, don't make the share button appear before Scratch did some validation of the project JSON.
The JSON of the remix would be compared with the JSON of the original project, excluding script positions, comments, etc… and only allows sharing if there are real changes detected. Also there won't be a share button if the original creator's name isn't in the credit's section of the description, because right now that validation is a bit weak. you can type whatever you want.

Why not hide the remix button itself? Well I sometimes remix a game but don't share it, just to save the game, and eg. don't lose my upgrades.

No support. If people are stealing your work, you can ask them to take it down. If someone makes a remix with no credit and no change, you should go to the original instead.

Tymewalk wrote:

No support. If people are stealing your work, you can ask them to take it down. If someone makes a remix with no credit and no change, you should go to the original instead.

There are some people who don't know that it's a copy…

ScratchinJoJo wrote:

Why not hide the remix button itself? Well I sometimes remix a game but don't share it, just to save the game, and eg. don't lose my upgrades.

Nope. Have you read the sticky?

Dylan5797 wrote:

TheMonsterOfTheDeep wrote:

It actually would be possible to make a system which would automatically report projects to the ST that didn't seem to have a lot of changes.

For example, if only 3% of the pixels are changed in a single costume, it might be suspicious. If there aren't very many changes between the scripts, it may be suspicious. If the only costume / background that was changed had a name such as “logo” or “intro” then it would definitely be suspicious.

Support.

That would be awesome. Maybe they could be really annoying and have it so the json has to be at least 500 characters shorter or longer.

Add a spam block that's 500 chars longer. Problem solved.

TheMonsterOfTheDeep wrote:

iamunknown2 wrote:

TheMonsterOfTheDeep wrote:

It actually would be possible to make a system which would automatically report projects to the ST that didn't seem to have a lot of changes.

For example, if only 3% of the pixels are changed in a single costume, it might be suspicious. If there aren't very many changes between the scripts, it may be suspicious. If the only costume / background that was changed had a name such as “logo” or “intro” then it would definitely be suspicious.

Support.

These are just people backed by MIT, not the next Larry Page

How about false positives? How about coloring contests? What about the moderators that already have to scour through a sea of reports?

False positives are the whole reason that the thing wouldn't just be deleted in the first place. Coloring contests generally consist of way more than 3% changes, and I'm guessing if this was implemented the threshold would be even lower - probably something like 0.5%. These types of reports could be sent to a different location then the rest so that moderators could look at them when they had time because the system would alert them to quite a few projects that were in fact illegitimate.

And, it still is possible to make scripts that automatically delete the projects if there are no changes - that is rather simple to do - just compare the images and JSON file and see if they are identical or not. It's also possible to detect projects where the only change is the position of scripts.

But the json is not the same unless you remove the “info” tag in the comparison.

iamunknown2 wrote:

ScratchinJoJo wrote:

Why not hide the remix button itself? Well I sometimes remix a game but don't share it, just to save the game, and eg. don't lose my upgrades.

Nope. Have you read the sticky?

??? Yes, so? To what part of the stickies are you referring? I haven't read anything about hiding the share button if a remix doesn't change anything….

ScratchinJoJo wrote:

iamunknown2 wrote:

ScratchinJoJo wrote:

Why not hide the remix button itself? Well I sometimes remix a game but don't share it, just to save the game, and eg. don't lose my upgrades.

Nope. Have you read the sticky?

??? Yes, so? To what part of the stickies are you referring? I haven't read anything about hiding the share button if a remix doesn't change anything….

No you didn't…

Why not hide the remix button itself?

Remix button != share button.

iamunknown2 wrote:

ScratchinJoJo wrote:

iamunknown2 wrote:

ScratchinJoJo wrote:

Why not hide the remix button itself? Well I sometimes remix a game but don't share it, just to save the game, and eg. don't lose my upgrades.

Nope. Have you read the sticky?

??? Yes, so? To what part of the stickies are you referring? I haven't read anything about hiding the share button if a remix doesn't change anything….

No you didn't…

Yes I actually did.

Why not hide the remix button itself?

Remix button != share button.

I know. I suggest hiding the share button, because remixing can be a way to save game progress, but you don't share the project.
I don't see anything in the stickies saying something about that.

ScratchinJoJo wrote:

I know. I suggest hiding the share button, because remixing can be a way to save game progress, but you don't share the project.
I don't see anything in the stickies saying something about that.

Scratch already doesn't let you remix unless you've changed something.

iamunknown2 wrote:

ScratchinJoJo wrote:

I know. I suggest hiding the share button, because remixing can be a way to save game progress, but you don't share the project.
I don't see anything in the stickies saying something about that.

Scratch already doesn't let you remix unless you've changed something.

Changed? I don't see a moved script or a comment that's added as a real change.

ScratchinJoJo wrote:

iamunknown2 wrote:

ScratchinJoJo wrote:

I know. I suggest hiding the share button, because remixing can be a way to save game progress, but you don't share the project.
I don't see anything in the stickies saying something about that.

Scratch already doesn't let you remix unless you've changed something.

Changed? I don't see a moved script or a comment that's added as a real change.

So you're suggesting to tighten up the criteria for remixing…?