||9 months ago|
|.github||11 months ago|
|examples||9 months ago|
|src||9 months ago|
|.gitignore||1 year ago|
|CHANGELOG.md||9 months ago|
|Cargo.lock||10 months ago|
|Cargo.toml||10 months ago|
|LICENSE.md||1 year ago|
|README.md||12 months ago|
|code_of_conduct.md||1 year ago|
mCaptcha uses SHA256 based proof-of-work(PoW) to rate limit users.
If someone wants to hammer your site, they will have to do more work to send requests than your server will have to do to respond to their request.
0.1.xis out, expect breaking changes as ergonomics and performance is improved. Checkout changelog for changes and migration pointers. Breaking changes will be frequent through
Why use mCaptcha?
- Free software, privacy focused
- Seamless UX - No more annoying captchas!
- IP address independent(sort of) - your users are behind a NAT? We got you covered!
- Automatic bot throttling
- Resistant to replay attacks - bye-bye captcha farms!
Demo servers are available at:
Core functionality is working but it's still very much work-in-progress.
Feel free to provide bogus information while signing up(project under development, database frequently wiped).
Please refer to mCaptcha/mCaptcha for instructions.
mCaptcha is made up of three components:
1. Front-end library
We have a WASM library now, Android and iOS libraries soon
2. Back-end library
We have Rust library, other languages will have support soon
3. Rate limiting service
A paid, managed service will be made available soon but I(@realaravinth) encourage you guys to self-host. Go decentralisation!