Tags: weather, youtube
Related to a discussion about winter weather and road conditions, I searched up a post in this blog a few years back. Embedded in the post is a YouTube video about slippery road conditions in Seattle. The video shows cars bumping into each other as drivers in Seattle are not accustomed to snow and ice on the streets and accordingly have no idea of the appropriate usage of winter tires.
As I tried to watch the video I was encountered with this screen, much to my amazement:
Come on, YouTube! Consequences of human behaviour are often harmful and driving on an icy street without proper tires can certainly have harmful effects but I am buffed to learn that YouTube has a policy of banning coverage of real life situations as they may occur. They obviously have a lot of censoring to be done to turn 100 % of the content into harmless fairy tale with no connection to real life.
Oh, and while I am at it, how harmful is the activity depicted in this clip, so far unbanned and watched by more than 100.000 times? I am adding a screan capture just in case the clip gets removed.
As Google announced yesterday they are no longer going to censor their search results at Google.cn. I can now present evidence that they are worth their word, regardless what the real reason behind their decision was and regardless that I still have trouble understanding that they agreed to censor the results in the first place:
A moment ago I was rated A +. Just so you know whose blog you are reading.
Say what! Rated? Here is the explanation:
Not serious at all. 🙂
Get your’s here.
Tags: pirate bay
The torrent bulletin board Pirate Bay was closed yesterday by a Swedish court injunction targeted against their ISP. And now, about 24 hours later the site is up and running again as if nothing had happened, displaying this cool t-shirt logo:
I am impressed by the speed of it. Just as I am impressed how Peter Sunde just casually broke the news in Twitter: “Oh, did i forget? TPB is up again.”
Welcome back, TPB!
Is Twitter being attacked again?
Tags: security, twitter
I appriciate that Twitter is concerned of my security but this is a bit too much of the good stuff. Locking me out of my account does not help me at all, neither does it prevent any unauthorised usage of my account. On the contrary, it makes things worse because as long as I have no access to my account, I am unable to make sure that nobody else has that access.
What happened was that I temporarily granted access to my account to a third party application. As soon as that app had done what it was supposed to, I cancelled the access and changed my Twitter password, just to be on the safe side. What I failed to observe was that when I changed my password in the web interface I had TweetDeck running all the time and I did not come to think that I needed to change the password there as well. Hence, TweetDeck kept trying to access my account using the old password and naturally failed.
Twitter apparently took this as an unauthorized attempt to crack my account. But rather than letting me update the password in TweetDeck they chose to lock me out in both TweetDeck and web interface. Security is fine but I wonder what the point in this action might be and how exactly is it going to increase my security.
Edit: Looks like I have my access back. I still honestly do not understand why it was necessary to keep me out for a couple of hours.
It is not the first time I receive this crazy error message when trying to enter a comment to a Facebook status update.
Now, if I am indeed offline as Facebook seems to be thinking, then what is the point in showing me this mesage? If I were offline I would obviously not see it.