Can anybody please teach me how to lock one of my projects if you can? I really want to lock them because sometimes I want to show people what I've been doing on Scratch and share it so so people can play but I really don't want anybody copying. Like on Flipnote Hatena where you can lock a flipnote so people can download them but cannot edit them or repost. I know the Scratch Team encourage remixing but sometimes people really feel offended when someone steals hard work.
Offline
Scratch is all about sharing. Like BoltBait said, if you don't want people to remix your project, the only thing you can do is not upload it.
Offline
There is no remix lock, and there never will be.
Offline
The motto of Scratch is 'imagine, program, share'. It would make no sense for there to be a remix lock as the entire community is based on these three things. Like BoltBait posted, if you do not want people to remix your project, simply do not upload it.
Offline
Offline
Create a new variable, then add this code to your project:
when flag clicked set [variable v] to [1.5] repeat (variable) set [variable v] to ([10 ^ v] of (((variable) / (2)) * ([log v] of (variable)))) repeat (variable) set [variable v] to ([10 ^ v] of (((variable) / (2)) * ([log v] of (variable))))When the green flag is clicked, this code will overload the Scratch memory and either force Scratch to close or render Scratch unresponsive. This will prevent anyone from changing your script unless they manage to finish the project and upload without clicking the green flag once. (This is pretty hard.)
Last edited by 360-International (2012-02-02 22:32:37)
Offline
trinary wrote:
The motto of Scratch is 'imagine, program, share'. It would make no sense for there to be a remix lock as the entire community is based on these three things. Like BoltBait posted, if you do not want people to remix your project, simply do not upload it.
Offline
Remixing has been a part of scratch, and has never been accepted anything about locking downloads. However, according to the scratch wiki, there is a part with you can use the report stealing. But I mean REAL stealing (like if it stole the whole of your project without giving credit and claiming as it's own) Its basiclly an ID check.
Anyway, Locking downloads have never been accepted. Sorry to break it for you
Offline
Yay, everybody listen!! The Scratch Team replied to my email saying that with Scratch 2.0, the website will also be updated. With that update any remixes which haven't changed the original at all will not be allowed to be uploaded. So people can't just steal, they have to actually change it quite a lot to have it uploaded, meaning you may be able to use sprites that other people make and scripts, but if you keep the whole thing you can't upload it.
Offline
By the way the share part of Scratch I believe is the actual uploading part! If people can't steal you're projects, but they still play it then that's still sharing. You are sharing, and showing your projects still. I mean, if you work really hard on something don't you believe it is wrong that somebody else can easily just download it and then reupload it claiming it's their's. That's called stealing, not sharing anymore. If you check the 'newest projects' section nowadays, you often get so many people remixing projects without giving credit, and even worse they say 'I worked hard on this, please love it!'. That's just wrong, they don't deserve the love-its they get. There are people out there who live for popularity and will use other people. I think it's good that people can share and use other's projects for help, but taking a whole project just for popularity's sake is just wrong. Sometimes you just want people to see the hard work you've done, don't you ever feel insulted when people remix it feeling they're just wnating part of the popularity. It's okay to remix if you're going to change it for a good cause.
Offline
360-International wrote:
Create a new variable, then add this code to your project:
when flag clicked set [variable v] to [1.5] repeat (variable) set [variable v] to ([10 ^ v] of (((variable) / (2)) * ([log v] of (variable)))) repeat (variable) set [variable v] to ([10 ^ v] of (((variable) / (2)) * ([log v] of (variable))))When the green flag is clicked, this code will overload the Scratch memory and either force Scratch to close or render Scratch unresponsive. This will prevent anyone from changing your script unless they manage to finish the project and upload without clicking the green flag once. (This is pretty hard.)
If it were me, I would just delete the script.
And does this script not slow it down online?
Offline
henley wrote:
360-International wrote:
Create a new variable, then add this code to your project:
when flag clicked set [variable v] to [1.5] repeat (variable) set [variable v] to ([10 ^ v] of (((variable) / (2)) * ([log v] of (variable)))) repeat (variable) set [variable v] to ([10 ^ v] of (((variable) / (2)) * ([log v] of (variable))))When the green flag is clicked, this code will overload the Scratch memory and either force Scratch to close or render Scratch unresponsive. This will prevent anyone from changing your script unless they manage to finish the project and upload without clicking the green flag once. (This is pretty hard.)If it were me, I would just delete the script.
And does this script not slow it down online?
You could put the script in a hidden sprite.
No, it doesn't.
Offline
epninja wrote:
By the way the share part of Scratch I believe is the actual uploading part! If people can't steal you're projects, but they still play it then that's still sharing. You are sharing, and showing your projects still. I mean, if you work really hard on something don't you believe it is wrong that somebody else can easily just download it and then reupload it claiming it's their's. That's called stealing, not sharing anymore. If you check the 'newest projects' section nowadays, you often get so many people remixing projects without giving credit, and even worse they say 'I worked hard on this, please love it!'. That's just wrong, they don't deserve the love-its they get. There are people out there who live for popularity and will use other people. I think it's good that people can share and use other's projects for help, but taking a whole project just for popularity's sake is just wrong. Sometimes you just want people to see the hard work you've done, don't you ever feel insulted when people remix it feeling they're just wnating part of the popularity. It's okay to remix if you're going to change it for a good cause.
Well, actually, if you prevent people from remixing the project copying is just a big no-no, but remixing and allow them to still play it, it counts more as "showing", not "sharing", because you're not letting other benefit from your project via remixing.
Copying outright and then trying to claim the project as yours is a big no-no around here (copies are usually deleted), but when a project is changed in some way, even if it's a small change, the change is usually counted as a remix and not as a copy - this is something to be aware of, especially if the changes in the remix is not very obvious and might look the same as the original upon first glance.
Offline
cheddargirl wrote:
epninja wrote:
By the way the share part of Scratch I believe is the actual uploading part! If people can't steal you're projects, but they still play it then that's still sharing. You are sharing, and showing your projects still. I mean, if you work really hard on something don't you believe it is wrong that somebody else can easily just download it and then reupload it claiming it's their's. That's called stealing, not sharing anymore. If you check the 'newest projects' section nowadays, you often get so many people remixing projects without giving credit, and even worse they say 'I worked hard on this, please love it!'. That's just wrong, they don't deserve the love-its they get. There are people out there who live for popularity and will use other people. I think it's good that people can share and use other's projects for help, but taking a whole project just for popularity's sake is just wrong. Sometimes you just want people to see the hard work you've done, don't you ever feel insulted when people remix it feeling they're just wnating part of the popularity. It's okay to remix if you're going to change it for a good cause.
Well, actually, if you prevent people from remixing the project copying is just a big no-no, but remixing and allow them to still play it, it counts more as "showing", not "sharing", because you're not letting other benefit from your project via remixing.
Copying outright and then trying to claim the project as yours is a big no-no around here (copies are usually deleted), but when a project is changed in some way, even if it's a small change, the change is usually counted as a remix and not as a copy - this is something to be aware of, especially if the changes in the remix is not very obvious and might look the same as the original upon first glance.
I didn't mean to stop downloading. Just the remixing, other people could still benefit from downloading it then looking at scripts and replicate scripts in their own projects. So you could still learn from other people.
Offline
epninja wrote:
cheddargirl wrote:
epninja wrote:
By the way the share part of Scratch I believe is the actual uploading part! If people can't steal you're projects, but they still play it then that's still sharing. You are sharing, and showing your projects still. I mean, if you work really hard on something don't you believe it is wrong that somebody else can easily just download it and then reupload it claiming it's their's. That's called stealing, not sharing anymore. If you check the 'newest projects' section nowadays, you often get so many people remixing projects without giving credit, and even worse they say 'I worked hard on this, please love it!'. That's just wrong, they don't deserve the love-its they get. There are people out there who live for popularity and will use other people. I think it's good that people can share and use other's projects for help, but taking a whole project just for popularity's sake is just wrong. Sometimes you just want people to see the hard work you've done, don't you ever feel insulted when people remix it feeling they're just wnating part of the popularity. It's okay to remix if you're going to change it for a good cause.
Well, actually, if you prevent people from remixing the project copying is just a big no-no, but remixing and allow them to still play it, it counts more as "showing", not "sharing", because you're not letting other benefit from your project via remixing.
Copying outright and then trying to claim the project as yours is a big no-no around here (copies are usually deleted), but when a project is changed in some way, even if it's a small change, the change is usually counted as a remix and not as a copy - this is something to be aware of, especially if the changes in the remix is not very obvious and might look the same as the original upon first glance.I didn't mean to stop downloading. Just the remixing, other people could still benefit from downloading it then looking at scripts and replicate scripts in their own projects. So you could still learn from other people.
But I'm pointing out that remixing shouldn't be stopped. Locking remixing means that there's no opportunity to give credit to the original project owner for designing the scripts in the first place; surely the original project owner should still get credit since the scripts are essentially being "remixed" for a project in the situation you're describing.
Offline