16 Commits

Author	SHA1	Message	Date
realaravinth	54b14291ec	Implement CAPTCHA configuration estimation from avg, peak and ... broke_my_site_traffic The above metrics are sourced from the user and are stored in the database to reuse at a later point in time when the mCaptcha instance's admin changes suggested configuration. I'm not sure if I want to recompute configuration every time the admin updates suggested configurations or give the user an option to recompute based on latest trends. If we recompute on every update, then should the admin choose very high difficulty_factors then it would hold back the user's visitors, which is not nice. But there should also be an option to rerun estimates when older configuration no longer works properly.	2021-12-03 14:26:23 +05:30
realaravinth	068c49080e	handle libmcaptcha actor errors	2021-08-20 18:15:55 +05:30
realaravinth	8830961e04	stats endpoint	2021-07-25 21:15:59 +05:30
realaravinth	fcdbe66b26	captcha stats	2021-05-27 14:47:29 +05:30
realaravinth	aa0c30f1bd	send notifications	2021-05-10 00:55:47 +05:30
realaravinth	527724ecda	pow stats for solution and verification	2021-05-09 19:33:28 +05:30
realaravinth	98719670df	sitekey list	2021-05-04 18:34:36 +05:30
realaravinth	a5cfa3b305	pow stats	2021-04-30 11:14:29 +05:30
realaravinth	d32350e2b6	email optional	2021-04-12 11:14:21 +05:30
realaravinth	884cb25e02	user secret	2021-04-10 21:00:30 +05:30
realaravinth	4e7e8da574	rm domains and added authorization check at all endpoints	2021-04-09 16:52:05 +05:30
realaravinth	51764817f9	domain verification	2021-03-26 22:18:01 +05:30
realaravinth	096dcd32e4	cascading delete, mcaptcha add/del and test suite	2021-03-11 20:58:18 +05:30
realaravinth	6be10af6fd	suplicate errors and database fkey null correction	2021-03-11 16:45:43 +05:30
realaravinth	328fe5ed3a	auth and migration util	2021-03-10 20:43:25 +05:30
realaravinth	2c54518e12	moved from mono repo	2021-03-09 15:58:54 +05:30