Future signup page idea #22
Labels
No Label
#19
Bad Style
Broken
Bug
Migration
Network
Priority: High
Priority: Low
Priority: Normal
Priority: URGENT
Suggestion
ToDo
nofun
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: root/threadr.lostcave.ddnss.de#22
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
see title
I have an idea regarding this:
Have sign up and user authentication controlled through a specified interface so that it is easy to create modules that hook into it instead of handling that inside ThreadR. There would still be a users table for everything else except authentication.
This would allow for things like "sigh up with GitHub / Google / whatever" or allow the admin who hosts an instance to run a CAPTCHA or verify email addresses externally.
ThreadR would only ship with three simple modules: "default", "default no CAPTCHA" and "default login only".
The "default" module would only accept a user name and a password as signup information and present the user with a CAPTCHA on user creation. The "default no CAPTCHA" is the same module just with the CAPTCHA stripped out and the "default login only" is the same but with signup stripped out completely.
While I would want ThreadR to support multiple modules being loaded at the same time, only the "default" module would be enabled by ... default.
scrap whatever is going on with the signup page rn, receiving an email is not a secure sanity check for usto Future signup page idea