• trollercoaster@feddit.de
    link
    fedilink
    arrow-up
    11
    ·
    edit-2
    10 months ago

    IMO error messages should be as short and precise as possible (the typical user doesn’t read past the word “error” before phoning support), with the option of not having them translated (this makes researching a particular error message online much easier). Please leave out “contact so-and-so” crap, because it leads to people excessively contacting that particular person for shit they could easily fix by themselves.

    • kubica@kbin.social
      link
      fedilink
      arrow-up
      13
      ·
      10 months ago

      I’m disgusted with some people’s reaction to alert messages. They have a close reflex, they don’t even know what they closed. Sometimes I’m trying to help someone and a message appears, while I’m trying to focus my sight they have already closed the message.

      • trollercoaster@feddit.de
        link
        fedilink
        arrow-up
        8
        ·
        10 months ago

        Yes, they close the message and then they call support. And then they get furious if nobody can help them without seeing the error message.

  • Kissaki
    link
    fedilink
    English
    arrow-up
    8
    ·
    10 months ago

    As long as it’s not “oops, something went wrong”

    I hate “oops”.

  • kryllic
    link
    fedilink
    arrow-up
    3
    ·
    edit-2
    10 months ago

    {Friendly error message sentence}

    {Appropriate code for developer debugging}

    [Take a Screenshot Button]

    In a perfect world, anyway

    • SatyrSack@lemmy.one
      link
      fedilink
      arrow-up
      5
      ·
      10 months ago

      Next to the screenshot button, a “copy error to clipboard” button that copies all the relevant info for a user to post in a bug report.