-
-
Notifications
You must be signed in to change notification settings - Fork 571
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
captcha in form #486
Comments
Thanks for reply. I was thinking more along the lines of captcha like
recaptcha for example.
…On Fri, 22 Mar 2024, 5:14 pm Bieber, ***@***.***> wrote:
Is that what you what 😀
image.png (view on web)
<https://github.com/teableio/teable/assets/113977203/0d30ae36-1be8-44ff-a640-d636de0baf8c>
—
Reply to this email directly, view it on GitHub
<#486 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXJ6UIQLCBOL7RZBYKKLH73YZPY7PAVCNFSM6AAAAABFC4R3WOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJUGY3DOMJVHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I see, you want to prevent spam submissions like bots. But I'm not sure if this is a just-needed scenario, and unless the form submission information is very sensitive, the risk should be limited. |
Thanks for your reply. Yes bots, i was unclear on that - my bad. The
password will help somewhat for basic bots but ones that just enter the
static password will easily bypass this because they are randomized.
Captcha is a standard option these days for most public facing forms and
resolve a massive problem of bots spamming the database rows.
…On Sat, 23 Mar 2024, 2:00 am Bieber, ***@***.***> wrote:
I see, you want to prevent spam submissions like bots. But I'm not sure if
this is a just-needed scenario, and unless the form submission information
is very sensitive, the risk should be limited.
Maybe a possible alternative is to require users to log in before
submitting.
—
Reply to this email directly, view it on GitHub
<#486 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXJ6UIWDOQHIFIT7LMCSA23YZRWVLAVCNFSM6AAAAABFC4R3WOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJVGYZTKMBRGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I also don't see a need for captcha in form it will slow the data entry flow , since there is a password and the spammers shouldn't be aware of it the password is more than enough |
It's common practice for forms and optional like the other fields at the
creators discretion, its not mandatory.
…On Sat, 23 Mar 2024, 9:14 pm mz0in, ***@***.***> wrote:
I also don't see a need for captcha in form it will slow the data entry
flow , since there is a password and the spammers shouldn't be aware of it
the password is more than enough
—
Reply to this email directly, view it on GitHub
<#486 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXJ6UIWWTVXBDXH2AZWYYNLYZV547AVCNFSM6AAAAABFC4R3WOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJWGQ4TEMRVGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
If you have a public form with a password to complete the form then you need to publicly announce said password. This is a risk as bots can easily spam the heck out of your database. A simple captcha option in the existing field options is a solution to this. Edit: The captcha is optional like any other form field element. Like most other form providers have. |
Hey, just checking in on this to see if it is in the roadmap at all? |
Due to the lack of significant necessity, we have not included it in our roadmap. |
Forms have a lot of elements, however to help combat spam it would be good to have an option for captcha. Forms can then safely be used publicly unlike currently.
The text was updated successfully, but these errors were encountered: