Comment on Oops, something went wrong!
hperrin@lemmy.ca 14 hours agoI want you to really pay attention to the last paragraph of my previous comment. It’s the most important part. You might like having more information that doesn’t help you, but that comes at the cost of thousands of useless tasks and posts that all have to be manually closed. It’s not only not helpful to give the user detailed error messages in a lot of cases, it’s actively harmful to a business. It doesn’t make any business sense to tell a user that a cache layer host or a db shard is down. As a developer of these kinds of systems, I’m not going to give extra information that you don’t need just to make a few users happy that they get a peek under the hood if it means hurting our support staff.
unhrpetby@sh.itjust.works 13 hours ago
How is a user sending a support request containing the information: “Site not working. Error message: A surge in requests is overloading the server. Everyone is being ratelimited” Any different from them just saying “Site not working.”?
If they were going to submit an issue for a problem that is already known, why would the error message significantly change the difficulty of dealing them?
hperrin@lemmy.ca 13 hours ago
Because if there’s no error code or specific message, they’re far less likely to submit a ticket. The reason these messages often say, “try again later” is because that is the appropriate action for the user to take.