What is technically wrong? What did I notice?: Is There A Problem Here?: What is technically wrong? What did I notice?

20090303

Problem ID: 6653399307735245140
Entered by: Pradeep Soundararajan

What is technically wrong? What did I notice?

I don't think I noticed anything but what you see in the following screenshot.

What is technically wrong?

If they aren't aware of what is wrong how would they know is it technical or non technical?

What are the non technical things that could go wrong?

Do you also notice that sentence that has information thanking me for noticing the problem, itself is hardly noticeable? I mean what you can or cannot read below the "Something is technically wrong".

Edit

6 Comments:

Comment ID: 5915880519149691116 Written by: Ben Simo: I like the Twitter error messages. They don't contain lots of useless (to me) technical details.

Twitter's error screens are great examples of how humor and cute images can be used to quell user frustration when things go wrong.

Ideally, I'd like to see Twitter take care of the errors on the back end and not show me any error messages. IMO, these cute images are the next best thing.
Comment ID: 230603032937000197 Written by: Anonymous: I would have to agree with Ben.

The Twitter error pages, even the whale one is much better than the standard error pages you see on other sites.
Comment ID: 2548822038458031273 Written by: Michael Bolton http://www.developsense.com: I like the whimsy, but I think the message could be much more informative. What went wrong? When are you going to fix it? Am I at risk? What about my data?

---Michael B.
Comment ID: 2170905746933354284 Written by: Anonymous: Ben, I'm sorry, saying "Ideally, I'd like to see Twitter take care of the errors on the back end and not show me any error messages" is the same as saying that you'd like Twitter to be the one perfect Web app. The user made a request and the Twitter server went kaboom. You'll either get a blank page, a useless server error message or a Twitter sorry-for-that-it-could-be-worse message. There are not much more options. Unless I'm missing something.
Comment ID: 5497484904332038591 Written by: Ben Simo: I'm not expecting Twitter, or any other app, to be perfect. However, in my experience, there is often more that could have been done to handle errors without involving the user.

I don't know what led to the error message above, so I don't know if this is a case that might have been handled better.

If the Twitter app were constructed to do so, it could possibly retry requests without involving the user. Maybe Twitter does.
Comment ID: 6638341919340338784 Written by: Pradeep Soundararajan: Let me explain what lead to above. I noticed that a new person had been following me. I went to that person's profile and then wanted to return to my own profile.

Boom! I got the above.

Usability Heuristics

from Jakob Nielsen

• Visibility of system status Visibility of system status: The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.
• Match between system and the real world Match between system and the real world: The system should speak the users' language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order.
• User control and freedom User control and freedom: Users often choose system functions by mistake and will need a clearly marked "emergency exit" to leave the unwanted state without having to go through an extended dialogue. Support undo and redo.
• Consistency and standards Consistency and standards: Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.
• Error prevention Error prevention: Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action.
• Recognition rather than recall Recognition rather than recall: Minimize the user's memory load by making objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to another. Instructions for use of the system should be visible or easily retrievable whenever appropriate.
• Flexibility and efficiency of use Flexibility and efficiency of use: Accelerators -- unseen by the novice user -- may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.
• Aesthetic and minimalist design Aesthetic and minimalist design: Dialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.
• Help users recognize, diagnose, and recover from errors Help users recognize, diagnose, and recover from errors: Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.
• Help and documentation Help and documentation: Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user's task, list concrete steps to be carried out, and not be too large.

Consistency Heuristics

from James Bach
and Michael Bolton

-F amiliar Familiar: The product is not consistent with the pattern of any familiar problem.
E xplainable Explainable: The product is explainable.
W orld World: The product is consistent with the real world.
H istory History: The present version of the product is consistent with past versions of it.
I mage Image: The product is consistent with an image that the organization wants to project.
C omparable Products Comparable Products: The product is consistent with comparable systems.
C laims Claims: The product is consistent with what important people say it’s supposed to be.
U ser Expectations User Expectations: The product is consistent with what users want.
P roduct Product: Each element of the product is consistent with comparable elements in the same system.
P urpose Purpose: The product is consistent with its purposes, both explicit and implicit.
S tatutes Statutes: The product is consistent with applicable laws.

FAILURE Heuristics

from Ben Simo

F unctional Functional: The error detecting, reporting, and handling functions properly.
A ppropriate Appropriate: Errors are reported at the appropriate time in an appropriate manner.
I mpact Impact: The impact of the failure is communicated to those impacted.
L og Log: The error is appropriately logged; or not logged.
U ser Interface User Interface: The error is reported in the user interface in terms that the user understands.
R ecovery Recovery: The user is informed of what they need to do to recover from the error.
E motions Emotions: The error handling and reporting has a positive influence on user emotions.

Security Vulnerabilities

the OWASP Top 10

1. Injection Injection: Injection flaws occur when untrusted data is sent to an interpreter as part of a command. The attacker’s hostile data can trick the interpreter into executing unintended commands or accessing data without authorization.
2. Broken authentication and session management Broken authentication and session management: Application functions related to authentication and session management are often not implemented correctly, allowing attackers to compromise passwords, keys, or session tokens, or to exploit other implementation flaws to assume other users’ identities.
3. Cross-Site Scripting Cross-Site Scripting (XSS): XSS flaws occur whenever an application takes untrusted data and sends it to a web browser without proper validation or escaping. XSS allows attackers to execute scripts in the victim’s browser which can hijack user sessions, deface web sites, or redirect the user to malicious sites.
4. Insecure Direct Object References Insecure Direct Object References: A direct object reference occurs when a developer exposes a reference to an internal implementation object, such as a file, directory, or database key. Without an access control check or other protection, attackers can manipulate these references to gain unauthorized access to data.
5. Security Misconfiguration Security Misconfiguration: Good security requires having a secure configuration defined and deployed for the application, frameworks, application server, web server, database server, and platform. Secure settings should be defined, implemented, and maintained, as defaults are often insecure. Additionally, software should be kept up to date.
6. Sensitive Data Exposure Sensitive Data Exposure: Many web applications do not properly protect sensitive data, such as credit cards, tax IDs, and authentication credentials. Attackers may steal or modify such weakly protected data to conduct credit card fraud, identity theft, or other crimes. Sensitive data deserves extra protection such as encryption at rest or in transit, as well as special precautions when exchanged with the browser.
7. Missing Function Level Access Control Missing Function Level Access Control: Most web applications verify function level access rights before making that functionality visible in the UI. However, applications need to perform the same access control checks on the server when each function is accessed. If requests are not verified, attackers will be able to forge requests in order to access functionality without proper authorization.
8. Cross-Site Request Forgery Cross-Site Request Forgery (CSRF): A CSRF attack forces a logged-on victim’s browser to send a forged HTTP request, including the victim’s session cookie and any other automatically included authentication information, to a vulnerable web application. This allows the attacker to force the victim’s browser to generate requests the vulnerable application thinks are legitimate requests from the victim.
9. Using Components with Known Vulnerabilities Using Components with Known Vulnerabilities: Running software components with known vulnerabilities can compromise the vulnerable components and anything those components can access -- undermining defenses.
10. Unvalidated Redirects and Forwards Unvalidated Redirects and Forwards: Using untrusted data, without validation, to determine the destination of redirects and forwards can enable attackers to redirect victims to phisihing or malware sites.

Is There A Problem Here?

20090303

What is technically wrong? What did I notice?

6 Comments:

Post a Comment

Problem or no problem?

Usability Heuristics

Consistency Heuristics

FAILURE Heuristics

Security Vulnerabilities

Popular

Recent Problems

Recent Comments