This is a read-only archive of the old Scratch 1.x Forums.
Try searching the current Scratch discussion forums.

#1 2007-05-29 00:23:33

fandebiao
Scratcher
Registered: 2007-05-15
Posts: 25

Ideas for preventing plagiarism

1.When submitting a project, the author can choose to make it undownloadable.
2.After a project is downloaded, it may be modified and re-uploaded, but the author remains same.  Modifiers have their names saved under a different tag after called "modifiers".
Feel free to add more.

Offline

 

#2 2007-05-29 00:39:03

kevin_karplus
Scratcher
Registered: 2007-04-27
Posts: 1000+

Re: Ideas for preventing plagiarism

There is no way that a project can be truly undownloadable. The .sb file has to be readable for the java applet to run it, and so it can be explicitly downloaded by name, even if there is no download link provided.

Offline

 

#3 2007-05-29 01:02:48

fandebiao
Scratcher
Registered: 2007-05-15
Posts: 25

Re: Ideas for preventing plagiarism

kevin_karplus wrote:

There is no way that a project can be truly undownloadable. The .sb file has to be readable for the java applet to run it, and so it can be explicitly downloaded by name, even if there is no download link provided.

i'm not sure about what you are saying but what if
1. .sb files were stored in a hidden directory that only the applet can access.
2. .sb files were encrypted and only the applet can decrypt them.

Last edited by fandebiao (2007-05-29 01:05:17)

Offline

 

#4 2007-05-29 04:49:32

Macca
Scratcher
Registered: 2007-05-01
Posts: 18

Re: Ideas for preventing plagiarism

It needs to read the actual .sb file which you submitted onto the internet. This means the page you see isnt the direct link of the .sb file, instead it uses JAVA to read the .sb file submitted elsewhere. Someone can easily find this file by typing in the right URL...

However, the person who made this website could simply use the login system on this webite to create restrictions to the pages of the actual .sb file so that only people in the database who have the 'admin' status ticked can enter that page. And no-one can access the database...


~Macca

Offline

 

#5 2007-05-29 10:32:56

ernestpazera
Scratcher
Registered: 2007-05-16
Posts: 5

Re: Ideas for preventing plagiarism

Some thoughts:

Scratch is supposed to be an open platform. Mechanisms to "Protect your IP"/prevent plagiarism are counter to the spirit of this openness. 

Try to think in terms of how your projects will benefit the scratch user group as well as the project itself, rather than in terms of "they are taking *MY* stuff". 

A few years from now, nobody will care that who wrote the whatever scratch application.

In part because of the surge in popularity (due to Digg and other exposure), and partly because of the (how to say this politely?) maturity level of many of the scratch users, plagiarism at this time is going to be rampant.

I am also a developer of Yahoo! Widgets, and the same sort of thing goes on, for the exact same reason: the platform is just so open.

Over time, many of the new found developers (mostly the plagiarists) will get bored and move on to something else.

Last edited by ernestpazera (2007-05-29 10:33:33)

Offline

 

#6 2007-06-01 09:11:07

jsimone
Scratcher
Registered: 2007-05-20
Posts: 28

Re: Ideas for preventing plagiarism

I think a simple comment somewhere on the web site or when you download to the effect "If you intend to modify this project, please give credit where credit is due." would suffice.

I tell students, if you download and modify someone else's work, please remember to give the original author credit in the program notes.

I don't see or know that the Author field in the project notes does anything or goes anywhere.  Does it?

Offline

 

#7 2007-06-01 09:43:40

PeterB
Scratcher
Registered: 2007-05-18
Posts: 14

Re: Ideas for preventing plagiarism

Do we complain because the rose has thorns or because the thorns have roses.

If you really think about it all the great technical developments have been built on plagarism, one could argue the Wright brothers plagerised Lenardo da vinci, but in the spirit of getting off the ground I dont da vinci would have been too bothered and probably would have taken great satisfaction in seeing someone bring his work to realisation, we would also not have windows if it was not plagerised from xerox (or so I'm lead to believe, just in case Bill's legal beagles are watching).

I'm sure at some point scratch will turn a corner and consider its self to be mature enough to be a chargeable and profit making entity, at that point I can think of no better reference then who, date and time of posting to the scratch website as a legal reference for the persuance of intellectual property or otherwise, as a result all subseqeunt postings using the same or copied code would lose any claim to IP.

So the only real consideration is weather MIT are maintaining a strict enough data retention policy for submissions so as to support any future IP reference is all that is needed to satisfy any legal arguements.

There is of course the other cop out which is to present posters with a 'you post at your own risk, do you wish to continue Y/N'  option to the upload capability.

I rest my case m'lud

Last edited by PeterB (2007-06-01 09:44:03)

Offline

 

#8 2007-06-01 13:46:45

kevin_karplus
Scratcher
Registered: 2007-04-27
Posts: 1000+

Re: Ideas for preventing plagiarism

There are two separate issues here that people are confusing:
   intellectual property
   plagiarism

Intellectual property gets into all sorts of messy legal tangles about who owns an idea and who has to pay whom to use it.

Plagiarism is not a legal matter (mostly) but an academic sin: claiming someone else's work as your own.  Even if you have permission to copy and modify something (so no intellectual property issues arise), it is still not acceptable to claim their work as yours.

Offline

 

#9 2007-06-26 08:31:51

bigB
Scratcher
Registered: 2007-06-09
Posts: 100+

Re: Ideas for preventing plagiarism

fandebiao wrote:

1.When submitting a project, the author can choose to make it undownloadable.
2.After a project is downloaded, it may be modified and re-uploaded, but the author remains same.  Modifiers have their names saved under a different tag after called "modifiers".
Feel free to add more.

i disagree with the first point.  i think all work should be downloadable. i frequently download projects just to see how they have done a particular thing.
the second point on-the-other-hand is a very good idea.  it could either be that modifiers are shown at the side or under the project it could say 'projectname' submitted by 'origionalcreator' modified by 'modifiername'.  it could also be made that this new version cannot recieve love-its or can only be accessed by a link from the origional.


http://scratch.mit.edu/projects/bigB/260981 Draw to Text
http://scratch.mit.edu/projects/bigB/181829 3D Stunt Flyer

Offline

 

#10 2007-07-05 12:32:53

andresmh
Scratch Team at MIT
Registered: 2007-03-05
Posts: 1000+

Re: Ideas for preventing plagiarism

We are not planning to disable downloading the source code of projects.

Kevin is right in distinguishing plagiarism from intellectual property. I tend to be convinced by the arguments against intellectual property, it seems that ideas shouldn't be treated as property.

Coming soon we will have ways of connecting projects to each other to attribute ideas. For example, you will be able to say "this project was inspired by this project" or "based on". This will give more visibility to both projects that are inspiring and inspired by others.


Andres Monroy-Hernandez | Scratch Team at the MIT Media Lab
on identi.ca and  twitter

Offline

 

Board footer