Wikivoyage:Travellers' pub/2011

From Wikivoyage
Jump to navigation Jump to search

The following are archived discussions from the Project:Travellers' pub. They should not be modified.

Am I being obtuse?[edit]

I'm having trouble understanding what an editor wants at Talk:Central_Europe#The_Central.2FEastern_Europe_debate. Comments welcome, maybe someone else can have better time of it. (WT-en) LtPowers 21:21, 3 January 2011 (EST)

OSM export woes [venting][edit]


The load average on the server is too high at the moment. Please wait a few minutes before trying again.

I'm trying to re-use your map tiles in a really productive way! Let me download your tiles! Graaaahh! --(WT-en) Peter Talk 17:00, 23 February 2011 (EST)

Atlanta Regions - request for feedback[edit]

User:(WT-en) BigPeteB has proposed some changes to the regional structure for Atlanta at Talk:Metro Atlanta that would benefit from additional comment from those who either know the area or have some time to examine his proposal. -- (WT-en) Ryan • (talk) • 13:51, 8 May 2011 (EDT)

How to handle information about trains[edit]


I have noticed that the Get in-sections of many cities mostly focuses on air travel and information about rail travel is scarce, I hav been trying to fill in some gaps mostly in Eastern European and Russian cities. I have been trying a few diffrent approches, in some cases adding train numbers and departure times for the most important routes. At other I have only added which cities have direct connections and added travel time in brackets. I think we should try and develop this section a bit more and find some standardised method. See for example Bratislava#By_train or Samarkand#By_train. --(WT-en) Jonas Ryberg 11:15, 29 May 2011 (EDT)

Does Project:Routebox_navigation help? (WT-en) Pashley 19:46, 29 May 2011 (EDT)
Your contributions to both articles look good and useful. All the better if you can add price information and a little more details on trains (for example, do they have sleeper and restaurant cars?). I think instead of forcing standardised sections throughout the entire site, it would be better to run the information given in a section against a subjective usefulness test on a case-by-case basis. And that's easy—think of yourself as a traveller in some distant, foreign land with no information source but article print-outs from Wikivoyage. Would you be satisfied with the information given? – (WT-en) Vidimian 17:20, 3 June 2011 (EDT)

Using Google Analytics[edit]

It is very surprising and shocking that Google Analytics (A 3rd party free and closed source tool) is being used to track user visits on wikivoyage. As a regular user of wikivoyage, I personally would not like to be tracked by Google (or any other company), or let my ipaddress be stored on some remote server which is controlled by Google. Although I understand that Google Analytics is a great tool to visualize user-traffic, it is possible that a significant portion of the visitors are unaware of the fact that wikivoyage uses Google to track their visits. Besides, this raises several other questions such as who is given access to these data ? How can I trust that wikivoyage would protect my privacy/anonymity ? I do not trust Google and certainly wikivoyage should not endorse Google. Wikipedia does not track users through Google Analytics. I suggest that Google Analytics be removed. 06:21, 4 June 2011 (EDT)

As I have no knowledge whatsoever about Google Analytics, I must ask questions before I can have any useful opinion.
  1. How do you know Google Analytics is being used?
  2. Is this something that the Wikivoyage community have any control of?
Cheers • • • (WT-en) Peter (Southwood) Talk 07:18, 4 June 2011 (EDT)
Google Analytics is being used at WT as it is on a huge majority of websites around the world. You can see the Google analytics tracking code by viewing the page source code of the Wikivoyage homepage. We have no control over this - the code is placed on the site by our hosts. It is a very useful tool for any website owner to use to track visitor stats (country, web browser used, how many pages are viewed per visit etc etc etc - it is almost endless). The Google conspiracy theorists out there will not like the presence of this code, but any site that relies on Google generated ad revenue (like WT) would be kind of nuts not to use Google Analytics. --(WT-en) Burmesedays 07:28, 4 June 2011 (EDT)

Admin assistance needed in Finnish Wikivoyage[edit]

It seems that article about Los Angeles in Finnish version of Wikivoyage gets constantly spammed. So far haven't seen any admin activity there. Does someone with power have time to check it out and maybe edit-protect it? Thanks 01:38, 7 November 2011 (EST)

REcaptcha enabled on Shared and all foreign language versions[edit]

See -- enabled as of this morning. Please report any bugginess/effectiveness against spam registrations.--(WT-en) IBobi 19:16, 20 December 2011 (EST)

Rendering failure with Firefox 9.0.1 / Seamonkey 2.6.1[edit]

There are some rendering problems with pre-1.16 MediaWiki-Wikis since the update of Firefox / Seamonkey a few days ago. I solved the problem with Wikivoyage in the following manner:

Seit wenigen Tagen stehen die Updates für Firefox 9.0.1 / Seamonkey 2.6.1 bereit. Jedoch mit einer Überraschung: die Navigationsleiste auf der linken Seite war nach unten verschoben. Ursache hierfür war nicht Gecko, sondern die MediaWiki-Software (in den Versionen 1.11 - 1.13), die noch einen Uralt-Patch für KHTML per Script (wikibits.js) „unsichtbar“ eingefügt hatte. Die einfachste Lösung bestand darin, die einzige Zeile in monobook/KHTMLFixes.css (nämlich #column-content { margin-left: 0; } ) zu löschen. Offensichtlich ist eine Funktion, wohl navigator.taintEnabled mit der neuen Firefox-Version deaktiviert worden, was dazu führte, das Firefox als KHTML angesehen wurde. Die Suche hat jedoch Stunden gedauert. Mittlerweile gibt es einen Bugreport auch bei MediaWiki (, --Roland 08:53, 25. Dez. 2011 (CET)
The problem is not Gecko but the MediaWiki software (at least for the versions 1.11 through 1.13). In that versions an "ancient" CSS patch for KHTML browsers is "invisible" included by the wikibits.js script. The simplest way to solve the problem is to remove the only line in monobook/KHTMLFixes.css, this is #column-content { margin-left: 0; }. I think the problem comes with the function navigator.taintEnabled which gives now false, i.e. it is de-activated. The result of this was that the Firefox seems to behold like KHTML. See also the bug report at --(WT-en) Unger 03:09, 25 December 2011 (EST)
Bug reports of this nature should go on Wikivoyage Shared. (WT-en) LtPowers 15:32, 27 December 2011 (EST)