It's a bug with the caching of diary views which should be fixed now.

It already detects the browser language setting, which is better than using geolocation as it should tell you what that user wants whereas guessing language based on location is really only a very rough heuristic.

Adding a way to manually change language for non-logged in users is on the to do list - the biggest problem is finding space for it in the UI,

There's not much point complaining about MapZen here - it's not something created by the OpenStreetMap project. It's created by a commercial company, CloudMade, so if you have a problem with it you need to talk to them.

Actually in english law a comment can be true and still be libellous. Silly maybe, but still true. Besides which neither you nor I have any way of knowing if the comment was true.

As to copyright, are you claiming that his emails were you were not sufficiently creative to gain copyright protection? or that by emailing you he somehow gave you a license to publish his creative work?

As to that other diary entry it appears to have been edited so I can't tell what it originally said but my memory is that it didn't identify what it was referring to. If there's anything still there that you object to then I will be happy to consider removing it.

It was removed by me because the original post arguably breached copyright and several of your later comments were potentially libellous. I had every intention of sending you a message to say why I had removed but I just hadn't had time yet.

To be precise, and assuming that "exclude" does mean close/delete, then the policy is detailed here:

osm.wiki/FAQ#How_can_I_close_my_account.3F

Do you really think it's appropriate to be doing large, poor quality imports of data sets of dubious quality and relevance without consulting the local community? I certainly don't...

Did you actually consult with the US community at all before importing all this data?

It was news, two weeks ago, when it was actually announced. It's also unclear if the government know what they're talking about as the data in question is not OS data yet the announcement was part of the OS data announcement.

Yes, pings (and most other things besides normal web traffic) are blocked at the boundary of the network that hosts our servers.

Are you completely insane?

Actually http://trac.openstreetmap.org/roadmap means precisely nothing as none of the milestones in trac have any meaning or correspond to anything at all - no idea who set them up but we certainly don't use them.

The markup is just HTML so no need to go looking at any source ;-) It will be sanitised so some things may not work but basic markup should.

Please don't "tag for the renderer" by adding reference numbers to the name - tag the data (which is our primary asset) correctly and then wait for the renderers to catch up and get cleverer about rendering things. They are improving all the time you know!

Adding URLs to images as tag values is certainly not supported by any renderers as far a I know, and quite likely never will be as it's a path to abuse. I realise there is an issue in countries like the US where it is common to have lots of different shield styles and people expect to see them on the map but we need a better solution than taking URLs from the tag data.

You find find http://api.openstreetmap.org/api/0.6/way/$WAY/full a bit simpler ;-)

Agree with Richard. I live about a mile from the A10 and know full well that it is not trunk in UK government terms, but it is trunk in OSM terms so please leave it alone.

Importing POIs from wikipedia is generally considered to be a bad idea due to the way much of wikipedia's geodata has been sourced - some of it at least is believed to have been derived from sources like google maps. See this recent mailing list thread for a discussion of the issue:

http://www.nabble.com/Wikipedia-POI-import--to23392791.html#a23394016

Jenny didn't have prawns - she had the Whitebait (http://en.wikipedia.org/wiki/Whitebait).

IE6 should be working again now.

Changing the language of a diary entry after it was written was not working due to a bug which I have just fixed.