realaravinth
81ad030338
feat: migrate captcha exists to use db_* interface
2022-05-12 19:32:08 +05:30
realaravinth
bd75fc625c
feat: migrate adding captcha to use db_* interface
2022-05-12 19:10:04 +05:30
realaravinth
049f2b6eea
feat: migrate update secret to use db_* interface
2022-05-12 10:42:55 +05:30
realaravinth
25b3d316db
feat: migrate get password and get secret to use db_* interface
2022-05-11 20:21:55 +05:30
realaravinth
39ee2ad221
feat: migrate update username to use db_* interface
2022-05-11 20:02:03 +05:30
realaravinth
748f48e0d2
feat: migrate update password to use db_* interface
2022-05-11 19:52:20 +05:30
realaravinth
f398c4b61c
feat: migrate get password to use db_* interface
2022-05-11 18:54:36 +05:30
realaravinth
78eac8b6b7
feat: migrate email update to use db_* interface
2022-05-11 15:26:00 +05:30
realaravinth
621e400ea8
feat: migrate email exists to use db_* interface
2022-05-11 13:33:30 +05:30
realaravinth
1cd4ce7318
feat: migrate username exists to use db_* interface
2022-05-11 13:33:29 +05:30
realaravinth
9f91854c4d
feat: migrate account deletion to use db_* interface
2022-05-11 13:33:29 +05:30
realaravinth
26a0935e5f
feat: implement user registration for postgres via sqlx
2022-05-11 13:33:29 +05:30
realaravinth
91c6f77cab
chore: update actix-* deps
2022-05-07 16:10:14 +05:30
realaravinth
53e966958b
update sqlx offline compilation schema data
2021-12-18 21:04:35 +05:30
realaravinth
ff3f5504dd
update sqlx offline compilation schema data
2021-12-18 17:44:07 +05:30
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
595e79a014
update sqlx data, delete user in username_change test
2021-08-12 17:22:41 +05:30
realaravinth
1d759fcb25
captcha stats
2021-07-27 15:28:21 +05:30
realaravinth
9bc11f3518
lazy init edit submit btn and update demo link
2021-07-26 11:49:07 +05:30
realaravinth
4b18992f6a
settings page, clipboard component
2021-07-20 18:14:23 +05:30
realaravinth
c3e43ff584
update password
2021-07-17 18:51:20 +05:30
realaravinth
ea8264054a
edit sitekey, router pattern matching, sitekey update optimization, rm level delete and level err handling
2021-07-16 17:40:52 +05:30
realaravinth
47cca5c9a7
notifications view
2021-07-12 21:22:26 +05:30
realaravinth
8d32ebcf95
sqlx update and verification button styling
2021-06-30 23:08:53 +05:30
realaravinth
1065fa3864
sqlx data for login with email
2021-06-29 19:59:27 +05:30
realaravinth
fcdbe66b26
captcha stats
2021-05-27 14:47:29 +05:30
realaravinth
f560e3f9db
sqlx offline queries
2021-05-26 13:04:41 +05:30
realaravinth
a4b409e914
sqlx offline compilation
2021-05-12 17:37:11 +05:30