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
..
20210310122154_mcaptcha_users.sql	handle libmcaptcha actor errors	2021-08-20 18:15:55 +05:30
20210310122617_mcaptcha_config.sql	sitekey list	2021-05-04 18:34:36 +05:30
20210310122902_mcaptcha_levels.sql	cascading delete, mcaptcha add/del and test suite	2021-03-11 20:58:18 +05:30
20210430032935_mcaptcha_pow_fetched_stats.sql	stats endpoint	2021-07-25 21:15:59 +05:30
20210509135118_mcaptcha_pow_solved_stats.sql	stats endpoint	2021-07-25 21:15:59 +05:30
20210509135154_mcaptcha_pow_confirmed_stats.sql	stats endpoint	2021-07-25 21:15:59 +05:30
20210509151150_mcaptcha_notifications.sql	send notifications	2021-05-10 00:55:47 +05:30
20211202141927_mcaptcha_sitekey_user_provided_avg_traffic.sql	Implement CAPTCHA configuration estimation from avg, peak and	2021-12-03 14:26:23 +05:30