Plagerism

[OlivierLaflamme]

https://github.com/mxrch/penglab

If you like the project you should simply fork it...

You cant be serious.... you should be the one contributing to the project instead of stealing it

[someshkar]

I can definitely link to it on the readme.

I didn't think running Hashcat on Colab was something never done before, I just realized that being able to backup and restore sessions when you run into the free limits was a fairly good idea.

Does this help your issue?

[OlivierLaflamme]

You definitely should, if youre not going to simply delete the repo and fork the original one if you like the project that much. And you should remove your lenience, seriously. Yeah im sure its not something thats never been done before. Thats completely besides the point! The point is that you've stolen someone else's code, and might potentially fool people and employers into thinking this is your own idea and code. which is reprehensible, in other words you're stealing his intellectual property,

[someshkar]

I'm really sorry if this got to you, but I really don't know what to say beyond that I'd never seen the other project before, and had been cracking on Colab for more than a year now. I just felt that sharing what I use very often for quickly cracking my neighbour's WPA2 hashes was something worthwhile.

Yes, I've linked to the other project. I'm not deleting the repository because this is my take on doing it, and if you have a look at how https://github.com/mxrch/penglab does it, you'll realise there's no code stealing at all.

[Jaroneko]

The point is that you've stolen someone else's code

Hold on. Did you actually go so far as to read the code for the two projects before accusing someone of stealing code from another project?

I did. They are absolutely not the same code. The projects have very similar aims, but accomplish this through different actions with slightly differing results and absolutely share no code. It's perfecctly reasonable to assume that both creators have had this idea separately and there's nothing particularly novel in installing hashcat. They just provide means for people to easily do this on Google Colab.

[Taubin]

The point is that you've stolen someone else's code, and might potentially fool people and employers into thinking this is your own idea and code. which is reprehensible, in other words you're stealing his intellectual property,

Seriously, stealing someone's idea? That's like accusing Pepsi of stealing their idea for a soda from Coke.

[fluffypony]

@OlivierLaflamme The code is not even remotely similar, they don't even take the same approach to many of the architectural decisions. Your suggestion that they fork another project should, frankly, be insulting to the developer.

I also think it's absurd to suggest that someone go and perform anything other than a cursory search before embarking on a project like this, and even if they do find that someone else has done it before they may choose to redo it from scratch without giving any credit to them.

Great minds think alike: https://en.wikipedia.org/wiki/List_of_multiple_discoveries

[dutyfruit]

initial project hasen't licence and you add one but why ? Because of the twitter fame ?skldjfikosadhfsdhjkofhdsjkfhjklsdhfkljsdhjfkdshjklfhadjklsfhjkldshfjkadshjk cheh

[fluffypony]

@dutyfruit adding a license is recommended by GitHub when you create a new project, and is pretty standard. Also the MIT license is insanely permissive, you can literally take his code and sell it for profit without giving him anything. I would be more concerned about a FOSS project being unlicensed.

[someshkar]

@fluffypony Yep exactly. GitHub recommends adding a license.

And yes, this is a case of two projects having similar goals but different approaches to doing it. I hadn't ever heard of the other project before, and I had made the Jupyter notebook almost a year ago and have been using it ever since. I just decided to make it open source now because I thought people would benefit from it.

[axman6]

@someshkar I recommend you close this issue, it’s clear that @OlivierLaflamme doesn’t know what they’re talking about and hasn’t looked at the code. Nice work on a cool project.

[someshkar]

@axman6 Alright then. If everyone's okay with it, I'm closing this issue.