introduction blog, contact and privacy policy

This commit is contained in:
Aravinth Manivannan 2021-05-26 14:18:41 +05:30
parent 226bd04358
commit fd5a7bb534
Signed by: realaravinth
GPG key ID: AD9F0F08E855ED88
8 changed files with 131 additions and 38 deletions

View file

@ -32,6 +32,12 @@
url = "/community/"
weight = 30
[[main]]
name = "Contact"
url = "/contact/"
weight = 40
[[social]]

View file

@ -1,8 +1,8 @@
---
title: "Blog"
description: "The Doks Blog."
date: 2020-10-06T08:49:55+00:00
lastmod: 2020-10-06T08:49:55+00:00
description: "mCaptcha Blog."
date: 2021-05-26 13:06
lastmod: 2021-05-26 13:06
draft: false
images: []
---

View file

@ -1,11 +1,76 @@
---
title: "Say hello to Doks 👋"
description: "Introducing Doks, a Hugo theme helping you build modern documentation websites that are secure, fast, and SEO-ready — by default."
lead: "Introducing Doks, a Hugo theme helping you build modern documentation websites that are secure, fast, and SEO-ready — by default."
date: 2020-11-04T09:19:42+01:00
lastmod: 2020-11-04T09:19:42+01:00
title: "Say hello to mCaptcha"
description: "Introducing mCaptcha, a kickass CAPTCHA systems that gives (DDoS) attackers a run for their money. Oh and UX is great too!"
lead: "We are mCaptcha. We build kickass CAPTCHA systems that gives (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-05-26
lastmod: 2021-05-26
draft: false
weight: 50
images: ["say-hello-to-doks.png"]
contributors: ["Henk Verlinde"]
contributors: ["Aravinth Manivannan"]
---
At mCaptcha, we believe in digital freedom and privacy and so we built an
[proof-of-work](https://en.wikipedia.org/wiki/Proof_of_work) based
CAPTCHA system that doesn't track. Seriously, no tracking. But that
isn't the killer feature, our system doesn't require the user to
pick cars or ID sidewalks --- our system does it's thing(usually
at the click of a button) and gets out of the way.
## How does it work?
mCaptcha uses SHA256 based proof-of-work(PoW) to rate limit users.
When a user wants to do something on an mCaptcha-protected website,
1. they will have to generate proof-of-work(a bunch of math that will
takes time to compute) and submit it to mCaptcha.
2. We'll validate the proof:
- if validation is unsuccessful, they will be prevented from accessing
the destination website
- if validation is successful, read on,
3. They will be issued a token that should be submit along with the
request/form to the destination website.
4. The destination website validates the submitted token with
mCaptcha before processing the request.
The whole process is automated from the user's point of view. All they
have to do is click on a button to initiate the process.
## Okay, but what about bad actors?
mCaptcha makes interacting with websites (computationally)expensive for
the user. A well-behaving user will experience a slight delay(no delay
when under moderate load to 2-3 seconds when under attack; PoW difficulty is
variable) but if someone wants to hammer your site, they will have to do
more work to send requests than your server you will have to do to respond
to their request.
## Why use mCaptcha?
- **Free software, privacy focused**
- **Seamless** UX --- No more annoying CAPTCHAs!
- **IP address independent:** your users are behind a NAT? We got you covered!
- **Automatic bot throttling**
- **Resistant to replay attacks:** proof-of-work configurations have short lifetimes(30s) and can be used only once. If a user submits a PoW to an already used configuration or an expired one, their proof will be rejected.
## How to migrate?
Our client libraries are mostly compatible with reCAPTCHA and hCaptcha.
A detailed guide will be published soon.
## Our Philosophy
Man has has come so far only because our ancestors chose to
share their knowledge with others. If everything was labeled
intellectual property, we might still be stuck in Stone Age. The idea of
intellectual property is alien to us. For this reason, all of our source
code is freely available(both as in freedom and beers) at [our
GitHub](https://github.com/mCaptcha/).
## Resources:
- [guard](https://github.com/mCaptcha/guard) - mCaptcha backend `AGPL`
- [frontend library](https://github.com/mCaptcha/browser) - mCaptcha frontend library. `MIT/APACHE`

19
content/contact/index.md Normal file
View file

@ -0,0 +1,19 @@
---
title: "Contact"
description: "mCaptcha contact information"
date: 2020-08-27T19:23:18+02:00
lastmod: 2020-08-27T19:23:18+02:00
draft: false
images: []
---
We have a [Matrix
community](https://matrix.to/#/+mcaptcha:matrix.batsense.net), come say
hi!.
You can find
me([@realaravinth](http://localhost:1313/contributors/aravinth-manivannan/))
on the [Matrix](https://matrix.to/#/@realaravinth:matrix.batsense.net),
on [GitHub](https://github.com/realaravinth) or email me at
[realaravinth@batense.net](mailto:realaravinth@batsense.net).

View file

@ -1,10 +1,10 @@
---
title: "Contributors"
description: "The Doks contributors."
date: 2020-10-06T08:50:29+00:00
lastmod: 2020-10-06T08:50:29+00:00
description: "The mCaptcha contributors."
date: 2021-05-26
lastmod: 2021-05-26
draft: false
images: []
---
The Doks contributors.
The mCaptcha contributors.

View file

@ -0,0 +1,12 @@
---
title: "Aravinth Manivannan"
description: "Creator of mCaptcha."
date: 2021-05-26
lastmod: 2021-05-26
draft: false
images: []
---
Creator of mCaptcha.
[@realaravinth](https://batsense.net)

View file

@ -1,12 +0,0 @@
---
title: "Henk Verlinde"
description: "Creator of Hyas."
date: 2020-10-06T08:50:45+00:00
lastmod: 2020-10-06T08:50:45+00:00
draft: false
images: []
---
Creator of Hyas.
[@HenkVerlinde](https://twitter.com/henkverlinde)

View file

@ -1,13 +1,14 @@
---
title: "Privacy Policy"
description: "We do not use cookies and we do not collect any personal data."
date: 2020-08-27T19:23:18+02:00
lastmod: 2020-08-27T19:23:18+02:00
draft: true
description: "We do not use cookies, we do not collect any personal data and logs aren't shared with third-parties."
date: 2021-05-26
lastmod: 2021-05-26
draft: false
images: []
---
__TLDR__: We do not use cookies and we do not collect any personal data.
**TLDR**: We do not use cookies, we do not collect any personal data and
logs aren't shared with third-parties.
## Website visitors
@ -20,17 +21,19 @@ __TLDR__: We do not use cookies and we do not collect any personal data.
### Information we collect and what we use it for
We run [Plausible](https://plausible.io/) analytics on getdoks.org. The following information is collected:
Website activity is logged and stored for a period of one month for
debugging purposes. We don't share this information with anyone nor do
we run analytics on it.
- __Page URL__. We track the page URL of each page view on this website. We use this to understand which pages have been viewed and how many times a particular page has been viewed. For example: _https://getdoks.org/_.
- __HTTP Referrer__. We use the referrer string to understand the number of visitors referred to this website from links on other sites. For example: _https://github.com/_.
- __Browser__. We use this to understand what browsers people use when visiting this website. This is derived from the User-Agent HTTP header. The full User-Agent is discarded. For example: _Chrome_.
- __Operating system__. We use this to understand what operating systems people use when visiting this website. We only use the brand of the operating system and dont include the version number or any other details. This is derived from the User-Agent HTTP header. The full User-Agent is discarded. For example: _GNU/Linux_.
- __Device type__. We use this to understand what devices people use when visiting this website. This is derived from window.innerWidth. The actual width of the browser in pixels is discarded. For example: _Desktop_.
- __Visitor Country__. We look up the visitors country using the IP address. We do not track anything more granular than the country of origin and the IP address of the visitor is discarded. We never store IP addresses in our database or logs. For example: _Canada_.
The following information is collected:
- **Page URL**. the page URL of each page view on this website. For
example: _https://mcaptcha.org/contact_
- **Browser**. We use this to reproduce browser-specific bugs people
see. This is derived from the User-Agent HTTP header. For example: _Chrome_.
## Contact us
[Contact us]({{< ref "contact/index.md" >}}) if you have any questions.
Effective Date: _27th August 2020_
Effective Date: _20th May, 2021_