Posts Tagged ‘yahoo’

RIP FireEagle. You Shall Share Location No More

Back in 2010, when I left Yahoo! to go and join Nokia, I wrote some words that at the time seemed full of hope for the future of the Geotechnologies group I’d left.

I’ll continue to use my core set of Yahoo! products, tools and APIs … YQL, Placemaker, GeoPlanet, WOEIDs, YUI, Flickr and Delicious. Not because I used to work for Yahoo! but because they’re superb products.

Time and changes of corporate heart have not been kind here. Maybe it’s time to take a look at the state of the geo union.

YQL. The Yahoo! Query Language. Still here although I haven’t used it in anger for several years as the service was frequently down.

Yahoo! Maps and the Yahoo! Maps API. RIP. Yahoo! Maps is now run by the back-end services of Nokia, my current employer and the Yahoo! Maps API finally got switched off in November 2012.

Placemaker and PlaceFinder. Still here. Sort of. Placemaker is now Placespotter and while PlaceFinder keeps its name they’re both part of Yahoo! BOSS Geo, which means if you want to use them it’s time to dig into your wallet for your credit card as they’re no longer free to use.

GeoPlanet. Still here. Still free. You have to ask the question for how long though.

WOEIDs. Still here and although you can still use WOEIDs through the GeoPlanet and Flickr APIs, the GeoPlanet Data download remains offline, although see also the fact that there’s no delete button for the Internet. WOEIDs are probably not going to go anywhere soon as Yahoo’s geotargeting platform depends on them. For now.

YUI. Still here and open sourced on GitHub.

Flickr. Still here, used on a regular basis by me and even flourishing with a renewed iPhone app and a horde of refugees from Instagram after that service’s on, off, on again change of licensing terms in December 2012.

Delicious. Still here and still used on a relatively regular basis by me but no longer owned or operated by Yahoo! who sold it to AVOS in 2011.

Did I mention that the old Yahoo! Geo Technologies blog, after years of being down, now redirects to the Yahoo! corporate blog? No? Well it does.

And now it seems that another of Yahoo’s geo products has finally done to the deadpool as FireEagle finally stops sharing people’s locations and Tom Coates, who I remember discussing what would become FireEagle over coffee back when we both worked at Yahoo, was in a sanguine mood on Twitter.

Tom Coates - FireEagle

The fate of FireEagle has long been been in the balance since it was mentioned as one of the products due to be sunsetted or merged with another product in 2010. The merging never happened and now FireEagle is no more.

Which is a great shame as FireEagle was way ahead of its time and in today’s age of location based services and social media sharing, the need for a way to share your location that makes sense for both the privacy of individuals and for businesses is needed more than ever.

If anyone’s looking to resurrect the notion of FireEagle, hopefully you’ll be the first to let me know.

Written and posted from home (51.427051, -0.333344)

A Year On And Yahoo’s Maps API Finally Shuts Down

Nothing on the interwebs is forever. Services start up and either become successful, get acquired or shut down. If they shut down they usually end up in TechCrunch’s deadpool. The same applies for APIs and when they finally go offline, they usually end up in the Programmable Web deadpool.

YDN Maps Shutdown

At around 1.30 PM London time yesterday, the Yahoo! Maps API got added to the Programmable Web deadpool for good. Despite the announcement I wrote about last year that it was being shutdown on September 13, 2011, up until yesterday the API was very much alive and well and still serving up map tiles, markers and polylines via JavaScript.

Yesterday I was running some tests on the latest pre-release version of Mapstraction, which still supported the Yahoo! Maps API and they were running without error all morning. Then they stopped. The API just wasn’t there anymore.

$ wget http://api.maps.yahoo.com/ajaxymap?v=3.8&appid=(redacted)
Resolving api.maps.yahoo.com... 98.139.25.243
Connecting to api.maps.yahoo.com|98.139.25.243|:80... connected.
HTTP request sent, awaiting response... 503 Service Unavailable

A quick look at the API’s home on the web at developer.yahoo.com/maps/ajax/ shows an update to the previous shutting down message, with developers now being redirected to developer.here.net, the home of Nokia’s new Here Maps API.

So whilst the demise of the Yahoo! Maps API in September of last year proved to be somewhat exaggerated, the plug has now been well and truly pulled.

I’ll always have a soft spot for the Yahoo! API; it was the first mapping API I really cut my teeth on and while things change on the interwebs on a daily basis I can’t help but feel sadly nostalgic.

This does mean that the next release of Mapstraction will no longer support the Yahoo! Maps API, though it will support Nokia Maps and Here Maps. My signed copy of Charles Freedman’s Yahoo! Maps Mashups will also continue to remain on my office bookshelf as a memento.

Written and posted from home (51.427051, -0.333344)

Farewell Yahoo! Maps API, Hello Nokia Maps API

Yahoo’s JavaScript and AJAX API was the first mapping API I ever used and it now seems hard to remember when Yahoo’s API offerings were the dominant player, always iterating and innovating. The Yahoo! API set formed and continued to underpin the majority of my online presence. When I wrote about leaving Yahoo! and joining Nokia in May of 2010 I said …

So whilst I’m going to Nokia, I’ll continue to use my core set of Yahoo! products, tools and APIs … YQL, Placemaker, GeoPlanet, WOEIDs, YUI, Flickr and Delicious. Not because I used to work for Yahoo! but because they’re superb products.

… and I meant every word of it. The Yahoo! APIs were stable, powerful and let create web experiences quickly and easily. But now a year later a lot has changed. I still use Flickr on a pretty much daily basis, but Delicious is no longer a Yahoo! property and I transitioned my other web presence from using YQL for RSS feed aggregation to use SimplePie as YQL was frequently down or just not working. The original core set of Yahoo! APIs I use in anger is now just down to Flickr and YUI.

YDN Maps Shutdown

Sadly, this trend is continuing and on September 13th, to badly mangle the quote from Cypher in The Matrix, “buckle up your seatbelts Map scripters, ’cause the Yahoo! Maps API is going bye-bye” and writing …

var map = new YMap(document.getElementById('map'));

… will be a thing of the past. Adam Duvander, author of the excellent Map Scripting 101, has written a eulogy for the Yahoo! Maps API over on Programmable Web, including some pithy quotes from old friend Tyler Bell, whom I worked with when I was part of the Yahoo! Geo Technologies group, which sadly echo my comments on the overall demise of Geo at the company.

Thankfully all is not doom and gloom in the world of mapping APIs and Nokia’s Maps API is firmly in the spotlight to take up the slack left by the addition of the Yahoo! Maps API to the deadpool. And if you’re using Mapstraction with the Yahoo! Maps API, it should be relatively trivial to swap your code over to the Nokia API as Mapstraction now supports Nokia Maps. I may have had a hand in that.

Written and posted from the British Airways Galleries Lounge at London Heathrow Terminal 5 (51.4702, -0.4882)

The Non Golden Rules of Geo (Redux)

Back when I used to work for Yahoo! I wrote a lot of posts for the Geo Technologies blog; for reasons partially explained in my last post, that blog is now offline, presumed dead. But one post that seems to keep catching people’s imagination is the one in which I, somewhat tongue in cheek, codified the Six Non Golden Rules Of Geo. Much to my satisfaction, it keeps getting mentioned, although the full original post is inaccessible, as is the rest of that blog. Nate Kelso reproduced part of it, as did John Goodwin but until earlier today I’d not been able to find the full post.

Step forward the aforementioned John Goodwin who, with a bit of internet detective work, managed to find a mirror of the post. While I much prefer to link to blog posts rather than reproduce them in full, in this case I’m plagiarising myself and making an exception on the ground of inaccessibility, and have mirrored the post in full here. It’s worth mentioning that this post was originally written in February of 2009, when I was still working for Yahoo! so it’s a little out of date and was originally posted as …

UK Addressing, The Non Golden Rules of Geo or Help! My County Doesn’t Exist

George Bernard Shaw once said the golden rule is that there are no golden rules and at Geo Technologies we understand that there is no one golden rule for geo and so we try to capture and express the world’s geography as it is used and called by the world’s people. Despite the pronouncement on golden rules, a significant proportion of the conversations we have with people about geo lend themselves to the Six Non Golden Rules of Geo, namely that:

  1. Any attempt to codify a series of geo rules into a formal, one size fits all, taxonomy will fail due to Rule 2.
  2. Geo is bizarre, odd, eclectic and utterly human.
  3. People will in the main agree with Rule 1 with the exception of the rules governing their own region, area or country, which they will think are perfectly logical.
  4. People will, in the main, think that postal, administrative and colloquial hiearachies are one and the same thing and will overlap.
  5. Taking Rule 4 into account, they will then attempt to codify a one size fits all geo taxonomy.
  6. There is no Rule 6, see Rule 1.

I codified these rules after a conversation last week, via Twitter and Yahoo! Messenger, with Andrew Woods, a US based developer who was, understandably, confused by the vagaries of the how addresses work in the UK. Andrew’s blog contains the full context but it can be distilled into three key questions:

  • If the country is The United Kingdom, how come the ISO 3166-2 code is GB?
  • If the country is The United Kingdom, is England a country?
  • If England is a country, do I use it in an address?

As a US developer, Andrew is naturally fluent with the US style of addressing, with all of its’ localised and regional exceptions. This is a good example of both Rules 3 and 4 in the real world; most people in the US will use number, street, city, State and ZIP for specifying an address. But how does this transfer to the UK? What’s the equivalent of a State … England, Scotland or Wales? Let’s try to answer some of these problems:

Middlesex In 1824

If the country is The United Kingdom, how come the ISO 3166-2 code is GB?

The UK’s full name is The United Kingdom of Great Britain and Northern Ireland and although the United Kingdom and Great Britain are used interchangeably, Great Britain really refers to England, Scotland and Wales. At the time of writing, both GB and UK are formal ISO 3166-2 codes for the United Kingdom with GB being the assigned code for Great Britain and UK being exceptionally reserved by the United Kingdom.

If the country is The United Kingdom, is England a country?

To be formal and precise, the United Kingdom is a unitary state, not a country, with four “member” countries; England, Northern Ireland, Scotland and Wales.

If England is a country, do I use it in an address?

Normally, no. A full UK address consists of the following:

  • The addressee’s name, if known or applicable
  • The company or organisation, if known or applicable
  • The building name; optional if the building has a number
  • The number of the building and the name of the street
  • The locality name;optional
  • The Post Town
  • The county; optional if a Post Town and Postcode are supplied
  • The Postcode

… for example, take our office address of Yahoo! Geo Technologies, 125 Shaftesbury Avenue, London, WC2H 8AD. This address has no building name, a building number and street, no locality name, a Post Town, no county as we have a Post Town and a Post Code, and a Post Code.

Which brings me neatly to another example of Rule 4 and the missing county of this post’s title. The UK’s postal hierarchy and administrative hierarchy are not the same. Since 1996 the first half of a UK postcode, known as the outward code, has been used to help in the sorting of mail but prior to this a set of postal counties were used as part of addresses and these frequently do not match the current set of administrative counties. For example, the county of Middlesex was formally abolished in 1965 with the majority of the county becoming part of Greater London. Despite this and despite the 1996 postcode changes, Middlesex lives on as a postal county and as informal area name with the side effect that it is still possible to send mail, and have it delivered, to places in a county which hasn’t existed for over 40 years.

Oh, and Yahoo! GeoPlanet, naturally, recognises Middlesex and correctly identifies it as a Historical County.

Written and posted from home (51.427051, -0.333344)

The Opposite Of Geolocation Is … Relocation?

First a disclaimer; there’s one elsewhere on this blog but this post merits another. I used to work for Yahoo! as part of the Geo Technologies group. I now work for Nokia as part of their Location group. The opinions and ideas expressed in this post are absolutely just my own, and should not be confused with, or taken for, those of my current or past employers. It’s just me here.

You may not have realised it but Friday May 27th. was a sad day for the Geo industry in London. Even without the benefit of knowing what was going on from ex-colleagues inside the company, the signs were there if you knew where to look for them and how to read them.

Before the Internet, companies, teams and projects could fade quietly into anonymity and into oblivion. But on the Internet, everything is in public and it’s much harder to hide the tell tale signs. API updates and bug fixes cease. A web site or blog stops being updated or goes down altogether. A Twitter feed stops being an active living thing and becomes merely a historical record. Ex-colleagues start following you on Twitter or you start getting connection requests on LinkedIn whilst other colleagues start polishing and updating their LinkedIn profiles.

And May 27th. 2011? That was the day that the last of the remaining members of my old team at Yahoo! Geo Technologies left the Yahoo! office in London and that was the day that Yahoo! ceased to have a Geo presence in the UK.

Sad Yahoo! Smiley

I joined Yahoo! in 2006 as Engineering Manager for Geo Location Targeting, also known as GLT (and not standing for Gay, Lesbian and Transgender, a mistake once made by someone at a conference with hilarious consequences), a group formed from the acquisition of WhereOnEarth.com a year earlier in 2005. As the name suggests, GLT was formed to use WhereOnEarth’s technology to build Panama, Yahoo’s geotargeting ad platform, a task which the technology was well suited to and a task at which the team succeeded.

But post Panama, we faced the challenge that most acquisitions face … “we’ve done what we were acquired for … now what“? In 2008 we started to answer the “now what?” question. With Tom Coates and the Yahoo! Brickhouse team, we provided the back-end geo platform for Fire Eagle. With Aaron Cope and Dan Catt, we provided the back-end geo platform for geotagging photos on Flickr. And with Martin Barnes, Tyler Bell and Mark Law we launched the GeoPlanet geodata gazetter API and the Placemaker geoparsing API. These were heady days for geo; GPS was reaching critical mass in consumer devices and web service mashups were ready to take advantage of powerful geo APIs and with Chris Heilmann evangelising furiously as part of YDN, the Yahoo! Developer Network, we were well placed to take the lead in the explosion of interest in all things geo that was starting then and continues to this day.

Yahoo!

Yet the company didn’t seem to know what to do with their Geo Technologies group. We were reorganised more times that I can remember, starting again with another Vice President and another group. The promising lead in this area started to loose ground and the long promised investment never seemed to materialise. In May 2010, Nokia made me an offer to be part of the their location group that I couldn’t refuse and I jumped ship. TechCrunch seemed to like this; twice to be exact. Over the next 12 months the group in London continued to shrink and continued to lack investment. The signs were all there for anyone to read … the YahooGeo Twitter feed was last updated in January 2011 with a total of 5 Tweets since I handed over the reins on May 28th. 2010. The blog at www.ygeoblog.com has been down for almost a year as well.

And on Friday May 27th. 2011, the last of the London team left the office in London’s Covent Garden for the final time as the Geo Technologies group transitioned and relocated to the Yahoo! corporate headquarters in Sunnyvale, California and to Bangalore; a sad day for the team in London and a sad day for the Geo industry overall. Hopefully the future will yield more developments of the YDN Geo APIs and the WOEID geoidentifier and while Geo Technologies in the company continues to live and to power the successor to the Panama geotargeting platform, the London presence where the technology grew and was developed is over.

Written and posted from home (51.427051, -0.333344)

Will The New Delicious Still Be … Delicious?

Delicious is dead! Long live Delicious. Like a lot of Delicious users, I recently received a mail urging me to authorise the transfer of my Delicious account and bookmarks to the new service once ownership transfers from Yahoo! to AVOS.

The reception to the news of Delicious’s new owners has been … varied. Marshall Kirkpatrick has written a post in favour of the transfer, but Violet Blue is not so sure. If you do a little bit of digging, you’ll see that the new Delicious has the potential to be far more restrictive on what you can, and what you can’t bookmark, especially where potentially offensive content is linked to. Offensive is a horribly vague and subjective term; one which means many different things to many different people.

Delicious

At the heart of the issue is the difference in wording between the old Delicious terms

The linked websites’ content, business practices and privacy policies are not under the control of Delicious, and Delicious is not responsible for the content of any linked website or any link contained in a linked website. (…) In accessing Delicious or following links to third-party websites you may be exposed to content that you consider offensive or inappropriate. You agree that your only recourse is to stop using Delicious.

… and the new ones

You agree not to do any of the following: post, upload, publish, submit or transmit any Content that: (…) violates, or encourages any conduct that would violate, any applicable law or regulation or would give rise to civil liability; (iii) is fraudulent, false, misleading or deceptive; (iv) is defamatory, obscene, pornographic, vulgar or offensive (…)

If a complaint is made and if the new terms are upheld, you run the risk of having all your bookmarks removed, without recourse and without warning. Admittedly that’s a lot of ifs.

A cursory trawl through my Delicious bookmarks doesn’t seem to have anything obscene or pornographic, but there’s a lot of linked content which is fictitious and could possibly be deemed misleading or deceptive. As the saying goes, you can please some people, some of the time, not all people, all of the time. When you have terms of service which are vague and ambiguous, you can rest assured that someone will exercise their right to be offended. For now, I’ve authorised my old Delicious account to be transferred to the new service, but I’ve also taken a backup, just to be on the safe side.

What’s also unclear is whether the Delicious API and RSS feeds will remain; one of my web sites relies on these to dynamically update the site’s content.

While Delicious lives on, whether I’ll continue to be a user of the service or migrate to my own, self hosted solution, as I’ve already done with my URL shortener, remains to be seen.

Photo Credits: Shaneblog on Flickr.
Written and posted from Theresa Avenue, Campbell, California (37.2654, -121.9643)

Facebook Places; Haven’t We Been Here Before?

A week and a half ago Facebook finally launched their Places feature to a predictable media furore over location privacy, regardless of whether it’s justified or not and, to location industry watchers at least, a strong sense of deja vu. Haven’t we been here before?

Let’s look at the key issues that seem to be getting people hot, bothered and generally up in arms.

Deja vu the first. According to Facebook, at the time of writing they have 500M users. But how many of them will actually use the service, regardless of whether they’ve updated their privacy settings?

Deja vu the second. So you decide you want to use Facebook Places? Only on an iPhone I’m afraid or from Facebook’s HTML5 mobile web site. Want an Android or Nokia app? You’re out of luck, for now. Want to use it outside the US? You’re even more out of luck, for now.

Facebook Places. The UK Version

Deja vu the third. So you decide you don’t want to use Facebook Places? It’s a location app so there’s bound to be privacy implications. Granted, Facebook have chosen to go down the opt-out route for location privacy, though you still have to physically use the service, but even the most cursory of web searches for “disable facebook places” yields loads of different takes on the same basic set of actions. Cult of Mac and ReadWriteWeb have great write ups, in non threatening, non technical language for how to ensure Facebook Places never sullies your Facebook stream.

Now take a step back, re-read the three points above and substitute, in order, Google’s Latitude, Foursquare’s, err, Foursquare and Yahoo’s Fire Eagle for Facebook Places. Granted the opt-out vs. opt-in approach to location sharing differs substantially (for Latitude, Foursquare and Fire Eagle it’s implicitly opt-in) but we’ve been here before. Many times. A new location sharing service is launched, people get worried due to media coverage and eventually the status quo is restored and everyone gets on with their lives as before, maybe with an additional bit of location richness added, maybe not. It’s worth bearing this in mind before you buy into the latest media coverage which over-uses the phrase “sparks privacy concerns“.

Update 1/9/10 – turns out I’m not the only one thinking along these lines. After I originally posted this, my daily trawl through my RSS feeds uncovered a post from Jonathan Crowe over at The Map Room blog that draws pretty much the same conclusions over Facebook Places as I do.

Written and posted from home (51.427051, -0.333344)

Locating The Next Role; The Yahoo! Years

Looking back at my career over the last 20 or so years, it’s immediately apparent that it’s always been a bit geo. Geophysical seismic survey processing for natural resources (OK, mostly for oil and gas) for Digicon … geo. Setting up operations for ERS-1, the European Space Agency’s first remote sensing synthetic aperture radar satellite … geo and rocket science. Short wave radio frequency planning to enable the BBC World Service to get transmissions into countries who would much prefer the BBC didn’t broadcast there … geo. Deploying the first geo-targeted ad system and rolling out a global place based view of the world internally and to the external developer community for Yahoo! … totally geo. Granted, there were other roles which had no geo context whatsoever but I always seem to keep coming back to this vague and nebulous mixture of place, location, maps and geography that we term geo.

this is who I am, who are you?

Some 4 years ago (actually 3 years and 10 months but let’s round up for the sake of convenience) I wasn’t really looking for a new role, but the opportunity arose to come and lead and engineering team for Yahoo! Now, four years later, it’s time to move onto another role, but more of that in a moment.

When I announced that I was leaving Yahoo! Geo I was taken aback at the reaction that it generated. Let’s rephrase that … I was taken aback, shocked, stunned and very deeply chuffed into the bargain. Techcrunch’s MG Siegler wrote about it under the brilliant headline Yahoo’s Director Of Geo Engineering Locates The Exit. Numerous friends, colleagues and geo-acquaintances offered congratulations and asked where next on Twitter, on Facebook, in blog posts and by the more old fashioned method of email. I didn’t expect any of this reaction, but it’s that reaction that, at least in part, prompted this blog post.

By the way, you shouldn’t believe everything you read in the media about working at Yahoo! It’s been an amazing experience and one I would willingly repeat if I had the opportunity to go back and do it all again. Before I joined Yahoo! I thought I had a pretty good handle on how the internet worked and how web applications and APIs worked. I didn’t but I did learn an awfully large amount from people do.

MacBook Pro and BlackBerry

Outside of the company, there’s also a popular misconception that there’s an uneasy cold war going on between Yahoo! and, in the geo space at least, their immediate competitors; Microsoft, Google, Mapquest and so on. True, there’s some major cultural differences between the organisations but there’s also much mutual respect for what each of our geo neighbours gets up to.

So how were the last 4 years? They went something like this …

The Highs

The Lows

  • People leaving the company as a result of the Microsoft bid; the unsuccessful Microsoft bid, something that never actually happened.
  • Reorganisations and new VPs; far too many of them. Six reorganisations in the space of twelve months and six VPs in the space of four years is too many by my reckoning and meant you spent more time rewriting your strategy than you do actually delivering and shipping product.
  • Teams that ship successful products in spite of the company not because of the company
  • Appearing on the once mighty ValleyWag as the result of a tweet about a wifi point called ‘valleywag’ at a Yahoo! All Hands meeting at the Sunnyvale based Yahoo! mothership.

I might have already mentioned the people at Yahoo! I met and worked with. Now would be a suitable point to mention them by name …

The Geo Technologies team, past and present: Bob Upham, Martin Barnes, Walter Andrag, Mike Dickson, Holger Dürer, Bob Craig, Roman Kirillov, Eddie Babcock, Samira Swarnkar, Rob Halliday, Rob Tyler, Chris Gent, Steve May, Ali Abtoy, Andrei Bychay, Chiho Kitahara

The YDN team: Sophie Davies-Patrick, Chris Heilmann, Anil Patel, Havi Hoffman & Stacy Millman

The Yahoo! alumni: Tyler Bell and Mark Law (ex Geo), Aaron Cope (ex Flickr), Tom Coates and Seth Fitzsimmonds (ex Brickhouse, Fire Eagle and Geo)

No Coffee Today

But now the Yahoo! years are behind me and after taking this week off to rest and do family stuff over the course of the UK Half Term school break I’ll be ready to join my new team and start to get to grips with my new role as Director of Ovi Places with Nokia.

Although it would be very tempting to think that my move to Nokia is in some way a result of the recently announced partnership between Yahoo! and Nokia that’s not the case. Nokia and I started the long conversation which ended with this blog post at the beginning on 2009; it took a while to get to this place.

So whilst I’m going to Nokia, I’ll continue to use my core set of Yahoo! products, tools and APIs … YQL, Placemaker, GeoPlanet, WOEIDs, YUI, Flickr and Delicious. Not because I used to work for Yahoo! but because they’re superb products.

Here’s looking forward to the rest of 2010; it could be geotastic.

Written and posted from home (51.427051, -0.333344)

Curiously Cartographic Creations #3 – The Special Relationship

Odd map of the London Underground? Check. Maps of how Swedes and Hungarians see Europe? Check. Ah … but what about how our neighbours across the Atlantic see the world? You know, the country that has a special relationship with the United Kingdom? I have just the very thing for you. Let’s start with a nice simplified version of the world.

The World according to America

He may no longer be Mr. President but apparently George. W. Bush had a curious grasp of the world’s geography.

The World According to Dubya

Keeping with the theme of President of the United States, this highly colourful view of the world comes from the mind of a Mr. Reagan. Allegedly.

The World According to Ronald Reagan

Photo Credits: irobot00 on Flickr.
Written and posted from the Yahoo! London office (51.5141985, -0.1292006)

Curiously Cartographic Creations #2 – Alternative Maps Of Europe

In the first of this occasional series, I looked at a curiously familiar but not quite right map of the London Underground evilly designed for tourists. In this second part of the series, it’s time to cast out gaze out across the English Channel to Europe and how two of the member states see the European Union.

First there’s how the Swedes see Europe; Britain is characterised by inventing soccer, inventing hooligans and beer (all three of which may be related) amongst others. The other European countries don’t fare much better.

Europe according to the Swedes

Heading South and slightly East is the self styled Chosen Nation of Hungary. While the descriptions are mostly one or two words, they’re not that flattering.  Britain is simply jobs, while other member states are characterised as tourist hordes, pizza, last minute hotels and beer land.

Europe according to the Hungarians

Written and posted from the Yahoo! London office (51.5141985, -0.1292006)