Photo by: C.Saetre

Join the campus mapping effort and OpenStreetMap competition this month at NTNU. I can attest that mapping is a bit addicting, and there is fun to be had by joining the collective NTNU effort.  Even if there weren´t prizes it would be fun—but there are indeed some prizes—good prizes.

Did I lose you?

OpenStreetMap is on its way in as NTNU´s official map app (cheering heard somewhere). A free editable, net-based, map of the world, OpenStreetMap (or OSM)  is made up of data collected and plotted by anyone who wants to.  For any who find this hard to digest, it could be described as the Wikipedia of mapping, if you will.

More about the prizes

The competition is open to both NTNU students and employees. Just by participating one will be eligible to win one of 3 gift checks for NOK 3000.  Prizes will be awarded in each of the following groups:

• Best contributor to NTNU campus regions.
• One random contributor to NTNU campus regions ( lottery drawing)
• One random contributor to Trondheim´s “midtby” regio (lottery drawing)

It´s never too late to get started,  but keep in mind that the competition ends on the 15th of November. One GPS track will earn you 10 lottery entries, 1 change-set with sensible comments will earn you 1 lottery entry, (max 1 change-sets per 3 minute interval).  Definitely read the official rules and registration, and if you are an exchange student in need of a translation, let me know.  Happy mapping!

Further Reading for OpenStreetMap fans

• Flickr Allows OpenStreetMap, FourSquare Geotags

From: Google itself

Building upon the breakthrough work of B. F. Skinner, Page and Brin reasoned that low cost pigeon clusters (PCs) could be used to compute the relative value of web pages faster than human editors or machine-based algorithms. And while Google has dozens of engineers working to improve every aspect of our service on a daily basis, PigeonRank continues to provide the basis for all of our web search tools. http://www.google.com/technology/pigeonrank.html

SEO (Search Engine Optimization) has its best practices, rules, and studies; and knowing a little bit about it is a good idea. If you were looking for information on that and arrived here, I mean no disrespect. Here is a good place to start:

• High Accessibility Is Effective Search Engine Optimization, (A List Apart)

But if you already know the rules of thumb, you probably are a geek like me and spend little time outside. My challenge to you: Go outside, or at least to the window. Fresh air FTW!

Humorous error messages diminish the irritation a bit: this “You are lost” 404-variant from The Telegraph made me smile. Fail Whale is a similar example. It wasn´t exactly funny, but over time Fail Whale had a similar effect on me, eliciting a “Hello again Fail Whale” response rather than peevishness.  Many of its fans agree.

A serious aside on the content of error messages: Emily Wilska, author of Non-fatal errors: Creating Usable, Effective Error Messages says that they are often an afterthought. This surprises no one, I gather?

Scrambling to get something–anything!–in the product to deal with problems users might encounter, we fall back on standard error messages, overly general or technical text, and confusing functionality.

The post goes on to offer a good overview of things to consider when, why, and how, borrowing a bit from Scott Burken´s  The Web Shouldn´t Be a Comedy of Errors. Recommended.

Error-message hits list

One could go on to reiterate the importance of tone (fault-free declarative or imperative) and the balance in the amount of information presented — but instead here is a little error-message hits list, as that is way more fun.

1. lp0 on fire (aka Printer on Fire) (Unix) – an error message with a legacy is still generated on some Unix/Linux operating systems for select printer errors. Line printers of yore used alcohol so a friction-related fire was thought possible. The original “printer on fire” message was a purely motivational message to users, trying to get them to check the printer under conditions Unix considered dangerous. No actual fire was occurring or necessarily imminent. Today, a CPU thermal failure can still yield “CPU#0: Possible thermal failure (CPU on fire ?)”.
2. Not a typewriter (Unix) – Haven´t received this myself, but imagine the surprise of learning this as you sit in front of your modern machine. (I think I would have to yell back at the machine “No kidding!”) Its origin is in the fact that “Typewriter” was what early UNIX systems called a terminal. The error message persists today, used to indicate that an attempt has been made to use a non-TTY device as a TTY device.
3. Fail Whale – Twitter. A must on any list for its iconic standing, and its innovative place in web 2.0 history.
4. Blue Screen of Death (Windows) – Infamous and truly terrible to behold.
5. The red ring of death (Xbox)  – No, not so much a message as a signal, but we get the message.
6. More new-fangled amusing error messages – Flickr, Digg, Technorati and Reddit server error notifications that are empathetic/humorous on purpose.

Digression: Am actually planning some of my own, with hopes that the IT-dept will be willing to deploy during the platform migration arriving at a theatre near me. Yep there is bound to be some stress involved with NTNU´s upcoming migration from Escenic to Liferay, and why not have some fun with it.

Make your own error message with the Atom Smasher´s generator.