Purvitekriwal wrote:

Scratch does not store history of a project.

Also what if someone just added a few dots in the invisible part of the costume or recoded the same thing. It is impossible to keep trck. Like if they removed say 30 block memorised them amd added them back a few days later so it is different from the previous history.

Support or not? /gen

Bump

This would effectively mean very simple projects would not be able to shared (art projects with a simple music script comes to mind). However I believe there is a solution, and that is to only to share the project if the copied code is only 100 blocks or less.
However, while it solves some of the problem, there is a problem that arises from this solution. Big scripts that are meant to be used in other projects (pen text engines comes to mind) would not be able to be shared. A solution that may come to mind is to see if the project has a reasonable amount of code. However, simple slideshow projects would suffer from this, as it's just text with some simple scripts.
What I propose to solve this problem is a tag that you can add to the project's page. I haven't come up with a name, but when your project is shared or unshared, you can go to its page and there will be an option to add a tag. This tag will indicate whether your project is made for the purpose of sharing a script that is supposed to be used in other projects. This tag is public. If your tag is marked with this, any project that is shared with that script will be able to be shared with no problems. A project containing the script will have a text appear in the project page saying that it uses a script from another project. There will be a link to the original project. Of course, old projects won't have this tag, however if you believe that's the project's purpose, you can report the project (nothing will happen to the creator of the project, unless the project is violating the Community Guidelines) and if enough reports are submitted, it will have this tag. Of course, people will mass report projects so that it would have a tag and can be more easily stolen (keep in mind there'll be a text to find the original source of the code), but there'll be an option to report the project if it does not fit the requirement for the tag (nothing will happen to the creator of the project, unless the project is violating the Community Guidelines). Anyone who misuses any of these options will have actions taken against their account.

TheTrillion wrote:

This would effectively mean very simple projects would not be able to shared (art projects with a simple music script comes to mind). However I believe there is a solution, and that is to only to share the project if the copied code is only 100 blocks or less.
However, while it solves some of the problem, there is a problem that arises from this solution. Big scripts that are meant to be used in other projects (pen text engines comes to mind) would not be able to be shared. A solution that may come to mind is to see if the project has a reasonable amount of code. However, simple slideshow projects would suffer from this, as it's just text with some simple scripts.
What I propose to solve this problem is a tag that you can add to the project's page. I haven't come up with a name, but when your project is shared or unshared, you can go to its page and there will be an option to add a tag. This tag will indicate whether your project is made for the purpose of sharing a script that is supposed to be used in other projects. This tag is public. If your tag is marked with this, any project that is shared with that script will be able to be shared with no problems. A project containing the script will have a text appear in the project page saying that it uses a script from another project. There will be a link to the original project. Of course, old projects won't have this tag, however if you believe that's the project's purpose, you can report the project (nothing will happen to the creator of the project, unless the project is violating the Community Guidelines) and if enough reports are submitted, it will have this tag. Of course, people will mass report projects so that it would have a tag and can be more easily stolen (keep in mind there'll be a text to find the original source of the code), but there'll be an option to report the project if it does not fit the requirement for the tag (nothing will happen to the creator of the project, unless the project is violating the Community Guidelines). Anyone who misuses any of these options will have actions taken against their account.

However, this chain is meant to stop exact remixing. Not backpacking an assets, or copying the code.

TheTrillion wrote:

This would effectively mean very simple projects would not be able to shared (art projects with a simple music script comes to mind). However I believe there is a solution, and that is to only to share the project if the copied code is only 100 blocks or less.
However, while it solves some of the problem, there is a problem that arises from this solution. Big scripts that are meant to be used in other projects (pen text engines comes to mind) would not be able to be shared. A solution that may come to mind is to see if the project has a reasonable amount of code. However, simple slideshow projects would suffer from this, as it's just text with some simple scripts.

I dont see how these projects would suffer, as this says..
However, this chain is meant to stop exact remixing. Not backpacking an assets, or copying the code.


What I propose to solve this problem is a tag that you can add to the project's page. I haven't come up with a name, but when your project is shared or unshared, you can go to its page and there will be an option to add a tag. This tag will indicate whether your project is made for the purpose of sharing a script that is supposed to be used in other projects. This tag is public. If your tag is marked with this, any project that is shared with that script will be able to be shared with no problems. A project containing the script will have a text appear in the project page saying that it uses a script from another project. There will be a link to the original project.

I like this idea, even though i don't fully understand it..


Of course, old projects won't have this tag, however if you believe that's the project's purpose, you can report the project (nothing will happen to the creator of the project, unless the project is violating the Community Guidelines) and if enough reports are submitted, it will have this tag. Of course, people will mass report projects so that it would have a tag and can be more easily stolen (keep in mind there'll be a text to find the original source of the code), but there'll be an option to report the project if it does not fit the requirement for the tag (nothing will happen to the creator of the project, unless the project is violating the Community Guidelines). Anyone who misuses any of these options will have actions taken against their account.

I don't understand this part


Katt

kattcrazy wrote:

TheTrillion wrote:

This would effectively mean very simple projects would not be able to shared (art projects with a simple music script comes to mind). However I believe there is a solution, and that is to only to share the project if the copied code is only 100 blocks or less.
However, while it solves some of the problem, there is a problem that arises from this solution. Big scripts that are meant to be used in other projects (pen text engines comes to mind) would not be able to be shared. A solution that may come to mind is to see if the project has a reasonable amount of code. However, simple slideshow projects would suffer from this, as it's just text with some simple scripts.

I dont see how these projects would suffer..

What I propose to solve this problem is a tag that you can add to the project's page. I haven't come up with a name, but when your project is shared or unshared, you can go to its page and there will be an option to add a tag. This tag will indicate whether your project is made for the purpose of sharing a script that is supposed to be used in other projects. This tag is public. If your tag is marked with this, any project that is shared with that script will be able to be shared with no problems. A project containing the script will have a text appear in the project page saying that it uses a script from another project. There will be a link to the original project.

I like this idea, even though i don't fully understand it..


Of course, old projects won't have this tag, however if you believe that's the project's purpose, you can report the project (nothing will happen to the creator of the project, unless the project is violating the Community Guidelines) and if enough reports are submitted, it will have this tag. Of course, people will mass report projects so that it would have a tag and can be more easily stolen (keep in mind there'll be a text to find the original source of the code), but there'll be an option to report the project if it does not fit the requirement for the tag (nothing will happen to the creator of the project, unless the project is violating the Community Guidelines). Anyone who misuses any of these options will have actions taken against their account.

I don't understand this part


Katt

What if there was a thing, to prevent the code from getting stolen that detects what project you backpacked something from, and then it tells you who you've got to credit in the notes and credits before you can share it (off topic, might start thread of this elsewhere)

zomboss1_1 wrote:

What if there was a thing, to prevent the code from getting stolen that detects what project you backpacked something from, and then it tells you who you've got to credit in the notes and credits before you can share it (off topic, might start thread of this elsewhere)

How about the script would be an undeletable comment?

Also, by loading a project in Turbowarp, you could bypass this, right?

(( zomboss1_1 )) What if there was a thing, to prevent the code from getting stolen that detects what project you backpacked something from, and then it tells you who you've got to credit in the notes and credits before you can share it (off topic, might start thread of this elsewhere) ((it wouldnt quote…))

Btw ur Quoting system broke Zomboss ))

That might work!

musicROCKS013 wrote:

How about the script would be an undeletable comment?

Also, by loading a project in Turbowarp, you could bypass this, right?

Im not sure


A reminder to everyone else, please Cut Your Quotes before posting



Augh why did it post twice

kattcrazy wrote:

What if there was a thing, to prevent the code from getting stolen that detects what project you backpacked something from, and then it tells you who you've got to credit in the notes and credits before you can share it (off topic, might start thread of this elsewhere)

Btw ur Quoting system broke ))

That might work!

musicROCKS013 wrote:

How about the script would be an undeletable comment?

Also, by loading a project in Turbowarp, you could bypass this, right?

Im not sure


A reminder to everyone else, please Cut Your Quotes before posting
XD your quote system broke as well, I think. Also, hmmm… The uneditable comment idea sounds good… But… That doesn't prevent them from not giving credit. It's just a reminder.

((Quote))A reminder to everyone else, please Cut Your Quotes before posting((end quote))
((Quote))
XD your quote system broke as well, I think. Also, hmmm… The uneditable comment idea sounds good… But… That doesn't prevent them from not giving credit. It's just a reminder.((end Quote))


Yeah i cant fix it XD im trying to neaten it up.
Yours did too
Lets put ((Quote)) and ((End Quote)) in for now…

I think the system would prevent you from posting/sharing until you had done what the pop up suggested…that being Credit ofc.

kattcrazy wrote:

A reminder to everyone else, please Cut Your Quotes before posting

XD your quote system broke as well, I think. Also, hmmm… The uneditable comment idea sounds good… But… That doesn't prevent them from not giving credit.
Edit: It's just a reminder that they should give credit. How would you make it to where they would HAVE to give credit if this were implemented?


Yeah i cant fix it XD im trying to neaten it up


Scratch is having a stroke I think (no offense: a joke me and my dad has for our Google when he's not functioning correctly. Please don't be mad.)

kattcrazy wrote:

I edited my post. It has needed information. Please look

Kk, that makes sense.

zomboss1_1 wrote:

kattcrazy wrote:

I edited my post. It has needed information. Please look

Kk, that makes sense.

Could you fix your post a little way up? It is confusing me XD

kattcrazy wrote:

Could you fix your post a little way up? It is confusing me XD

Which one XD? I fear I don't understand.

Quote

zomboss1_1 wrote:

kattcrazy wrote:

What if there was a thing, to prevent the code from getting stolen that detects what project you backpacked something from, and then it tells you who you've got to credit in the notes and credits before you can share it (off topic, might start thread of this elsewhere)

Btw ur Quoting system broke ))

That might work!

musicROCKS013 wrote:

How about the script would be an undeletable comment?

Also, by loading a project in Turbowarp, you could bypass this, right?

Im not sure


A reminder to everyone else, please Cut Your Quotes before posting
XD your quote system broke as well, I think. Also, hmmm… The uneditable comment idea sounds good… But… That doesn't prevent them from not giving credit. It's just a reminder.

Quote
—
This one

kattcrazy wrote:

Quote

zomboss1_1 wrote:

kattcrazy wrote:

What if there was a thing, to prevent the code from getting stolen that detects what project you backpacked something from, and then it tells you who you've got to credit in the notes and credits before you can share it (off topic, might start thread of this elsewhere)

Btw ur Quoting system broke ))

That might work!

musicROCKS013 wrote:

How about the script would be an undeletable comment?

Also, by loading a project in Turbowarp, you could bypass this, right?

Im not sure


A reminder to everyone else, please Cut Your Quotes before posting

XD your quote system broke as well, I think. Also, hmmm… The uneditable comment idea sounds good… But… That doesn't prevent them from not giving credit. It's just a reminder.

Quote
—
This one
I think I made it make more sense.

Ok. Now, back on task. I like making lists so….. (when you quote, remember to snip the list)

Ideas
- Pop Up ‘Suggestion’
- Change Detector
- Undeletable Credit Comment
- If a file is uploaded, check it for similarity to shared projects, then proceed with the system for Remixed Projects, listed above.
- Project Type Tag

Cons
- Remix + Sign projects might not be allowed. ~ can be fixed with tag idea
- Support-By-Remixing projects might be taken down ~ can be fixed with tag idea
- Some people may avoid crediting still

Pros
- Stops exact-copy remixes
- Credit will be rightfully given
- We will have influenced Scratch, will would feel pretty cool!

Notes
- When people download a file then upload it they can evade the detector (idea: if a file is uploaded, check it for similarity to shared projects)
- There was smth else but i forgot it

XxxxxxxxxxxxX

Snip Quotes Before Posting

kattcrazy wrote:

Cons
- Remix + Sign projects might not be allowed
- Support-By-Remixing projects might be taken down

Didn't someone above suggest tags for these kinds of projects? Like, if the project has that tag, remixing without bug changes are allowed.

zomboss1_1 wrote:

kattcrazy wrote:

Cons
- Remix + Sign projects might not be allowed
- Support-By-Remixing projects might be taken down

Didn't someone above suggest tags for these kinds of projects? Like, if the project has that tag, remixing without bug changes are allowed.

Oh yeah i forgot. Ill add that now. Thx (waits 60 seconds impatiently)