As an article sums up in IEEE”s Spectrum Magazine, this past week was a bad one for Twitter and Facebook users. First, on Tuesday, a scripting security hole – that had been located and fixed weeks earlier – was created again by mistake, which left the front door open for hackers to attack the site. The result was many Twitter accounts going crazy automatically retwitting colorful messages when users moused over a link in the tweet.

The official Twitter statement about the incident reads:

Early this morning, a user noticed the security hole and took advantage of it on First, someone created an account that exploited the issue by turning tweets different colors and causing a pop-up box with text to appear when someone hovered over the link in the Tweet. This is why folks are referring to this an ‘onMouseOver‘ flaw — the exploit occurred when someone moused over a link.

This exploit affected and did not impact our mobile web site or our mobile applications. The vast majority of exploits related to this incident fell under the prank or promotional categories. Users may still see strange retweets in their timelines caused by the exploit. However, we are not aware of any issues related to it that would cause harm to computers or their accounts. And, there is no need to change passwords because user account information was not compromised through this exploit.

On Wednesday, problems hit Facebook. According to many sources, “some users” could not access their accounts but I know of people in 4 continents who could not access their profile… Anyhow, Facebook blamed the problem to a third party vendor. A statement made to Mashable said

We are experiencing an issue with a third party networking provider that is causing problems for some people trying to connect to Facebook,” the company told Mashable in a statement. “We are in contact with this provider in order to explore what can be done to resolve the issue. In the meantime, we are working on deploying changes to bypass the affected connections.

Finally, yesterday Facebook experienced a 2.5 hours outage  in what was defined as the worst outage in 4 years. The problem was caused by a change in a Facebook system that checked for verifying configuration values. Facebook released an official statement explaining what happened.

The article at IEEE”s Spectrum Magazine.

I think I might have posted this before, but every time something is wrong with Facebook I remember of this great South Park chapter: