Use CC BY-NC-SA licence for projects instead of CC BY-SA

qloakonscratch

dhuls wrote:
qloakonscratch wrote:
dhuls wrote:
I like how everybody is misinterpreting the Terms of Use.
You do own what you made with both editors, because that's user generated content, and doesn't fall under the Scratch IP
That also means the ST can't change the license of our projects without our permission
The ST can change the license of our projects without our permission. If we release it on their platform, using their tools, they own it. It's like the United States. If you create a company, using US resources (money and stuff) then the U.S owns that building. You can control it, but they control it more. That same logic applies to Scratch projects.
Read the Terms of Use
5.1 Except for any user-generated content, the Scratch Team owns and retains all rights in and to the Scratch code, the design, functionality, and architecture of Scratch, and any software or content provided through Scratch (collectively “the Scratch IP”). If you want to use Scratch in a way that is not allowed by these Terms of Use, you must first contact the Scratch Team. Except for any rights explicitly granted under these Terms of Use, you are not granted any rights in and to any Scratch IP.

The exact excerpt I talked about. When they say any user generated content, they mean the art, the idea, and the gameplay. The project is owned by the Scratch Team (and the project creator) because it contains the Scratch Code and functionality.

dhuls

qloakonscratch wrote:
dhuls wrote:
qloakonscratch wrote:
dhuls wrote:
I like how everybody is misinterpreting the Terms of Use.
You do own what you made with both editors, because that's user generated content, and doesn't fall under the Scratch IP
That also means the ST can't change the license of our projects without our permission
The ST can change the license of our projects without our permission. If we release it on their platform, using their tools, they own it. It's like the United States. If you create a company, using US resources (money and stuff) then the U.S owns that building. You can control it, but they control it more. That same logic applies to Scratch projects.
Read the Terms of Use
5.1 Except for any user-generated content, the Scratch Team owns and retains all rights in and to the Scratch code, the design, functionality, and architecture of Scratch, and any software or content provided through Scratch (collectively “the Scratch IP”). If you want to use Scratch in a way that is not allowed by these Terms of Use, you must first contact the Scratch Team. Except for any rights explicitly granted under these Terms of Use, you are not granted any rights in and to any Scratch IP.
The exact excerpt I talked about. When they say any user generated content, they mean the art, the idea, and the gameplay. The project is owned by the Scratch Team (and the project creator) because it contains the Scratch Code and functionality.

The sb3 files don't however.
Unzip an sb3 and look at the project.json file. Where does it contain the Scratch code.

qloakonscratch

dhuls wrote:
qloakonscratch wrote:
dhuls wrote:
qloakonscratch wrote:
dhuls wrote:
I like how everybody is misinterpreting the Terms of Use.
You do own what you made with both editors, because that's user generated content, and doesn't fall under the Scratch IP
That also means the ST can't change the license of our projects without our permission
The ST can change the license of our projects without our permission. If we release it on their platform, using their tools, they own it. It's like the United States. If you create a company, using US resources (money and stuff) then the U.S owns that building. You can control it, but they control it more. That same logic applies to Scratch projects.
Read the Terms of Use
5.1 Except for any user-generated content, the Scratch Team owns and retains all rights in and to the Scratch code, the design, functionality, and architecture of Scratch, and any software or content provided through Scratch (collectively “the Scratch IP”). If you want to use Scratch in a way that is not allowed by these Terms of Use, you must first contact the Scratch Team. Except for any rights explicitly granted under these Terms of Use, you are not granted any rights in and to any Scratch IP.
The exact excerpt I talked about. When they say any user generated content, they mean the art, the idea, and the gameplay. The project is owned by the Scratch Team (and the project creator) because it contains the Scratch Code and functionality.
The sb3 files don't however.
Unzip an sb3 and look at the project.json file. Where does it contain the Scratch code.

It contains the Scratch Code inside the .json file.

dhuls

qloakonscratch wrote:
dhuls wrote:
qloakonscratch wrote:
dhuls wrote:
qloakonscratch wrote:
dhuls wrote:
I like how everybody is misinterpreting the Terms of Use.
You do own what you made with both editors, because that's user generated content, and doesn't fall under the Scratch IP
That also means the ST can't change the license of our projects without our permission
The ST can change the license of our projects without our permission. If we release it on their platform, using their tools, they own it. It's like the United States. If you create a company, using US resources (money and stuff) then the U.S owns that building. You can control it, but they control it more. That same logic applies to Scratch projects.
Read the Terms of Use
5.1 Except for any user-generated content, the Scratch Team owns and retains all rights in and to the Scratch code, the design, functionality, and architecture of Scratch, and any software or content provided through Scratch (collectively “the Scratch IP”). If you want to use Scratch in a way that is not allowed by these Terms of Use, you must first contact the Scratch Team. Except for any rights explicitly granted under these Terms of Use, you are not granted any rights in and to any Scratch IP.
The exact excerpt I talked about. When they say any user generated content, they mean the art, the idea, and the gameplay. The project is owned by the Scratch Team (and the project creator) because it contains the Scratch Code and functionality.
The sb3 files don't however.
Unzip an sb3 and look at the project.json file. Where does it contain the Scratch code.
It contains the Scratch Code inside the .json file.

Where?
Seriously, actually read the file.

Last edited by dhuls (Feb. 23, 2022 01:04:46)

qloakonscratch

dhuls wrote:
qloakonscratch wrote:
dhuls wrote:
qloakonscratch wrote:
dhuls wrote:
qloakonscratch wrote:
dhuls wrote:
I like how everybody is misinterpreting the Terms of Use.
You do own what you made with both editors, because that's user generated content, and doesn't fall under the Scratch IP
That also means the ST can't change the license of our projects without our permission
The ST can change the license of our projects without our permission. If we release it on their platform, using their tools, they own it. It's like the United States. If you create a company, using US resources (money and stuff) then the U.S owns that building. You can control it, but they control it more. That same logic applies to Scratch projects.
Read the Terms of Use
5.1 Except for any user-generated content, the Scratch Team owns and retains all rights in and to the Scratch code, the design, functionality, and architecture of Scratch, and any software or content provided through Scratch (collectively “the Scratch IP”). If you want to use Scratch in a way that is not allowed by these Terms of Use, you must first contact the Scratch Team. Except for any rights explicitly granted under these Terms of Use, you are not granted any rights in and to any Scratch IP.
The exact excerpt I talked about. When they say any user generated content, they mean the art, the idea, and the gameplay. The project is owned by the Scratch Team (and the project creator) because it contains the Scratch Code and functionality.
The sb3 files don't however.
Unzip an sb3 and look at the project.json file. Where does it contain the Scratch code.
It contains the Scratch Code inside the .json file.
Where?
Seriously, actually read the file.

Are you telling me that

"opcode":"control_wait"

isn't the wait block that Scratch created? Are you telling me that Scratch didn't create the wait block?

dhuls

qloakonscratch wrote:
Seriously, actually read the file.

Are you telling me that

"opcode":"control_wait"

isn't the wait block that Scratch created? Are you telling me that Scratch didn't create the wait block?
Is that the code to the wait block?

qloakonscratch

dhuls wrote:
qloakonscratch wrote:
dhuls wrote:
Seriously, actually read the file.
Are you telling me that
"opcode":"control_wait"
isn't the wait block that Scratch created? Are you telling me that Scratch didn't create the wait block?
Is that the code to the wait block?

That's the code that recognizes the wait block. The function of the wait block is stored in the editor.

Last edited by qloakonscratch (Feb. 23, 2022 01:07:08)

qrcool

If I remember correctly, blocks in the editor correspond to specific json code

dhuls

qloakonscratch wrote:
The project is owned by the Scratch Team (and the project creator)

If that's the case (even though it isn't) they would still need your approval to change the license, especially since CC-BY-SA and CC-BY-NC-SA aren't compatible.

sharkode

dhuls wrote:
qloakonscratch wrote:
dhuls wrote:
I like how everybody is misinterpreting the Terms of Use.
You do own what you made with both editors, because that's user generated content, and doesn't fall under the Scratch IP
That also means the ST can't change the license of our projects without our permission
The ST can change the license of our projects without our permission. If we release it on their platform, using their tools, they own it. It's like the United States. If you create a company, using US resources (money and stuff) then the U.S owns that building. You can control it, but they control it more. That same logic applies to Scratch projects.
Read the Terms of Use
5.1 Except for any user-generated content, the Scratch Team owns and retains all rights in and to the Scratch code, the design, functionality, and architecture of Scratch, and any software or content provided through Scratch (collectively “the Scratch IP”). If you want to use Scratch in a way that is not allowed by these Terms of Use, you must first contact the Scratch Team. Except for any rights explicitly granted under these Terms of Use, you are not granted any rights in and to any Scratch IP.

Ok, I'm just dying of confusion right now

ideapad-320

sharkode wrote:
qloakonscratch wrote:
sharkode wrote:
~snip~
Unless Scratch says you don't have to, which they do, then yes (though you do have to say they were made using Scratch)

This is because all user generated content is created through Scratch, using Scratch materials. Yes, you do own your projects, but Scratch owns them more than you do.
Also ST can decide who to sue and who not to sue, meaning if I sell my own project ST could just go like “ok”, but if someone else sells my project and I make a complaint ST could go

no you are both wrong unless you use one of scratch's assets, then scratch does not own your project.

DarthVader4Life

DarthVader4Life wrote:
From what I understand, that would make Scratch, not us, the licensor. Us the project creators wouldn't be able to sell our projects because we are not licensors. It is through Scratch that our projects receive the license. We don't hold the rights, as far as I understand.

This is a concern of mine that was ignored, so yes.
In order to avoid simply quoting my original post here, I shall delve further into what I mean.
We get our license through Scratch, and in turn, whoever remixes our projects would get a license from us, too, but since it's on Scratch, they, too, get the same license, but from two sources. Since we get our license through Scratch (and Scratch provides the same license to the remix), would that mean that Scratch is the licensor that the CC-BY-NC-SA is referring to? I'd rather keep things how they are now, since the situation you are fearing is quite rare and the license we have now is simpler to understand.

Last edited by DarthVader4Life (Feb. 23, 2022 18:16:30)

qloakonscratch

DarthVader4Life wrote:
DarthVader4Life wrote:
From what I understand, that would make Scratch, not us, the licensor. Us the project creators wouldn't be able to sell our projects because we are not licensors. It is through Scratch that our projects receive the license. We don't hold the rights, as far as I understand.
This is a concern of mine that was ignored, so yes.
In order to avoid simply quoting my original post here, I shall delve further into what I mean.
We get our license through Scratch, and in turn, whoever remixes our projects would get a license from us, too, but since it's on Scratch, they, too, get the same license, but from two sources. Since we get our license through Scratch (and Scratch provides the same license to the remix), would that mean that Scratch is the licensor that the CC-BY-NC-SA is referring to? I'd rather keep things how they are now, since the situation you are fearing is quite rare and the license we have now is simpler to understand.

This is what I was saying.

banana439monkey

sharkode wrote:
banana439monkey wrote:
you don't have to share your project

Banana
It's still unfair if someone capitalise on your project without even thanking you and you don't even get a single cent

if you share the project and they make a profit then that goes against the license's terms and they can be sued for it

Banana

sharkode

banana439monkey wrote:
sharkode wrote:
banana439monkey wrote:
you don't have to share your project

Banana
It's still unfair if someone capitalise on your project without even thanking you and you don't even get a single cent
if you share the project and they make a profit then that goes against the license's terms and they can be sued for it

Banana

ST can choose not to sue you

banana439monkey

sharkode wrote:
banana439monkey wrote:
sharkode wrote:
banana439monkey wrote:
you don't have to share your project

Banana
It's still unfair if someone capitalise on your project without even thanking you and you don't even get a single cent
if you share the project and they make a profit then that goes against the license's terms and they can be sued for it

Banana
ST can choose not to sue you

not saying the st will sue you

Banana

patrovich

Regarding the making money with your scratch projects, it is legal as long as you haven't uploaded them to the scratch website, and here's the proof:
https://en.scratch-wiki.info/wiki/Can_Scratch_projects_be_sold%3F

sharkode

patrovich wrote:
Regarding the making money with your scratch projects, it is legal as long as you haven't uploaded them to the scratch website, and here's the proof:
https://en.scratch-wiki.info/wiki/Can_Scratch_projects_be_sold%3F

You can still upload the project to the site, but people would probably not buy it as it's available for free

sharkode

banana439monkey wrote:
sharkode wrote:
banana439monkey wrote:
sharkode wrote:
banana439monkey wrote:
you don't have to share your project

Banana
It's still unfair if someone capitalise on your project without even thanking you and you don't even get a single cent
if you share the project and they make a profit then that goes against the license's terms and they can be sued for it

Banana
ST can choose not to sue you
not saying the st will sue you

Banana

ST can choose to sue people who steal projects to sell them, and not sue people who sell their own projects

banana439monkey

sharkode wrote:
banana439monkey wrote:
sharkode wrote:
banana439monkey wrote:
sharkode wrote:
banana439monkey wrote:
you don't have to share your project

Banana
It's still unfair if someone capitalise on your project without even thanking you and you don't even get a single cent
if you share the project and they make a profit then that goes against the license's terms and they can be sued for it

Banana
ST can choose not to sue you
not saying the st will sue you

Banana
ST can choose to sue people who steal projects to sell them, and not sue people who sell their own projects

if the project creator shares a project and some rando capitalises off of it, then the project creator can sue them. if you sell the project and the rights to it, you'll get the money for it

Banana

Discuss Scratch