crazyfrogcat wrote:

(#100)
is it rejected

The Official List of Rejected Suggestions wrote:

3.2 Disable remixing or censor minor remixes

One of the most important ideas of Scratch is the share aspect. Scratch is a website not only for displaying your work, but also for sharing it with others, and by posting your project on the Scratch website you agree to allow others to remix your work. You are not allowed to write “Do not remix this project” in the Notes and Credits of your project; you may get alerted for this, because it discourages remixing. This suggestion extends to the ability to require permission to remix a project, as you have already given permission to others to use your creations by sharing a project on Scratch; for more information, see this post.

‎

A remix of a project is allowed on Scratch, even if the remix only contains minor changes (this includes recolors). However, when you remix a project, you should put in the Notes and Credits what you changed. If you see a project that contains no noticeable changes, please use the Report button on it so the Scratch Team can take a look at it. This suggestion extends to “extremely minor remixes,” such as a remix of a game that gives you 2 points per second instead of 1. As long as the user explains what they changed about the project and gives proper credit, this is okay.

‎

However, a feature that prevents unchanged remixes from being shared is NOT rejected. You can discuss it on this topic.

View source

I'll give no support

read the last 2 sentences of that thing you're quoting please

-ShadowOfTheFuture- wrote:

sti_scratch wrote:

I agree.

But the blocker should block every remix except if the remix includes one or more of these criteria:

- Adds one or more blocks in a script, excluding blocks in the “Control” tab.
- Adds one more script with at least one block from the “Events” tab.

Well, yeah, but what if somebody added another script, remixed the project, and removed it?

No support, this would be way too easy to work around. Support for the concept, though, but it would be really hard to implement a foolproof copy-preventing system.

make it so you cant remove it

lapisi wrote:

(#101)

crazyfrogcat wrote:

(#100)
is it rejected

The Official List of Rejected Suggestions wrote:

3.2 Disable remixing or censor minor remixes

One of the most important ideas of Scratch is the share aspect. Scratch is a website not only for displaying your work, but also for sharing it with others, and by posting your project on the Scratch website you agree to allow others to remix your work. You are not allowed to write “Do not remix this project” in the Notes and Credits of your project; you may get alerted for this, because it discourages remixing. This suggestion extends to the ability to require permission to remix a project, as you have already given permission to others to use your creations by sharing a project on Scratch; for more information, see this post.

‎

A remix of a project is allowed on Scratch, even if the remix only contains minor changes (this includes recolors). However, when you remix a project, you should put in the Notes and Credits what you changed. If you see a project that contains no noticeable changes, please use the Report button on it so the Scratch Team can take a look at it. This suggestion extends to “extremely minor remixes,” such as a remix of a game that gives you 2 points per second instead of 1. As long as the user explains what they changed about the project and gives proper credit, this is okay.

‎

However, a feature that prevents unchanged remixes from being shared is NOT rejected. You can discuss it on this topic.

View source

I'll give no support

read the last 2 sentences of that thing you're quoting please

and the topic i linked there was quite literarily this topic

AonymousGuy wrote:

mathfreak231 wrote:

Define “any changes”.

You didn't do anything on the project but push “remix”.
At least that's my definition
Well, or you didn't do anything worth an autosave in Scratch's opinion.

Which is basically not doing anything but pushing “remix”.

Everything is worth an autosave if something has been changed and it's been five minutes (this includes moving a script from the left of the editor space to the right without changing it)

Bump

Changing the title should not count as a change, to prevent certain types of spamchains.

Lets say you have to add/change at least 10 blocks or change the art.
That way, even if people spend time placing useless blocks, itll encourage them to do more.

or make it where it can't remake the project that is being remixed without making changes to it.

does this topic fit with the topic you are seeing now?

valentines support

hotcrystal wrote:

Changing the title should not count as a change, to prevent certain types of spamchains.

Yeah, and the same goes for the description (Instructions, Notes & Credits). Of course, this is very easily worked around by just comparing the project.json files, rather than the project API JSON, as the description and title are both stored in the project's API page, and the project itself (the project.json file) is not, and assets are stored elsewhere on the servers and referenced in the project.json.

It also eliminates changing the thumbnail as counting as a change, because that also isn't stored in the project.json.

Sometimes users would like to share an unmodified project just to discuss, dissect, or keep track of it, but this rule disallows that. New users won't know what makes a “change” and will be frustrated if their remix is not sharable. In some cases, sharing an unmodified copy is beneficial for collaborative work or versioning, but this rule disallows that use case. Even small modifications (like fixing a bug or renaming a file) might not be identified properly, so it would look like “no changes” were made.

I think that even if there is an easy workaround, this could still be easily implemented and should at least exist, especially because this could effectively reduce the time of what I like to call spam-remixing, which is becoming a bigger problem more recently. I don't think there is really a reason to not implement at least anything like this, even if stuff like this could still happen.


If there were any important things I missed in this topic, please let me know, as I didn't read all of this!

savaka wrote:

If you didn't make any changes you can't share the remix.

Could still be bypassable

hoppingcoin404 wrote:

savaka wrote:

If you didn't make any changes you can't share the remix.

Could still be bypassable

yes. any method would be bypassable somehow.
you can't reject something for not being a perfect solution - no solution is perfect.

There should be a message saying “You need to make a change to this remix in order for it to be shared.”

oodle123 wrote:

There should be a message saying “You need to make a change to this remix in order for it to be shared.”

Yeah, this is what I was about to say - I think a pop-up with a notice about not making exact remixes, plus a link to the remix culture section of the community guidelines, would be useful a it would teach Scratchers what they did wrong instead of only blocking the project.

Support.

bumpo

report button crying in the corner rn