this post was submitted on 18 Aug 2025
10 points (67.9% liked)

AssholeDesign

9718 readers
2 users here now

This is a community for designs specifically crafted to make the experience worse for the user. This can be due to greed, apathy, laziness or just downright scumbaggery.

founded 2 years ago
MODERATORS
10
This may be useful. (lemmy.world)
submitted 1 month ago* (last edited 1 month ago) by rtxn@lemmy.world to c/assholedesign@lemmy.world
 

I'm getting this error that says Error. I can't tell if I fat-fingered the community name in the URL, or it got removed, or it doesn't exist in the first place, or maybe there's a legitimate issue with the software, but I hope it's useful!

I need to clarify because some people apparently never encountered the error page: it used to show the actual error. It was later changed to not do that.

(apologies for the atrocious aspect ratio)

top 8 comments
sorted by: hot top controversial new old
[–] Pechente@feddit.org 14 points 1 month ago* (last edited 1 month ago) (1 children)

This is bad design and not intentionally deceiving.

Edit: /c/crappydesign@sh.itjust.works

[–] asudox@lemmy.asudox.dev 9 points 1 month ago

!crappydesign@sh.itjust.works

[–] SpaceNoodle@lemmy.world 5 points 1 month ago (2 children)

This might actually be helpful. The fact that it's just the word "Error" in red could be just the clue the developer needs. You don't know.

[–] RizzRustbolt@lemmy.world 4 points 1 month ago

ERROR: An ERROR has occurred. Please correct this ERROR.

[–] rtxn@lemmy.world 2 points 1 month ago (1 children)

It used to show the type of error, like couldnt_find_post. It was changed and now it returns Error for everything. How is that helpful?

[–] SpaceNoodle@lemmy.world 5 points 1 month ago

Well, your original post lacked that context.

[–] bleistift2@sopuli.xyz 2 points 1 month ago

I assume this is in a browser. You might have more luck checking the network protocol. Press F12 (Windows/Linux and Firefox/Chrome; don’t know about Apple) to open the dev tools. Open the network tab, and retry your request. One of the new lines in the log should be red. Click that and check “Response”.

[–] blarghly@lemmy.world 2 points 1 month ago

Better fit for /c/programmerhumor.

There is nothing maliscious about this. Tons of websites do their own error handling because if they just show 500: Internal Server Error, then they start getting emails from their clients telling them the website hacked their browser. Catching all errors and displaying a generic error message while staying on the same page and keeping the same styling is less scary to non-technical users.

And of course, since all code any developer has ever written is perfect, there is no need to create good error handling that explains the problem in a way that will make it easy to debug.