All the development time went into the option that requires the user to agree to more surveillance. Did they even attempt to do QA on the “disagree” option?
I was thinking of a case where there was a network connection problem and instead of precisely reporting that, the frontend told the user it was a 500 instead.
8 Comments
glimse@lemmy.world · 13 pts · 1y
Errors are dystopian?
Stovetop@lemmy.world · 9 pts · 1y
CTDummy@lemm.ee · 15 pts · 1y
Isn’t 500 a http error?
A misconfigured server isn’t really dystopian.
spankmonkey@lemmy.world · 4 pts · 1y
Intentionally misconfigured to guarantee a malicious default setting is dystopian.
glimse@lemmy.world · 2 pts · 1y
A temporary server error while trying to save settings to a server is not dystopian
Oisteink@feddit.nl · 1 pts · 1y
Nah
Stovetop@lemmy.world · 4 pts · 1y
PlasticExistence@lemmy.world · 5 pts · 1y
All the development time went into the option that requires the user to agree to more surveillance. Did they even attempt to do QA on the “disagree” option?
markstos@lemmy.world · 3 pts · 1y
500 errors may be transient, possibly because the app isn’t connected to the network.
It may well work fine a minute later or for someone else.
dajoho@sh.itjust.works · 2 pts · 1y
markstos@lemmy.world · 1 pts · 1y
You are right.
I was thinking of a case where there was a network connection problem and instead of precisely reporting that, the frontend told the user it was a 500 instead.