Reconsider the data required for signup
Open
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 755
- Forks
- 128
- PR merge metrics
- No merged PRs in 30d
Description
You require people to fill in their data. Of course lot of people prefer not to input the data.
So I propose to
- not to collect emails. Allow signing up and signing in without it, for example using a nickname as a login, or even having separate a login and a nickname.
- allow restoration of a lost password without using emails. For example by giving a user a secret on first use. Or use crypto authentication protocols.
- allow signing up and in not by a login and a password, but using crypto authentication protocols.
- allow signing up and in using github and gitlab accounts (no scopes should be requested!)
- not to collect any other information, no mandatory surnames
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the current signup, sign-in, password-recovery, and profile-data flows, then review how authentication and external GitHub/GitLab accounts are handled. Done requires a decided, scoped privacy and authentication design rather than the several alternatives listed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, gitlab, php
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100