home.social

#errormessages — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #errormessages, aggregated by home.social.

  1. Ah, yes, the profound wisdom of error messages 🍋✨: "Just a moment...Enable #JavaScript and #cookies to continue." Because clearly, the best way to solve life's problems is by blaming the user for their tech settings 🤦‍♂️.
    wix-ux.com/when-life-gives-you #errorMessages #userBlame #techHumor #lifeLessons #HackerNews #ngated

  2. Ah, yes, the profound wisdom of error messages 🍋✨: "Just a moment...Enable #JavaScript and #cookies to continue." Because clearly, the best way to solve life's problems is by blaming the user for their tech settings 🤦‍♂️.
    wix-ux.com/when-life-gives-you #errorMessages #userBlame #techHumor #lifeLessons #HackerNews #ngated

  3. Ah, yes, the profound wisdom of error messages 🍋✨: "Just a moment...Enable #JavaScript and #cookies to continue." Because clearly, the best way to solve life's problems is by blaming the user for their tech settings 🤦‍♂️.
    wix-ux.com/when-life-gives-you #errorMessages #userBlame #techHumor #lifeLessons #HackerNews #ngated

  4. Ah, yes, the profound wisdom of error messages 🍋✨: "Just a moment...Enable #JavaScript and #cookies to continue." Because clearly, the best way to solve life's problems is by blaming the user for their tech settings 🤦‍♂️.
    wix-ux.com/when-life-gives-you #errorMessages #userBlame #techHumor #lifeLessons #HackerNews #ngated

  5. Ah, yes, the profound wisdom of error messages 🍋✨: "Just a moment...Enable #JavaScript and #cookies to continue." Because clearly, the best way to solve life's problems is by blaming the user for their tech settings 🤦‍♂️.
    wix-ux.com/when-life-gives-you #errorMessages #userBlame #techHumor #lifeLessons #HackerNews #ngated

  6. 🚫🔒 "Access Denied" – CNBC's cutting-edge #journalism on China's latest chess move against #Meta gets blocked faster than you can say "Great Firewall." Because who needs actual content when you can just enjoy the endless loop of error messages? 📉😂
    cnbc.com/2026/04/27/meta-manus #AccessDenied #GreatFirewall #China #ErrorMessages #HackerNews #ngated

  7. 🙄 Ah, the age-old #debate of closing tags in #HTML... because who needs structure when you have chaos? 🤷‍♂️ Rest assured, if you're searching for guidance, #ModSecurity has your back with its cryptic error messages. 🔍✨
    blog.novalistic.com/archives/2 #ErrorMessages #WebDevelopment #CodingChaos #HackerNews #ngated

  8. 🎓📚 Behold, the literary masterpiece that is 950 pages of inaccessible Feynman notes! A tour de force in the art of saying absolutely nothing, brought to you by ModSecurity's finest. If you thought physics was hard, try understanding this error message! 🚫✨
    thehugheslectures.info/the-lec #FeynmanNotes #InaccessibleLiterature #ModSecurity #PhysicsHumor #ErrorMessages #HackerNews #ngated

  9. 🎓📚 Behold, the literary masterpiece that is 950 pages of inaccessible Feynman notes! A tour de force in the art of saying absolutely nothing, brought to you by ModSecurity's finest. If you thought physics was hard, try understanding this error message! 🚫✨
    thehugheslectures.info/the-lec #FeynmanNotes #InaccessibleLiterature #ModSecurity #PhysicsHumor #ErrorMessages #HackerNews #ngated

  10. 🎓📚 Behold, the literary masterpiece that is 950 pages of inaccessible Feynman notes! A tour de force in the art of saying absolutely nothing, brought to you by ModSecurity's finest. If you thought physics was hard, try understanding this error message! 🚫✨
    thehugheslectures.info/the-lec #FeynmanNotes #InaccessibleLiterature #ModSecurity #PhysicsHumor #ErrorMessages #HackerNews #ngated

  11. 🎓📚 Behold, the literary masterpiece that is 950 pages of inaccessible Feynman notes! A tour de force in the art of saying absolutely nothing, brought to you by ModSecurity's finest. If you thought physics was hard, try understanding this error message! 🚫✨
    thehugheslectures.info/the-lec #FeynmanNotes #InaccessibleLiterature #ModSecurity #PhysicsHumor #ErrorMessages #HackerNews #ngated

  12. "Ah, yes, the perfect guide to learning Egyptian Hieroglyphs: an error message! 📜🚫 Apparently, it's hieroglyphic for 'We have no idea what we're doing.' 🙃 Enjoy decoding ModSecurity's wisdom instead. 🕵️‍♂️💻"
    egyptianhieroglyphs.net/egypti #EgyptianHieroglyphs #ModSecurity #ErrorMessages #TechHumor #CodingWisdom #LearningJourney #HackerNews #ngated

  13. "Ah, yes, the perfect guide to learning Egyptian Hieroglyphs: an error message! 📜🚫 Apparently, it's hieroglyphic for 'We have no idea what we're doing.' 🙃 Enjoy decoding ModSecurity's wisdom instead. 🕵️‍♂️💻"
    egyptianhieroglyphs.net/egypti #EgyptianHieroglyphs #ModSecurity #ErrorMessages #TechHumor #CodingWisdom #LearningJourney #HackerNews #ngated

  14. "Ah, yes, the perfect guide to learning Egyptian Hieroglyphs: an error message! 📜🚫 Apparently, it's hieroglyphic for 'We have no idea what we're doing.' 🙃 Enjoy decoding ModSecurity's wisdom instead. 🕵️‍♂️💻"
    egyptianhieroglyphs.net/egypti #EgyptianHieroglyphs #ModSecurity #ErrorMessages #TechHumor #CodingWisdom #LearningJourney #HackerNews #ngated

  15. "Ah, yes, the perfect guide to learning Egyptian Hieroglyphs: an error message! 📜🚫 Apparently, it's hieroglyphic for 'We have no idea what we're doing.' 🙃 Enjoy decoding ModSecurity's wisdom instead. 🕵️‍♂️💻"
    egyptianhieroglyphs.net/egypti #EgyptianHieroglyphs #ModSecurity #ErrorMessages #TechHumor #CodingWisdom #LearningJourney #HackerNews #ngated

  16. Ah, another riveting piece on how our ancestors weren't exactly rockstars in the realm of #innovation 🤯. A deep dive into why time travel is unnecessary when you've got #ModSecurity serving up error messages like it's the early 2000s 💾. But hey, #nostalgia, right? 😂
    juliawise.net/the-past-was-not #errorMessages #timeTravel #history #HackerNews #ngated

  17. A New Best Practice for User Friendly 404 Page Design?

    I clicked a link from a 2-year-old Hacker News thread, and Nielsen Norman Group served up a 404 page. On that 404 page, NN/G served up an educational message for visitors who arrive from ChatGPT, Claude, or another LLM: (Did an AI chat send you here? They sometimes get URLs wrong or hallucinate nonexistent NN/G articles.) Is this a new best practice for 404 page design? […]

    kerrick.blog/posts/2025/a-new-

  18. A New Best Practice for User Friendly 404 Page Design?

    I clicked a link from a 2-year-old Hacker News thread, and Nielsen Norman Group served up a 404 page. On that 404 page, NN/G served up an educational message for visitors who arrive from ChatGPT, Claude, or another LLM: (Did an AI chat send you here? They sometimes get URLs wrong or hallucinate nonexistent NN/G articles.) Is this a new best practice for 404 page design? […]

    kerrick.blog/posts/2025/a-new-

  19. A New Best Practice for User Friendly 404 Page Design?

    I clicked a link from a 2-year-old Hacker News thread, and Nielsen Norman Group served up a 404 page. On that 404 page, NN/G served up an educational message for visitors who arrive from ChatGPT, Claude, or another LLM: (Did an AI chat send you here? They sometimes get URLs wrong or hallucinate nonexistent NN/G articles.) Is this a new best practice for 404 page design? […]

    kerrick.blog/posts/2025/a-new-

  20. A New Best Practice for User Friendly 404 Page Design?

    I clicked a link from a 2-year-old Hacker News thread, and Nielsen Norman Group served up a 404 page. On that 404 page, NN/G served up an educational message for visitors who arrive from ChatGPT, Claude, or another LLM: (Did an AI chat send you here? They sometimes get URLs wrong or hallucinate nonexistent NN/G articles.) Is this a new best practice for 404 page design? […]

    kerrick.blog/posts/2025/a-new-

  21. 👨‍💻 Ah yes, the eternal struggle of Linux users: deciphering cryptic error messages as if translating ancient hieroglyphs. 🤔 OpenSSH 9 bravely redefines "intuitive" by defaulting to a protocol that half the world doesn't support, only to leave you googling 'O parameter' like it's the Holy Grail. 🔍⚡
    blog.x-way.org/Linux/2025/11/0 #LinuxUsers #OpenSSH9 #ErrorMessages #TechStruggles #AncientHieroglyphs #HackerNews #ngated

  22. 👨‍💻 Ah yes, the eternal struggle of Linux users: deciphering cryptic error messages as if translating ancient hieroglyphs. 🤔 OpenSSH 9 bravely redefines "intuitive" by defaulting to a protocol that half the world doesn't support, only to leave you googling 'O parameter' like it's the Holy Grail. 🔍⚡
    blog.x-way.org/Linux/2025/11/0 #LinuxUsers #OpenSSH9 #ErrorMessages #TechStruggles #AncientHieroglyphs #HackerNews #ngated

  23. 👨‍💻 Ah yes, the eternal struggle of Linux users: deciphering cryptic error messages as if translating ancient hieroglyphs. 🤔 OpenSSH 9 bravely redefines "intuitive" by defaulting to a protocol that half the world doesn't support, only to leave you googling 'O parameter' like it's the Holy Grail. 🔍⚡
    blog.x-way.org/Linux/2025/11/0 #LinuxUsers #OpenSSH9 #ErrorMessages #TechStruggles #AncientHieroglyphs #HackerNews #ngated

  24. 👨‍💻 Ah yes, the eternal struggle of Linux users: deciphering cryptic error messages as if translating ancient hieroglyphs. 🤔 OpenSSH 9 bravely redefines "intuitive" by defaulting to a protocol that half the world doesn't support, only to leave you googling 'O parameter' like it's the Holy Grail. 🔍⚡
    blog.x-way.org/Linux/2025/11/0 #LinuxUsers #OpenSSH9 #ErrorMessages #TechStruggles #AncientHieroglyphs #HackerNews #ngated

  25. Error messages should be independent. If you solve the underlying issue of one, it should not also solve another error message. Reporting multiple errors with the same underlying cause will just overload your users.

    I think that's what's happening here: stackoverflow.com/q/79816819/1. You can solve 4/5 errors by just adding an extra argument to the `foldr` call.

    #haskell #errormessages #usability

  26. 🤖✨BREAKING: Infinite AI #content is *still* terrible! Who knew? Apparently, the secret sauce was simply forgetting to actually provide any content at all. 🔍🚫 Welcome to the #future, where even error messages are cutting-edge journalism! 🙃
    arnon.dk/the-trust-collapse-in #InfiniteAI #Terrible #Journalism #ErrorMessages #HackerNews #ngated

  27. 🚀🌍 Ah, nothing like an exclusive front-row seat to a tragic #spectacle you’ll never actually read about! 🛑 Access Denied: Because who needs inconvenient truths when you can just stare at error messages? 🔐
    telegraph.co.uk/world-news/202 #exclusiveaccess #errormessages #inconvenienttruths #technews #HackerNews #ngated

  28. 🚀🌍 Ah, nothing like an exclusive front-row seat to a tragic #spectacle you’ll never actually read about! 🛑 Access Denied: Because who needs inconvenient truths when you can just stare at error messages? 🔐
    telegraph.co.uk/world-news/202 #exclusiveaccess #errormessages #inconvenienttruths #technews #HackerNews #ngated

  29. 🚀🌍 Ah, nothing like an exclusive front-row seat to a tragic #spectacle you’ll never actually read about! 🛑 Access Denied: Because who needs inconvenient truths when you can just stare at error messages? 🔐
    telegraph.co.uk/world-news/202 #exclusiveaccess #errormessages #inconvenienttruths #technews #HackerNews #ngated

  30. 🚀🌍 Ah, nothing like an exclusive front-row seat to a tragic #spectacle you’ll never actually read about! 🛑 Access Denied: Because who needs inconvenient truths when you can just stare at error messages? 🔐
    telegraph.co.uk/world-news/202 #exclusiveaccess #errormessages #inconvenienttruths #technews #HackerNews #ngated

  31. Bobbie Chen enlightens us with the revelation that error messages are mystical oracles 🧙‍♂️, apparently capable of predicting the future 🔮. Instead of just, you know, telling us what went wrong. Because who needs useful information when you can have ✨mystical nonsense✨?
    digitalseams.com/blog/any-dece #errorMessages #mysticalOracles #techHumor #BobbieChen #futurePredictions #softwareDevelopment #HackerNews #ngated

  32. To the user-interface designers and programmers out there: If the unfortunate event happens and you have to show an error message, please make sure the message is actually helpful for identifying the issue. You might think that hiding technical details is user-friendly, but in fact, the opposite is true. Do not make us guess what is wrong, tell us what you know!

    You might be afraid that this confuses users who are less tech-savvy. Not necessarily, if you give them a rough idea first (maybe in a more emphasized font) and then continue with the details you have (maybe in a smaller font). I am quite sure users are able to ignore the parts they do not understand, and if they need support, at least the person giving support has something to work with.

    Some simple examples:

    ❌ "Cannot connect to bluetooth device."
    ❓ "Okay, but why?"
    ✅ "Cannot connect to bluetooth device 'foo' (maybe it is turned off?): The device does not respond."

    ❌ "Cannot open file."
    ❓ "Which file? And again, why?"
    ✅ "Cannot open file 'testfile.txt' for reading: Permission denied"

    ❌ "Something went wrong when trying to load the website."
    ❓ "Again, what's the problem? Is the network interface down? Is the DNS server down? Is the target server itself down? Give me a hint, please!"
    ✅ "Cannot load the website. Maybe your computer is not connected to the Internet? Details: No route to host (192.168.10.1) when attempting to connect to the DNS server."

    This is nothing new. In fact, it is just an adaptation of the top-down writing approach we also use when writing scientific papers, for example: You begin with a rough overview and give increasingly more details later in the text.
    But do not omit the details completely!

    #usability #userinterfaces #userinterfacedesign #errormessages #programming #writing #technicalwriting

  33. To the user-interface designers and programmers out there: If the unfortunate event happens and you have to show an error message, please make sure the message is actually helpful for identifying the issue. You might think that hiding technical details is user-friendly, but in fact, the opposite is true. Do not make us guess what is wrong, tell us what you know!

    You might be afraid that this confuses users who are less tech-savvy. Not necessarily, if you give them a rough idea first (maybe in a more emphasized font) and then continue with the details you have (maybe in a smaller font). I am quite sure users are able to ignore the parts they do not understand, and if they need support, at least the person giving support has something to work with.

    Some simple examples:

    ❌ "Cannot connect to bluetooth device."
    ❓ "Okay, but why?"
    ✅ "Cannot connect to bluetooth device 'foo' (maybe it is turned off?): The device does not respond."

    ❌ "Cannot open file."
    ❓ "Which file? And again, why?"
    ✅ "Cannot open file 'testfile.txt' for reading: Permission denied"

    ❌ "Something went wrong when trying to load the website."
    ❓ "Again, what's the problem? Is the network interface down? Is the DNS server down? Is the target server itself down? Give me a hint, please!"
    ✅ "Cannot load the website. Maybe your computer is not connected to the Internet? Details: No route to host (192.168.10.1) when attempting to connect to the DNS server."

    This is nothing new. In fact, it is just an adaptation of the top-down writing approach we also use when writing scientific papers, for example: You begin with a rough overview and give increasingly more details later in the text.
    But do not omit the details completely!

    #usability #userinterfaces #userinterfacedesign #errormessages #programming #writing #technicalwriting

  34. To the user-interface designers and programmers out there: If the unfortunate event happens and you have to show an error message, please make sure the message is actually helpful for identifying the issue. You might think that hiding technical details is user-friendly, but in fact, the opposite is true. Do not make us guess what is wrong, tell us what you know!

    You might be afraid that this confuses users who are less tech-savvy. Not necessarily, if you give them a rough idea first (maybe in a more emphasized font) and then continue with the details you have (maybe in a smaller font). I am quite sure users are able to ignore the parts they do not understand, and if they need support, at least the person giving support has something to work with.

    Some simple examples:

    ❌ "Cannot connect to bluetooth device."
    ❓ "Okay, but why?"
    ✅ "Cannot connect to bluetooth device 'foo' (maybe it is turned off?): The device does not respond."

    ❌ "Cannot open file."
    ❓ "Which file? And again, why?"
    ✅ "Cannot open file 'testfile.txt' for reading: Permission denied"

    ❌ "Something went wrong when trying to load the website."
    ❓ "Again, what's the problem? Is the network interface down? Is the DNS server down? Is the target server itself down? Give me a hint, please!"
    ✅ "Cannot load the website. Maybe your computer is not connected to the Internet? Details: No route to host (192.168.10.1) when attempting to connect to the DNS server."

    This is nothing new. In fact, it is just an adaptation of the top-down writing approach we also use when writing scientific papers, for example: You begin with a rough overview and give increasingly more details later in the text.
    But do not omit the details completely!

    #usability #userinterfaces #userinterfacedesign #errormessages #programming #writing #technicalwriting

  35. To the user-interface designers and programmers out there: If the unfortunate event happens and you have to show an error message, please make sure the message is actually helpful for identifying the issue. You might think that hiding technical details is user-friendly, but in fact, the opposite is true. Do not make us guess what is wrong, tell us what you know!

    You might be afraid that this confuses users who are less tech-savvy. Not necessarily, if you give them a rough idea first (maybe in a more emphasized font) and then continue with the details you have (maybe in a smaller font). I am quite sure users are able to ignore the parts they do not understand, and if they need support, at least the person giving support has something to work with.

    Some simple examples:

    ❌ "Cannot connect to bluetooth device."
    ❓ "Okay, but why?"
    ✅ "Cannot connect to bluetooth device 'foo' (maybe it is turned off?): The device does not respond."

    ❌ "Cannot open file."
    ❓ "Which file? And again, why?"
    ✅ "Cannot open file 'testfile.txt' for reading: Permission denied"

    ❌ "Something went wrong when trying to load the website."
    ❓ "Again, what's the problem? Is the network interface down? Is the DNS server down? Is the target server itself down? Give me a hint, please!"
    ✅ "Cannot load the website. Maybe your computer is not connected to the Internet? Details: No route to host (192.168.10.1) when attempting to connect to the DNS server."

    This is nothing new. In fact, it is just an adaptation of the top-down writing approach we also use when writing scientific papers, for example: You begin with a rough overview and give increasingly more details later in the text.
    But do not omit the details completely!

    #usability #userinterfaces #userinterfacedesign #errormessages #programming #writing #technicalwriting

  36. To the user-interface designers and programmers out there: If the unfortunate event happens and you have to show an error message, please make sure the message is actually helpful for identifying the issue. You might think that hiding technical details is user-friendly, but in fact, the opposite is true. Do not make us guess what is wrong, tell us what you know!

    You might be afraid that this confuses users who are less tech-savvy. Not necessarily, if you give them a rough idea first (maybe in a more emphasized font) and then continue with the details you have (maybe in a smaller font). I am quite sure users are able to ignore the parts they do not understand, and if they need support, at least the person giving support has something to work with.

    Some simple examples:

    :X: "Cannot connect to bluetooth device."
    :question: "Okay, but why?"
    :white_check_mark: "Cannot connect to bluetooth device 'foo' (maybe it is turned off?): The device does not respond."

    :X: "Cannot open file."
    :question: "Which file? And again, why?"
    :white_check_mark: "Cannot open file 'testfile.txt' for reading: Permission denied"

    :X: "Something went wrong when trying to load the website."
    :question: "Again, what's the problem? Is the network interface down? Is the DNS server down? Is the target server itself down? Give me a hint, please!"
    :white_check_mark: "Cannot load the website. Maybe your computer is not connected to the Internet? Details: No route to host (192.168.10.1) when attempting to connect to the DNS server."

    This is nothing new. In fact, it is just an adaptation of the top-down writing approach we also use when writing scientific papers, for example: You begin with a rough overview and give increasingly more details later in the text.
    But do not omit the details completely!

    #usability #userinterfaces #userinterfacedesign #errormessages #programming #writing

  37. Oh wow, an "article" that tells us absolutely nothing about large language models except that it's not here! 🧐🔍 Apparently, the only history lesson we're getting is how to generate a 406 error. 🛑💻 Bravo, content gods, bravo! 👏
    gregorygundersen.com/blog/2025 #LargeLanguageModels #ContentCreation #TechHumor #ErrorMessages #HackerNews #HackerNews #ngated

  38. 🐞✨ Wow, congrats to #Ladybird for passing the "Apple 90% threshold" in web tests! 🎉 Too bad no one can see it because #JavaScript is hiding in the corner, sulking like a moody teenager. 🙄 Maybe next they'll solve the mystery of why x.com insists on self-sabotaging with endless error messages. 🤷‍♂️
    twitter.com/awesomekling/statu #WebTests #AppleThreshold #ErrorMessages #HackerNews #ngated

  39. 🚨 STOP THE PRESSES! 🚨 #AI is revolutionizing #accessibility by... generating error messages for the blind? 🤖🙈 Truly, nothing screams "progress" like a server's heartfelt "Not Acceptable." 🍾🎉
    robertkingett.com/posts/6230/ #ErrorMessages #Progress #TechRevolution #BlindCommunity #HackerNews #ngated

  40. Oh, look! The pinnacle of 2016 wisdom: a page that teaches you absolutely nothing about programming or people, but excels in one thing—being consistently "Not Acceptable." 🛑🔒 Apparently, we've discovered the only resource where the server's error message is more insightful than the content itself. 😆
    leftoversalad.com/c/015_progra #NotAcceptable #ProgrammingFails #ErrorMessages #2016Wisdom #HackerNews #HackerNews #ngated

  41. Oh, look! The pinnacle of 2016 wisdom: a page that teaches you absolutely nothing about programming or people, but excels in one thing—being consistently "Not Acceptable." 🛑🔒 Apparently, we've discovered the only resource where the server's error message is more insightful than the content itself. 😆
    leftoversalad.com/c/015_progra #NotAcceptable #ProgrammingFails #ErrorMessages #2016Wisdom #HackerNews #HackerNews #ngated