# Overview

If you’re doing this, you’re doing it wrong…:

2016-05-31 10:19:45.493314 Client 92.x.x.192 hamburg, germany/hamburg/hamburg
2016-05-31 10:19:48.443380 Client 74.x.x.189 greensboro, united_states/north_carolina/greensboro
2016-05-31 10:19:56.733260 Client 50.x.x.50 beaverton, united_states/oregon/beaverton
2016-05-31 10:19:56.745653 Client 50.x.x.50 beaverton, united_states/oregon/beaverton
2016-05-31 10:19:56.759656 Client 50.x.x.50 beaverton, united_states/oregon/beaverton
2016-05-31 10:19:56.819283 Client 50.x.x.50 beaverton, united_states/oregon/beaverton
2016-05-31 10:20:16.287744 Client 5.x.x.13 kaiserslautern, germany/rhineland-palatinate/kaiserslautern
2016-05-31 10:20:35.182942 Client 85.x.x.140 katowice, poland/silesia/katowice
2016-05-31 10:20:47.029550 Client 193.x.x.226 oslo, norway/oslo/oslo/oslo

Lots of people use the finger service @graph.no in an automated way. That’s quite alright, it’s what it’s there for. As an example:

# The idea

Yr.no has a brilliant hour by hour view. A simple picture where you get all info you need for planning your next 48 hours.

They also give out all their weather data for free! Having a special fascination for the command line, I wondered if I could represent the same information in a basic, ASCII, 80x22 terminal.

# Development

Earlier I’d made my first telnet service for keeping an eye on the status of the office coffee pot (coffee.graph.no / telnet graph.no). After that, I pondered for a while on how to allow for choosing location via such a limited protocol. I did not want to make a service that had to be used by hand, like wunderground, which I discovered later, but one that could be used in an automated sense.