Wikivoyage:Travellers' pub Voyage Tips and guide

Welcome to the pub

Shortcuts:
WV:Pub
WV:TP

Contents

The travellers' pub is for general discussion on Wikivoyage, and the place to ask questions when you're confused, lost, afraid, tired, annoyed, thoughtful, or helpful. To start a new topic, click the "Add topic" tab, so that it gets added at the bottom of the page, and sign your post by appending four tildes (~~~~)

Before asking a question or making a comment:

• Have a look at our Help, FAQ and Policies pages.
• If you are a new user and you have any questions about using the website, try the Arrivals lounge.
• If you have a question or suggestion about a particular article, use the article's talk page to keep the discussion associated with that article.
• If you'd like to draw attention to a comment to get feedback from other Wikivoyagers, try Requests for comment.
• If you are wanting travel advice on a specific matter see the tourist office.
• If you have an issue you need to bring to the attention of an administrator, try Ongoing vandalism.
• If you are having a problem that you think has to do with the MediaWiki software, please post that on Phabricator instead.
• If you want to celebrate a significant contribution to Wikivoyage by yourself or others, hold a party at Celebrate a contribution.
• Discuss issues related to more than one language version of Wikivoyage in the Wikivoyage Lounge on Meta.
• Anything that is Nigeria-related is now meant to go in the Nigeria café instead. Anything that is Kosovo or Albania related is now meant to go in the Kosovo and Albania café instead. This includes announcements, initiatives, celebrations, and issues with certain articles.

You can review old Pub discussions in the Wikivoyage:Travellers' pub/Archives.

Pull up a chair and join in the conversation!

Click here to start a new thread

It's been a while since I've posted anything major on the pub, but one of the things I'm quite pleased with the way we do things here is the fact that we are very open and accommodating to users who can't speak or speak English with a large length of difficulty. We don't have any policies forcing the use of English in discussions and if someone has shown a genuine interest in the project, it isn't unorthodox for someone to go out of their way and respond in another language they know on this site.

It comes back to when @Andyrom75: told me on itwikivoyage (around when itwikivoyage hit 10k articles, iirc) that it's possible to contribute to Wikivoyage without really knowing the language – and it's true. Most of my activity on itwikivoyage has since been doing minor fixes, adding listings with no description (since you don't need to know the language to add listings, opening hours, urls, address and such), removing closed businesses/out of date info, fixing dead links and the like. Since many of our articles also follow a similar structured format, it's very easy to contribute to the site so long as you're aware of your limitations.

Some ideas I had in mind to perhaps make this wiki even more inviting to those who might not have the English skills necessary to contribute text but still want to help:

• A community written guide on this, similar to Wikivoyage:Welcome, business owners, Wikivoyage:Welcome, locals or Wikivoyage:Welcome, Wikipedians
• Finish User:SHB2000/admins table, move to the Wikivoyage namespace, add the table to Wikivoyage:Administrators, and add any advanced perms from other WMF projects.
  • Perhaps also make a similar table for non-admins who are reasonably active on this site.

More thoughts and ideas would be appreciated – even better if we can facilitate this on other language Wikivoyages.

//shb (t | c | m) 10:11, 4 June 2025 (UTC)Reply

Contribute in another language version of Wikvoyage it's just a matter of willingness and time. For a certain amount of time. For few years I've supported sv:voy without knowing any word in Swedish :-D Nowadays unfortunately I don't have enough time, so I can only concentrate it on it:voy :-(

PS your support on it:voy @SHB2000 is always extremely appreciated! :-) Andyrom75 (talk) 17:14, 4 June 2025 (UTC)Reply

I occasionally do the same kind of thing at the Haitian Creole Wikipedia. I can't write in the language, but I can check a maintenance category and fix the wikitext errors there.

Based on my experience, I'd say that there are two main opportunities for contribution:

• 'technical' contributions, such as fixing wikitext or broken URLs
• language-agnostic contributions, such as adding phone numbers, websites, and lat/long coordinates to listings; adding images that require no caption or only a simple/obvious one (e.g., "Disneyland" or "Town Name Church"); removing listings for closed restaurants, etc.

@Piotrus might have some ideas about which tasks are easiest for his English-language learners to do. WhatamIdoing (talk) 22:48, 4 June 2025 (UTC)Reply

Yeah this very much explains it in a nutshell. :) //shb (t | c | m) 23:13, 4 June 2025 (UTC)Reply

@WhatamIdoing Indeed, some of my ESL students have effectively only a beginner level of English at best. These days, machine translation is getting good enough to understand a lot, and contribute text that's "mostly ok". It will only get better as AI tools and student use of them improve. Anyway, you can see my activities for students at User:Hanyangprofessor2 Piotrus (talk) 01:12, 5 June 2025 (UTC)Reply

I have added images that I have taken to many different language variants of Wikipedia. I use Google translate for the text and and hope that a native user if that language will make any corrections. Martinvl (talk) 11:22, 5 June 2025 (UTC)Reply

I recently added a listing about Japan in ja.voy despite not knowing Japanese. The listing editor really makes it simple to improve an article. Last week I presented a Wikidata talk about Listing Editor and mentioned that it's a really good gateway to get more contributors. OhanaUnited^{Talk page} 15:58, 5 June 2025 (UTC)Reply

The Listing Editor really does! Particularly because they're very standardised across most language Wikivoyages, so the only "bad" listing editor is a malfunctioning/broken listing editor. //shb (t | c | m) 02:27, 21 June 2025 (UTC)Reply

Created a draft at Wikivoyage:Contributing with little to no knowledge of English – now that I have more time on my hands this week, I will try developing the page based on what has been mentioned in this discussion. //shb (t | c | m) 08:53, 4 July 2025 (UTC)Reply

Wikivoyage is a travel guide and not intended to be a collection of biographies. Still, travel topics and itineraries might mention important individuals, such as explorers, artists, monarchs, and politicians. Wikivoyage:What is an article? discourages from creating an article for a living celebrity, as these are more difficult to finish than articles for Christopher Columbus, Frank Lloyd Wright or Astrid Lindgren. Articles such as Presidents of the United States and Monarchy of the United Kingdom describe living individuals who have not concluded their careers, and they are certainly controversial. When writing Jewish Stockholm tour, Stockholm environmentalist tour and Nordic monarchies, a couple of famous living people came to mind, but I found it advisable to mention them as briefly as possible. Which general principles should we follow? /Yvwv (talk) 12:58, 9 June 2025 (UTC)Reply

It looks like foundation:BLP encourages us to have a formal policy, even if there isn't much to say. Project:Don't be evil, maybe?

We already have Wikivoyage:Photographs of identifiable people and Wikivoyage:Image policy#People in photos, which discourage photos of people. WhatamIdoing (talk) 20:36, 9 June 2025 (UTC)Reply

I'd support a policy for the same reason. //shb (t | c | m) 11:40, 11 June 2025 (UTC)Reply

I think this is largely not that relevant to a travel guide, but it is actually common to have "Maps of the Stars" or tours of celebrity homes in the Los Angeles region, which to me is completely crazy and behavior that should not be encouraged. Considering Whatamidoing's point about the WMF encouraging this kind of documentation, I think having a guideline/policy is wise. Good thinking. —Justin (koavf)❤T☮C☺M☯ 21:00, 9 June 2025 (UTC)Reply

Yeah, I would absolutely oppose any article for a tour that takes people to the homes of celebrities who would rather be private in their own homes. If this kind of tour existed in New York, New Yorkers would be up in arms about it and pressing the City Council to pass a law about it. Ikan Kekek (talk) 21:35, 9 June 2025 (UTC)Reply

The page and section about photos say very little, mostly discouraging photos of yourself, which isn't what this is about. says a lot more and should probably be followed also regarding locally uploaded pictures. None of those three says anything about text about people (other than that captions shouldn't be defamatory).

I think we probably shouldn't write a policy unless there are real issues. We have no reason to write about most people, and it seems common sense, like what Yvwv showed above, works reasonably well. Writing a policy opens up for loopholes and wikilawyering.

–LPfi (talk) 21:50, 9 June 2025 (UTC)Reply

I wonder if our "BLP policy" could be a section in our existing Wikivoyage:Be fair policy. Basically, a few principles about avoiding mentioning individuals, and especially avoiding saying anything contentious or unfairly invading their privacy. WhatamIdoing (talk) 16:40, 10 June 2025 (UTC)Reply

That sounds reasonable. In the past I have opposed a suggestion to create an itinerary based on the travels of a living individual.

A more common situation is where a listing mentions something about the people that work in the hotel or restaurant. "Friendly owners" or "poor service from the waiters" is ok, but referring to staff by name needs more care. AlasdairW (talk) 23:04, 10 June 2025 (UTC)Reply

It's surely OK when the name of the Chef de Cuisine or Pastry Chef are printed on menus or are well-known chefs the restaurant promotes. Ikan Kekek (talk) 23:40, 10 June 2025 (UTC)Reply

Can an artist's personal life be separated from their work? At least, death is useful to conclude a life story. As Georg Riedel past away one year ago, he deserves to be described in the Jewish Stockholm tour. Aleksander Wolodarski is another person appropriate to mention, but as he is well and alive (and to some degree a divisive character in Swedish architecture) the description of him in the same article is very brief. The Harry Potter tourism barely mentions the author, and that might be good as it is. /Yvwv (talk) 10:16, 11 June 2025 (UTC)Reply

I think it would be fine to note the name of a celebrity chef ("Thomas Keller's restaurant, The French Laundry"), or even a relatively public non-celebrity ("The restaurant owner, Mary Smith, is also the long-time mayor of this small town" or "Olly Owner is happy to pack a picnic upon request").

However, as an extension of Wikivoyage:Avoid negative reviews, we don't really want "Chris Celebrity is pretentious and their restaurant is overpriced" or "Wendy Waitress is unfriendly and slow". WhatamIdoing (talk) 17:26, 11 June 2025 (UTC)Reply

I think we should avoid "Wendy Waitress is unfriendly", but "Some staff are unfriendly" is ok. It is important to report negative aspects of a place if either it is balanced by "excellent cooking and wonderful bread" or it is the only place in town. It becomes more difficult with one person businesses. AlasdairW (talk) 20:24, 11 June 2025 (UTC)Reply

Wikivoyage should not be interested in people: that is the province of Wikipedia. Wikivoyage is however interested in places associated with people and to this end should be cautious about their privacy. If however the individual concerned invites members of the public to their homes or businesses (for example Donald Trump has a website for Mar-a-Lago) then it is no longer Wikivoyage's role to protect his privacy: if he publicises his home, then it is incumbent on him to look after his own privacy. In contrast, Joe Biden does not appear to advertise his home, so neither should Wikivoyage (even if a search on the internet will reveal Joe Biden's properties).Martinvl (talk) 15:18, 12 June 2025 (UTC)Reply

Does something like this feel about right?

----

As a general rule, Wikivoyage is interested in places, not people. Occasionally, providing a fair description will involve mentioning a specific person. In such cases, these principles apply to protect living people:

• Avoid contentious matter about living people to the maximum extent possible, to show respect for human dignity and personal privacy. Publishing personal information that is tangential to the needs of the article, trivial, ephemeral, or constitutes a negative review is unfair. For example, if a restaurant owner promotes dubious beliefs to customers, then omit the listing completely rather than writing about the owner's beliefs.
• Avoid whole articles focused on living people, such as an itinerary to see the private homes of celebrities. It is fair to have an itinerary focused on Taylor Swift's concert tours; it is not fair to have an article focused on her homes.
• Individual listings that name a living public figure are acceptable so long as the content is not contentious. However, you should avoid naming living people when a general description is adequate. For example, write "The owner is happy to talk about local history" instead of "Harry Historian, the owner, is happy to talk about local history", even though you would name the celebrity chef Thomas Keller as the owner of the restaurant The French Laundry.

----

What should be changed, added, omitted? WhatamIdoing (talk) 16:39, 12 June 2025 (UTC)Reply

Thanks for offering a rough draft! The one part that sticks out to me as problematic is the part about "dubious beliefs," which gives an opening to intolerant atheists to complain about a bismillah or cross in a restaurant. Ikan Kekek (talk) 17:12, 12 June 2025 (UTC)Reply

I was thinking about political beliefs, and specifically about an anti-masking restaurant I read about during the pandemic, but you're right: That needs to be re-worded. WhatamIdoing (talk) 23:30, 12 June 2025 (UTC)Reply

Still a good start, I'd say. //shb (t | c | m) 12:15, 13 June 2025 (UTC)Reply

I don't think that businesses should be removed because of beliefs of the owner or personnel; that the owner touts antivacc or flat-earth theories might be entertaining rather than a reason to avoid them. One might tell that they might raise controversial topics. For dangerous practices, such as not using masks when needed, that would be treated like them using contaminated water or whatever. Yes, sometimes that warrants removing the listing in line with no bad reviews, but that has little to do with privacy.

For a Finnish business, it was suggested that the listings be removed because of bigotry, in effect a boycott by Wikivoyage. I am not sure about to what extent to do that, but I assume we might tell something about the owner in that case, if we leave the choice whether to use their services to our readers. I would oppose individual editors removing listings because of views that don't conform with their own, but they may of course choose not to add them.

–LPfi (talk) 12:28, 13 June 2025 (UTC)Reply

I think there might be a spectrum of issues, but some types of (e.g.,) bigotry are not compatible with Wikivoyage:The traveller comes first. Inclusion constitutes a recommendation, at least when there are other alternatives. If we list a restaurant, it should be because travellers are welcome. If the restaurant's listing would need to have a disclaimer along the lines of "BTW, only white people are allowed to eat here" or "People whom the owner thinks look Jewish/Muslim/Black/gay/trans will be refused service", then that restaurant shouldn't be included in Wikivoyage at all. Listed restaurants should normally be open to all of the general public.

On the other end of the spectrum, if the owner cheerfully accepts all customers, but he privately belongs to a racist organization, then that's not really relevant to the travellers' experience, so we needn't mention that. Travellers who want to patronize only businesses owned by people who share the same politics/religion/race/sexual orientation should look elsewhere for that information.

Somewhere in the middle is factual information that travellers may interpret in opposite ways. For example, if a given deli in New York City is kosher, it'd be worth noting that in the description. Most travellers won't care. Some travellers will prefer it (either for religious reasons or because kosher meat is considered more ethical than conventional meat). Some travellers will reject it. But knowing that it might appeal (or not) to different travellers is not the same as different travellers not being allowed to eat at the deli. WhatamIdoing (talk) 20:02, 13 June 2025 (UTC)Reply

I see no problem in describing a restaurant in terms of the religious beliefs that it portrays provided that it is done in a neutral manner - for example , "The XYZ resaurant is a kosher/halal/vegetarian establishment". The reader can then make up their ow mind about patronising the establishment - after all Wikivoyage has many articles about various places of worship. Martinvl (talk) 21:05, 13 June 2025 (UTC)Reply

I think the general point is that we want "XYZ is a kosher/halal/vegetarian restaurant" but not "The owner of XYZ is a Jew/Muslim/vegetarian person". WhatamIdoing (talk) 17:10, 14 June 2025 (UTC)Reply

I agree here. //shb (t | c | m) 06:56, 18 June 2025 (UTC)Reply

• Suggested rewrite of the first point (Changes in bold):

"Avoid contentious matter about living people to the maximum extent possible, to show respect for human dignity and personal privacy. Publishing personal information that is tangential to the needs of the article, trivial, ephemeral, or constitutes a negative review is unfair. For example, if a restaurant owner promotes particular beliefs to customers, then omit the listing completely rather than writing about the owner's beliefs. If however the establishment itself caters for certain beliefs and/or ethics, it is reasonable, or maybe even desireable, to add those beliefs/ethics to the description in a neutral manner - such as including the words "kosher/halal/vegetarian" to the establishment's description." Martinvl (talk) 21:14, 13 June 2025 (UTC)Reply

• I suggest that the second point be extended as follows (additions in bold):

Avoid whole articles focused on living people, such as an itinerary to see the private homes of celebrities. It is fair to have an itinerary focused on Taylor Swift's concert tours; it is not fair to have an article focused on her homes. However, if the celebrity concerend advertises their home to the general public (for example Mar-a-Lago, home of Donald Trump or Blenheim Palace, home of the Duke of Marlborough) , then it is perfectly in order to mention the home in an article and ideally to include a web address the description or article.

Martinvl (talk) 21:27, 13 June 2025 (UTC)Reply

I think all this discussion of beliefs and politics is bad and not something about which we want policies. Also, bad reviews are by no means inherently unfair, and I'm mystified by how anyone could think that's the case; it's just that Wikivoyage chooses with some exceptions to simply refrain from listing businesses, rather than stating that they are bad. I also don't see why we would need to add a policy that establishments that discriminate against people based for example on their ethnicity, appearance or national origin, such as a historic restaurant in Düsseldorf that refused admission to East Asians early in the pandemic, be delisted, because we already do that based on preexisting policies. Right now, I think that based on the drafts circulated in this thread, we risk approving a new policy that is worse than none. Ikan Kekek (talk) 21:40, 13 June 2025 (UTC)Reply

It might be best to try the smallest possible addition. After all, it's usually easier to get a policy expanded later if we really need it, than to get it shortened later. WhatamIdoing (talk) 17:08, 14 June 2025 (UTC)Reply

Here's a shorter version:

----

As a general rule, Wikivoyage is interested in places, not people. Occasionally, providing a fair description will involve mentioning a specific person. In such cases, these principles apply to protect living people:

• Avoid contentious matter about living people to the maximum extent possible, to show respect for human dignity and personal privacy. Individual listings that name a living public figure are acceptable so long as the content is not contentious.
• Avoid whole articles focused on living people, such as an itinerary to see the private homes of celebrities.

----

We could also soften "the maximum extent possible". It's always "possible" to avoid mentioning anyone's name, but it's not always "reasonable" to do so. WhatamIdoing (talk) 17:14, 14 June 2025 (UTC)Reply

What about the article on U.S. presidents? We don't avoid contentious facts about living current and former presidents; we just agree on what should be in the blurbs about them based on the existing Wikivoyage:Be fair guidelines. I still fail to see how adding at least your first proposed guideline will improve anything. Also, are we creating a solution for a nonexistent problem? Can you cite a previous example of an article that had unnecessarily contentious facts about living people that we were not able to deal with by using existing guidelines? Ikan Kekek (talk) 07:33, 17 June 2025 (UTC)Reply

Presidents of the United States is not a "whole article focused on living people"; it is a whole article focused on mostly long-dead people with just five living US Presidents being mentioned (and mostly in a "public museum" way, not a "current private home" way). This would therefore be acceptable as a case of "Individual listings that name a living public figure" that "show respect for human dignity and personal privacy".

The existing problem to be solved is: The Board of Directors for the WIkimedia Foundation said that every project needs to have an official, written BLP policy. They said this about 16 years ago, so we're running a bit behind schedule, but we should have something. Their resolution encourages "special attention to the principles of neutrality", so I think putting a few sentences inside our version of the "NPOV" policy would be appropriate. We could even create a WV:BLP shortcut to it, so the Wikipedia folks can find it easier. WhatamIdoing (talk) 17:16, 17 June 2025 (UTC)Reply

My problem is not with your second proposed provision, which is fine, but your first, and that's what my last reply addressed. If it stated that when living people have to be mentioned, we must be fair and come to a consensus about anything contentious, I'd be happy. Ikan Kekek (talk) 17:33, 17 June 2025 (UTC)Reply

Can you think of any contentious or derogatory information a travel guide – especially one that does not cite external sources – needs to include? WhatamIdoing (talk) 17:37, 18 June 2025 (UTC)Reply

I already gave you an example! And what about when we fairly describe countries as dictatorships? We've sometimes had users object and try to whitewash articles, and in such cases, we are armed with Wikivoyage:Be fair, not some ridiculous claim that anything "contentious" is bad and must be avoided, which would have played into their hands. Wikivoyage is a travel guide, not a site that tries to be neutral. We expressly don't have an NPOV policy, but instead a policy that requires fairness. Ikan Kekek (talk) 18:10, 18 June 2025 (UTC)Reply

I agree that we can fairly describe a country as being a dictatorship. Do we need to describe an individual living person as a dictator, when doing so would be contentious (e.g., produce disputes and disagreements on wiki)? I just checked every article containing the words "a dictator" and "the dictator"; none of them refer to living people.

If your prior example was "What about the article on U.S. presidents?", I've already answered that question. I don't see anything privacy-invading in Presidents of the United States, and I don't see anything contentious about any living person in there, either. The contents are not universally approved by the campaign team, but nobody actually disputes or "contends" over the facts (e.g., that Clinton was involved in a sex scandal, or that Trump is technically a convicted felon). WhatamIdoing (talk) 01:07, 20 June 2025 (UTC)Reply

If you haven't had the misfortune of speaking with a Trumper lately, consider yourself lucky. There are tens of millions of hard-core Trumpers in the U.S. who don't accept basic scientific facts and advance all kinds of conspiracy nonsense as truth. I dealt with a cabbie in New Rochelle yesterday who gratuitously started talking about politics. He claimed Biden already had cancer 4 years ago, and "they" covered it up, that claims of fossil fuels causing global warming are "bullshit" and that if the Democrats had been elected last year, we'd all be driving electric cars already, among other things. So I very much contest your confident assertion that statements of fact about Trump, Biden, Obama, etc. are not "contentious". We need to remove that word from consideration as something Wikivoyage cannot be. Do you remember years ago when there was someone who spent a couple of weeks or more trying to whitewash descriptions of Cuba by claiming that it was really a democracy, their elections are really free and fair, and the Communists have never been dictators or oppressed anyone there? Or the ones that claimed that China is a democracy and it was the U.S. (pre-Trump) that was really oppressive (the latter of which of course has never been completely false, but that was entirely beside the point in a travel guide as well as being pure whataboutism that disproves nothing). We've had all kinds of politically motivated contentions against facts. That's why our standard is Wikivoyage:Be fair, not "Wikivoyage/Avoid saying anything anyone could argue with", which is what "contentious" means or would mean in the hands of anyone who wants to use a travel guide to grind an axe, rather than to improve a resource for travelers. Ikan Kekek (talk) 02:14, 20 June 2025 (UTC)Reply

I agree with Ikan. I was brought up in South Africa during the Apartheid era. Had Wikivoyage been around at that time, would we have deleted everything about South Africa on grounds that almost every establishment was required by law to practice racial discrimination? I do not think that would not have been appropriate. However I think that it would have been appropriate to include a section on how to navigate the country's racial policies. Martinvl (talk) 22:22, 5 July 2025 (UTC)Reply

Since yesterday (and possibly earlier), the images in listings can be viewed in the dynamic map but trying to click on it to go to the full description page will lead to a broken link if they are in a city district page. This raises the issue on image attribution. You can test it on any listings with images at Queens/Flushing-Northeast and Toronto/Etobicoke. Anyone have insight on what recent changes broke this functionality? OhanaUnited^{Talk page} 15:46, 12 June 2025 (UTC)Reply

Yes, needs to be fixed. For some reason, the File: prefix is prefixed by the district name. I try to check Module:Listing for the bug. –LPfi (talk) 11:52, 13 June 2025 (UTC)Reply

Oops, the city name, not the district. Seemingly the article name is included in the image argument, and removed, but not properly so for subarticles. Module:Marker is possibly more relevant than Listing, but it is some underlying functionality that is the culprit. My understanding of how modules work is too weak for me to find it. –LPfi (talk) 12:10, 13 June 2025 (UTC)Reply

The marker on the map seems to be constructed using mw.text.jsonEncode. Where can one read that code? Was there some change recently? –LPfi (talk) 08:30, 30 June 2025 (UTC)Reply

[split off as suggested by OhanaUnited 02:39, 30 June 2025 (UTC). –LPfi (talk) 08:17, 30 June 2025 (UTC)]Reply

The images embedded within listings are often not the best currently available. They don't display unless you click and faff about, so they don't enhance the page appearance encountered by the general reader. Wouldn't it be neat if there was some repository of images that were the best available copyfree, that could be simply incorporated into the page layout? We'd be sure to use those instead, right? Grahamsands (talk) 20:20, 15 June 2025 (UTC)Reply

The main problem with that is that somebody needs to pick those best available images. That's done in Commons' galleries, where images uploaded in the last dozen years aren't included. We could use the image on Wikidata, but they might not be chosen according to what they are like as thumbnails. Perhaps a specific wikidata property could be created for thumbnail images or even Wikivoyage thumbnail images (like for our banners). About having to click several times, that could be improved, but we don't want clutter, so some discussion is needed on the trade-off if we want to change the status quo. –LPfi (talk) 18:33, 17 June 2025 (UTC)Reply

Picking those best images and considering how best to display them is exactly what editors should do, same as picking the best attractions or accommodations to list in a town, we shouldn't lazily accept what's already on the page. It's hardly an onerous task, and we want the best for our readers. Grahamsands (talk) 19:00, 17 June 2025 (UTC)Reply

Maybe we can take assistance from AI tools to ease out the problem, just like we sometimes use AI to pick the best attractions to visit, and choose the appropriate accommodation. Sbb1413 (he) (talk • contribs) 19:07, 17 June 2025 (UTC)Reply

I haven't heard about us letting such decisions to AI, and I'm not sure we should do it with images. But regardless of what way the images get chosen, it would be good if the choice were saved at Wikidata, to be used automatically. As the images aren't shown in the article itself, the less effort we need to use choosing, the better. –LPfi (talk) 19:55, 17 June 2025 (UTC)Reply

How much effort do we need to save here? The first example cited was Queens / Flushing. That page is under-illustrated, with one strong image and two so-so. It took me 10 min to find six more good images on Commons, about the right number for a page of this length. Inserting them might take 3 mins apiece, say 20 min, which I'm not volunteering to do as the entire page needs updating, a solid day's work. Grahamsands (talk) 21:07, 17 June 2025 (UTC)Reply

Choosing images sounds like a task that some people would love to do. Maybe we could advertise it better? It's even a task that people who don't speak English well should be able to do. WhatamIdoing (talk) 17:40, 18 June 2025 (UTC)Reply

It could be a good task, but I have seen a lot of image adding that isn't optimal: ignoring our guideline of Minimal use of images, trying to illustrate individual listings instead of the article as a whole, writing captions to that effect, and placing the images in ways that suite the editor's browser window rather than conform to best practices.

Increased advertising of this activity should thus be done cautiously, to avoid frustration both among those adding images and those patrolling.

The original issue was about images for the dynamic map, which is different from illustrating the article.

–LPfi (talk) 07:00, 19 June 2025 (UTC)Reply

As a side note, Wikivoyage:Image policy#Minimal use of images probably needs both a little re-writing ("1 image per screen": Whose screen size?) and some reconsidering, as availability of internet access has generally improved since then (the last significant update was in 2018, based on a discussion started in 2016).

But I agree that it's a tangent for the current thread. WhatamIdoing (talk) 01:18, 20 June 2025 (UTC)Reply

How carefully did you read Minimal use?

"1 image per screen (1,000–2,000 bytes)"

I suppose you want to suggest an increase in the number of images we should use, and if so, do that at Wikivoyage talk:Image policy. But keep in mind that the mobile interface sucks and the site is still better viewed on a computer. I would be likely to oppose any change in the language, as there is flexibility to use more images than stated in the guideline as long as there isn't an unbroken stream on the left side; images left, right and center; or images that go below the end of the article, which looks terrible. Ikan Kekek (talk) 02:19, 20 June 2025 (UTC)Reply

I read that, and I wondered which method we're using to measure "1,000 bytes". One screenful – edge to edge, top to bottom, on my laptop, with my font, my size (larger than default), my zoom (120%), etc. – is right around 2000 characters for me, but others may have half that, or four times that. Shorter lines (e.g., using only half the line at the end of a paragraph, or a short item in a list) adds volume without adding characters.

If we're using the file size, then wikitext and URLs add bulk to the file without affecting the screen size. We could have "1,000 bytes" and have a half-full screen (on my laptop) or "2,000 bytes" and still have a half-full screen. WhatamIdoing (talk) 20:41, 20 June 2025 (UTC)Reply

These are rough estimates. An A4 with 67×47=3150 is quite close to 2k, if there are images, headings and paragraph breaks, probably much less if there are lists. I suppose an A4 is close to readability optimum (my browser and Emacs windows are not far off). My mobile phone seems to have 50×33=1650, perhaps 1k with images etc. The numbers don't seem to be too far off. Without prescribing a test with some specific browser window size, we cannot give precise advice. LPfi (talk) 14:16, 22 June 2025 (UTC)Reply

From your estimate, the numbers appear to be off by 50%. 3150 = would be "quite close" to 3K, not 2K.

I think that a more practical suggestion would be: Every well-developed section should usually have one image, so long as this can be done without the images dropping down into the next section. On desktop, this usually requires a minimum of 10 to 12 lines of text per landscape image. Very long sections can have two images.

This would address the wikitext-vs-displayed problem and the difference between a solid paragraph and a long bullet list with one or two words on each line.

But as we noted above, this is a separate discussion from the original concern. WhatamIdoing (talk) 17:15, 22 June 2025 (UTC)Reply

Can we take the "select the best picture" conversation into a sub-section? My original intention of this post is to report a bug which leads to the legal issue of image attribution. OhanaUnited^{Talk page} 02:39, 30 June 2025 (UTC)Reply

While the Commons bot that alert us to images about to be deleted was revived, images are still being deleted without notification, namely those (I assume), that were nominated before 4 May. The issue was told in the linked announcement, but I did not realise its implications. So, expect some imgages to be removed with no notification on the talk page. If they might be valuable, they should be temporarily restored for local upload, like when the bot wasn't working. –LPfi (talk) 11:51, 13 June 2025 (UTC)Reply

More languages • Please help translate to your language

Hello all,

The call for candidates for the 2025 Wikimedia Foundation Board of Trustees selection is now open from June 17, 2025 – July 2, 2025 at 11:59 UTC [1]. The Board of Trustees oversees the Wikimedia Foundation's work, and each Trustee serves a three-year term [2]. This is a volunteer position.

This year, the Wikimedia community will vote in late August through September 2025 to fill two (2) seats on the Foundation Board. Could you – or someone you know – be a good fit to join the Wikimedia Foundation's Board of Trustees? [3]

Learn more about what it takes to stand for these leadership positions and how to submit your candidacy on this Meta-wiki page or encourage someone else to run in this year's election.

Best regards,

Abhishek Suryawanshi
Chair of the Elections Committee

On behalf of the Elections Committee and Governance Committee

[1] https://meta.wikimedia.org/wiki/Special:MyLanguage/Wikimedia_Foundation_elections/2025/Call_for_candidates

[2] https://foundation.wikimedia.org/wiki/Legal:Bylaws#(B)_Term.

[3] https://meta.wikimedia.org/wiki/Special:MyLanguage/Wikimedia_Foundation_elections/2025/Resources_for_candidates

MediaWiki message delivery (talk) 17:44, 17 June 2025 (UTC)Reply

I haven't had the time to fully look into it and I've been quite busy IRL this month, but it seems we have a new copycat site called https://www.localcityguide.net/. It mirrors Wikivoyage pages word-for-word with "2022 © Local City Guide. All rights reserved." and some pages like Itineraries ([1]) do nothing to even remove mentions of Wikivoyage. What's interesting about this site is that they've listed those behind the site so openly in the About us section – I'm not sure how accurate it is, but it could be something to go off. What are the WMF's protocols when a site copies an entire project and what can we do about it? //shb (t | c | m) 08:59, 18 June 2025 (UTC)Reply

It has a nice presentation, a handful of blog entries posted in June 2022, and it looks like the foundation of the site is our stuff, refreshed regularly. (Changes I made yesterday already appear.) There is no ability to edit articles. Ground Zero (talk) 10:11, 18 June 2025 (UTC)Reply

This is against the terms of service, CC license restrictions, and American copyright law. You should contact the Legal Team via email at legal[little-anarchy-symbol]wikimedia[point]org. —Justin (koavf)❤T☮C☺M☯ 10:22, 18 June 2025 (UTC)Reply

I picked an arbitrary page of which I have knowledge, but which is not on the average tourist itinerary, Estcourt. It has an outline status. I clicked on "outline" and the first sentence read:

"An outline article is a status rating for any article in Wikivoyage ... " [My emphasis].

This is proof that they are copying the WIkivoyage site. Martinvl (talk) 16:00, 18 June 2025 (UTC)Reply

It seems that the contents are incorporated by a script directly from Wikivoyage similar to the html frame technology that's why the articles are up-to-date. I made a small change in some status ratings of the German Wikivoyage, and immediately you can read that this is a usable Wikivoyage article in the footer. --RolandUnger (talk) 17:24, 18 June 2025 (UTC)Reply

Copying Wikivoyage's contents is okay. However, you have to provide "reasonable" attribution. That's usually done with something like a simple link to the original article on Wikivoyage. I don't see Wikivoyage mentioned on their website, so they need to fix that – but remember that the goal is for them to fix it, not to punish them or prevent them from sharing our information.

w:en:WP:BACKWARDSCOPY has some advice on how to contact websites that haven't complied with the license terms. WhatamIdoing (talk) 19:27, 18 June 2025 (UTC)Reply

I have sent the developers of the site an email about this. //shb (t | c | m) 02:38, 21 June 2025 (UTC)Reply

I've also forwarded it to WMF legal (cc Koavf). //shb (t | c | m) 02:40, 21 June 2025 (UTC)Reply

Merci. —Justin (koavf)❤T☮C☺M☯ 02:52, 21 June 2025 (UTC)Reply

15 days later and no response. Sigh... :/. //shb (t | c | m) 06:50, 6 July 2025 (UTC)Reply

As expected from copycats. They can't even attribute us for providing free content. Veracious (talk) 09:55, 14 July 2025 (UTC)Reply

Some input at Wikivoyage talk:Naming conventions#Disambiguators for Mexican destinations would be appreciated. //shb (t | c | m) 13:41, 19 June 2025 (UTC)Reply

It looks like Thailand just lost its crown to Malaysia, at least for Q1 2025. Should we update our articles to reflect that, or should we wait and see if Malaysia can sustain its lead? The dog2 (talk) 16:11, 23 June 2025 (UTC)Reply

@The dog2: I think you should update the articles to say that both Thailand and Malaysia are the most visited countries of SE Asia, along the lines of, "Thailand, along with Malaysia, are...", "Malaysia, along with Thailand, are..." or even "Malaysia and Thailand are...". Sbb1413 (he) (talk • contribs) 17:11, 23 June 2025 (UTC)Reply

I think we should wait till yearly figures are available before changing anything. Too many things can change from one quarter to the next. Ikan Kekek (talk) 19:52, 23 June 2025 (UTC)Reply

Agreed – one quarter might not be a true reflection. //shb (t | c | m) 00:24, 24 June 2025 (UTC)Reply

I have added a static map in Maharashtra, but it disappears without showing a dynamic map when I click/press the link "switch to interactive map". Same happens in West Bengal, Andhra Pradesh, Chennai, etc. I think there's a bug in {{Regionlist}} that causes this disappearance, as the template itself was last edited on August 2024. Sbb1413 (he) (talk • contribs) 13:36, 26 June 2025 (UTC)Reply

Same issue on it:voy. For sure is caused by a change server side. I'll try to figure out if we can solve locally or if we need to open a ticket. Andyrom75 (talk) 06:46, 27 June 2025 (UTC)Reply

I've patched it. Now it works again. Be sure to refresh/purge the page you test. Andyrom75 (talk) 07:32, 27 June 2025 (UTC)Reply

Dear Wikimedia Community,

The Community Affairs Committee (CAC) of the Wikimedia Foundation Board of Trustees assigned the Sister Projects Task Force (SPTF) to update and implement a procedure for assessing the lifecycle of Sister Projects – wiki projects supported by Wikimedia Foundation (WMF).

A vision of relevant, accessible, and impactful free knowledge has always guided the Wikimedia Movement. As the ecosystem of Wikimedia projects continues to evolve, it is crucial that we periodically review existing projects to ensure they still align with our goals and community capacity.

Despite their noble intent, some projects may no longer effectively serve their original purpose. Reviewing such projects is not about giving up – it's about responsible stewardship of shared resources. Volunteer time, staff support, infrastructure, and community attention are finite, and the non-technical costs tend to grow significantly as our ecosystem has entered a different age of the internet than the one we were founded in. Supporting inactive projects or projects that didn't meet our ambitions can unintentionally divert these resources from areas with more potential impact.

Moreover, maintaining projects that no longer reflect the quality and reliability of the Wikimedia name stands for, involves a reputational risk. An abandoned or less reliable project affects trust in the Wikimedia movement.

Lastly, failing to sunset or reimagine projects that are no longer working can make it much harder to start new ones. When the community feels bound to every past decision – no matter how outdated – we risk stagnation. A healthy ecosystem must allow for evolution, adaptation, and, when necessary, letting go. If we create the expectation that every project must exist indefinitely, we limit our ability to experiment and innovate.

Because of this, SPTF reviewed two requests concerning the lifecycle of the Sister Projects to work through and demonstrate the review process. We chose Wikispore as a case study for a possible new Sister Project opening and Wikinews as a case study for a review of an existing project. Preliminary findings were discussed with the CAC, and a community consultation on both proposals was recommended.

The application to consider Wikispore was submitted in 2019. SPTF decided to review this request in more depth because rather than being concentrated on a specific topic, as most of the proposals for the new Sister Projects are, Wikispore has the potential to nurture multiple start-up Sister Projects.

After careful consideration, the SPTF has decided not to recommend Wikispore as a Wikimedia Sister Project. Considering the current activity level, the current arrangement allows better flexibility and experimentation while WMF provides core infrastructural support.

We acknowledge the initiative's potential and seek community input on what would constitute a sufficient level of activity and engagement to reconsider its status in the future.

As part of the process, we shared the decision with the Wikispore community and invited one of its leaders, Pharos, to an SPTF meeting.

Currently, we especially invite feedback on measurable criteria indicating the project's readiness, such as contributor numbers, content volume, and sustained community support. This would clarify the criteria sufficient for opening a new Sister Project, including possible future Wikispore re-application. However, the numbers will always be a guide because any number can be gamed.

We chose to review Wikinews among existing Sister Projects because it is the one for which we have observed the highest level of concern in multiple ways.

Since the SPTF was convened in 2023, its members have asked for the community's opinions during conferences and community calls about Sister Projects that did not fulfil their promise in the Wikimedia movement.[1][2][3] Wikinews was the leading candidate for an evaluation because people from multiple language communities proposed it. Additionally, by most measures, it is the least active Sister Project, with the greatest drop in activity over the years.

While the Language Committee routinely opens and closes language versions of the Sister Projects in small languages, there has never been a valid proposal to close Wikipedia in major languages or any project in English. This is not true for Wikinews, where there was a proposal to close English Wikinews, which gained some traction but did not result in any action[4][5], see section 5 as well as a draft proposal to close all languages of Wikinews[6].

Initial metrics compiled by WMF staff also support the community's concerns about Wikinews.

Based on this report, SPTF recommends a community reevaluation of Wikinews. We conclude that its current structure and activity levels are the lowest among the existing sister projects. SPTF also recommends pausing the opening of new language editions while the consultation runs.

SPTF brings this analysis to a discussion and welcomes discussions of alternative outcomes, including potential restructuring efforts or integration with other Wikimedia initiatives.

Options mentioned so far (which might be applied to just low-activity languages or all languages) include but are not limited to:

• Restructure how Wikinews works and is linked to other current events efforts on the projects,
• Merge the content of Wikinews into the relevant language Wikipedias, possibly in a new namespace,
• Merge content into compatibly licensed external projects,
• Archive Wikinews projects.

Your insights and perspectives are invaluable in shaping the future of these projects. We encourage all interested community members to share their thoughts on the relevant discussion pages or through other designated feedback channels.

We'd be grateful if you want to take part in a conversation on the future of these projects and the review process. We are setting up two different project pages: Public consultation about Wikispore and Public consultation about Wikinews. Please participate between 27 June 2025 and 27 July 2025, after which we will summarize the discussion to move forward. You can write in your own language.

I will also host a community conversation 16th July Wednesday 11.00 UTC and 17th July Thursday 17.00 UTC (call links to follow shortly) and will be around at Wikimania for more discussions.

-- Victoria on behalf of the Sister Project Task Force, 20:57, 27 June 2025 (UTC)Reply

I definitely hate to say it but Wikinews has to be one of the most failed WMF projects. The English Wikinews is barely sustaining and I think that is fine for the timebeing, but the other Wikinews projects simply lack the editor base to actively review new news articles. It came up in tawikinews' closure proposal where their newest article dated to 2018! //shb (t | c | m) 02:56, 28 June 2025 (UTC)Reply

I think that we're meant to post that kind of thing on the Meta-Wiki project pages: Public consultation about Wikispore and Public consultation about Wikinews. WhatamIdoing (talk) 22:42, 28 June 2025 (UTC)Reply

I'm aware; I just wanted to give out my 2c in short form – I have a longer list of suggestions planned which I'll do when I get a bit more spare time. //shb (t | c | m) 23:44, 28 June 2025 (UTC)Reply

I am not a big fan of Wikinews, but one thing about the report published by Sister Projects Task Force is concerning. This report is written in a very critical manner, namely, it does not mention that dozens if not hundreds of volunteers have spent a considerable amount of their time on developing Wikinews. The report does not mention any single good thing about their work, which does not seem fair. The report demonstrates that the current level of activity and content development at Wikinews is low (and this statement is fair), but it does not set any threshold of what would be good enough metrics for a community to deserve the resources from WMF. Moreover, the report does not attempt to analyze which steps Wikinews editors took to develop their project, and why these steps were unsuccessful. It just says: you did a bad job, so we will close you down and even deprive you of any possibility of moving Wikinews elsewhere because the name stays with Wikimedia Foundation.

Wikivoyage is a smaller project too, and it would be discouraging if a similarly critical report about our work appears. It is not completely unrealistic when half of the language versions are dormant, while many others are somewhat comparable in their metrics to the most active editions of Wikinews. I think that only English Wikivoyage is clearly above that threshold, although the actual threshold is not even defined, so almost any level of activity can be deemed "low" if one wants to say so.

What are your thoughts on that? --Alexander (talk) 09:53, 28 June 2025 (UTC)Reply

I have not been using Wikinews, so my reflections are based on the closure of Wikinews in Swedish and the current discussion, linked above. One point raised in the discussion is that the metrics chosen didn't take into account the special nature of the project.

I assume the Sister Project Task Force is right in that this kind of evaluations need to be done from time to time, but also think that the evaluations should focus on whether there are paths forward, rather than on whether the project is viable according to current trends.

Wikinews has the problem that a significant dedicated editor base i needed – Wikipedia or even Wikivoyage can stay alive and stay interesting even with no edits for a year or two, while a news outlet would loose nearly all of its readers. The coverage needs to be adequate on at least some areas (geographic or thematic) for the site to stay interesting. The critical mass needed is much larger – and that critical mass additionally needs to be able to counter people with a bias (good-faith or not) or with an agenda not aligned with the project goals – keeping touting at bay is much easier. I assume new language versions should be started only if there is hope of quickly building that critical mass.

–LPfi (talk) 10:36, 28 June 2025 (UTC)Reply

Yes I do believe that LangCom has decided to suspend the creation of all new Wikinews projects for that very reason. //shb (t | c | m) 23:46, 28 June 2025 (UTC)Reply

Alexander, it's true "that dozens if not hundreds of volunteers have spent a considerable amount of their time on developing Wikinews", but it's also true that keeping a failing project because of past efforts is an example of w:en:Sunk cost fallacy.

I suspect that if someone made a credible proposal to move Wikinews to another host, the WMF would be be open to negotiations over the name. (But any new sponsor might prefer to come up with their own name.) WhatamIdoing (talk) 03:31, 29 June 2025 (UTC)Reply

I guess my main problem is the absence of any well-defined criteria that distinguish a sustainable project from a failing one. Do you understand what these criteria are? -- Alexander (talk) 08:35, 29 June 2025 (UTC)Reply

A well-defined criteria that defines what a sustainable project would still heavily rely on how the project functions, though. For Wikinews, it needs to be very active and metrics that may be appropriate for Wikivoyage or Wikibooks like number of articles aren't super relevant because 20000 articles is no good if the last one was written 2 months ago (the numbers are hypothetical but my point stands). //shb (t | c | m) 08:50, 29 June 2025 (UTC)Reply

I agree that the same metrics can not be applied to all sister projects, but "very active" leaves a lot of room for interpretation. Imagine someone decides that Wikivoyage is not sustainable because it contains a lot of outdated travel information that has not been updated in the last 5 years. That would be a problem... -- Alexander (talk) 09:27, 29 June 2025 (UTC)Reply

We don't want well-defined criteria. There needs to be judgement on the projects actual prospects. Opening a community discussion is good, as that's a way to see whether the metrics give a correct picture – although there should be discussions with the projects before opening a discussion like this (I don't know to what extent there have been such discussions). –LPfi (talk) 20:13, 29 June 2025 (UTC)Reply

I still don't love the way the SPTF decided to mass-send these messages to every wiki without consulting the Wikinews community; it really should be up to them (and when I mean them, I mean the more active Wikinews projects such as en or ruwikinews) to decide their project's future, not the rest of us or the vast majority who don't get involved with Wikinews. //shb (t | c | m) 23:01, 29 June 2025 (UTC)Reply

Yes. The issues should have been raised with the projects first (not only the big ones, but all projects affected). I don't know whether that was done, but seemingly not enough, anyway. It seems the SPTF (?) wanted to introduce a more general practice of re-evaluating projects, and just chose the two as examples. They should have understood that doing it that way, without consultations, would upset people. –LPfi (talk) 06:40, 30 June 2025 (UTC)Reply

TBF, there were several closure proposals before, including one for all language Wikinews. Those for major projects failed, but one can argue that this was a signal to the communities to evaluate their performance which they apparently did not get. I agree though that opening such discussion before notifying the Wikinews communities first is not really good. Ymblanter (talk) 08:54, 30 June 2025 (UTC)Reply

They definitely should have; I hope they use this as a learning lesson because the general sentiment from the enwikinews community is quite clearly unimpressed from that discussion. //shb (t | c | m) 09:01, 30 June 2025 (UTC)Reply

Well this comment certainly aged like milk. //shb (t | c | m) 13:59, 30 June 2025 (UTC)Reply

Oh dear. I hope there are others in the SPTF who are more keen-eared. This risks degenerating into one more of the WMF-not-respecting-the-community affairs. –LPfi (talk) 08:40, 1 July 2025 (UTC)Reply

SPTF (or Victoria, at the very least) seems so predetermined to close Wikinews that I've never heard something so blatantly biased such as "However, I expect that the wikinewsians would be in COI" – so to them I assume knowing the ins and outs of your own project is apparently a conflict of interest? It's a massive insult to non-Wikipedia based projects. //shb (t | c | m) 11:04, 1 July 2025 (UTC)Reply

I can understand her view, but I think it is misguided, and somebody in her team should get them to discuss their actual mission. If a project indeed needs to be laid down, the process needs to be lead very sensitively – and the consultation in this phase shouldn't be on whether to lay Wikinews down. It is "to work through and demonstrate the review process", "a community reevaluation" and "potential restructuring efforts".

The demonstration of the process has been a disaster and potential restructuring efforts require a good understanding of he project, which cannot be had without a keen-eared discussion with the communities.

The "re-evaluation" should be based on such potential restructuring paths, where restructuring isn't about where to dump the Wikinews content, but how to save the project, if possible.

–LPfi (talk) 13:13, 1 July 2025 (UTC)Reply

I fully agree with you about about the "re-evaluation" but the way they have been responding to community feedback feels as though they have the result pre-determined and this is merely being used as a box ticking exercise – which is why I think it's crucial that we as a fellow sister project speak up about the way this was poorly handled because who knows what they will do when it's our turn to undergo public consultations. //shb (t | c | m) 14:04, 1 July 2025 (UTC)Reply

I wrote about some concerns in meta:Talk:Public consultation about Wikinews#Process and analysis seem flawed. –LPfi (talk) 21:34, 1 July 2025 (UTC)Reply

Cheers, LPfi; hopefully our project will be fine (I think it will because Wikivoyage or really any other WMF project does not have the same issues as Wikinews does of requiring an active community), but more feedback is certainly better. //shb (t | c | m) 03:49, 2 July 2025 (UTC)Reply

Whereas I agree that the process it to some extend flawed (and I agree with the points LPfi makes in the response on Meta), it would be useful to see whether some metrics used for analysis (in whatever flawed way) could be improved for Wikivoyage, so that they are out of discussion. Ymblanter (talk) 08:18, 2 July 2025 (UTC)Reply

@Victoria: as primary author and for what I think is trenchant feedback: to the extent that this taskforce is assessing the sibling projects, it would be helpful if the individual communities knew what kind of rubric there is to grade their health. —Justin (koavf)❤T☮C☺M☯ 19:55, 2 July 2025 (UTC)Reply

First of all, the Taskforce in not assessing all siblings projects, the Wikispore/Wikinews was a proof-of-concept exercise.

We used this rubric, which was discussed in a public consultation a year ago - but didn't get much attention, because Meta is littered with documents that are never implemented.

In the Wikispore consultation we ask for the proposals for the clarification of the "activity" and other criteria. Victoria (talk) 09:11, 3 July 2025 (UTC)Reply

Thanks for this and thanks for letting me ping-pong you around various WMF projects with pings. —Justin (koavf)❤T☮C☺M☯ 09:38, 3 July 2025 (UTC)Reply

You are welcome. I'm happy to answer anywhere in English/Russian/Belarusian when there's no personal attacks involved. Victoria (talk) 10:15, 3 July 2025 (UTC)Reply

I've been going through some of the stats, and "very active" is an interesting point. The defenders of the "very active" Wikinews language editions seem to be engaged overwhelmingly in copying/pasting content from suitably licensed external sites. They have turned Wikinews into mirrors for other sites, rather than writing articles.

Just imagine how we at Wikivoyage would react if someone here said "I am a very active Wikivoyage editor. I spend at least an hour a day copying and pasting pages from other travel websites!" WhatamIdoing (talk) 21:34, 2 July 2025 (UTC)Reply

We do copy info from hotel websites and other sources, but we don't have the luxury of reliable free content written in our style. Being a channel for reliable news could be a mission of Wikinews (more or less the same way some "social media" sites do it). If so, the question is whether they can do it well enough for it to be worthwhile as a WMF project (and whether the other things they do are done well). But that's not the discussion the SPTF initiated, they chose to go by statistics instead. –LPfi (talk) 22:12, 2 July 2025 (UTC)Reply

It was mentioned somewhere that the stats may be skewed by bots – I'm still confused on how you'd be able to tell if the stats were skewed by bots or not. //shb (t | c | m) 23:11, 2 July 2025 (UTC)Reply

Most bots, especially most big ones, do have an appropriate user agent field in their page request, so the server logs can be used to tell apart at least those. With more advanced techniques, you can also distinguish typical bot behaviour from that of human users. There are some grey areas (such as a human using a tool other than a typical web browser, or using some script through the browser, and bots configured to look like humans), but I don't think it is impossible to get quite an accurate and reliable picture of bot vs human traffic. –LPfi (talk) 10:37, 3 July 2025 (UTC)Reply

Very interesting to know – I suppose you can tell by things like sudden influx in page views as one example but yeah unless you told me I wouldn't be specifically able to pick it out. //shb (t | c | m) 10:42, 3 July 2025 (UTC)Reply

From aggregated data, some patterns can be recognised as probably bot-caused, but to know for certain, you have to check the user agent fields, and where ordinary user agents cause bot-like patterns, you have to analyse behaviour of individual traffic sources – not trivial if somebody is really trying to hide their bot as multiple human users. –LPfi (talk) 10:54, 3 July 2025 (UTC)Reply

LPfi, I'm not talking about copying "information"; I'm talking about copying entire pages, word-for-word.

We do have copy-able options; there are multiple travel websites with appropriate copyright licenses. You know what happens to any editor who decides to "help" by copying from Wikitravel. Look at https://travel.fandom.com/wiki/Travel_Wiki whose pages are similar in style but with different section headings. WhatamIdoing (talk) 17:39, 3 July 2025 (UTC)Reply

Why? When I look in edit mode, I can see links to archives in Talk:China, but not when I simply look at that talk page. Will Wikivoyage in mobile mode ever not suck? Ikan Kekek (talk) 02:30, 29 June 2025 (UTC)Reply

I can't answer your first question, but the answer to your latter question, as we both know, is never (we are a massive afterthought for the WMF). //shb (t | c | m) 02:51, 29 June 2025 (UTC)Reply

In which case, we will eventually read that the Wikimedia Foundation dropped Wikivoyage from lack of sufficient participation. Would we be able to fork in that case, or does Wikimedia own the copyright for Wikivoyage as they do for Wikinews? Ikan Kekek (talk) 03:09, 29 June 2025 (UTC)Reply

Each individual editor, including IPs/logged-out editors, owns the copyright to whatever copyrightable material they post on wiki. The Wikimedia Foundation owns the domain names and the trademarks (e.g., name and logo). Anyone who wants to fork can do so freely. The Wikimedia Foundation will sometimes even informally help people do so. The mobile site does have the links to the archives. Click on the "(i) Learn more about this page" button at the top of the page to find the "invisible" content. WhatamIdoing (talk) 03:27, 29 June 2025 (UTC)Reply

@Ikan Kekek: Please don't be that fearful when Wikinews is proposed to be shut down or merged with Wikipedia. I wanted to work in the Bengali Wikinews Incubator project, but my lack of activity in recent weeks has prevented me from participating further. So, I have focused on Commons and Wikivoyage, where I am still highly active. I don't think the SPTF would suggest something similar for Wikivoyage, and I think it is actually a popular website. My static map of West Bengal is now widely shared on Facebook (both English and Bengali versions), along with an AI-generated list of places to visit in the state. Sbb1413 (he) (talk • contribs) 03:35, 29 June 2025 (UTC)Reply

You are a superb Wikivoyage content creator! I'm not afraid in the very near term, but usage of all websites nowadays has to be mostly mobile, so if this site's mobile interface remains terrible, its eventual demise is a foregone conclusion. Ikan Kekek (talk) 03:44, 29 June 2025 (UTC)Reply

Are you refering to the archive links that appear when I click "more about this page" at the top?

The issues with the mobile site exist as this project does not have active interface admins.

Note: The WMF has nothing to do with the content or presentation of content for this site.

Relevant links:

• https://www.mediawiki.org/wiki/Extension:WikimediaMessages#Site_admin_helper
• https://www.mediawiki.org/wiki/Recommendations_for_mobile_friendly_articles_on_Wikimedia_wikis

Jdlrobson (talk) 03:09, 30 June 2025 (UTC)Reply

Yes, "Learn more about this page." I didn't know to click that. Ikan Kekek (talk) 03:27, 30 June 2025 (UTC)Reply

I don't see why the WMF would have nothing to do with presentation of content on Wikivoyage. We are using MediaWiki and settings provided by the WMF, and we indeed are a WMF project.

Not having active interface admins (I thought we have some) shouldn't mean too much – having technically knowledgable people locally is a bonus, it (and them dedicating time to do major work) shouldn't be a prerequisite for a WMF project.

–LPfi (talk) 06:51, 30 June 2025 (UTC)Reply

We do indeed have 5 Wikivoyage:Interface administrators, which User:Jdlrobson should know, because he is one of them. Ikan Kekek (talk) 07:01, 30 June 2025 (UTC)Reply

I am an interface admin but I would not consider myself active. Maintenance of the listing editor for example causes me more anxiety than enjoyment these days.

In my time in this project I have seen quite a few complaints about the mobile experience but nobody has articulated clearly what needs improving. I personally dont think that overall it is a bad experience and the fact most of our page views are on mobile should be reassuring. That said there are templates like climate data that I think could be improved on mobile.

If you really want to improve the mobile experience I'd recommend making a wiki page with discussion of changes, proposal/consensus and then implementing them. I havent seen this sort of thing since Wikivoyage:Banner Expedition. I guarantee the majority of changes you want do not need WMF involvement but they will require discussion and community consultation. Jdlrobson (talk) 15:53, 1 July 2025 (UTC)Reply

Wauterz is certainly active. Have you ever tried adding a listing or reverting more than one edit at a time in mobile mode? I'm sure we can compile a list of badness from the mobile interface. Where is the best page to put it on? Ikan Kekek (talk) 16:25, 1 July 2025 (UTC)Reply

Andyrom75 is also fairly active on itwikivoyage. //shb (t | c | m) 22:18, 1 July 2025 (UTC)Reply

To answer the very first question of @Ikan Kekek, I've noticed that the infobox has a "display:none" style that hide those boxes in mobile view. I think this style is added serverside (maybe @Jdlrobson you can confirm), because it's not added by the template neither by the templatestyles.

However, as said from @WhatamIdoing, you can still see it clicking on the "(i)" button. Andyrom75 (talk) 17:09, 2 July 2025 (UTC)Reply

In the example you have provided the archive links provided here could be shown at the top of the page as on desktop and would be a single line change to Template:Infobox (adding the ext-discussiontools-emptystate class). We have to tell the software how to behave.

That said doing this looks really bad IMO as it makes every talk page require considerable scrolling to get to the content so personally as someone who primarily uses mobile I would oppose that change. The archive links as they currently behave work perfectly well for me.

Perhaps placing a single link "view archives" there that reveals them would be a good compromise to make this more obvious via some minor changes to the template? Jdlrobson (talk) 04:05, 6 July 2025 (UTC)Reply

Yeah, I think the text "View archives" would be really helpful. We really need to take you up on the offer to put up a litany of Wikivoyage Mobile badness up on some page, but no-one has suggested a good place for it. Do you have any ideas? I see there's no Wikivoyage:Mobile version page. Ikan Kekek (talk) 04:57, 6 July 2025 (UTC)Reply

I'm not sure what the status quo is but I would just be bold and create it: Wikivoyage:Mobile version.

Let's see if anyone is interested in collaborating and see what evolves. Jdlrobson (talk) 22:24, 6 July 2025 (UTC)Reply

Hi everyone, we (Kiwix) are planning to make an offline app based off WikiVoyage content that people could download ahead of Wikimania (taking place this year in Nairobi). The organizers would like us to add a couple of pages from the Wikimania Wiki [2] [3][4][5], but we can't build a ZIM file off two separate locations.

My idea at this stage would be to copy these here somewhere. Where do you think would be best / least problematic? Thanks, The other Kiwix guy (talk) 13:29, 3 July 2025 (UTC)Reply

Could it be in the Project: namespace (e.g., Wikivoyage:Wikimania 2025 and subpages)? WhatamIdoing (talk) 17:42, 3 July 2025 (UTC)Reply

See Past events/Wikimania 2018 Cape Town Guidebook (which would have been Wikimania 2018 Cape Town Guidebook during the event) for how we have done it in the past. There was also Wikimania 2014 London Guidebook, but that was merged and redirected into London/City of London. I don't think that Project space is appropriate for such a guide, so I would suggest Wikimania 2025 Nairobi Guidebook, with subpages if required. AlasdairW (talk) 20:15, 3 July 2025 (UTC)Reply

Perfect, thanks a lot. The other Kiwix guy (talk) 12:19, 4 July 2025 (UTC)Reply

Please be notified that there is a request for comment on Meta about paid editing and advanced rights, at m:Requests for comment/Should paid editing as a CU be allowed. You can voice your concerns regarding the topic.

This message is to notify those who haven't made comments in this RFC. For those who have made comments there, you can ignore this message.

Please do not reply to this message. 〈興華街〉📅❓ 08:43, 4 July 2025 (UTC)Reply

@HingWahStreet: I don't see this being relevant to this project; no Wikivoyage project in any language has CUs for this to matter. //shb (t | c | m) 09:11, 4 July 2025 (UTC)Reply

@SHB2000 Sorry I don't know about this. 〈興華街〉📅❓ 09:45, 4 July 2025 (UTC)Reply

@HingWahStreet: Well I asked because you only left a message on this project (as per GUC check) – I get if you wanted to send this to all projects (which I also wouldn't do but who am I to stop you from doing so), but the only project you sent this to doesn't even have CUs. //shb (t | c | m) 09:52, 4 July 2025 (UTC)Reply

@SHB2000 You mean only CUs (not others) can join the discussion? 〈興華街〉📅❓ 13:36, 4 July 2025 (UTC)Reply

@HingWahStreet: No, I never said that – what I'm trying to convey that only notifying enwikivoyage for an RfC that doesn't even remotely affect this project is what got me wondering. //shb (t | c | m) 13:40, 4 July 2025 (UTC)Reply

The story here: A CU on a small Wikipedia recently created a business to write Wikipedia articles. This has made some people suddenly realize that CUs are not officially prohibited from being "paid editors". They propose that CUs be banned from having some paid editing jobs (e.g., writing articles for companies) but not others (e.g., writing articles for an art museum).

I doubt that it will make any difference to us, and I doubt that it will make much difference overall. WhatamIdoing (talk) 16:48, 4 July 2025 (UTC)Reply

I may be mistaken, but I believe HingwahStreet has a bit of a history with Bojan (the srwiki CU involved with paid editing), too (not that it matters for the outcome of this RfC). //shb (t | c | m) 23:01, 4 July 2025 (UTC)Reply

Saved you a click: CU == Checkuser Brycehughes (talk) 18:29, 7 July 2025 (UTC)Reply

But wait wtf is a checkuser Brycehughes (talk) 18:37, 7 July 2025 (UTC)Reply

Checkusers are a small group of users on some wikis that have access to tools that reveal IP address info of usernames. We haven't found the need to appoint any. AlasdairW (talk) 21:12, 7 July 2025 (UTC)Reply

There is an argument to be made that this wiki can have CUs and there is a benefit to that, but as the person who's made all this wiki's SRCU requests since 2022, I consider that stewards doing our CU checks are sufficient enough for the timebeing. //shb (t | c | m) 08:58, 8 July 2025 (UTC)Reply

m:CheckUser. —Justin (koavf)❤T☮C☺M☯ 22:03, 7 July 2025 (UTC)Reply

(cc @Ikan Kekek, ThunderingTyphoons!:) Special:VerifyOATHForUser now exists for bureaucrats as well. There isn't much of a use case, but it is a WMF requirement that all interface admins have 2FA enabled; this new change means that were any new IAs to be appointed, you can actually check instead of relying on word of mouth. //shb (t | c | m) 10:02, 8 July 2025 (UTC)Reply

Hi, I just did a major edit on the San Juan (Puerto Rico) page. Within "Get Around", there was a big block of info about buses under "By public transportation", and another big block of somewhat repetitive info under "By bus". (And the other public transport info is under By Train, By Ferry, etc.)

I merged the two sections into one hopefully coherent block, and put it under "By bus". But the system won't let me delete "By Public Transportation" - it says that's a harmful edit (even though the content is now redundant). Can someone please help clean up by removing "By Public Transportation"?

Thanks!! 2604:B000:A217:FF41:C1DA:4A9C:9D3C:9EB5 15:09, 8 July 2025 (UTC)Reply

Update: It did let me edit the "By public transportation" section down to a single paragraph instead of deleting it entirely. I still think the section should be deleted, but at least there's not a massive duplication of content from my previous merge.

I think you can do the edit by yourself. New or non-logged-in users aren't allowed to remove too much content in a single edit, with some exceptions (such as article template comments, self-created pages and some specific types of garbage). You hit that limit. –LPfi (talk) 16:20, 9 July 2025 (UTC)Reply

Happens both on the Vector 2022 and Vector 2010 skins, and on Edge and Opera. This is only when there are too many horizontal pixels, so shrinking the window would fix the problem. Leaderboard (talk) 13:09, 12 July 2025 (UTC)Reply

I'm aware of the issue, and I've 'fixed' it several times before, but evidently not enough. It seems there's always a few cases where the result is just wonky. The issue is moreso that Vector 2022's auto-scaling text doesn't really like playing nice in cases like these as it works primarily by using page widths. I'll see if I can just make this text static, without the skin being able to scale it, because I'm not looking forward to constantly having to tweak {{Mapbanner}} either.
― Wauteurz (talk) 15:32, 12 July 2025 (UTC)Reply

I believe I have fixed the padding issue. What remains is the text scaling, which is entirely down to the proportional resize. This resizing is based primarily on screen width, and seemingly keeps scaling forever. I have tried to but cannot seem to overwrite its scaling though CSS. In other words, fixing the text scaling issue is beyond my capabilities.

@Jdlrobson: Would you maybe know of a way to force js-proportional-resize to stop scaling at a certain point within {{Mapbanner}}? In my findings it begins to overflow at screen widths past 2100px, at which point the font size is roughly scaled to 160%. A cap at 150% would be preferred to play it safe, though.
― Wauteurz (talk) 00:46, 19 July 2025 (UTC)Reply

Is it really using screen width? Why? Is there any reason not to use the window width instead? (I understand this might have nothing to do with the current problem, but I am quite frustrated with web designs where things are placed outside the window on the assumption that the screen size tells the window width.) –LPfi (talk) 20:40, 19 July 2025 (UTC)Reply

I cannot say with certainty whether it's screen width or viewport (window) width. The thing is, regardless of which it uses, the issue will persist as the template can infinitely grow in width. The template is only limited in height, so the scaling should be defined relative to that. And even if I were to set the max font size as font-size: max(5vh) (5% of the viewport's height), js-proportional-resize takes priority over it.
― Wauteurz (talk) 22:51, 19 July 2025 (UTC)Reply

That said, I have just bodged up a solution that should stop the text from scaling, in lieu of a proper solution that retains the full-width mapbanner but limits the text scaling. Downside: {{Mapbanner}} can now only be at most 1400px wide, which is full width on a 2048px window. Any width beyond that, the template will stop widening, the text will stop scaling, and the template will be centred. I'll set the same limit for {{Bottomboxes}}, so that none of it looks too out of place.
― Wauteurz (talk) 23:01, 19 July 2025 (UTC)Reply

Thanks for the ping! I wasn't aware of js-proportional-resize. Resizing elements via JavaScript is not a great performance experience (we should be minimizing "reflows" after page load) and really shouldn't be necessary with some good media queries. Where else do we use this CSS class? Can we move away from that... at least on this page?

I think the crux of the issue here is we are using position: absolute for the text, when instead we could be using display: flex with position absolute for the background and a clickable image map of the world which has various accessibility and discovery problems. This ping was the first time I realized you could actually click on the map and I've been seeing this map for many years now :-)

I'm going to have a poke around at Template:Mapbanner2# and see if I can build something a little more modern, particularly because Template:Mapbanner looks terrible on a mobile device. Jdlrobson (talk) 23:58, 21 July 2025 (UTC)Reply

There should be code for a mobile banner included in Mapbanner as well. It doesn't show on your side because your mobile device is wider than the defined cut-off, I would assume. I think for mobile, it'd be better to just build a new top-of-main-page element from scratch at this point. The mobile versions of {{Banner}} also look (and work) horrific, but my experience with mobile design and development is close to non-existent, so I'm hesitant to tackle it myself.

As for js-proportional-resize: I haven't a clue where it comes from or where else it appears. It's better practise to just define fonts as a certain percentage or relative to the viewport height in cases like these, so I'd be all to happy to get rid of it if we can.
― Wauteurz (talk) 00:11, 22 July 2025 (UTC)Reply

Yep that's what I'm looking at in Template:Mapbanner2# (note the "2" - I want to rewrite it). Collaboration welcome! Jdlrobson (talk) 02:22, 22 July 2025 (UTC)Reply

TLDR; A misleading AI-generated tourism video recently went viral, tricking unsuspecting travelers into embarking on a futile journey to a nonexistent cable car attraction. https://www.thestandard.com.hk/world-news/article/306539/ OhanaUnited^{Talk page} 07:13, 13 July 2025 (UTC)Reply

Decades ago, I read about a family unsuccessfully searching for a little side street they saw on their map. They eventually learned that it was a mapmaker's trap street. That's the closest I've heard of to someone searching for a fake attraction in the pre-AI world. I would not be surprised if this happened more often now, especially if someone believed the AI-generated source and spread the myth elsewhere.

I remember teaching older people about e-mail chain letters and to check Snopes.com before forwarding anything. I wonder if the kids these days will be teaching my generation how to identify AI-generated videos, and if there will be a Snopes-like website for AI-generated things. WhatamIdoing (talk) 19:39, 13 July 2025 (UTC)Reply

Snopes.com is still operating, so maybe that'll be the one. Ikan Kekek (talk) 19:43, 13 July 2025 (UTC)Reply

(Apologies for posting in English, you can help by translating into your language)

Hello everyone, the Wikidata For Wikimedia Projects team is excited to announce an upcoming change in how Wikidata edit changelogs are displayed in your Watchlists and Recent Changes lists. If an edit is made on Wikidata that affects a page in another Wikimedia Project, the changelog will contain some information about the nature of the edit. This can include a QID (or Q-number), a PID (or P-number) and a value (which can be text, numbers, dates, or also QID or PID’s). Confused by these terms? See the Wikidata:Glossary for further explanations.

The upcoming change is scheduled for 17.07.2025, between 1300 - 1500 UTC. The change will display the label (item name) alongside any QID or PIDs, as seen in the image below:

These changes will only be visible if you have Wikidata edits enabled in your User Preferences for Watchlists and Recent Changes, or have the active filter ‘Wikidata edits’ checkbox toggled on, directly on the Watchlist and Recent Changes pages.

Your bot and gadget may be affected! There are thousands of bots, gadgets and user-scripts and whilst we have researched potential effects to many of them, we cannot guarantee there won’t be some that are broken or affected by this change.

Further information and context about this change, including how your bot may be affected can be found on this project task page. We welcome your questions and feedback, please write to us on this dedicated Talk page.

Thank you, - Danny Benjafield (WMDE) on behalf of the Wikidata For Wikimedia Projects Team. MediaWiki message delivery (talk) 12:46, 14 July 2025 (UTC)Reply

I'm looking forward to this change. WhatamIdoing (talk) 05:24, 15 July 2025 (UTC)Reply

Would be interesting to see. //shb (t | c | m) 07:30, 18 July 2025 (UTC)Reply

As an addendum, you can already see changes to Wikidata items associated with your watchlist as a one-off by choosing the appropriate filter or permanently at Special:Preferences#mw-prefsection-watchlist. Not everyone seems to know this. —Justin (koavf)❤T☮C☺M☯ 07:51, 18 July 2025 (UTC)Reply

Does anyone know why there's an extra space in the Pergamon Museum entry after the museum's name at Museums#World-renowned_museums or how to fix it? Sdkb ^talk 06:03, 17 July 2025 (UTC)Reply

I'm not seeing an extra space on my computer. I'll try looking at the article on my cellphone tomorrow. Ikan Kekek (talk) 06:33, 17 July 2025 (UTC)Reply

I also do not see this space, nor does anything in the HTML seem like it would make a space. —Justin (koavf)❤T☮C☺M☯ 07:15, 17 July 2025 (UTC)Reply

@Ikan Kekek, Koavf: I can see the extra space from my laptop screen. The space after a listing name is probably a "tab" character (&[hash]9;) rather than a "space" character (&[hash]20;). Sbb1413 (he) (talk • contribs) 11:59, 17 July 2025 (UTC)Reply

I checked on a second computer with a different browser and still don't see it. :/ —Justin (koavf)❤T☮C☺M☯ 16:38, 17 July 2025 (UTC)Reply

I believe @Ground Zero fixed it in this edit. Sdkb ^talk 18:35, 17 July 2025 (UTC)Reply

Indeed. I just deleted whatever was there, and put in a proper space. I am glad it worked. Ground Zero (talk) 19:26, 17 July 2025 (UTC)Reply

Pop quiz time: Do you know what "BS 1363" refers to? How about "NEMA 1-15, NEMA 5-15"? I suspect our readers do not, but this is the language used in {{Quickbar}} that appears in places like here and here. It arises from the fact that the Quickbar (sensibly) uses Wikidata, and Wikidata uses technical names rather than the far more common "Type G" or "Type A/B" (the examples above), which is the only label we ourselves use at Electrical systems.

This seems like something we should really try to change. I'd prefer not to abandon the Wikidata integration, but perhaps we could ensure that all plug types have the nickname property defined and then instruct Quickbar to use that. Or (less preferably) we could maybe code something into Quickbar that automatically changes the value "BS 1363" into "Type G". Sdkb ^talk 15:38, 17 July 2025 (UTC)Reply

I find "BS 1363" easier to recognise than "Type G", but "British" is easiest. I can't remember all the different type letters, but I know that BS standards are British and NEMA ones are American. As a first step these formal terms should be added to Electrical systems. I have just looked at one of my plugs and saw that it was a BS 1363 plug with a BS 1362 fuse.

If there is room, I would prefer something like "Type G (BS 1363 - British)". AlasdairW (talk) 22:24, 17 July 2025 (UTC)Reply

Ugh, those code numbers are impenetrable.

Could someone possibly add a little picture of what the plug is supposed to look like? I know what the picture means. WhatamIdoing (talk) 07:02, 18 July 2025 (UTC)Reply

The terms and the images should be in Electrical systems. If we could get links from the type in the quickbar to the appropriate entry in our article, the term used in the quickbar wouldn't be that important. Most less travelled readers would have to check regardless of what we call the plug (and even if we include an image – you need to know what to look for to make sure your plug is the one shown in the image). –LPfi (talk) 10:16, 18 July 2025 (UTC)Reply

EFF on challenge to Online Safety Act. This will affect us too. Pashley (talk) 03:51, 18 July 2025 (UTC)Reply

See also https://wikimediafoundation.org/news/2025/07/17/wikimedia-foundation-challenges-uk-online-safety-act-regulations/ WhatamIdoing (talk) 07:03, 18 July 2025 (UTC)Reply

https://thesailingboard.substack.com/p/voyages-003-paris-france —Justin (koavf)❤T☮C☺M☯ 18:36, 23 July 2025 (UTC)Reply

This is a healthy and interesting point of view. Wikivoyage might seem rigged for "check-list tourism", but we can use the Understand, See and Do to inspire other ways to travel; in particular for famous destinations such as Paris, which tends to leave many visitors disappointed. /Yvwv (talk) 21:52, 23 July 2025 (UTC)Reply

Agreed and glad that I got some validation. More content based around itineraries and what it's like to be somewhere should probably be the direction of the site over a bunch of listings. —Justin (koavf)❤T☮C☺M☯ 22:41, 23 July 2025 (UTC)Reply

I've recently heard about three experiences of Paris (all middle-aged US women): One went to Paris, had her phone stolen, got food poisoning, and loved it. The other two went to Paris, had no apparent problems, and would not recommend it to anyone. The only difference I can identify is that the one who loved it speaks some French, and the other two don't. WhatamIdoing (talk) 17:51, 24 July 2025 (UTC)Reply

That's interesting. I can't relate to people being disappointed by Paris unless they had terrible experiences like the first woman who nevertheless loved it, but when I showed up for my first visit, I had already studied 3.5 years of French and my head swam for only a week before I started speaking reasonably well. There's no need for visitors to France to speak French fluently, but a bit of effort to speak some French and follow some French etiquette is appreciated. Ikan Kekek (talk) 19:00, 24 July 2025 (UTC)Reply

https://blog.openstreetmap.org/2025/07/22/vector-tiles-are-deployed-on-openstreetmap-org/

For those who aren't familiar: w:en:raster graphics and w:en:vector graphics. For abstract shapes and lines (think graphics like a flag), vector graphics are far more efficient and allow for things like embedding text that can be translated and indexed or easily including relevant metadata or changing appearances easily with CSS. The general process of replacing raster maps with vector ones will greatly improve performance, internationalization, accessibility, etc. —Justin (koavf)❤T☮C☺M☯ 22:49, 23 July 2025 (UTC)Reply

Nice to hear. I hope we will get them work on WMF sites too. Vector tiles allow serving customised maps without having to waste server space on the different versions or violating privacy by fetching different versions on demand. We already do that partly with layers for markers etc., but having the background map in vector format allows changing the appearance of the background map features, choosing what to emphasize (by {{mapframe}} parameters or the like – or having different-looking maps on Wikivoyage and Wikipedia). –LPfi (talk) 07:32, 24 July 2025 (UTC)Reply

https://www.altaonline.com/dispatches/a64895127/us-highway-89-road-trip-west/

If you, like me, are a sucker for purple prose, the American Southwest, and big photographs, you will like this. I also think that this is the kind of direction this site should move in the future, as I mentioned in the above thread about Paris, travelogue writing that has a personal dimension and that we used to have with Wikitravel Extra and personal blogs could provide really meaningful educational content that isn't really captured with the current lcoation-and-listing style that we have for most of the writing here. —Justin (koavf)❤T☮C☺M☯ 02:33, 25 July 2025 (UTC)Reply

I don't agree with you. A travel guide cannot be a personal blog. There's a reason that personal blogs are on other sites. Ikan Kekek (talk) 03:14, 25 July 2025 (UTC)Reply

How do you use the Nearby feature (mainly the one in the Wikipedia app)?

It still shows all kinds of articles such as cemeteries, schools, train stations, etc that aren't relevant to a traveler so I wonder why nobody seems to have any issues with it and why there seems to be little involvement of wikivoyage users with that map despite that it could be so useful for vacations / exploring places / wikivoyage-things. Maybe people here use something else or have some tricks to make the Nearby map useful in realworld scenarios or there is some related discussion. Prototyperspective (talk) 21:10, 27 July 2025 (UTC)Reply

I think it's just something that a lot of us have forgotten since it's a feature not talked about often. //shb (t | c | m) 00:14, 28 July 2025 (UTC)Reply

I just tried it and it worked without issues, but I'd be open to changes if it has flaws. It's one of those features that perhaps readers of the site use more than editors. --Comment by Selfie City (talk) (contributions) 01:07, 28 July 2025 (UTC)Reply

I forgot it existed, too. Ikan Kekek (talk) 01:19, 28 July 2025 (UTC)Reply

Have you tried it in a real-world scenario or just for testing at home?

I'm asking because there is no engagement with phab:T360197 and this feature seems like it has a huge potential – in particular for wikivoyage-related things like vacations – where some changes seem needed in most cases to make it truly useful for real-world applications.

See meta:Community Wishlist/Wishes/Filters for types of items shown on the Wikipedia app Nearby places map. I can't use this feature for exploring places except when it's some remote area with barely any articles at all on the map.

Lastly, I don't know why this is a widely forgotten feature on wikivoyage – it seems like THE wikivoyage feature, e.g. the feature in the Wikipedia app by which most people would learn about and use wikivoyage for the first time. Prototyperspective (talk) 11:19, 28 July 2025 (UTC)Reply

I'd say it's because you can't really use it on desktop, where most editing occurs. Wikivoyage on mobile, where this feature most comes in handy, is shit to deal with, so a lot of us simply forgot it existed. //shb (t | c | m) 23:37, 28 July 2025 (UTC)Reply

It's available in the mobile app. Since the map there is much more advanced and useful than the desktop version where one doesn't even have a map or input box for entering a location, I was referring to the Nearby feature in the mobile app. (By the way I think I read somewhere a proposal for a Wikivoyage mobile app.) Prototyperspective (talk) 23:41, 28 July 2025 (UTC)Reply

Wikivoyage doesn't have a mobile app as of yet, unfortunately. :( //shb (t | c | m) 00:51, 29 July 2025 (UTC)Reply

Yes, that's what I was referring to at I read somewhere a proposal for a Wikivoyage mobile app. With It's available in the mobile app I was referring to the Wikipedia app which I named in my prior comment. Prototyperspective (talk) 11:25, 30 July 2025 (UTC)Reply

I strongly disagree that "train stations...aren't relevant to a traveler", and I happen to have a fondness for visiting old cemeteries. Perhaps we need filters, but it may be difficult to figure out what to include or exclude. WhatamIdoing (talk) 15:08, 28 July 2025 (UTC)Reply

This is so that users can configure it. Train stations obviously are very relevant to many travelers. Prototyperspective (talk) 16:01, 28 July 2025 (UTC)Reply

Nice feature, but is there a way to integrate it into WV, or one has to use the WP app? I was actually thinking to invent something similar - basically grab the nearaby articles, get all listings from them, and show that on a map, ideally sorted by WP views. I think WV cannot just show WP articles, otherwise there'd be no point in maintaining the listings... -- andree 11:53, 30 July 2025 (UTC)Reply

Hello, this message is to notify that Chealer has been nominated for a global ban at m:Requests for comment/Global ban for Chealer. You are receiving this notification as required per the global ban policy as they have made at least 1 edit on this wiki. Thanks, //shb (t | c | m) 11:22, 28 July 2025 (UTC)Reply

FTR for some added context, this is the user that we indef blocked last month for the blatant disrespect of our links to Wikipedia policy and later engaged in empty threats and such. //shb (t | c | m) 23:35, 28 July 2025 (UTC)Reply

Following discussion in Wikivoyage:Mobile_version I've proposed Template:ArchivedDiscussions for use on talk pages for archive links. This works exactly the same on desktop as it currently does but improves visibility on mobile by providing a direct link (rather than hiding it under the general "more information about this page")

You can see it in action on Talk:London.

If we're happy with this we'll (or I'll!) need to apply it to the remaining 133 pages and use it for future archiving. Thoughts? Jdlrobson (talk) 15:43, 29 July 2025 (UTC)Reply

For comparison purposes:

• https://en.wikivoyage.org/wiki/Talk:London (new template on desktop)
• https://en.m.wikivoyage.org/wiki/Talk:London (new template on mobile)
• https://en.wikivoyage.org/wiki/Talk:Barcelona (old template on desktop)
• https://en.m.wikivoyage.org/wiki/Talk:Barcelona (old template on mobile)

You're looking for the light blue box with a title like "Archives". Jon, I think it's an improvement. WhatamIdoing (talk) 03:48, 30 July 2025 (UTC)Reply

I concur with WhatamIdoing – cheers, Jdlrobson :). //shb (t | c | m) 09:46, 30 July 2025 (UTC)Reply