Arkisto: April 2014



Gays Stormed Post’s Webshop

25. Aprilta, 2014 | Kirjoittaja: Antti Niittyviita

We have frequently highlighted ‘surprises’ that Internet service failures. All of them have the same old story: The popularity of the Internet service came as a surprise, even though according to the hype and pre-release publicity it should not have happened.

This week’s ‘winter took drivers by surprise’ award goes to Finnish Post office Itella, whose advance booking of Tom of Finland – themed stamps overcame the expectations. This resulted, naturally, in the webshop crashing.

According to Itella’s information liaison Merja Suomalainen, the webshop crash was caused by too many users.

‘We had more visitors than expected. It got us a little bit by surprise’, Suomalainen says.

Hopefully there weren’t systems that handled post delivery, on the same servers as the online store.

That should not genuinely take them by surprise. Media has been talking for over two weeks about the stamps. Hakkarainen (PS) and Niikko (PS) , members of Finnish parliament, partook by sending a written question to the government, demanding the stamps to be pulled.

Since seldom do we have the opportunity to use Tom of Finland’s art in any form in a relevant context, we do so now. This is one of the three stamps that caused the buyers to go wild:

When members of the parliament demand your product to be pulled from the market by taking official measures, you can be sure that your product has demand. Ensure that your technology does not become a hindrance.

Easter Traffic Takes No One By Surprise.

8. Aprilta, 2014 | Kirjoittaja: Antti Niittyviita

Easter is next week. Outgoing traffic is at a high the entire Thursday. I can already say what the radio will be chanting. The traffic is very jammed around the capital region and between the roads connecting Lahti, Heinola, Tampere and Jyväskylä. It comes as no wonder that roads get packed full of cars when hundreds of thousands of people start their holidays at the same time.

On the other hand, I cannot help but be surprised by Internet-based service providers whining about ‘unexpected’ traffic.

In the States:

Unexpected traffic resulted in HBO Go-service crashing, keeping the service out of commission for several hours.

And in Finland:

As a second, and more likely, explanation for Ruutu.fi’s problems has been said to be HK’s code campaign, which would have resulted in a massive traffic spike in the service.

I wonder, were the playoffs even seen by the subscribers who paid nearly thirty euro a month?

Ensure that the technology works before starting the marketing procedures. A good idea might function as expected. An excellent campaign might end up a nightmare.

EDIT: According to Iltalehti, the service crash was caused by a denial of service attack, which targeted ruutu.fi’s service provider, UpCloud.

Clock Towards the Summer

2. Aprilta, 2014 | Kirjoittaja: Antti Niittyviita
Comments: 1

On Sunday morning I woke up at a usual time. Or actually, I did not. The time was one hour more than it was the day before at the same time. According to a rule of thumb I have learned, you adjust clocks always towards the summer. In the spring forwards and during the autumn backwards. Towards the summer, it is.

I opened WhatsApp first thing in the morning and the flood of complaints in the group chat was quite reassuring. My good friend Mark (name changed) complained along the lines:

So, what the f*ck is the brain damage that resulted in meeting times changing when daylight savings time comes over? I mean, really! Where would one even need such a ‘feature’ for?

That complaint was not the only one. It was the same song evenly from the Android, iOS and Windows Phone –users. The problems did not visit everyone, but the loudest ones were the ones whose calendars had got messed up. The origin of the problem is still unknown, but it seems to be linked to calendar server’s and the phone’s co-operative functions.

Phone developer passes the blame over to the server’s developer.

The server’s developer passes the blame over to the phone’s developer.

In road traffic, one can easily find oneself blaming the car in front of you for bad driving. It is, after all, his car right in front of your very eyes. For traffic jams, the original fault for is usually further away, at the distance of a few cars ahead. It is a rare driver that thinks so far. The same rings true for the world of software development.

End users usually blame the problematic part for the entire problem. Passing over the blame at the developer’s side is for naught. The one who takes care of the repairs is the one who paying customer would primarily point at.