forked from mCaptcha/website
39 lines
1.7 KiB
Markdown
39 lines
1.7 KiB
Markdown
---
|
|
title: "Survey"
|
|
description: "We are conducting a survey to benchmark and gather
|
|
performance metrics of our system on various devices"
|
|
lead: "We are mCaptcha. We build kickass CAPTCHA systems that give (DDoS) attackers a run for their money. And we do all of this without tracking your users. Oh and did I mention our UX is great?"
|
|
date: 2021-10-28
|
|
lastmod: 2021-10-28
|
|
draft: false
|
|
weight: 50
|
|
images: ["icon.png"]
|
|
contributors: ["Aravinth Manivannan"]
|
|
---
|
|
|
|
**Survey link:** [https://survey.mcaptcha.org/survey/campaigns/b717e51e-24d4-4ab6-912f-de2dfe3ce1fe/about](https://survey.mcaptcha.org/survey/campaigns/b717e51e-24d4-4ab6-912f-de2dfe3ce1fe/about)
|
|
|
|
**NOTE:** The survey(at least, the lucky draw is temporarily suspended
|
|
due to some logistical reasons. Apologies for any inconvenience caused.
|
|
|
|
mCaptcha relies on a
|
|
[proof-of-work(PoW)](https://en.wikipedia.org/wiki/Proof_of_work)
|
|
mechanism to guard against bots. In order for this to be effective, the
|
|
difficulty factor should be configured properly. If the difficulty
|
|
factor is too high all the time, it will inconvenience the users and if
|
|
it's too low during attack, the defence will be weak.
|
|
|
|
So we are conducting a survey to gather performance benchmarks from
|
|
various devices and browsers. The data collected from the survey will be made
|
|
public, we believe it will guide sysadmins configure difficulty factor
|
|
properly.
|
|
|
|
If you are interested in the lucky draw, please save the `submission ID` and the `proof` will be presented
|
|
to you at the end of the survey.
|
|
|
|
{{% img src="survey-id.jpg" alt="survey lucky draw identifier credentials" caption="Lucky draw credentials" %}}
|
|
|
|
## Winners
|
|
|
|
This blog post will be updated with the winning submission IDs and the
|
|
winners should provide the matching `proof` to claim their rewards.
|