Copyright issue on Sololearn - discussion!

Question

Earlier in a feed post of Donna the question was pondered how we would defend ourselves if someone stole our code - and then blamed us for stealing that code.

You could always argue: 'I posted it then and then on Sololearn.'

But that's hardly a point when you can change your file content anytime.

Let's say you create an empty file in January; you steal a fresh Code in February; then in March you 'discover what has been done to you' and claim: 'I wrote that - see when I posted it!'

A solution idea came up. There could be a third option to save a code: As a file that can not be changed after creation.

So whenever you are about to 'publish' a code here, you could voluntarily create such an 'immutable' copy, and if someone came ablaming, you could point your finger on a validation that Sololearn can confirm.

What do you (also the moderation) think about this?

Answer 1

https://www.sololearn.com/post/65958/?ref=app

Answer 2

HonFu Suggestions about this are been proposed in past. Some solutions have to be implement to app level then, we mods, can only send the suggestion and nothing more... Futhermore, in mods group, there is been a long discussion about this just few hours ago the other suggestions will be sended... For now, write always than you dont allow copy of your code in source, its not a solution but will be more easy handle the destiny of copied code when finded

Answer 3

🤔
While I tend to agree with everything THE TRUMP said except the part about open-sourcing code means it belongs to everyone, I also agree that some parts are slightly divergent from the original question.

It's true that the best way to prevent others from stealing your code is to keep it proprietary and to protect your trade secrets with non-disclosure agreements. Putting your code in a SoloLearn project repository puts the code under the purview of SoloLearn's Terms of Use (no longer a secret). Privated projects in a SoloLearn repository can still be accessed by anyone with the URL, even if they may not show up in a search.

When it comes to defending against a thief who is accusing you of stealing their code, just remember that the burden of proof is on them as plaintiff. They must first prove ownership of the copyrighted work (not you) and this can be quite complicated for them -- before they are even allowed to start arguing that their rights were infringed upon and by you.

So don't sweat it. 😊

Answer 4

You would have to be a pretty low person in order to create a new file, for the sole purpose of using it to point at the "creation date", in case at some future time you come across a code that you want to copy and claim as originally yours.

In almost all cases, the recorded "creation date" should be enough defence. In case anyone doesn't know, you can see the creation date as well as the last modified date of your code by clicking the 3 dots and then clicking "details".

Answer 5

I think that would be a great idea!

Answer 6

Rather than creating a file just for that purpose, what might be more likely is a thief writing over one of their own previous codes, that they don't care about, that has an earlier "creation date" than the code they copied and are trying to claim.

Answer 7

The features "It's already there "

Answer 8

bigger issues around, a pal during graduation year had project on the go in the final year, he was focused on obtaining the outcome. that was obtained and around 6 months later his code started picking professional referee for each fixture in a national sports organisations setup. Turns out his project all intelectual property inside it was given up soon as he entered the course. he could have dropped out never submitted the work and walked away with a healthy income. beware who actually owns whats created in some setups

Answer 9

Some people do not think the feeling of the original code's creator😥.

Sometimes, the Sololearner who has a collection of good codes here copied them from the other sources. In fact, they are not really great. Just a copier😫

Answer 10

That it would be indeed quite low does not necessarily mean it wouldn't happen though.

And a few changes in the code? How's that suspicious?

Person could say: 'I just changed a few minor details here and there!'

Answer 11

Yeah, and it would lead to the same situation.

Answer 12

Charan LEo25, well, yeah, you may be able to simulate what I am talking about: Create a copy of your code and don't touch it after creation.

But it's a bit inconvenient because you have to keep track of that and always be on your guard not to accidentally open that file.

Also I think some mods can write into your file so that it's not completely sealed.

Answer 13

THE TRUMP, you are fighting a strawman here, painting an ugly picture of people only seeking the clicks, and reducing the whole problem to just that.

The reasons why people feel protective of their codes, and the problem that it's hard to prove your authorship of a code in case you have to, are two separate matters.

Answer 14

security through obscurity https://en.m.wikipedia.org/wiki/Obfuscation_(software) thats a tried and tested approach but only in some areas, reverse engineering is pretty hard to prevent given enough efforts.