Dopplr import fail

I use Dopplr and TripIt, to keep track of traveling colleagues, update people on my own travel, and just generally simplify life. (I’ve blogged about each many times as well: see posts containing dopplr or TripIt).

I’m getting tired of Dopplr’s consistent FAIL on a common (for me) use case- a one day trip to NY on Delta.

Whenever I forward such a confirmation here’s what Dopplr does:

Thanks for sending us a message by email.

We automatically created a trip to Atlanta, GA, United States (from Newburyport, MA, United States) between February 10th and February 13th

We won’t share coincidences from this newly-created trip with your fellow travellers until February 18th. This is to give you a chance to check and correct any problems in interpretation.

If you’d like to check, go to [link removed]

Yours sincerely,
The Dopplr Team.

The problem is, I’m not going to or from Atlanta – that’s where Delta airlines headquarters is, sure, but it’s a long detour on the Boston->New York route.

I’m also not travelling Feb 10 to Feb 13, I’m leaving and returning on the 13th, and the trip was booked on the 10th.

I can (and do) go in and manually fix the trip in Dopplr, but in this type of case TripIt’s import feature just works.

On the Internet, People Know if you’re a dog

(Update, 2pm ET: Scott Hintz from TripIt replied in the comments on the original post apologizing for the employee’s behavior – thanks Scott.)

One of the famous cartoons of the first internet craze was this one from the New Yorker:

On the Internet Nobody Knows You're a Dog

The reality is, however, that increasingly people’s online identity can be mapped to their offline identity. (Check out Who Controls the Internet? for a well informed and very smart extended exploration on what this means from a legal perspective, and this reality checkfrom UNC).

Earlier this week, I wrote a blog post about TripIt and Dopplr, two major companies in the social travel market, which people use to share information about various trips they are taking or planning. It was a perfectly innocuous post, describing some of Dopplr’s new features which make it more like TripIt, and presumably more competitive with TripIt as a result.

That post recieved the following comment, from someone identifying himself as Thomas, with an email address at Yahoo! mail, and no url:

Well, in regards to Dopplr’s generic email import approach, I’ve tried forwarding several different emails I have from my company, travel agent, and from major airlines such as American Airlines, but they don’t work one bit. For example, Dopplr thinks I’m going to different places in Europe when I send in my opentable reservation.

In contrast, most of these work “out of the box” with TripIt. And when I complained about my travel agent not being supported, they added it within a day.

What’s more, is that I don’t really want to “discover” people I do not know on a trip. All I’ve been wanting to do is to manage my business travels better and inform my family. TripIt fits that bill perfectly.

So, I don’t really find Dopplr very useful. My two cents.

Thanks for the nice write-up though.

Best,
Thomas

Not itself a controversial comment, and I almost approved it without a second thought. But then I noticed that the IP address from which the comment was posted (69.12.150.246) is mapped to a machine called wall.tripitinc.com:

jeckman$ nslookup 69.12.150.246

Non-authoritative answer:
246.150.12.69.in-addr.arpa name = wall.tripitinc.com.

(I would likely not have even noticed, but either WordPress itself or one of my plugins actually adds that info to the email it sends me letting me know that a comment has been recieved and is awaiting moderation).

So I emailed “Thomas” – using the yahoo.com address he provided – and suggested he disclose that in his comment.

I never heard back – perhaps the email wasn’t valid to begin with. So, I decided to post the comment, but also note what I had determined about its origin.

Lesson learned? It’s easier than you think to determine who you are when you do various things on the net. If you’re going to post comments on blogs that discussion your product(s), disclose your relationships. Nothing wrong with posting – I’ve had many comments from folks whose products/services I discuss in blog posts – but posting a comment like the above without disclosure is basically astroturfing, and it never works.

Dopplr gets Email, Twitter, SMS import

One of the more popular posts on this blog is the one which describes how to import trips from TripIt into Dopplr, in order to avoid the re-entry tax. After all, as I wrote in my comparison of the two services last October, TripIt’s email import was the critical factor in my decision of how to manage this information:

Tripit’s mechanism for adding trips is superior. The ability to simply forward (or even set an automatic rule to forward) confirmation emails is a major step forward . . . Where TripIt seems better at pulling data in, Dopplr seems to be better so far at pushing their data out, or letting people pull it into other contexts.

Well, now Dopplr’s gone and added some new import mechanisms of their own. This post from the Dopplr blog (ok, it was posted back on July 8th, but it has been sitting in my queue to write about) lays out three new options: Twitter, SMS, and Email:

Today I’m really happy to say we’re taking the wraps off a number of new ways to get your future into Dopplr and share your travel information with those you trust: Dopplr by Twitter, SMS and… Email!

Although I love twitter as a notification service (a way of letting me know something relevant happened) I don’t see myself using it as a data input service. For those of you who would like to, just follow the dopplr user and send direct messages with your trips, like: d dopplr a trip to London July 28th to August 3rd. (Nicely, it also happily accepts @dopplr posts, in case you want to announce your trips as well as put them in dopplr). SMS is another option – you associate your SMS number with your Dopplr account and you can text message the same types of messages to Dopplr’s number.

Finally, they’ve got email working at trips@dopplr.com (wonder how many people will confuse plans@tripit.com with trips@dopplr.com – did they make plans@dopplr.com an alias?).

Interestingly, you can use the same kind of shorthand messages used for Twitter or SMS – “a trip to London July 28th to August 3rd” – or you can forward confirmation messages from booking services (which is how TripIt handles import). This is because Dopplr did not set out to parse all the complex formats used by different agencies, but took a simper approach, as explained by MattB:

There are an awful lot of ways to format a travel itinerary. When people asked us to extract trips from emails, we looked at our long history of e-tickets, confirmations and reservations, and scratched our heads.

Inspiration came in the shape of Apple’s last OS X release, Leopard, and an intriguing feature called “Data detectors“.

We realised that instead of creating a piece of code to decode every email format out there, we could look for patterns of dates and place names in the text (and later, other information too) and turn those into trips.

A happy side-effect of this approach is that as well as extracting information from automatic reservation emails, it works well with short text strings like “I’ll be in San Francisco from 3rd July to 7th July”. This means we can work with many hand-written emails, with Twitters, and with SMSes too.

Of course it won’t work with every variation under the sun (for example, it’s most reliable when an email contains just a return trip in a single hop), but we’ve had very satisfying results in our testing. And of course every email you send us will be added to our test suite so that our engine can get better and better over time.

In other words, rather than specifically targeting all the different potential formats, and parsing them in some structured way, Dopplr looks for some specific patterns in the text and tries to understand their meaning without knowing the format of the email in advance.

I wonder how different this is from what TripIt actually does behind the scenes – how much they plan for specific formats they know in advance – and how successful it will be “in the field.” For now it is enough to convince me to turn off my automated importing and give trips@dopplr.com a try on my next few confirm messages. Then, I can automate a rule in my email such that travel confirmations get auto-forwarded to both plans@tripit.com and trips@dopplr.com, and be sharing my travel plans painlessly.

Automated Import to Dopplr from TripIt

I use both TripIt and Dopplr, as each is better at certain things than the other.

In my ideal world, the act of forwarding a travel confirmation to TripIt, which establishes a trip, would also create the same trip in Dopplr, which my Dopplr badge, news feed on Facebook, Fire Eagle account, and lifestream would then share with the public, abstracting the details of flights and hotels and such. (Not that I’m terribly worried one could discover them, but just to simplify as Dopplr does well, so that only those who actually want to connect need to get to the details).

That possible crept a bit closer as Dopplr announced the ability to subscribe to your Google Calendar and learn your trips from it.

For some time, Dopplr has been able to export trips to calendars; TripIt can also adds trips to a calendar, but does so in a much more precise fashion, actually adding the flight info and such.

[Update: I had originally posted that the format Dopplr expects is different enough from the one TripIt produces that the two cannot be linked. I was wrong - they can be.]

To link your TripIt account to your Dopplr account, log in to TripIt and locate your iCal feed on your “MyTrips” page (click on the green ICAL feed icon):

Then, log in to Dopplr, go to “Your Account” and choose “Import trips from external calendars.”

Paste in the address of your TripIt iCal feed and Voila! – automated import of TripIt trips into Dopplr.

The logic is smart enough to notice where you already have trips, and not double book you in Dopplr.

Very cool. Now all I need is an Action Stream plugin for Movable Type which notes actual travel segments, so that I can add “John flew from Boston to Austin” to a day like today on JohnEckman.com. I suppose I could write one that checks the iCal feed from TripIt once or twice a day, and creates an action only when the travel date matches today’s date?