Archive for October, 2006

Quikmaps gets a new server

Scaling with rails… This will be especially of interest to those who’ve had to deal with quikmaps downtime due to past hosting provider issues.

Over the weekend Quikmaps was ported over to a new server, and is now hosted by the fine folks at rimuhosting.com. This new server configuration gives Quikmaps it’s own dedicated portion of system resources, detaching us from the slow-downs often encountered with the previous shared hosting plan, and allowing us to scale effectively when quikmaps are posted on high-traffic websites. In short, we have a much bigger and much more stable computer.

For those of you interested in the ruby on rails techno-speak, we’ve set up an apache 2.2 front-end on a Linux VPS, using mod_proxy_balancer to manage a cluster of (for now) 4 mongrel processes. A number of high-profile ROR applications employ an identical strategy, including the official ruby on rails site.

Comments (2)

The essence of web 2.0

Ahh, web 2.0.

Means little to most of my friends, and means absolutely nothing to my parents. Intended to capture our current web boom, complete with it’s $1.6 billion rags to riches deals, personal broadcasting and networking pages (a la myspace), and wiki-driven content, it seems no one is really able to qualify what exactly it means. Tim O’Reilly’s assessment of ‘the web as platform’ is probably the most quoted, but the meat of his article consists of comparisons (web 2.0 is wikipedia and not Encyclopedia Britannica, Adsense and not Double Click, tagging and not taxonomy, etc). The authors of Wikipedia’s article suggest other phrases, such as ‘network of participation’, ‘perpetual beta’, and ‘the long tail’.

That’s all well and nice, of course, but we all know that web 2.0 really consists of pastel colours, boxes with rounded corners, fuzzy user profile images, and the phrase ‘cool new’. Or, as Bill Amend, Foxtrot comic artist, suggests, web 2.0 is essentially blank web pages:

Foxtrot web 2.0

All this talk has fueled my own creative web 2.0 juices, and so, with help from walter zorn’s considerable talents, I submit my own response to Bill’s comic: The web 2.0 essence.

Hint: draw some raindrops. Click here to erase them. Or, try a larger canvas.

Comments

Kathmandu, Everest photos posted to Flickr

Finally, I’ve broke down, purchased a pro account on Flickr, and put effort into uploading photos from my not-so-recent time in and around Kathmandu. Those of you who know me well are of course aware that I spent a few months in 2005 lending technical hands to literacy workers in Nepal. For those of you who don’t know me well, I guess you’ve just learned something new…

So, have a browse at the photos, if you like. You’ll find the most recent uploaded shots in the Everest and Kathmandu valley sets.

This shot is my favourite, looking down on the gokyo valley and ngozumpa glacier. Note the early morning frost.

gokyo valley and a canadian

Comments

Tracking wanderingken with Telus, an iDen, Mologogo, and Geonames

So, as one might expect given my propensity to hack around with google maps, I’m fascinated by the idea of GPS receivers inside cellular phones. Cell phones have a significant advantage over traditional GPS devices in that not only can they pinpoint your location, they can immediately send that information. Immediately upon receiving your location, a 3rd party (say, your cell provider, google maps, etc…) can return relevant location-based information. Very cool.

Nearly all cell phones now have forms of GPS capability built-in, as GPS is now required by the U.S. FCC for enhanced 911 services, although in many cases GPS capabilities area actually assisted GPS, estimated by proximity to cell towers and not retrieved via satellite. However, as discussed recently on NPR recently, and I’m sure many cell owners have discovered, cell users can’t necessarily get at the information. Privacy concerns are play a significant role in this, of course, though one also has to believe cell providers are protecting location information until they can figure out how to make money from it..

I discovered all this a year or so ago, with my Sanyo SCP-2300 — GPS enabled, and I could turn the GPS function on and off, but good luck getting the phone to spit out a latitude and longitude. 911 could find out where I was, though, as I discovered when I called to report dangerous roadkill on Alberta’s highway #2.

Anyway, it turns out Sprint / Nextel in the U.S. is bucking the trend, allowing access to GPS on Motorola iDen phones, which has prompted the fellows at Mologogo to write a little J2ME live tracking app which plots you (and your phone) on a google map, on your phone. As an added feature, you can specify a server URL to which to post this location when obtained (via HTTP GET), and even ask your phone to show you where your fellow mologogo-friends are. It’s also free.

Motorola iDen 850

In Canada, iDen phones are sold by Telus Mobility for their Mike network, and, it turns out, Telus also allows GPS access on these phones. So, when my recent move from Toronto to Edmonton provided an excuse to buy a new phone, I figured I’d try see if I could create a little live blog tracker here in Canada and hooked myself up with one of these fellows (an i850, as in the photo). It works! Wanderingken.com tracks my wanderings in real-time (provided I’ve got mologogo running and it’s sunny outside). If you’re watching at the right time, you’ll even see the marker move before your very eyes. My own little Where’s Tim.

Here’s how: You’ll need both a USB data cable (I haggled a free one from the cell store guys) and a Motorloa Java application loader. Good luck, though, on the application loader. Motorola has an application form here, but it’s rather restrictive. Or, you can try wade through this site (as I did, and ended up installing a 7-step something or other that did, actually, work). Complex as hell, and only necessary because both Sprint / Nextel and Telus see fit to disallow downloading J2ME application types via the mobile browser, something Bell Mobility, interestingly, does not restrict.

After that, you’ll need to create a little end-point url which saves latitudes and longitudes arriving as GET parameters into a server-side file, and specify this url in the mologogo preferences (on your phone). Then, map the latitude and longitude to a place name via geonames, sprinkle in a a little google maps code and an Ajax-based periodic updater, and ta-da, live tracker.

Comments (17)