Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

List of confirmed cheaters #1378

Open
DonaldKellett opened this issue Apr 12, 2018 · 642 comments
Open

List of confirmed cheaters #1378

DonaldKellett opened this issue Apr 12, 2018 · 642 comments

Comments

@DonaldKellett
Copy link
Member

DonaldKellett commented Apr 12, 2018

jhoffner I really don't want to publicly shame CW cheaters here but recently there seems to be an increase in the number of cheaters who aren't getting banned quick enough. Some cheaters have already lingered for months, wearing a 1 kyu/1 dan badge when they actually don't deserve it. If this doesn't stop quickly, the morale of genuine Codewarriors may be damaged and CW will gradually lose their trust. So, here is a list of confirmed cheaters:

- https://www.codewars.com/users/aditya7iyengar (edit: handled)

(List to be updated as more and more cheaters are discovered/confirmed)

┆Issue is synchronized with this Clickup by Unito

@jhoffner

This comment has been minimized.

@jhoffner
Copy link
Member

BTW we have a plagiarism service in the works. Its being built for Qualified but we will use it for CW to detect cheaters as well.

We also no longer allow banned users to delete their account or change their name. So any user who wants to use an identifiable name that means anything to them, once they get caught, they are stuck that way.

@Blind4Basics

This comment has been minimized.

@Blind4Basics

This comment has been minimized.

@Voileexperiments

This comment has been minimized.

@Voileexperiments

This comment has been minimized.

@kazk
Copy link
Member

kazk commented Apr 13, 2018

See, the main problem here is that some smarter people already know straight out copying is too blatant, so they are copying existing solutions with cosmetic changes, and the existing service is powerless in detecting this. Manual inspection is the only way to be sure

One approach that I've been (personally) looking into recently is to use sklearn to detect similar solutions. This works even if things are moved around and have some changes.

So I compared solutions for SKI kata by those two (by the way, you can run this on Codewars :)).

from sklearn.feature_extraction.text import TfidfVectorizer
from sklearn.metrics.pairwise import linear_kernel
v = TfidfVectorizer().fit_transform([xenoexploratorSKI, aditya7iyengarSKI])
print(linear_kernel(v[0:1], v).flatten())
# [ 1.          0.43158685]

I'd say that's already pretty high for advanced kata. And after removing comments, the similarity increases to 0.99867269. I'm still learning about it, but this seems useful even without specifying options like tokenizer.

@Blind4Basics

This comment has been minimized.

@Blind4Basics

This comment has been minimized.

@docgunthrop

This comment has been minimized.

@Voileexperiments

This comment has been minimized.

@Voileexperiments

This comment has been minimized.

@Blind4Basics

This comment has been minimized.

@kazk

This comment has been minimized.

@Blind4Basics

This comment has been minimized.

@kazk

This comment has been minimized.

@Blind4Basics

This comment has been minimized.

@Blind4Basics

This comment has been minimized.

@docgunthrop

This comment has been minimized.

@kazk

This comment has been minimized.

@Voileexperiments

This comment has been minimized.

@Voileexperiments

This comment was marked as resolved.

@Voileexperiments

This comment has been minimized.

@Blind4Basics

This comment has been minimized.

@docgunthrop

This comment has been minimized.

@Blind4Basics

This comment has been minimized.

@Blind4Basics

This comment has been minimized.

@kazk

This comment has been minimized.

@Blind4Basics

This comment has been minimized.

@ejini6969

This comment was marked as resolved.

@ejini6969

This comment was marked as resolved.

@ejini6969

This comment was marked as resolved.

@ejini6969

This comment was marked as resolved.

@ejini6969

This comment was marked as resolved.

@ejini6969

This comment was marked as resolved.

@ejini6969

This comment was marked as resolved.

@ejini6969

This comment was marked as resolved.

@ejini6969

This comment was marked as resolved.

@ejini6969

This comment was marked as resolved.

@ejini6969

This comment was marked as resolved.

@ejini6969

This comment was marked as resolved.

@ejini6969

This comment was marked as resolved.

@ejini6969

This comment was marked as resolved.

@ejini6969

This comment was marked as resolved.

@ejini6969

This comment was marked as resolved.

@ejini6969

This comment was marked as resolved.

@ejini6969

This comment was marked as resolved.

@ejini6969

This comment was marked as resolved.

@ejini6969

This comment was marked as resolved.

@ejini6969

This comment was marked as resolved.

@ejini6969

This comment was marked as resolved.

@ejini6969

This comment was marked as resolved.

@ejini6969

This comment was marked as resolved.

@ejini6969

This comment was marked as resolved.

@ejini6969

This comment was marked as resolved.

@ejini6969

This comment was marked as resolved.

@ejini6969

This comment was marked as resolved.

@ejini6969
Copy link

ejini6969 commented Feb 24, 2024

Some Java cheaters now ~~

1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52

@ejini6969
Copy link

1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests