Jul 052014
 

Varig oppholdsbevis
After being in Norway for 16+ years, I finally have a permanent residence permit (or varig oppholdsbevis as it’s called in proper Norwegian)!
Now I can stay as long as I want, without having to renew my permit every 5 years. :cool:

(If you’re also an EU resident, and have been in Norway for 5+ years, check whether you qualify as well!)

Jul 042014
 

Posten Sporing app - screenshot
I just came across an interesting feature in the Posten Sporing app of Posten Norge AS.
This app does the following (translated from the product description on Google Play):

Record tracking makes it easy to monitor packages on their way to you with the Post Office.
When you register with your mobile number and email we find automatically packages on the way to you. To achieve this, we rely on that the sender has registered your mobile number or email. We therefore constantly check if there are packages on the way to you and alert you via push when there is a new package. We will notify you when you can get it at the post office or possibly when it will be delivered to your home.

All good and well, of course. It also let’s you enter a package tracking number manually. Handy of course, should you have a package coming your way that didn’t make it into the system automatically.

Posten Sporing - 12345But… here you can also enter some totally random number like… 12345

And then it suddenly gets interesting! I see a long list of packages, none of them mine (see screenshot, which I mutilated a bit on purpose). I can track their whereabouts, and it wouldn’t surprise me if I’d get a hentekode (pickup code) in the app when the package I selected makes it to the post office and is ready for pickup.

I wonder how long it will take before less honest people will start abusing this ‘feature’…

Their website on http://sporing.posten.no/ is even worse. There I can also search by phone number. This makes it very easy for anyone to track exactly where their neighbours, colleagues & family shop, and quite often it also gives a fair idea of what’s been purchased…
Continue reading »

Feb 282014
 

html_status_code_502_azureAzure wasn’t having one of its best days yesterday. The mess started around 07:30 local time, and lasted until almost 16:00. In other words, our sites were down for the full duration of the business day!

The following table contains the ‘explanations’ Microsoft shared with the public during the downtime:

time (UTC)
seriousness
status
06:35AdvisoryAn alert for Web Sites in West Europe is being investigated. It has not been determined if this is customer impacting. More information will be provided as it is known.
08:15AdvisoryWe are experiencing an issue with Web Sites in the West Europe sub-region. A very small number of customers may see intermittent timeouts or slow response when attempting to access sites. We are actively investigating. Further updates will be published to keep you apprised of the situation.
08:15Partial Performance DegradationWe are experiencing an issue with Web Sites in the West Europe sub-region. A very small number of customers may see intermittent timeouts or slow response when attempting to access sites hosted in this sub-region. We are actively investigating. Further updates will be published to keep you apprised of the situation.
09:15Partial Performance DegradationEngineers are actively investigating the issue. A very small number of customers may still see intermittent slowdown or timeouts. Further updates will be published within 2 hours.
11:15Partial Service InterruptionEngineers are currently evaluating repair options. A subset of customers may experience interruption to web sites hosted in West Europe. Further updates will be published within 2 hours.
13:15Partial Service InterruptionEngineers are continuing to evaluate and implement mitigation options. A subset of customers may experience interruption to web sites hosted in West Europe. Further updates will be published within 3 hours.
14:53AdvisoryThe repair steps have been successfully executed and validated. Full Web Sites functionality has been restored in the West Europe sub-region.

  • No mention of the cause. If they’d told us what the problem was we could have made a guesstimate ourselves on the duration of the downtime, and temporarily moved sites elsewhere.
  • No mention of how many sites/customers were affected by this. ‘a subset’ & ‘a very small number’ are as vague as one can get

And if all of this wasn’t bad enough, around 18:00 excrement again came in touch with ventilation devices! And this time both the West Europe & North Europe regions were affected. In other words: all hosting Azure has in Europe.
Again little/no explanations were shared:

time (UTC)
seriousness
status
16:50AdvisoryAn alert for Web Sites in West Europe is being investigated. It has not been determined if this is customer impacting. More information will be provided as it is known.
18:10Partial Performance DegradationSome customers may experience intermittent time out errors or slow response when accessing their web sites. Engineers are actively gathering monitoring and alerting details to troubleshoot Web Sites in the West Europe sub-region. Further updates will be published to keep you apprised of the situation.
19:07Partial Performance DegradationThe repair steps have been successfully executed and validated. Full Web Sites functionality has been restored in the North Europe sub-region.

This one lasted ‘only’ 2 hours. Resolved around 20:00.

This morning I did some Googling and came across even scarier rumours: While repairing whatever caused the downtime yesterday apparently Microsoft has restored old(er) versions of files, without informing the customers involved!
I can not confirm whether or not this actually happened, but fact is that several of our site-indexes were corrupt and needed rebuilding…

At the moment of writing, 24+ hours after the incidents, there is still no explanation whatsoever (believe me, I have Googled!) for what was the cause of this monster outage. And when I don’t know the cause, I wonder… What are the chances this will happen again, and when?

Feb 052014
 

Cyanogenmod logoAre you unable to send SMS text messages after upgrading (to) Cyanogenmod? Here’s something you should check! (This fixed it for me after installing Cyanogenmod 11 on my Nexus 4)
Open the Voice+-app. As it mentions, ‘Voice+ enables all apps to send SMS messages through Google Voice’. Well… this apparently doesn’t work for everyone. So if you have trouble sending SMS via your Messaging app, disable this. After I did that, I was able to send SMS again! :cool:

(Not sure which versions of Cyanogenmod this applies to. Applies perhaps also to other custom roms, or even to stock roms. Probably only for people outside the USA)

Nov 262013
 

GothenburgWell, in a matter of speaking…

I’ve been exercising on a daily basis on my WaterRower since the end of September. First 3 minute intervals, then 4 minute intervals, and since the 15th of November I’ve been doing 5000 meters/day.
All of this slowly begins to add up. If I’d actually been moving, as the crow flies, I would have arrived in Gothenburg (or Göteborg, as the natives prefer to call it) today. Not too shabby, if I do say so myself!

reduction
%d bloggers like this: