Random thoughts

Spoilt by the improvements in running in the first two years, I had to drop down a gear this year. After finishing the first few races in 2015, including two marathons and two halfs, and accumulating 1000 km running by year end, the following year was even better. The improvements over all distances brought me recognition and a nice collection of cups by the Running@IBM club.


This year was off to a slow start. Suffering from colds for several months, running was out of question. I reluctantly skipped a long-distance event only after luring a colleague to consider the event, and haven't been training much until recently.

With only two long jogs in the last quarter, going for the marathon distance seemed unreasonable, and I postponed the decision to the racing day. After a good first half I decided to go for the full distance anyway. The lack of training did show in the second half when I hit the wall around km 30 but eventually finished, slower than in previous years with 04:55:13 h.



Still an enjoyable run, happy that I made it through!

Labels: personal, running

When I started running some 15 months ago, my goal was to relax and live healthier.  If you know me, I haven’t been much of a runner before, aside from occasional runs through the Wiener Prater or along the beach a few times per year.




Today I completed my 1000th kilometer this year. I have run two full marathons and two halfs, competed in a trail run and some shorter races and finished ninth place in the local Running@IBM cup.

Why I started running

Like most nerds spending long hours in front of their computers, I had been sitting in my office chair for long hours, seeing my health parameters getting worse at every annual checkup, not to alarming levels but still, constantly gaining weight, and getting recommendations from my doctor to eat less and exercise more … and found tons of excuses why I had other things to do first and could never find the time.

Over the years I have admired sporty family members, friends and co-workers, including an Olympic walker, marathoners, ultra-runners and triathletes, and have drawn inspiration from their determination and their successes. But it was a newspaper ad from an insurance company that literally flipped the switch, a lonesome runner in the middle of the night explaining that some folks call him “Daddy” and he’d like to keep it that way for long.

Starting slow

And so I got my old sports shoes out and started running. Took the stairs instead of the elevator. Made an effort to eat healthier and intermittently switched to alternate day fasting (“weekday 10-in-2”).  Joined the Running@IBM club and made new friends there. Downloaded training plans and (here comes the nerdy part) wrote some scripts to ease importing them into my calendar. Bought a book on long-distance running.

The beginning was hard. I barely managed short distances non-stop. Soon I started seeing improvements, and in October last year I boldly decided to go for the full marathon distance in April and as an extra motivation join the #Run4CARE charity campaign. The initial response when I started telling people about my plans later on was usually along the lines of “You? Seriously?!”, usually followed by encouragement and support.

The first marathon

During winter I mostly followed my training plans, regardless of weather conditions. Facebook somewhat made up for the lack of a training buddy (finding someone nearby for midnight and early morning runs wouldn’t work out), the Likes and comments helped me staying on track. When I eventually finished the Wien Energie half marathon in March, I felt a great sense of accomplishment and pride, and even more so in April after doing the full distance at the Vienna City Marathon.

What was meant to be a once-in-a lifetime experience has turned into a bit of an addiction. I was hooked and just have to keep on running.

Happy New Year everyone, and Happy Running!

Labels: personal, running

Yes, I did it! Today I finished my first marathon race, the Vienna City Marathon 2015

More than 9,000 runners completed the marathon, of 42,742 athletes overall who participated in five disciplines.

We had a beautiful day, with sunshine in the morning and some light clouds and wind in the afternoon, and the volunteers, the co-runners and the spectators made  this a friendly and enjoyable event.

One of my favorite signs, displayed by a supporter towards the end of the track, read: “Going back now would be a bad idea.” So we kept running.

My finishing time was 04:54:15.

I dedicate my first marathon to my dad, an experienced long distance runner who ran the Vienna City Marathon before, in just over three hours.

Thank you everyone for your encouragement, support and advise, and also for the generous donations for the #Run4CARE charity run.

PS. One small suggestion for the organizers: Waste bins after the supply stations would be great to keep the track at least somewhat cleaner. Running on layers of crunching plastic cups and through seas of Powerade is no fun.

Labels: personal, running

Today I finished my first race ever, the Wien Energie half marathon 2015, in 2:06:26.

Weather conditions were fine, with 7°C, modest winds and no rain, and I had a nice run at almost constant speed throughout the race. I even ran right next to the unbeatable Lemawork Ketema, if only for a split second, as he was passing the field to start his third round. Thanks to the organizers, support staff, cheerleaders, drummers and spectators for making this a great event!

Now that I have completed the half marathon distance, I have even more respect for the challenge ahead of me.

Next month I will #Run4CARE at the Vienna City Marathon and raise funds for charity. CARE is a leading humanitarian organization fighting global poverty, providing disaster relief and supporting sustainable development projects.

Please help my quest and support the “Packages for Children in Need” campaign. Thank you kindly!

Labels: personal, running

40,000 runners from around the world will participate in the Vienna City Marathon under the theme “We are Europe” on 12 April 2015. I plan to be one of them and have signed up for the challenge.

I have three goals for the Vienna City Marathon 2015:

1. Running the full marathon distance and finishing the race in reasonable time.
   This will be my first marathon. In fact, unless I find a good practice race, it will be my first running competition ever. Running the marathon should be doable still. I have run half-marathon distances just for kicks without much training. Finishing the race in reasonable time will be tougher. A friend of mine was joking that she walked faster than I ran. I will do my best but expect no miracles, anything before the cut-off time counts!
   
   
2. Raising funds for “CARE – Packages for Children in Need”.
   CARE is the charity of my choice for the Vienna City Marathon 2015. Whether you want to help a good cause or just motivate me to complete my first marathon, please donate now to keep those packages coming:
   
   
   Donate now  Jetzt spenden
   
   Raising funds for CARE and supporting children in need is an extra motivation to finish, if not an obligation to the charity team and to you, my dear friends, whom I trust to generously contribute to the #Run4CARE charity run.
   
   All donations will go directly to CARE in support of the “Packages for Children in Need” campaign. CARE is a leading humanitarian organization fighting global poverty, providing disaster relief and supporting sustainable development projects. When crises or natural disasters force families to flee their homes, CARE is on site and provides emergency relief.
   
   
3. Encouraging others to join in.
   Lastly, I hope that others will join in, too. Running is an excellent way to improve physical fitness and also to refresh your mind. There is nothing like an early morning round in the park to start the day. I can do this, and so can you!

Related information

• Vienna City Marathon 2015 http://www.vienna-marathon.com/
• CARE Österreich http://www.care.at/
• CARE International http://www.care-international.org/

CARE Österreich has been awarded the OSGS quality seal for charities. Donations can be made by credit card and bank transfer.

Update: The Wien Energie half marathon mid March turns out to be a good test race, so I will run there first before I attempt a full marathon next month.

Labels: personal, running

Nikon cameras have suffered from various battery related issues, caused by problems with the lens mount or firmware bugs.

Recently my Nikon D300S, which had been a reliable companion and worked well under adverse conditions, started showing the dead battery syndrome quite frequently, and of course at the most inopportune times while shooting events. Cleaning the lens mount, replacing the battery and applying the long overdue firmware upgrade showed no noticeable improvement.

The problem seems to be with the battery compartment door. With frequent battery replacements, the door wears out and no longer applies enough pressure on the battery to ensure reliable contact. Fortunately there is a simple fix, and it doesn't cost more than 1 c (and a drop of glue).


Disclaimer: The Euro cent had the perfect thickness for my camera. Depending on wear and tear of your camera, alternate spacers such as a cardboard stripe may be more suitable.

Labels: photography

 

Labels: ibm, personal

Some twenty developers and security experts gathered at the Stockwork Coworking Space for today´s joint Vienna DevOps & Security and System Architects Group meetup http://meetu.ps/2v2DGg.

Best practices for AWS Security

Philipp Krenn (@xeraa) nicely explained the fundamental risks of AWS services:
Starting services on AWS is easy. So is stopping.

Recent incidents show that a compromised infrastructure can cause more than short disruptions. Several companies went out of business when not only their online services but also data stores and backups were gone:

• Code Spaces goes dark after AWS cloud security hack
• DrawQuest permanently shuts down after security breach
• Bonsai.io suffers from an AWS security incident

(Some) recommendation for using AWS services:

• Lock away the root account. Never use this account for service or action authentication, ever.
• Create an IAM user with a password policy for every service or action to limit damage in case an API key gets compromised.
• Use groups to manage permissions.
• Use two-factor authentication (2FA) using Google Authenticator.
• Never commit your credentials to a source code repository.
• Enable IP restrictions to limit who can manage your services even with an API key.
• Enable Cloudtrail to trace which user triggered an event using which API key.

Other cloud security providers may offer different security features

The (fancy!) slides are available here: https://speakerdeck.com/xeraa/i-am-what-iam-for-devops-vienna

ISO 27001 - Goals of ISO 27001, relation to similar standards, implementation scenarios

Roman Kellner, Chief Happiness Officer :-) at @xtradesoft, gave an overview of the ISO 27001 and related standards:

• ISO 27001:2013 Information Security Management System (ISMS) Requirements
• ISO 27002:2013 Code of Practice
• ISO 31000 Risk Management

Information security management is not limited to computer security; it is equally relevant for paper documents, human knowledge, etc.

The structure of ISO 27001 looks somewhat similar to ISO 9001 Quality Assurance, including the monitoring and continuous improvement loop of Plan-Do-Check-Act (PDCA).

For a successful implementation and certification, the ISO 27001 efforts must be supported and driven by the company leadership

The third talk about Splunk unfortunately had to be postponed.

Labels: cloud, events, itarchitecture, security, technology

JPEG images downloaded from a digital camera often contain thumbnails in the EXIF metadata, which Windows 7 appears to use for the thumbnails shown in folders.

Unfortunately not every image editor also updates the thumbnails. As a result, changes to images are only visible on the full image, not on the thumbnail preview.


That's where the marvelous ExifTool library and command-line application by Phil Harvey come into play. This one-liner removes the thumbnail image and related size information, and sets the file modification timestamp to the capture timestamp:

exiftool -if "$exif:IFD1:XResolution" "-filemodifydate<datetimeoriginal" -ext jpg -IFD1:all= %*

Combined with Matt Ginzton's CmdUtils, the full batch script for Windows removes image backup copies before and after processing:

@echo off
if exist *.JPG_original recycle -f *.JPG_original
exiftool -if "$exif:IFD1:XResolution" "-filemodifydate<datetimeoriginal" -ext jpg -IFD1:all= %*
if exist *.JPG_original recycle -f *.JPG_original

Labels: photography

Thirty years ago, on July 2, 1984, I started my first summer job in the accounting department of Gebrüder Ulmer, a hardware retailer and wholesale firm.

The little I remember from those days are fixed working hours from 8–12 and 14–18, with sufficient time for a lunch break at home, handwritten memos, a plethora of documents arriving every few hours that needed to be stamped, sorted, numbered, processed and forwarded to the next department or stored in the archive, and the mix of historic and then-modern business machines.

My responsibilities were mostly sorting and archiving documents, and typing letters on an ancient mechanical Underwood typewriter.
The most advanced device was “the accounting machine”, most likely a Philips P354 Visible Records Computer or similar. Accounting information was stored on large Magnetic Ledger Cards, with transactions getting recorded on a magnetic stripe as well as printed on the card, so one could easily access the information without a computer. Transactions were recorded on individual customer and supplier account cards, and the totals got transferred to the general ledger cards automatically at the end.

The accounting system was eventually re-implemented on an IBM System/36 minicomputer, and later ported to the IBM AS/400. As a teenager who proudly owned a Commodore 64, these big irons were quite impressive and a motivation to know more about business computing, data modelling and programming languages. (I still have a copy of the COBOL 78 manual, just in case.)

In the thirty years since my first summer job, there have been tremendous changes. No longer do most of us work fixed working hours, rarely do we exchange handwritten memos, and data processing usually means instantaneously and electronically, not in paper batches.

I am grateful for what I learned during my first summer job and during my professional career since, and looking forward to the next big shifts ahead.


Photo courtesy of The Centre for Computing History - Computer Museum, http://www.computinghistory.org.uk/det/505/philips-p354-visible-records-computer/

Labels: personal, technology

When the World Wide Web was created 25 years ago few people probably realized how much change this would bring, not only to the academic community where this started but to the world at large.

Twenty years ago, IBM published the first homepage on www.ibm.com. The initial site on May 24, 1994 had only a few pages of content and an audio greeting by then-CEO and Chairman Lou Gerstner. (That was the time when most homepages greeted visitors with “Welcome to the Internet”.) Among the things Gerstner said, in retrospective the most important statement was “We are committed to the Internet, and we are excited about providing information to the Internet community”.

Back then I was happily coding System/370 mainframe applications and just had my first encounter with the now defunct Trojan Room Coffee Machine at the University of Cambridge. SNA and Token Ring were our preferred network technologies, and access to the Internet required special permission and signing an NSFnet Acceptable Use Policy document outlining the rules for commercial activities on international networks. Soon much of our business would become e-business.

Only a few years later was I invited to join the www.ibm.com team, a very fine, special team. At a time when business was mainly local, we were already globally integrated, collaborating electronically through an internal IRC network (Alister, remember our daily "gma, hay?" routine) and eventually the predecessor of IBM Sametime.

Last week the creators of the first homepage and some who worked in Corporate Internet Programs in the early days came together in New York City for an unofficial “motherserver meeting” to celebrate the anniversary. I missed the party, but the pictures brought back memories of the good times (and yes, occasionally bad times) we had running the IBM Website.

Happy Birthday, www.ibm.com!

Labels: ibm, technology

This month’s ViennaJS meetup brought together a bunch of awesome people with awesome talks at the new location Sektor 5:

• Veganizer: Having fun with image manipulation using canvas and vegetables (including a commercial for filepicker.io) https://github.com/franzenzenhofer/veganizer by @enzenhofer
• Enterprise Software Development for JavaScript refugees – Scala.JS (and not EJBJS 2.0, LOL) @rafacm @sebnozzi
• Responsiveview: http://rv.k94n.com/ https://github.com/k9ordon/responsiveview.
  Other tools at http://responsinator.com/ http://lab.maltewassermann.com/viewport-resizer @thisisgordon
• Web components: Cool talk by @nikgraf about HTML imports and more. http://www.x-tags.org/ can be used to enable Web components in current browsers already

Twitter hashtag: #viennajs

Labels: javascript, technology, webdevelopment

IT security is not just about computers and smartphones any more. Your smart TV may be allow attackers to get access to sensitive information and control the device, as security start-up ReVuln demonstrates for Samsung's Smart TV.

Once simple stand-alone receivers, TV sets, set top boxes and digital recorders are full featured computers and connect to home networks for downloading program guides and software updates, sharing pictures and videos and enabling social media integration.

Read more about recently discovered security flaws in home entertainment equipment on The Register.

Labels: security, technology

One year has passed since I left Phnom Penh after my IBM Corporate Service Corps assignment in Cambodia had ended.

In the following months, I wrote articles about the CSC experience for our local employee magazine and for our corporate social responsibility site. A professional writer covered the story for the THINK! Magazin. Our company internal Global Web Services newsletter featured another article. This one happened to find its way to my client HRINC, where it got published on their company website as well.

In February, another #ibmcsc team visited Cambodia and worked with a different group of clients, mostly educational institutions. During their preparation I had the pleasure to share some of our team’s experiences, including recommendations for sight-seeing, dining and entertainment.

Writing and talking with colleagues, friends and family about the trip always brings back fond memories of the great time spent in Cambodia with the “Tissabamokah” team, our hosts and the various people we met during our stay.

I occasionally hear from my friends at HRINC about life and work, and follow the updates from the Cambodia Retirement Village (CRV) project.

The IBM team has stayed in loose contact also. We didn’t manage to arrange our first annual reunion that we had talked about before we left, and we never completed our team video. Somewhere that raw footage is waiting to be edited and cut, maybe for another anniversary.

If you ever have an opportunity to spend some time on a voluntary assignment, whether as a company sponsored activity or with a volunteer organization like Australian Business Volunteers (ABV), go for it, and if you don’t, try harder to find one.

Looking back a year later, I wouldn’t say that one month abroad made me a completely different person, but I certainly learned a few things about myself too. What made the most lasting impression on me was the Khmer people’s positive and cheerful attitude, which I admire and often miss.

Related links:

• IBM Corporate Service Corps
• CSC Cambodia 1 team blog
• Blog posts tagged with #cambodia

Labels: cambodia, ibmcsc, travel

Starting new job today, and I am excited about it!

Some fifteen years (or seventy web years) ago I started working on the IBM Web presence as webmaster in Corporate Internet Programs and Enterprise Web Management. During that time, and later as Web effectiveness manager in IBM Inside Sales, I had the pleasure to work with many great people around the world. I learned a lot about business and technology. I had the opportunity to travel to various places and attend and speak at international conferences. It's been a lot of fun and a great learning experience, and I look back fondly on the many things we achieved together.

Now the time has come to move on. Effective immediately, I am joining the IBM Global Business Services organization in Austria, leading the Enterprise Architecture team in Application Innovation Services.

I am very much looking forward to this new opportunity in a different area of the business, in a more technical capacity, working with local customers, and I am honored to join an amazingly skilled and experienced team.

Have you ever wondered how much of your carefully designed Web page is actually visible to the people coming to your site?

Then take a look at Google Browser Size, an amazingly simple and effective tool for Web designers to see what percentage of users sees which content, like this:


Of course we all know to place important content towards the top, above the fold, we have seen the heatmaps from eye tracking studies, and we all test at different screen sizes, right? Google Browser Size, already launched back in December 2009, just makes the testing easier and brings this home with shocking immediacy (Mike Moran at Biznology).

The visualization is based on browser window sizes of people who visit Google, not on actual browser window sizes used when accessing a particular site. Depending on how closely your audience matches the average Google visitor, results may vary.

One caveat: As mentioned on the Browser Size website, the tool works best on web pages with a fixed layout aligned to the left. The visualization can be misleading for liquid or reactive pages that adjust to the available screen width, we well as centered pages.

Labels: google, seo, usability, webdevelopment

Web companies, big and small, face the same challenges. Our pages must be fast, our infrastructure must scale up (and down) efficiently, and our sites and services must be reliable … without burning out the team.
Velocity Europe conference Website

Three years after its inception in California O’Reilly’s Velocity Web Performance and Operations Conference finally made it to Europe. Some 500 people, web developers, architects, system administrators, hackers, designers, artists, got together at Velocity Europe in Berlin on November 8 and 9 to learn about the latest developments in web performance optimization and managing web infrastructure, exchange ideas and meet vendors in the exhibition hall.

Velocity Europe was well organized and run. There were power strips everywhere and a dedicated wireless network for the participants, although the latter barely handled the load when everyone was hogging for bandwidth. Seeing bytes trickling in slowly at a performance conference was not without irony. Some things never change: Getting connected sometimes requires patience and endurance. Back in the days I was volunteering at the W3C conferences preparation involved running cables and configuring the “Internet access room”, only then contention for network resources meant waiting for an available computer.

As expected for a techie conference, about the only people wearing jackets and ties were the AV operators, food was plentiful and good, and the sponsors handed out T-shirts, caps, and other give-aways. Plenary sessions were recorded and streamed live, and #velocityconf on Twitter also has a good collection of facts and memorable quotes for those who couldn’t attend in person.

Steve Souders and John Allspaw led through two busy days packed with plenary sessions, lighting talks and two parallel tracks on Web performance and Web operations. While bits and bytes certainly mattered to the speakers and the audience, the focus was clearly on improving the Web experience for users and the business aspects of fast and well-managed Web sites.

The conference started with a controversial talk about building a career in Web operations by Theo Schlossnagle, and I couldn’t agree more with many of his observations, from suggesting discipline and patience (and recommending martial arts to develop those virtues), learning from mistakes, developing with operations in mind to seeing security not as a feature but a mentality, a state of mind. Along the same lines, Jon Jenkins later talked about the importance of dev ops velocity, why it’s important to iterate fast, deploy fast, and learn from mistakes quickly, mentioning the OODA loop. Some of the Amazon.com deployment stats are just mind-boggling: 11.6 seconds mean time between deployments, and over 1,000 deployments in a single hour to thousands of hosts.

Joshua Bixby addressed the relationship between faster mobile sites and business KPIs. Details of the tests conducted and the short-term and long-term effects on visitor behaviour are also available in his recent blog post about a controlled performance degradation experiment conducted by Strangeloop. Another interesting observation was the strong preference of customers for the full Web sites over mobile versions and native apps: One retailer in the U. S. found that of the online revenue growth for that company was driven by the full site. 35% of the visitors on their mobile site clicked through to the full site immediately, 24% left on page 1, another 40% left after page 1, and only 1% bought something.

Performance also matters at Betfair, one of the world’s largest betting providers. Doing cool stuff is important too, but according to Tim Morrow’s performance pyramid of needs that’s not where you start:

1. It works.
2. It’s fast.
3. It’s useful. (I personally have a slight preference for useful over fast.)
4. It’s cool.

Jeffrey Veen of Hotwired, Adaptive Path, TypeKit fame kicked off the second day with an inspiring talk on designing for disaster, working through crises and doing the impossible. I liked the fancy status boards on the walls, and the “CODE YELLOW” mode, the openness and the clear roles when something bad happens. And something bad will happen, as John Allspaw pointed out: “You will reach the point of compensation exhausted, systems, networks, staff, and budgets.” A helpful technique for planning changes is to write down the assumptions, expectated outcomes and potential failures individually, and then consolide results as a group and look for discrepancies. If things still go wrong, Michael Brunton-Spall and Lisa van Gelder suggested to stay calm, isolate failing components, and reduce functionality to the core. Having mechanisms in place to easily switch on and off optional features is helpful, down to “page pressing” to produce static copies of the most frequently requested content to handle peak loads.

Several talks covered scripting performance and optimization techniques. Javascript is already getting really fast, as David Mandelin pointed out, running everything from physics engines to an H.264 decoder at 30 fps, as long as we avoid sparse arrays and the slow eval statements and with blocks. Using proven libraries is generally a good idea and results in less code and good cross-browser compatibility, but Aaron Peters made the point that using jQuery (or your favorite JavaScript library) for everything may not be best solution, and accessing the DOM directly when it’s simple and straightforward can be a better choice. Besides that, don’t load scripts if the page doesn’t need them – not that anyone would ever do that, right? – and then do waterfall chart analysis, time and again. Mathias Bynens added various techniques for reducing the number of accesses to the DOM, function calls and lookups with ready-to-use code snippets for common tasks.

For better mobile UI performance, Estelle Weyl suggested inlining CSS and JS on the first page, using data: URLs and extracting and saving resources in LocalStorage. Power Saving Mode (PSM) for Wi-fi and Radio Resource Control (RRC) for cellular are intended to increase battery life but have the potential to degrade perceived application performance as subsequent requests will have to wait for the network reconnection. Jon Jenkins explained the split browser architecture of Amazon Silk, which can use proxy servers on Amazon EC2 for compression, caching and predictive loading to overcome some of these performance hogs.

IBM’s Patrick Mueller showed WEINRE (WEb INspector REmote) for mobile testing, a component of the PhoneGap project.

Google has been a strong advocate for a faster Web experience and long offered tools for measuring and improving performance. The Apache module mod_pagespeed will do much of the heavy lifting to optimize web performance, from inlining small CSS files to compressing images and moving metadata to headers. Andrew Oates also revealed Google’s latest enhancements to Page Speed Online, and gave away the secret parameter to access the new Critical Path Explorer component. Day 2 ended with an awesome talk by Bradley Heilbrun about what it takes to run the platform that serves “funny cat videos and dogs on skateboards”. Bradley had been the first ops guy at YouTube, which once started with five Apache boxes hosted at Rackspace. They have a few more boxes now.

With lots of useful information, real world experiences and ideas we can apply to our Websites, three books signed by the authors and conference chairs, High Performance Web Sites and Even Faster Web Sites, and Web Operations: Keeping the Data On Time, stickers, caps and cars for the kids, Velocity Europe worked great for me. The next Velocity will be held in Santa Clara, California in June next year, and hopefully there will be another Velocity Europe again.

Related links

• Velocity Europe conference 2011
• Videos and presentations
• #velocityconf on Twitter

Photo credit: O´Reilly

Labels: events, javascript, metrics, networking, technology, webdevelopment

Google recently announced plans to make search more secure.

This effort includes encrypting search queries, which is especially important when using an unsecured Internet connection or accessing the Internet through intermediate devices which have the ability to log requests. Encrypting the search interface will automatically block referrer information for unencrypted sites, and would provide an incentive for companies to join the industry effort to use SSL/TLS encryption more widely.

But Google takes this a step further, hiding query information from encrypted searches. The click-through tracking link for unencrypted search includes the search term parameter “q”, which gets passed to the visited website:
http://www.google.com/url?sa=t&rct=j&q=&esrc=s&frm=1&url=http%3A%2F%2Fexample.com%2F

The link for encrypted search, however, leaves the parameter “q” empty. Interestingly click-throughs for encrypted searches are tracked on an unencrypted connection, thus revealing the visited site address to an eavesdropper:
http://www.google.com/url?sa=t&rct=j&q=example&url=http%3A%2F%2Fexample.com%2F

With this change, the visited website receives no information about the search term. What enhances privacy for searchers holds website owners off important information for optimizing their websites to best serve visitors.

Browsers already provide mechanisms for controlling referrer information, for example the network.http.sendRefererHeader preference setting or the customizable RefControl extension for Firefox. Google’s privacy enhancement takes control away from the users by not passing referring information, period.

Google’s move has the potential to change the search engine marketing (SEM) landscape. Search terms in paid ads will remain trackable unchanged. For organic search, the only way for website owners to get access to, albeit delayed, aggregated and limited to the top 1,000, search terms is through Google webmaster console, a very fine tool but not a replacement for an integrated web analytics solution.

The impact of this change goes beyond web analytics and search engine optimization (SEO): Sites often use the search terms that led visitors to the site for dynamic customization, offering related information and links. With encrypted search, visitors will no longer have access to these enhancements either.

Labels: google, metrics, security, seo

Delicious is a social bookmarking web service for storing, sharing, and discovering web bookmarks, says Wikipedia. Well, at least it was until a few days ago.

When AVOS took over, they promised Delicious would become “even easier and more fun to save, share, and discover”.

I haven’t quite figured out what the new site is about. All I can tell is that I am not interested in the featured stacks about synths and electronic music, 7 top articles on Michael Jackson, or Beyonce and beyond. I WANT MY BOOKMARKS!

One reason for using an online bookmarking service is the ability to share bookmarks between browsers and computers. Sure enough the site no longer works with Internet Explorer 8 at all and suggests that it might work better on Firefox.


Tag lists were temporarily broken. Search suggests fairly useless related tags (anyone in Vienna looking for dentists in London, Syracuse and Colorado?) Even bookmarking, the raison d'être of this site, doesn’t work well any more.

It’s obviously time to look for another bookmarking service while the Delicious export to save a bookmarks file locally still works.

Goodbye, Delicious!

Labels: technology, web2.0

Renata was the first to leave on Saturday morning, and probably the last one to arrive home after an amazing 68 hours odyssey with delayed flights, missed connections and a closed airport.

While others were checking out and heading to the airport, I went for a five hour walk to explore Phnom Penh by foot again. The first sight was the main post office, a recently renovated colonial-era building, with time tables for letter postings and a commemorative stamp counter where the clerk would patiently search through piles of first-day covers and stamp packs to find the desired items. Here I could also finally mail the postcards I had written a fortnight ago; unlike in most other countries stamps are not available from stores and I didn't see letter boxes anywhere in the city either.



The next stop was Wat Phnom, a pagoda on a green hill and a place where people make generous donations of food and money, and only foreigners pay a modest entrance fee.


The railway station looks as if it was still in operation, with nice wooden benches in the waiting area and time tables listing train connections, only no trains have been running for many years and only now there are attempts to start at freight services again.


The Olympic stadium provided protection from a sudden monsoon rain, and the security staff was kind enough to let me take a peek inside where some soccer game was about to start.


The real athletes were outside though, two workers mounting a huge billboard and climbing the scaffold with ease in their flip-flops.



The day ended with a nice dinner with friends of a friend of mine, a couple living in Phnom Penh who invited me to their beautiful colonial style house and afterwards to Rahu, a new and very stylish restaurant at the riverside.

On Sunday morning I began to appreciate everyone's complaints about packing. Although I had resisted the temptations at the various markets and had not bought much, I ended up with a full suitcase, a seriously overweight backpack and a large extra bag of dried fruits from Cambodian Dried Harvest Fruit, one of the companies our team had worked with.

Patricia and her friend left early to catch a bus for a ten hour drive to the north, on-board Karaoke included. Since the weather great I decided to spend my last day visiting a few more sights by car with a wonderful driver, Chin Bond Sreang (his contact information at the time of this writing: phone +855-12855281, e-mail bondservice81@yahoo.com).

The first stop was Phnom Chisor, a temple ruin set on a hill, some 300 steps from the parking area. Arriving in a fancy four-wheel drive on a lazy Sunday has its disadvantages, especially when you are one of the very few tourists in the area, so I had plenty of kids wanting to show me around. After having seen Angkor the temple remains here are not so special, but the view from the top over to Vietnam and Thailand is spectacular.



Next I visited the Phnom Tamao zoo, a sanctuary for birds, lions, tigers, crocodiles, snakes, elephants and monkeys, lots of monkeys. A young and very knowledgeable volunteer guide showed me around and we talked about his plans to finish school and move to Phnom Penh to become a tuk-tuk driver one day. The way he talked about the capital, full of passion and desire, it sounded like a wonderful place far away.



There are many beggars along the road to the park, which is quite popular with locals too, and some special figures too. On the way out when the afternoon rain started I was glad to be in the car, not on a tuk-tuk, as the road was getting quite muddy and all the carefully cleaned motorbikes and their drivers looked much less clean within minutes.



Last was Ta Promh, another temple ruin in a scenic setting, near a pagoda and a lake where people spend their weekends.



Along the way I saw again packed vans with some people sitting on the roof, motorbikes loaded with poultry and pigs, and near a wet area several food stands offering grilled frogs. Before you ask, I was not hungry and didn't try any, although they looked pretty good.



Thus ended my last day here, goodbye Cambodia!

Thank you to everyone who made this trip possible, memorable and enjoyable, first and foremost my family for letting me be away for so long, the “Tissabamokah” team and our colleagues at IBM who helped with enabling this assignment, our organizers and hosts from ABV, our client teams, the wonderful staff at Boddhi Tree hotel, our drivers and tour guides, and all the people we met in Cambodia, សូមអរគុណ!

Post scriptum: The flights from Phnom Penh to Vienna via Bangkok and Frankfurt went well, only I forgot that Thailand is on a different time zone and almost missed my connecting flight to Frankfurt. As I boarded the plane the captain was just announcing that they were waiting for two more passengers, I guess one of them was me, ouch! I left Phnom Penh with temperatures in the thirties at night. Upon arrival on Monday morning, Frankfurt reported rain and a temperature of 12° C, and Vienna wasn't much better. I will miss a thing or two from Cambodia for sure.

Labels: cambodia, ibmcsc, travel