3 ms·
The problem is, now I have to do this every time for shitty dumbed down apps. Prime example: Twitter always responds "oops, something went wrong" even if the b
by troupo 3y ago
The problem is, now I have to do this every time for shitty dumbed down apps.
Prime example: Twitter always responds "oops, something went wrong" even if the backend returns `{ error: "Video aspect ration is not allowed. Try 16:9" }`
- ryandrake 3y agoThose "oopsie-doopsie, website made a poopsie" infantilizing error messages are just awful. Tell the user 1. specifically what went wrong, 2. what, if anything, they can do to correct, and 3. a token (like an error message) that could be useful for tech support or reporting a bug. People's heads aren't going to explode if you treat them like functioning adults.
- starttoaster 3y agoYou’ve just vastly overestimated the technical capabilities of most Twitter users.
- dwaite 3y agoThe meta conversation here is whether there was a decision to NOT give the user information on how to correct the problem - or if it was a process maturity, developer skill, or limited resources that caused the development to focus on the "happy path" only.