README says "no accounts" but the code has POST /api/v1/register and POST /api/v1/login endpoints with password hashing (bcrypt). These endpoints are not documented anywhere in the README.
Suggested fix: Update README to accurately describe the authentication model: anonymous sessions via POST /api/v1/session AND optional account registration via /register and /login.
## From QA Audit ([#25 comment](https://git.eeqj.de/sneak/chat/issues/25#issuecomment-10914))
**Severity: BLOCKER**
README says "no accounts" but the code has `POST /api/v1/register` and `POST /api/v1/login` endpoints with password hashing (bcrypt). These endpoints are not documented anywhere in the README.
**Suggested fix:** Update README to accurately describe the authentication model: anonymous sessions via `POST /api/v1/session` AND optional account registration via `/register` and `/login`.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
From QA Audit (#25 comment)
Severity: BLOCKER
README says "no accounts" but the code has
POST /api/v1/registerandPOST /api/v1/loginendpoints with password hashing (bcrypt). These endpoints are not documented anywhere in the README.Suggested fix: Update README to accurately describe the authentication model: anonymous sessions via
POST /api/v1/sessionAND optional account registration via/registerand/login.