Twitter: Is There A Problem Here?: Twitter

Showing posts with label Twitter. Show all posts

20120307

Problem ID: 6394719955663010196
Entered by: Ben Simo

What's happening, Twitter?

The further I scroll down a Twitter page, the further the header bar drops down the screen.

20110926

Problem ID: 3981715398200164815
Entered by: Ben Simo

The Twitter location selection feature has recently broken. Notice a problem?

Space; and lots of it.

The huge gaps between location options prevent the entire list from displaying on the screen. Plus, given that the option to turn off location sharing is at the bottom of the list, there is no way to disable location sharing.

I've been consistently encountering this issue across multiple browsers with multiple Twitter accounts.

Edit

20100401

Problem ID: 2009353837662950344
Entered by: Anonymous

Stressing out a bit

Jay Philips reports:

Tried doing a Twitter search today and received this error “Twitter is stressing out a bit right now, so this feature is temporarily disabled.”

Ben Simo adds:

Disabling non-essential features during times that system resources are stressed may actually be a good part of a performance management strategy. Of course, it is frustrating to those users wanting to use the disabled features.

Edit

20100116

Problem ID: 3166838339812542576
Entered by: Ben Simo

Twitter is stressing out a bit

@yrodr006: Trying to change my profile pic and got this error message. lol

Disabling non-essential features during times of excessive usage can be a good way to manage performance.

Edit

20100102

Problem ID: 5388726962921106776
Entered by: Ben Simo

Twitter links disappear on mouseover

I can't click links that disappear when I move the mouse pointer over them.

Edit

20091230

Problem ID: 6956567289779743540
Entered by: Ben Simo

WhatâЄ™s happening?

“Twitter fail?” - @miker1993

Edit

20091228

Problem ID: 3029821834473433976
Entered by: Ben Simo

Bit.ly to FeedBurner

I had been using Bit.ly, a URL-shortening service, to shorten links to this blog tweeted on Twitter. It worked fine for me and I assumed it was working for others until Amit Kulkarni (@mumbaitesting) contacted me (@QualityFrog):

"IsThereAProblemHere? Pop-under menus?: Not only does this newspaper web site page have no real content, but the me... http://bit.ly/4oowSH" - @QualityFrog

"@QualityFrog If I try to access the tiny URL in your tweets, the 1st time I get Feedburner Err and 2nd time it works. hapnd 2nd time." - @mumbaitesting

"@mumbaitesting Interesting. The bit.ly URLs in tweets via TwitterFeed when scheduled blog posts get published? Or some other URL?" - @QualityFrog

“@QualityFrog This might help you:” - @mumbaitesting

"@mumbaitesting Interesting. Does it happen the 1st time you click each of those bit.ly links? Feedburner should redirect to the blog." - @QualityFrog

"@QualityFrog Thats what the pattern I've observed until now...waiting for another such URL from you, to confirm." - @mumbaitesting

Sure enough, Amit encountered the same problem with later Bit.ly URLs. So I changed to another URL-shortening service. I haven't yet confirmed that the problem is the combination is Bit.ly and Feedburner.

However, I do see reports by others encountering the same problem with Bit.ly links to FeedBurner. Here's one example:

"#iPhone iTablet Rumor Updates — Hardened 10″ Panels, and iSlate Nostalgia for MessageSlate: So... http://bit.ly/7DVYDW @theiphoneblog" - @AllThingsiPhone

“@AllThingsiPhone feedburner error on last tweet..” - @tebailey

Edit

20090318

Problem ID: 2577280056992948579
Entered by: Ben Simo

Actually, I'm not logged in

Authentication successful? You are now logged in?

In fact, I am not logged in.

The technical call stack info likely makes sense to the developers that coded this. However, is it helpful to scare users with the words "Fatal error" and a call stack dump?

Edit

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

20090217

Problem ID: 8333992797528899465
Entered by: Pradeep Soundararajan

Twittering thing about Twitter

The questions that I ask are:

Is -119860 more than 140?
Is there a problem here?
Should the user be allowed to type so much?
If yes, could the information be conveyed in a way that might appear to be better than this one?
What would you suggest to be displayed in the error message?

Edit

Usability Heuristics

• 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

-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

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

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?

20120307

What's happening, Twitter?

20110926

Space, White

20100401

Stressing out a bit

20100116

Twitter is stressing out a bit

20100102

Twitter links disappear on mouseover

20091230

WhatâЄ™s happening?

20091228

Bit.ly to FeedBurner

20090318

Actually, I'm not logged in

20090303

What is technically wrong? What did I notice?

20090217

Twittering thing about Twitter

Problem or no problem?

Usability Heuristics

Consistency Heuristics

FAILURE Heuristics

Security Vulnerabilities

Popular

Recent Problems

Recent Comments