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

feat: Recaptcha verification during signup #2444

Open
wants to merge 2 commits into
base: development
Choose a base branch
from

Conversation

chanmol1999
Copy link
Member

Fixes #2350

Changes: Add recaptcha during signup.

Screenshots for the change:
captcha

@auto-label auto-label bot added the feature label Jan 7, 2020
@chanmol1999
Copy link
Member Author

@atm1504 Please review

@@ -37,6 +41,7 @@ class SignUpActivity : AppCompatActivity(), ISignUpView {
private lateinit var forgotPasswordProgressDialog: Dialog
private lateinit var builder: AlertDialog.Builder
private var checkDialog: Boolean = false
private val RECAPTCHA_KEY = "6LcKhbMUAAAAAGFbYZeNFzqol-7EjOHUK5MvEeOE"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This shouldn't be hardcoded

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What else can I do to avoid this @iamareebjamal

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See where all configs are placed

}
})
.addOnFailureListener(this, OnFailureListener { e ->
Timber.e("Error: " + e)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not correct way of using Timber.e

@atm1504
Copy link
Member

atm1504 commented Jan 10, 2020

The screenshot you provided has been copied from #2360
Its a case of plagiarism.

@atm1504 atm1504 closed this Jan 10, 2020
@chanmol1999
Copy link
Member Author

@atm1504 I don't think this is a case of plagiarism.
Although I have not used your screenshot but still if you feel that the screenshot has been copied from your pull request you could have asked me to do the required changes.
Simply closing the pr without any valid reason is not under the guidelines of open source contributions. Also, you shouldn't favor pull request of other contributors
These things are totally unexpected from mentor of the project in such a great organization.This has given me a lot of disappointment.I may not contribute to this project in the future if such things happen again.
As far as I know this is an open source project and using someone's screenshot doesn't come under plagiarism.
Please look into this @iamareebjamal and @mariobehling and ensure such things do not repeat in future with some other contributors.
Thanks.

@iamareebjamal iamareebjamal reopened this Jan 13, 2020
@iamareebjamal
Copy link
Member

OK @atm1504 Why should copying your screenshot, or even your code be considered plagiarism? You contributed that as open source. Unless you have complete your PR, why shouldn't anyone else even use your code to do it? And here, it's not even code being copied. I don't think you understand plagiarism. Screenshot was not even required in the PR.

@atm1504
Copy link
Member

atm1504 commented Jan 13, 2020

@iamareebjamal I don't consider copying code as plagiarism in open source. But the thing is that this pr was created without even testing the code, which can be proved directly by seeing the screenshot.
Creating a pr without even testing it is a really bad habit. My point was that only.
Also, the key he has provided is the same as that was supplied. Now, suppose that the key has expired for now, but he created the pr, claiming that he worked and the code executed properly (without even testing), is that a good habit. SHouldn't all this be checked properly?

@iamareebjamal
Copy link
Member

You didn't write any of that. Only about screenshot being copied

@atm1504
Copy link
Member

atm1504 commented Jan 13, 2020

@iamareebjamal that was my fault that I didn't mention all the reasons.

@chanmol1999
Copy link
Member Author

@atm1504 I checked it with my key but I thought that maybe the key you used previously was still active and is in current use.
Also, You should have mentioned that before claiming plagiarism.
And also I was already going to make changes as requested by @iamareebjamal Sir.
And In that changes definitely this key is supposed to be removed.
Please do mention things correctly before reaching to a conclusion.

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

Successfully merging this pull request may close these issues.

Add ReCaptcha for Signup attempt
3 participants