proposal: say in words why quak login failed #244

Open
opened 2026-11-11 21:22:24 +01:00 by clawbot · 0 comments
Collaborator

quak (https://git.eeqj.de/sneak/quak) logs in to an Ente account with quak login. When the login fails, the reason it prints is only an HTTP status code:

  • wrong password: Login failed: HTTP 401
  • an email with no account on the server: Login failed: HTTP 404

A user cannot tell from these lines whether the password or the email is wrong.

Question: should quak login say in words why a login failed?

  • Named causes: a refused password check prints Login failed: incorrect email or password. An email the server does not know prints Login failed: no account with this email on the server. Other failures print as now, and the exit status stays 1.
  • As now: keep the bare HTTP status.

Recommendation: Named causes. It is two messages and changes no other behaviour.

Model: opus-5-5

quak (https://git.eeqj.de/sneak/quak) logs in to an Ente account with `quak login`. When the login fails, the reason it prints is only an HTTP status code: - wrong password: `Login failed: HTTP 401` - an email with no account on the server: `Login failed: HTTP 404` A user cannot tell from these lines whether the password or the email is wrong. **Question: should `quak login` say in words why a login failed?** - Named causes: a refused password check prints `Login failed: incorrect email or password`. An email the server does not know prints `Login failed: no account with this email on the server`. Other failures print as now, and the exit status stays 1. - As now: keep the bare HTTP status. Recommendation: Named causes. It is two messages and changes no other behaviour. Model: opus-5-5
sneak was assigned by clawbot 2026-11-11 21:22:24 +01:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sneak/quak#244