Errors are dystopian?
this post was submitted on 19 Jan 2025
-4 points (45.2% liked)
A Boring Dystopia
10036 readers
221 users here now
Pictures, Videos, Articles showing just how boring it is to live in a dystopic society, or with signs of a dystopic society.
Rules (Subject to Change)
--Be a Decent Human Being
--Posting news articles: include the source name and exact title from article in your post title
--If a picture is just a screenshot of an article, link the article
--If a video's content isn't clear from title, write a short summary so people know what it's about.
--Posts must have something to do with the topic
--Zero tolerance for Racism/Sexism/Ableism/etc.
--No NSFW content
--Abide by the rules of lemmy.world
founded 2 years ago
MODERATORS
The inability to disable a tracking feature due to an error is dystopian.
Isn’t 500 a http error?
Internal server error: A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.
A misconfigured server isn’t really dystopian.
Intentionally misconfigured to guarantee a malicious default setting is dystopian.
A temporary server error while trying to save settings to a server is not dystopian
Nah
Seems it to me. Users are defaulted to location tracking without consent, which is fucked up in and of itself, and the system doesn't work when trying to turn it off? I get that it's probably a one-off, but something tells me the corporation cares more about keeping their data collection system functional more than they care about the opt out feature.
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?
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.
Backend Dev here. 500 is an HTTP sever response, so requires a working connection to happen. If the app isn't connected to the network, in almost all cases, you would experience a different error, such as connection timed out, but not a 500.
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.