Wikivoyage:Travellers' pub

From Wikivoyage
Jump to navigation Jump to search
Welcome to the pub

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 Vandalism in progress.
  • 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

I didn't create these templates, and the former has existed for a while (the latter was created recently by Roovinn), but I'm interested to hear the community's opinion if we opted to design these templates similar to how Commons designed them (see c:Template:Retired and c:Template:Semi-retired) instead of the simplistic Wikipedia style. --SHB2000 (talk | contribs | meta) 08:54, 4 March 2024 (UTC)[reply]

Heads up that linking in this style in the header makes it difficult for some tools to link directly to it. the {{tl|Example}} style breaks some things versus the [[Template:Example]] style. (See an above thread where I did the same.) I changed it if you don't mind. —Justin (koavf)TCM 08:55, 4 March 2024 (UTC)[reply]
No, I don't mind. Thanks for the fix, Koavf! --SHB2000 (talk | contribs | meta) 09:02, 4 March 2024 (UTC)[reply]
The three versions (the original blue, the current black and the Commons one) demonstrate that a retiring user cannot know what such a template will look like after they left. Thus the template should perhaps be regarded not as a message from the user, but as one from the community (in most cases based on a statement from the user, of course).
For a message from the community, it makes sense to use a (uniform) template. What kind of message do we want to convey with the design? I personally prefer the one on Commons, which looks much more friendly, especially as contrasted with the current black one, but it is unnecessarily wordy, as bans are few enough here that we don't need to explicitly address that issue. One point to keep in mind is that the template shouldn't offend anybody who got the template put on their user page by somebody else (after them having declared their retirement elsewhere) or who put the template there when it looked different.
LPfi (talk) 10:45, 4 March 2024 (UTC)[reply]
I'm with you on the bans, but I'm leaning in favour of mentioning the ban bit as "This is not indicative of breaking any Wikimedia policies." seems quite harmless and I presume most passer-by users have no idea how many bans a wiki issue (I, for one, frequently lurk Meta-Wiki and have zero clue how many are issued on a monthly basis). Otherwise I fully agree with you and think some of it should be mentioned in the documentation as a disclaimer for clarity. --SHB2000 (talk | contribs | meta) 10:51, 4 March 2024 (UTC)[reply]
I prefer the look of the Commons versions.
Not a big issue, but maybe we should consider if "of their own volition" is always applicable. If an editor is semi-retired because they are in hospital or in prison, then it probably isn't of their own volition. Similarly if retired is added because another editor has heard of an editor's passing. Or are there alternatives to use in these circumstances? AlasdairW (talk) 23:50, 4 March 2024 (UTC)[reply]
Accounts of deceased Wikimedians are globally locked, for the record. SHB2000 (talk | contribs | meta) 00:39, 5 March 2024 (UTC)[reply]
The "retired" template is on just 13 pages. Four of them are blocked/glocked. That means that just over 30% of current users of this template were breaking policies, and should therefore not have a message indicating that they weren't. Eight of the 13 (just over 60%) made less than 50 edits total. The only account that I'd find that template even remotely useful for is @Saqib, who is active on other projects and therefore easily reached with a ping. In short: No practical need to have this template at all.
The "semi-retired" template is one one user's page. That person made an edit today.
If we see this template less as a means of self-expression (see meatball:Goodbye and w:en:WP:YDOW) and more as a practical thing (namely, those of us who are here need to know whether you're still around), I suggest that we get rid of the rarely used and mostly misleading templates, and instead install the m:User:SMcCandlish/userinfo.js and and m: MediaWiki:Gadget-markblocked.js gadgets, default on. Then we'll spot blocked users every time there's a link to their user pages, and the top of every user page/user talk page will have a note about how long it's been since that user's last edit. WhatamIdoing (talk) 00:05, 5 March 2024 (UTC)[reply]
I cannot really see what the gadgets do, but I think having detailed info shown by default is a privacy issue, and it may have annoying effects on the project culture. Also, we might – just might – want to give some weight also to "global" status/activity, which it seems the gadgets don't care about. –LPfi (talk) 09:10, 5 March 2024 (UTC)[reply]
Global activity is apparently difficult to detect, though I agree that it would be good to have.
What the UserInfo script does is replace the line that says "From Wikivoyage." under your =User page title= with simple public information from Special:ListUsers and Special:Contributions. In my case, right now, it says "An autopatrolled, 9 years 9 months old, with 4,193 edits. Last edited 3 minutes ago. From Wikivoyage." I find that the "Last edited" line is the most useful, as it lets you know that I'm probably online (or that I haven't been around for years, or whatever). Other editors seem to think it's most useful for noticing that someone is a newbie (e.g., if it says "with 2 edits"). See File:Userinfo Screen Shot.png for a screenshot of what it looks like on a narrow screen.
The MarkBlocked script is useful in discussions and in page histories. It adds strikethrough to links (e.g., WhatamIdoing) and makes the link a lighter color so that you can see at a glance whether you're about to reply to someone who has been blocked locally. WhatamIdoing (talk) 17:41, 5 March 2024 (UTC)[reply]
If a bread at a bakery is stale, you don't stop making bread at all; instead, you work to fix the issue. A similar analogy here should also apply, instead of outright claiming that there isn't a practical need to have a template to have it all. The solution to this is to simply restrict its usage for users who are not banned, blocked or locked (with a policy explicitly allowing any user in good-standing to remove such a template if misused). Also, I agree with LPfi about the privacy issue. --SHB2000 (talk | contribs | meta) 09:37, 5 March 2024 (UTC)[reply]
I would add to that list "users who have made very few edits". Several of our "retired" editors have made exactly two edits: to create their userpage and then to replace it with this template. They haven't "retired" from Wikivoyage; they were functionally never here in the first place. At which point there are so few uses of it that the template's contents could be placed directly on the (two? three?) users' individual pages, rather than putting it first in the Template: namespace and then transcluding it.
Try this: remove the template from all the user pages that are blocked/glocked, and from anyone who hasn't made, say, 50 edits. See how long the list is after that. Then ask: Do we need to use a tool designed to make it easy to repeat something across "many" pages ...when there aren't even "a few" pages to post it on? WhatamIdoing (talk) 17:32, 5 March 2024 (UTC)[reply]

Japanese Romanization[edit]

I've noticed in recent months users have been changing all Japanese names and articles to use diacritics in spite of what is written in both Wikivoyage:Naming conventions and Wikivoyage:Romanization that state:

  • For article titles, use the name most commonly used in English for a place, regardless of local character sets.
  • Articles should use the city, region or country name most commonly used in English-speaking countries
  • If a place has a common English name, use it, but always provide the local script and correct romanization in parentheses.

Maybe users are confused because the overriding rules are written separately from the Japanese Romanization subheading, but a significant number of Japanese place names have been romanized and do not use the diacritics. I recently moved Zaō Onsen to Zao Onsen, because search results show that Zao Onsen is clearly the most common English name (Zaō Onsen retrieves only 19,000 results which include Zao Onsen in some of the results, while "Zao Onsen" retrieves 1,970,000 results of which none that I see contain the diacritics). It is very clear that the article should be title Zao Onsen with (蔵王温泉 Zaō Onsen) written in the lede however, I did not realize until after I moved it that it was moved TO the wrong name before that. A lot of place names have also been changed in spite of having established English romanizations. It seems users have forgotten, are ignoring, or are unaware of the overarching romanization rules and perhaps are unaware that the diacritics are still able to be written in parenthesis.

Is there a way to make this clearer? Or should I just send a message to users when I notice it happening? ChubbyWimbus (talk) 10:08, 4 March 2024 (UTC)[reply]

I would support making it very clear on Wikivoyage:Naming conventions with a subheading for "Japan" in a very similar fashion to Wikipedia. --SHB2000 (talk | contribs | meta) 10:34, 4 March 2024 (UTC)[reply]
A split of #Disambiguation is probably also overdue. --SHB2000 (talk | contribs | meta) 10:37, 4 March 2024 (UTC)[reply]
Hey yo, since you're talking about me you could at least have @'d me in? Anyway, I wrote the Japanese romanization policy back in 2004, but these days I disagree with my old self and so does Wikipedia: I don't see any good reason not to use macrons for Japanese place names, particularly if we're simultaneously pretending Uluṟu-Kata Tjuṯa National Park is the most common form in Australia. Of course Tokyo, Osaka and other household names don't need macrons, but Zaō Onsen isn't exactly in the same league. I've formally proposed the change at Wikivoyage talk:Romanization.Jpatokal (talk) 01:57, 11 March 2024 (UTC)[reply]
In either case, shouldn't Wikivoyage:Naming conventions continue to apply? Are these macrons most commonly used in English? -- Ikan Kekek (talk) 04:54, 11 March 2024 (UTC)[reply]
They are almost never the most commonly used names in English for Japanese place names online OR within Japan. Given that the user proposing this does not consider over 99% non-diacritic usage to be enough to qualify as "common usage", it seems clear that the proposal is intended to eliminate the current Wikivoyage:Naming conventions and replace it with one that advocates for usage of diacritics OVER and INSTEAD OF whatever is commonly used. ChubbyWimbus (talk) 12:36, 11 March 2024 (UTC)[reply]
At least my observation is that diacritics are generally not used in English when transliterating Japanese names, except in material specifically aimed at English speakers who are learning Japanese as a foreign language. It certainly would be helpful to indicate to English speakers which vowels are long and which vowels are short since that distinction is important in Japanese, and Japanese people will have no idea what you are talking about if you confuse long and short vowels. That said, Wikivoyage:Naming conventions says that the most common English name should be used, which is clearly without the diacritics. I think the solution would be to adopt the same policy that we do for our articles about Chinese cities. For say, Beijing, we have the page name without the tone marks, but in the lede we indicate what the correct pronunciation with the tone marks is (Běijīng). So for Japanese cities, we can just leave the page names without the diacritics, and indiciate in the lede correct pronunciation with diacritics to indicate the long vowels. So the page name would be "Tokyo" without the diacritics, but we indicate in the text of the lede that it is actually pronunced Tōkyō with the long vowels. The dog2 (talk) 15:25, 11 March 2024 (UTC)[reply]
I agree. Ikan Kekek (talk) 18:46, 11 March 2024 (UTC)[reply]
You have described the status quo, that's exactly what we do today. Jpatokal (talk) 20:00, 11 March 2024 (UTC)[reply]
Incorrect. Our current policy is that macrons may never be used in Japanese article titles, period, and this overrides the general naming convention that names should be "with or without accents/diacritics".
I'm suggesting that we a) allow them, and b) start using them when Wikipedia has determined that the macroned version is the common name. (For example, w:Zaō Onsen.) Jpatokal (talk) 19:59, 11 March 2024 (UTC)[reply]
See also: en:wikt:Wiktionary:Grease_pit/2024/March#FYI:_Major_romanization_change_coming_in_Japan and en:wikt:Wiktionary:Beer_parlour/2024/March#How_should_we_transliterate_(into_Japanese_script_or_other_scripts),_romanize,_and_lemmatize_Ryukyuan?. —Justin (koavf)TCM 20:28, 11 March 2024 (UTC)[reply]
We should not outsource all decisions about what names are most commonly used in English to Wikipedia, especially if there are claims on Wikipedia that a Japanese place name with macrons is the most common spelling in English. Really? I don't think The dog2's suggestion requires a tweak to current Wikivoyage naming policy, since it would be used just in the beginnings of articles to show a transliteration of the Japanese characters, but if it does, I'd be happy to support that limited change. Ikan Kekek (talk) 20:36, 11 March 2024 (UTC)[reply]
Did you make some mistake and respond to me when you meant to respond to someone else? I didn't write anything about Wikipedia at all. —Justin (koavf)TCM 20:44, 11 March 2024 (UTC)[reply]
I'm replying in chronological order, so Jpatokal and others see my reply easily. You'd prefer for me to thread the response so that it's more easily lost in the middle. Ikan Kekek (talk) 20:50, 11 March 2024 (UTC)[reply]
I would prefer that you respond to messages with messages that respond to them. The way that you're doing it is unintelligible. That's why the : and :: syntax exists. If you respond ostensibly to Person A but in reality, it's written to Person B several paragraphs down, that is confusing. See also the [reply] links that are made so that you can directly reply to the relevant comment. —Justin (koavf)TCM 20:55, 11 March 2024 (UTC)[reply]
I'm responding to the overall thread. If you want to enforce subthreads, feel free to create a subheading and move stuff accordingly, and do that every time, because your preferences are not the common practice on this site. Ikan Kekek (talk) 20:57, 11 March 2024 (UTC)[reply]
Source? Please just use the [reply] link and don't respond to my comments with off-topic noise. You're making it much harder to follow the conversation. —Justin (koavf)TCM 20:59, 11 March 2024 (UTC)[reply]
The [reply] links were apparently introduced to support the style of threaded discussions that's standard on Wikipedia, without regard to what is most used in the English Wikivoyage community. Here we usually add comments in chronological order, as Ikan Kekek said. It's a small cultural difference – different WMF projects are in some ways like different towns or countries. —Granger (talk · contribs) 22:09, 11 March 2024 (UTC)[reply]
But if we are going to do that, it's infinitely more confusing to have the :- or *-based comments, as that implies that there is some kind of reason to responses. We should just have a flat series of comments (which itself would be ugly and unintelligible, but at least not actively misleading). —Justin (koavf)TCM 22:14, 11 March 2024 (UTC)[reply]
I don't find it more confusing, and both maintaining chronological order and providing a visual separation between successive comments, even when it meant looking like you were replying to a subsequent person, was the more common style at enwiki until the Reply tool became popular.
To cope with this, I've noticed a small increase in people deliberately naming the person/comment they're replying to, either with small quotations or by starting the comment with a user's name (e.g., "Ikan, I'm not sure about..." or "I agree with Ikan that...").
The other practice, which was used in the past and is still important now, is to assume that if the person's reply doesn't make sense as a reply to your own comment, then it's not a reply specifically to your own comment. WhatamIdoing (talk) 17:45, 13 March 2024 (UTC)[reply]
I don't recall that being standard here or there. It's very distracting to not use the built-in ability to respond directly to someone else. —Justin (koavf)TCM 19:39, 13 March 2024 (UTC)[reply]
Other people find it very difficult to tell which comment came from which person, when there is no visual distinction, especially if there is no distractingly decorated sig in the earlier comment(s). WhatamIdoing (talk) 17:18, 14 March 2024 (UTC)[reply]

FYI: Is it safe to travel to Mexico, Jamaica, and the Bahamas in 2024?[edit]

https://boingboing.net/2024/03/04/is-it-safe-to-travel-to-mexico-jamaica-and-the-bahamas-in-2024.html

In a real tragedy for the scale of a blog post, they link the wrong article. Here is the correct one. —Justin (koavf)TCM 23:50, 4 March 2024 (UTC)[reply]

FYI: 11 Remote Destinations That Are Definitely Worth the Effort to Visit[edit]

https://www.outsideonline.com/adventure-travel/destinations/most-remote-places-on-earth/Justin (koavf)TCM 23:50, 4 March 2024 (UTC)[reply]

Good article, but I find it a bit US-centric. --SHB2000 (talk | contribs | meta) 21:06, 11 March 2024 (UTC)[reply]
Agreed: I thought it was weirdly US-centric and I'm an American. —Justin (koavf)TCM 21:09, 11 March 2024 (UTC)[reply]
What really surprised me was the lack of any Russian destinations. --SHB2000 (talk | contribs | meta) 21:11, 11 March 2024 (UTC)[reply]
That is one of the least surprising things I can imagine, particularly writing to an American audience (which Outside is, to the extent that it is an American publication). I could not in good conscience recommend anyone go there. It's no North Korea or active war zone, but there's a remote-yet-much-too-hi prospect that you'll be arrested for holding a blank piece of paper in public or something and then be a pawn in State Department negotiations for 19 months until an international terrorist is released in a prisoner swap. :/ —Justin (koavf)TCM 21:17, 11 March 2024 (UTC)[reply]
Parts of Russia are definitely active war zones, in the sense that they've been attacked by drones and apparently by Ukrainian Special Forces, so things get targeted or torched every so often. Ikan Kekek (talk) 22:24, 11 March 2024 (UTC)[reply]
Yeah, that too and certainly the "parts" of "Russia" that are actually stolen land of Ukraine. —Justin (koavf)TCM 22:27, 11 March 2024 (UTC)[reply]

FYI: I flew to Japan with my baby. Here's what I learned about traveling with young kids[edit]

https://www.npr.org/2024/03/05/1196978785/traveling-with-babies-and-toddlers-tips-tricksJustin (koavf)TCM 14:59, 5 March 2024 (UTC)[reply]

Report of the U4C Charter ratification and U4C Call for Candidates now available[edit]

You can find this message translated into additional languages on Meta-wiki. Please help translate to your language

Hello all,

I am writing to you today with two important pieces of information. First, the report of the comments from the Universal Code of Conduct Coordinating Committee (U4C) Charter ratification is now available. Secondly, the call for candidates for the U4C is open now through April 1, 2024.

The Universal Code of Conduct Coordinating Committee (U4C) is a global group dedicated to providing an equitable and consistent implementation of the UCoC. Community members are invited to submit their applications for the U4C. For more information and the responsibilities of the U4C, please review the U4C Charter.

Per the charter, there are 16 seats on the U4C: eight community-at-large seats and eight regional seats to ensure the U4C represents the diversity of the movement.

Read more and submit your application on Meta-wiki.

On behalf of the UCoC project team,

RamzyM (WMF) 16:25, 5 March 2024 (UTC)[reply]

Template?[edit]

What's up with the templates inserting a completely useless contents block on the left side of every topic? In some cases it produces astoundingly ugly and unusable page layouts (especially for countries and regions). Did somebody do this on purpose? Mrkstvns (talk) 19:15, 6 March 2024 (UTC)[reply]

I'm not sure what you're experiencing. Is this when you're editing or reading? What pages do you see this on? What do you mean by "topic"? WhatamIdoing (talk) 21:04, 6 March 2024 (UTC)[reply]
When reading. I see it on every page on the site: Cities, regions, countries, parks, travel topics, etc.
Gray box with links to all the sections.
Pagebanner
[+] Understand
[+] Get in
[+] Get around
.... Mrkstvns (talk) 21:17, 6 March 2024 (UTC)[reply]
I think it's a bug, see T359446 on Phabricator. -- Alexander (talk) 21:29, 6 March 2024 (UTC)[reply]
I can see it now. That box is the "Table of Contents". WhatamIdoing (talk) 04:37, 7 March 2024 (UTC)[reply]
@Andyrom75: Do you think you could possibly reinsert that temporary fix you made sometime back? --SHB2000 (talk | contribs | meta) 12:44, 7 March 2024 (UTC)[reply]
@SHB2000, I've temporary patched Template:Pagebanner. Please, ping me as a reminder when the bug has been solved. Andyrom75 (talk) 15:34, 7 March 2024 (UTC)[reply]
Thank you, Andyrom! SHB2000 (talk | contribs | meta) 20:25, 7 March 2024 (UTC)[reply]
@Andyrom75, the bug report says the patch was riding this week's deployment train, so it should be fixed now. (You'll need to double-check that it actually did get fixed; all I can confirm is that the deployment train has been here.) WhatamIdoing (talk) 17:50, 13 March 2024 (UTC)[reply]
@WhatamIdoing, thanks for the ping. The server-side changes has been been reverted, so I've done the same with my temporary patch.
Now it seems that the previous behavior has been restored. Andyrom75 (talk) 22:36, 13 March 2024 (UTC)[reply]
Thank you for your vigilance, Andyrom! --SHB2000 (talk | contribs | meta) 09:40, 14 March 2024 (UTC)[reply]

Wikimedia Canada survey[edit]

Hi! Wikimedia Canada invites contributors living in Canada to take part in our 2024 Community Survey. The survey takes approximately five minutes to complete and closes on March 31, 2024. It is available in both French and English. To learn more, please visit the survey project page on Meta. Chelsea Chiovelli (WMCA) (talk) 00:21, 7 March 2024 (UTC)[reply]

April 1st..[edit]

Any thoughts? ShakespeareFan00 (talk) 17:28, 7 March 2024 (UTC)[reply]

I had an idea already the last year, but have yet to finalize it... Do we do this 'in secret'? :-D -- andree 09:14, 8 March 2024 (UTC)[reply]
In the past, it's been done as collabrative draft in userspace. What's the idea? ShakespeareFan00 (talk) 09:18, 8 March 2024 (UTC)[reply]
Basically something like https://www.reddit.com/r/place (or also w:en:The_Million_Dollar_Homepage), but with world map, and editors could claim some land (and in return must do some edits there, to keep it! :) ). -- andree 08:10, 10 March 2024 (UTC)[reply]
r/place but without the bots, shall we put it? --SHB2000 (talk | contribs | meta) 08:20, 10 March 2024 (UTC)[reply]
Last year we decided to do something different and rickroll our readers. I want to do something similarly unconventional this time but I'm not sure what. --SHB2000 (talk | contribs | meta) 09:44, 8 March 2024 (UTC)[reply]
I had a suggestion, which might be a bit interesting, which was 'travel' into one's gender expression, But wasn't sure how that might work within a typical WikiVoyage type article, whilst remaning respectful to genuinely Transgender readers. ShakespeareFan00 (talk) 11:24, 8 March 2024 (UTC)[reply]
That sounds extremely difficult, especially since what feels respectful varies from culture to culture. WhatamIdoing (talk) 18:55, 8 March 2024 (UTC)[reply]
I agree with WhatamIdoing. --SHB2000 (talk | contribs | meta) 19:52, 8 March 2024 (UTC)[reply]
@ShakespeareFan00, Andree.sk, WhatamIdoing: As a last-ditch effort, I made a very low-effort page on User:SHB2000/Stubbington – as you can probably tell, it's very minimalist. Provided we find a banner, are we good to feature this on Monday? --SHB2000 (talk | contribs | meta) 06:09, 29 March 2024 (UTC)[reply]
Great article! I have one more touch in mind, tbd on Monday, though :-) -- andree 07:08, 29 March 2024 (UTC)[reply]
We could use File:My House FTT Banner.jpg as a banner - an unused one from 2020, but something more stub related would be better. AlasdairW (talk) 00:43, 30 March 2024 (UTC)[reply]

Wikivoyage talk:Joke articles would be the place to discuss this. Ground Zero (talk) 11:39, 8 March 2024 (UTC)[reply]

I've kicked off a discussion there. My suggestion: places with unusual names, for example a Morón & Mörön double bill. Jpatokal (talk) 23:01, 13 March 2024 (UTC)[reply]
With 3 days left, should we proceed with Jpatokal's suggestion. --SHB2000 (talk | contribs | meta) 10:28, 28 March 2024 (UTC)[reply]
He himself is busy, so somebody else should do this, or create an article on some other theme. I'll be away too, so won't do it. –LPfi (talk) 16:55, 28 March 2024 (UTC)[reply]
Stubbington could work, also because it's the birthday of the recently elected Finnish president :D . Or Travel rant.
Other than that, ten years ago we featured Wikipedia. I've suggested to make a joke article about Wikivoyage along the same lines, it'd be something that all of us would know something about. --Ypsilon (talk) 10:32, 30 March 2024 (UTC)[reply]
Hmm, that could work, but we only have two days left. It would be nice to feature Wikivoyage, though. --SHB2000 (talk | contribs | meta) 10:50, 30 March 2024 (UTC)[reply]
I went ahead and created a Wikivoyage article in my lab. Also, for folks that were here back in the Wikitravel times may remember that the joke articles were not to be finished by April Fools Day but the articles were rather written during the day. --Ypsilon (talk) 16:35, 31 March 2024 (UTC)[reply]
Will move it to Joke articles section in an hour or so. And if someone has better ideas, we can always run several articles like in 2016. --Ypsilon (talk) 16:38, 31 March 2024 (UTC)[reply]
Yes Done, the Main Page banner is below. It would be nice if someone could add it to the Main Page in about five hours (midnight UTC), possibly together with any other banners for Joke articles. And feel free to expand the article! --Ypsilon (talk) 18:52, 31 March 2024 (UTC)[reply]
That works! Thanks for the last minute fix, Ypsi! --SHB2000 (talk | contribs | meta) 21:12, 31 March 2024 (UTC)[reply]


Where did the table of contents go?[edit]

I'm using Vector 2022 skin. I vaguely recalled clicking on the hide button which made the table of contents on the left-hand side disappear. But I can't re-enable it. I already tried "Preferences" -> "Misc" tab and the options in "Table of contents". I do notice that in MediaWiki, there is a button beside the page title to re-enable the "Contents" section but that doesn't seem to be an option here. And oddly enough, talk pages show the table of contents. OhanaUnitedTalk page 04:28, 9 March 2024 (UTC)[reply]

Could this be related to #Template? above? —Granger (talk · contribs) 04:55, 9 March 2024 (UTC)[reply]
@Andyrom75:? SHB2000 (talk | contribs | meta) 06:02, 9 March 2024 (UTC)[reply]
@SHB2000, @Mx. Granger, @OhanaUnited, I confirm that this is related to the temporary patch I've applied on #Template?.
Once the bug T359446 will be solved, the patch could be removed and the normal behavior will be restored.
Sorry for the temporary inconvenience. Andyrom75 (talk) 07:34, 9 March 2024 (UTC)[reply]
Yeah, it's understandable. Hopefully the bug should be fixed sooner than later. --SHB2000 (talk | contribs | meta) 09:12, 9 March 2024 (UTC)[reply]
Thanks for confirming. —The preceding comment was added by OhanaUnited (talkcontribs)
@OhanaUnited, please check if now the "Table of contents" can be shown. --Andyrom75 (talk) 22:39, 13 March 2024 (UTC)[reply]
Yes it reappeared. Thanks. OhanaUnitedTalk page 05:54, 14 March 2024 (UTC)[reply]

Suggested task[edit]

If somebody would like to edit, here's a suggestion:


The brand Thalys does not exist anymore. It has merged with Eurostar. So everything that was Thalys before belongs now to Eurostar.


So search "Thalys" via the Wikivoyage search box and replace/merge everything regarding that brand name to/with Eurostar. 80.187.75.63 18:57, 9 March 2024 (UTC)[reply]

OP, please plunge forward as you see fit! --SHB2000 (talk | contribs | meta) 08:20, 10 March 2024 (UTC)[reply]
It looks like 57 articles still mention this name. I updated one but left the old name in ("Eurostar (formerly Thalys)") in case it might be useful to readers who were looking for the old name. WhatamIdoing (talk) 18:01, 13 March 2024 (UTC)[reply]

Ukraine's Cultural Diplomacy Month 2024[edit]

Hello all.

Check this out: https://meta.wikimedia.org/wiki/Ukraine%27s_Cultural_Diplomacy_Month_2024

Think this might be of interest to many of you. It definitely is of interest to me. Roovinn (talk) 06:26, 10 March 2024 (UTC)[reply]

Sadly it seems to target Wikipedia only. OhanaUnitedTalk page 02:04, 11 March 2024 (UTC)[reply]

Informative status[edit]

I see a that "informative status" has been created as an article category at Wikivoyage:Article status. A discussion took place Wikivoyage talk:Article status#Creating a new status for something in between usable and guide? which seemed to find support for the idea two years ago, but Wikivoyage:Informative articles still refers to the concept as "experimental". I personally support the proposal, but we do need to decide whether we should implement this concept more broadly or withdraw it. If we do approve it, many articles would need to be recategorized over time. --Comment by Selfie City (talk) (contributions) 19:01, 12 March 2024 (UTC)[reply]

I like the idea of a status in between usable and guide, but I think the criteria for making an article "informative" should be better described. It would be nice if it were at least a little bit more demanding than simply a usable article with at least 3-4 listings. Crikey! All of my "usable" articles meet that low threshold. I think that in order to be considered "informative" there should be a well-written lede and a good "Understand" section that explains what's special about a place (maybe with Infoboxes for cultural traditions, etc.) Just a thought... Mrkstvns (talk) 20:01, 12 March 2024 (UTC)[reply]
As the proposer, I think it's time to withdraw it. It's a great idea in theory but the logistical challenges of implementing this on a mass-scale has become near-impossible. --SHB2000 (talk | contribs | meta) 20:30, 12 March 2024 (UTC)[reply]
There is no need to have all eligible articles updated to the new status. That can be done as article status is otherwise checked, given that the status is widely known. The problem is in defining the criteria. In trying to do that, I saw quite some oddness in the present criteria. Can we adjust the criteria at all, making some usable articles revert to outline and some guides to usable (or informative)? If we can, we can do the same with a new status. However, the discussion stalled, it seems with not too much interest from the community. –LPfi (talk) 11:56, 13 March 2024 (UTC)[reply]
Which is partially why I'm on the side of abolishing this status. Without much community input (I presume the numbers post-COVID will remain like this for a while), it's hard to make bold changes like an entirely new status. --SHB2000 (talk | contribs | meta) 12:01, 13 March 2024 (UTC)[reply]
I don't know if I'm being a bit too pessimistic or if I'm biased as the one who initially proposed it. --SHB2000 (talk | contribs | meta) 12:05, 13 March 2024 (UTC)[reply]
I think if we create a new status, it will be adopted over time. However, we would need to form a new consensus on the qualifications of this article status, IMO. --Comment by Selfie City (talk) (contributions) 14:12, 13 March 2024 (UTC)[reply]
Well, we have and it's existed for over two years, but very little has been done on it for cases where the criteria is evident. SHB2000 (talk | contribs | meta) 09:41, 14 March 2024 (UTC)[reply]
I don't think we get much value from increasing the number of possible ratings. The fewer categories we have, the less time we'll spend on bureaucracy. WhatamIdoing (talk) 18:03, 13 March 2024 (UTC)[reply]
I guess it's less so the bureaucracy and more so just the time spent to make the status mainstream. --SHB2000 (talk | contribs | meta) 20:46, 13 March 2024 (UTC)[reply]
I just don't think there's such a drastic difference between usable, informative and guide for town and small village pages. Take Kuujjuarapik that I created last month while I travelled there. I added practically everything there is about the town. Right now I'm already hung up on whether changing it from usable to guide (because the only thing missing for guide is "go next" one-liners). If we introduce informative and I added the "go next" one-liners, I honestly don't know whether my article is considered to be informative or guide. And I think many editors will also be confused by this somewhat blurred distinction between the two. OhanaUnitedTalk page 06:24, 14 March 2024 (UTC)[reply]
Wikivoyage talk:Park article status has some discussion on the issues. If people are interested in getting this forward, I think it is worth skimming through (at least for those working with parks). One should do some analysis about what differs between a just barely usable and a good usable article (of some category), and what holds articles from becoming guide, as I suggest on that talk page. We could make a comment on forgetting about informative in the case of small towns ("just make them guide instead"); for real cities I think there is a huge difference between barely usable and near guide. –LPfi (talk) 07:10, 14 March 2024 (UTC)[reply]
The status I aim for on any page where I do substantial work is PDG. That means it's Pretty Damn Good, and is a near complete self-sufficient guide to the place. But I almost never upstage beyond "usable" precisely because I don't want the quagmire of definitions and hair-splitting. Another day gone, another town PDG, and tomorrow onto the next. Grahamsands (talk) 22:01, 14 March 2024 (UTC)[reply]

Wikimedia Foundation Board of Trustees 2024 Selection[edit]

You can find this message translated into additional languages on Meta-wiki.

Dear all,

This year, the term of 4 (four) Community- and Affiliate-selected Trustees on the Wikimedia Foundation Board of Trustees will come to an end [1]. The Board invites the whole movement to participate in this year’s selection process and vote to fill those seats.

The Elections Committee will oversee this process with support from Foundation staff [2]. The Board Governance Committee created a Board Selection Working Group from Trustees who cannot be candidates in the 2024 community- and affiliate-selected trustee selection process composed of Dariusz Jemielniak, Nataliia Tymkiv, Esra'a Al Shafei, Kathy Collins, and Shani Evenstein Sigalov [3]. The group is tasked with providing Board oversight for the 2024 trustee selection process, and for keeping the Board informed. More details on the roles of the Elections Committee, Board, and staff are here [4].

Here are the key planned dates:

  • May 2024: Call for candidates and call for questions
  • June 2024: Affiliates vote to shortlist 12 candidates (no shortlisting if 15 or less candidates apply) [5]
  • June-August 2024: Campaign period
  • End of August / beginning of September 2024: Two-week community voting period
  • October–November 2024: Background check of selected candidates
  • Board's Meeting in December 2024: New trustees seated

Learn more about the 2024 selection process - including the detailed timeline, the candidacy process, the campaign rules, and the voter eligibility criteria - on this Meta-wiki page, and make your plan.

Election Volunteers

Another way to be involved with the 2024 selection process is to be an Election Volunteer. Election Volunteers are a bridge between the Elections Committee and their respective community. They help ensure their community is represented and mobilize them to vote. Learn more about the program and how to join on this Meta-wiki page.

Best regards,

Dariusz Jemielniak (Governance Committee Chair, Board Selection Working Group)

[1] https://meta.wikimedia.org/wiki/Special:MyLanguage/Wikimedia_Foundation_elections/2021/Results#Elected

[2] https://foundation.wikimedia.org/wiki/Committee:Elections_Committee_Charter

[3] https://foundation.wikimedia.org/wiki/Minutes:2023-08-15#Governance_Committee

[4] https://meta.wikimedia.org/wiki/Wikimedia_Foundation_elections_committee/Roles

[5] Even though the ideal number is 12 candidates for 4 open seats, the shortlisting process will be triggered if there are more than 15 candidates because the 1-3 candidates that are removed might feel ostracized and it would be a lot of work for affiliates to carry out the shortlisting process to only eliminate 1-3 candidates from the candidate list.

MPossoupe_(WMF)19:57, 12 March 2024 (UTC)[reply]

If anyone is curious what I think would be helpful in Board members, I've put a list of questions at m: User:WhatamIdoing/Board candidates. It always amazes me that some editors believe that fixing thousands of typos on Wikipedia would make a person qualified to set a multi-million dollar budget and lead 600 employees. IMO we need volunteers who understand financial statements and have some general idea of employment law. If you've got some business-related experience and are willing to put in a few hundred unpaid hours for the next three years, please consider volunteering. WhatamIdoing (talk) 18:31, 13 March 2024 (UTC)[reply]

Harrassment[edit]

Apologies to bring this unpleasantness here, however user SHB2000 has a vendetta against me and is harassing me on my talk page (protected for time being). I will be clear - I want no further contact with them, and I would ask the other Admins to counsel them on their behavior. Obviously, I won't contribute to this thread further because I really want no more to do with them Thanks. Andrewssi2 (talk) 10:34, 14 March 2024 (UTC)[reply]

To the community, please comment on Wikivoyage:User rights nominations#User:Andrewssi2 (removal) for their abuse of admin privileges and UCoC violations. --SHB2000 (talk | contribs | meta) 10:45, 14 March 2024 (UTC)[reply]
And TIL that leaving talk page messages about misuse of rollback was "harassment". --SHB2000 (talk | contribs | meta) 10:46, 14 March 2024 (UTC) [comment hidden by LPfi at 11:25, 14 March 2024, comment unhidden on 11:30, 14 March 2024][reply]
Let's keep the discussion on the nomination page. –LPfi (talk) 11:25, 14 March 2024 (UTC)[reply]
@LPfi: Why did you hide my comment? At least you could have given me a courtesy notice on my talk page. I will unhide it as there are no policy-based grounds for hiding that comment. --SHB2000 (talk | contribs | meta) 11:29, 14 March 2024 (UTC)[reply]
I didn't think about a courtesy notice having been appropriate. I assume most regulars watch this page and the threads on it they find interesting. I thought making the hiding obvious was enough. Sorry for misinterpreting best practices.
My reason to hide the comment in the first place was that it was making an accusation, which could prompt a response and a thread partly doubling the one linked above. Referrals to discussions elsewhere should generally (and especially if the topic is sensitive or heated) be made as neutrally as possible.
LPfi (talk) 11:57, 14 March 2024 (UTC)[reply]
Thank you for explaining it through (censoring isn't the best practice for that, though). --SHB2000 (talk | contribs | meta) 12:00, 14 March 2024 (UTC)[reply]
I'm really disturbed to hear about this. Both of you have been valued admins. I will comment on the linked thread. Ikan Kekek (talk) 17:34, 14 March 2024 (UTC)[reply]
As a side note: could someone else possibly not mind editing Andrewssi's comment from "SMB2000" to "SHB2000" – I understand that this was a typo made in good faith but "SMB" is a very inappropriate text slur. --SHB2000 (talk | contribs | meta) 20:30, 14 March 2024 (UTC)[reply]
Well I hope this doesn't preclude everyone from calling you SMB2000. Brycehughes (talk) 02:08, 17 March 2024 (UTC)[reply]

Global ban proposal for Slowking4[edit]

Hello. This is to notify the community that there is an ongoing global ban proposal for User:Slowking4 who has been active on this wiki. You are invited to participate at m:Requests for comment/Global ban for Slowking4 (2). Thank you. Seawolf35 (talk) 19:45, 14 March 2024 (UTC)[reply]

They have made just one edit here, are indefinitely blocked on five projects and a hasty look shows they might have deserved it. –LPfi (talk) 20:47, 14 March 2024 (UTC)[reply]
Yeah, this ban might be a negative for Wikisource but it is probably for the better for the wider WMF world. SHB2000 (talk | contribs | meta) 06:13, 15 March 2024 (UTC)[reply]

Your wiki will be in read-only soon[edit]

Trizek (WMF), 00:00, 15 March 2024 (UTC)[reply]

@Trizek (WMF), is this hoped to be one minute or so? Or is this expected to be longer than the previous ones even if everything goes perfectly? WhatamIdoing (talk) 16:47, 16 March 2024 (UTC)[reply]
We can't know in advance. This time, some scripts took longer than expected to execute, and the read-only happen a donen of minutes after 14:00 UTC. It lasted 3 minutes though. Trizek (WMF) (talk) 16:31, 21 March 2024 (UTC)[reply]

Accessibility of map pins / tube map references[edit]

Hey there, I've been slowly preparing Wikivoyage for night mode. On the most part it's looking pretty good for that, but I'm noticing that we have many problematic accessibility issues in the standard version of the site. I'm using https://chromewebstore.google.com/detail/wcag-color-contrast-check/plnahcmalebffmaghcpcmpaciebdhgdf to get an overview of the issue in our pages.

  1. Problem 1 - Listing numbers
    In our use of colors for maps - for example the map pins we use e.g. the Do, See etc.. templates we generate boxes with the pin number inside them. In the London article for example "Watch Tennis at Wimbledon" as a gray box with white text. This does not pass WCAG AA ( https://webaim.org/resources/contrastchecker/) so means that text is unreadable to certain users.
  2. Problem 2 - the pins. For the pins themselves, I am not sure of the constraints at play here, but again the colors and backgrounds are not always accessible.
  3. I'm also seeing some accessibility issues in templates like  VIC  where the white text on blue is not accessible to some readers. In this case we can probably switch from white text to black text, or alter the background colors slightly (where possible).

Proposed solutions:

  • I'd like to suggest that we move away from text on backgrounds for this sort of thing. For example instead we could move the color alongside the text it represents like in this example:

https://en.m.wikivoyage.org/w/index.php?title=London&diff=4847875&oldid=4847186&title=London&diffonly=1. Could we do something similar to this work for the See, Do etc.. templates?

  • I think we should provide some better guidelines to editors - particularly in the template namespace. Do we have any existing pages that guide editors around how they use colors on this site?


Thanks in advance for your input and ideas!

Jdlrobson (talk) 22:52, 17 March 2024 (UTC)[reply]

I can only really comment anything meaningful to your third point, being a major contributor to RINT myself. Editing labels like  VIC  would be highly problematic, as RINT's purpose is to reflect the labelling as it appears in place. The Victoria line simply uses that blue and that white. Switching the colours to anything else would make it more difficult for a reader to recognise the branding when visiting. Besides, a lot of these colours have passed design boards galore - TfL's lines are one of those. A single Chrome plugin flagging it as an accessibility issue is not something I would value over representing reality accurately. There no doubt are some labels that pose genuine accessibility issues, but they are best resolved in a case-by-case scenario.
That said, I did change {{RbE}}, the template responsible for generating the RINT labels, to use red instead of light grey whenever a colour is not defined, as red is the most common line colour. That should resolve the biggest accessibility issue with RINT that can be fixed en-masse.
Wauteurz (talk) 21:33, 18 March 2024 (UTC)[reply]
Yeah, while it is tempting to change the colours from an accessibility standpoint, changing the colour defeats the entire purpose of the template. --SHB2000 (talk | contribs | meta) 09:59, 20 March 2024 (UTC)[reply]

This page might need an update. Are any of the social media accounts still active? (none of the 6 users in charge of maintaining WV's FB and X/Twitter accounts are active anymore) --SHB2000 (talk | contribs | meta) 09:58, 20 March 2024 (UTC)[reply]

Looking at it, May 30, 2021 for FB and some date around 3 years ago for X/Twitter (need an account to open the page). Should the English Wikivoyage permanently abandon its social media accounts? --SHB2000 (talk | contribs | meta) 10:31, 20 March 2024 (UTC)[reply]
Keep — Since many people in the world are interconnected with social media (including me, of course), I think the social media accounts of Wikivoyage should be kept as they are obvious platforms to promote our project. We should also venture into the Threads app to promote our project to the Insta users. Sbb1413 (he) (talkcontribs) 17:31, 23 March 2024 (UTC)[reply]
I agree in principle, but those accounts are literally abandoned and there's no way for any of us to take over both the FB and X/Twitter accounts since almost all of users maintaining those accounts have left. --SHB2000 (talk | contribs | meta) 09:00, 27 March 2024 (UTC)[reply]
If we can't take over those accounts, then it is better permanently abandoning those accounts in favor of new ones. Sbb1413 (he) (talkcontribs) 09:45, 27 March 2024 (UTC)[reply]
Are the people who maintained them not contactable? I assume they have other things going on in their lives, but they may be reading their email, and somebody may even have their phone numbers. If so, they should be able to hand over rights to the accounts. Leaving abandoned accounts behind and creating new ones gives a bad image. If we have to create new ones, we need to create some mechanism for the situation not to be repeated (and put a note and link on the old ones, if possible). –LPfi (talk) 10:36, 27 March 2024 (UTC)[reply]
Hmm, I suppose LtPowers might be contactable given they've made sporadic edits both here and on Wikipedia, but all of the others haven't made edits in years (except Andre, who left due to abuse of admin tools on Commons). --SHB2000 (talk | contribs | meta) 10:56, 27 March 2024 (UTC)[reply]
Those two both have their email enabled. If their email addresses are stable non-throw-away ones, them not editing doesn't affect being able to reach them. Some in the community may also have personal contacts to them. Similarly with the others. –LPfi (talk) 12:49, 27 March 2024 (UTC)[reply]
Yes, for heaven's sake, I'm still pingable and emailable. Andrew did such a good job with the Facebook postings that I fell out of the habit, and no one notified me when he stopped doing them. Plus I didn't (and don't) really have the time to keep up with it. I will say that I don't know that we ever got much engagement on Facebook (can't speak to the other social media), but I'm happy to add other people as admins if anyone wants to step forward. Powers (talk) 13:47, 27 March 2024 (UTC)[reply]

I would suggest that at minimum, we post Destination of the Month, Off the Beaten Path and Featured Travel Topic each month. They seem like low hanging fruits, high quality entries and give us something to post about on a regular basis without looking too spammy or bot-like. OhanaUnitedTalk page 19:18, 27 March 2024 (UTC)[reply]

I don't disagree, but someone has to write the blurbs. It gets to be a lot for one person. Powers (talk) 19:48, 27 March 2024 (UTC)[reply]
Just use the lead section of those articles as blurbs. No need to reinvent the wheel. OhanaUnitedTalk page 04:16, 28 March 2024 (UTC)[reply]
Or use the blurbs that will go on the main page. --SHB2000 (talk | contribs | meta) 04:24, 28 March 2024 (UTC)[reply]

Early access to the night mode (mobile web, logged-in)[edit]

Hi everyone, as announced in November, the Web team at the Wikimedia Foundation is working on night mode. A very early version of this feature is now available on a small set of wikis. Because there are active technical editors in your community, we have decided to roll it out here. But don't worry, the new feature is not disruptive! (See the "known limitations" section below.) It's important for us to work together with you before we release this feature to a wider audience. Our goals for the early rollout are to:

  • Show what we've built very early. The earlier you are involved, the more your voices will be reflected in the final version
  • Get your help with flagging bugs, issues, and requests
  • Work with technical editors to adjust various templates and gadgets to the night mode

Go to the project page and the FAQ page to see more information about the basics of this project.

Known limitations of the initial release

  • Currently, night mode is only available on mobile, for logged-in users who have opted into advanced mode, as an opt-in feature.
  • Gadgets may initially not work well with night mode and may have to be updated.
  • Our first goal is making night mode work on articles. Special pages, talk pages, and other namespaces have not been updated to work in night mode yet. We have temporarily disabled night mode on these pages.

What we would like you to do (the broad community)

Consider linking to the Recommendations for night mode compatibility on Wikimedia wikis on pages explaining how to format templates and similar pages. Soon, this page will be marked for translation. We would like to emphasize that the recommendations may evolve. For this reason, we are not suggesting to create your local wiki copies of recommendations. At some point, the copy could become different from the original version.

What we would like you to do (template editors, interface admins, technical editors)

When most bugs are solved, we'll be able to make the night mode available for readers on both desktop and mobile. To make this happen, we need to work together with you on reporting and solving the problems.

  1. To turn it on, use the mobile website (for example, this is what the main page looks like on mobile) and go to the settings part of your menu and opt into advanced mode, if you haven't already.  Then, set the color to night. (Later, we will be allowing the device preferences to set night mode automatically).  
  2. Next, go to different articles and look for issues:

Thank you. We're looking forward to your opinions and comments! SGrabarczuk (WMF) (talk) 18:24, 20 March 2024 (UTC)[reply]

@SGrabarczuk (WMF), I'm having a problem with https://night-mode-checker.wmcloud.org/enwikivoyage-mobile-light/ When I click one of the names to uncollapse the list of errors, it uncollapses it, and then opens the page on top of the list. Should that be opening the article in a new tab? WhatamIdoing (talk) 01:38, 22 March 2024 (UTC)[reply]
Hey @WhatamIdoing! Are you asking if the page could be opened in a new tab instead of the same tab? SGrabarczuk (WMF) (talk) 11:33, 22 March 2024 (UTC)[reply]
That's one way to solve my problem. WhatamIdoing (talk) 21:56, 22 March 2024 (UTC)[reply]
I see. Well, I was asking because I wasn't sure I understood what the problem was. Could you rephrase the question? SGrabarczuk (WMF) (talk) 23:46, 22 March 2024 (UTC)[reply]
As a contributor who would like to resolve problems, I want to look at the list of errors on a page. However, when I go to https://night-mode-checker.wmcloud.org/enwikivoyage-mobile-light/, the list of errors is collapsed. When I click on (for example) "Main_Page - Total Errors: 12", the Cloud Services tool is immediately overwritten by the Main Page. I don't want to see the Main Page itself in this tab; I want to see the list of errors. WhatamIdoing (talk) 18:48, 23 March 2024 (UTC)[reply]
it's just a bad UI :). You can expand by clicking outside of the links or right click and open in new tab.
The list of errors is not too useful out of context to be honest. I would recommend using the browser extension on the pages with a high amount of errors.
Szymon - you can talk to Kim about improving the UI while I am out!
I think it would be useful to finish up my video too. Jdlrobson (talk) 10:32, 25 March 2024 (UTC)[reply]
Is there a way to turn on dark mode on desktop? Special:Preferences#mw-prefsection-rendering doesn't have anything for me. --SHB2000 (talk | contribs | meta) 06:05, 22 March 2024 (UTC)[reply]
Hello @SHB2000, great question. It's too early to enable it on desktop. We'll roll it out on more wikis on mobile, and then on desktop, as a beta feature. You may read more about this in our FAQ. There's a table there with all the details. SGrabarczuk (WMF) (talk) 11:36, 22 March 2024 (UTC)[reply]
That's all good. I do like the look of it on mobile, though. --SHB2000 (talk | contribs | meta) 11:40, 22 March 2024 (UTC)[reply]
If people can opt in on mobile and let me know via my talk page if you see any articles that look broken I will be happy to get those fixed. The top 100 most read are looking good so hopefully this will be on desktop soon. Jdlrobson (talk) 16:03, 23 March 2024 (UTC)[reply]
@Jdlrobson: I notice Template:Infobox is broken, not displaying content, e.g. see the one under United States of America#Holidays. Was it this edit? Brycehughes (talk) 15:40, 24 March 2024 (UTC)[reply]
Seems it was. I rolled it back but now the HTML table styling is off. Brycehughes (talk) 15:55, 24 March 2024 (UTC)[reply]

──────────────────────────────────────────────────────────────────────────────────────────────────── At the German Wikivoyage, we are using the solution of the English Wikipedia for desktop computers. It is working well (now only for logged-in readers). --RolandUnger (talk) 16:51, 24 March 2024 (UTC)[reply]

Article suggestion[edit]

If anyone is up to the task of writing it, I think a Canada without a car article will be a good one to have, along the lines of the United States without a car and Australia without a car. I've never lived in Canada, but based on my visits there. Canada is also a very car dependent country. And it seems that Canada's famed national parks are very hard to explore without a car. If anyone knows if any of them can be explored without a car, that information will certainly be useful. The dog2 (talk) 15:15, 25 March 2024 (UTC)[reply]

This looks like a viable topic. Perhaps some of these webpages would inspire someone to create it:
WhatamIdoing (talk) 17:31, 25 March 2024 (UTC)[reply]
Re alternative transport. Brycehughes (talk) 18:11, 25 March 2024 (UTC)[reply]
Yeah, from experience the Vancouver metro area is easy to get around without a car, but I needed to rely on one of my mum's friends in rural BC. A guide like this would be very helpful for many travellers. --SHB2000 (talk | contribs | meta) 08:59, 27 March 2024 (UTC)[reply]
Because of overcrowding at the parking lots, Banff National Park has shuttle buses to get people around, but other parks are difficult to access. Park Bus has sporadic trips from Toronto to ten parks in summer. Rouge Park is a national park in Toronto, accessible by city bus. Ground Zero (talk) 11:47, 27 March 2024 (UTC)[reply]

Multilingual static maps[edit]

I did a little experiment with File:Norðoyar regions map.png, where I tried to minimise the amount of English I used and always use the local dialect if possible to make the map as multilingual as possible. This would prevent having to translate static maps across different-language Wikivoyages, but it would also mean that the map contains some non-English phrases. There isn't any policy surrounding this, so what does everyone else think of minimising the amount of English used to ensure the same map can be used on different-language Wikivoyages. --SHB2000 (talk | contribs | meta) 03:18, 29 March 2024 (UTC)[reply]

This seems like a great use case for translatable SVG. Is there some incentive for what is clearly a non-representational map to be PNG? See e.g. File:ABO blood group diagram.svg and the many pages using c:Template:Translate. —Justin (koavf)TCM 03:36, 29 March 2024 (UTC)[reply]
Unfortunately, using a translatable SVG isn't on the table here since the quality of the SVGs that come from Inkscape is beyond hopeless. --SHB2000 (talk | contribs | meta) 03:42, 29 March 2024 (UTC)[reply]
0___o? There are a lot of good maps on c: made in SVG, whether Inkscape or something else. —Justin (koavf)TCM 04:05, 29 March 2024 (UTC)[reply]
They work fine if you use a text editor or Illustrator, but not Inkscape. It is the only reason why policy requires uploading both a PNG and an SVG file. --SHB2000 (talk | contribs | meta) 04:53, 29 March 2024 (UTC)[reply]
Is the code needed for translation difficult? Otherwise, as you edit the map as SVG anyway, why wouldn't you include the translations in the SVG code? Or is it that the base map is horrendous Inkscape code and Inkscape lacks the functionality?
I like having the map mostly in the local language (I don't think anybody regards Faroese a dialect), but there will be issues when the English name is very different (cf Jorvik for York), or there are different scripts (I cannot use maps in Chinese or Hebrew).
The key in the local language and English makes it usable to most people, but even for Swedish or French, the English looks a bit imperialistic. For projects in English the bilingualism is nice – I'd like having Swedish maps e.g. for Euskadi to be trilingual (Swedish/Basque/Spanish).
LPfi (talk) 11:06, 29 March 2024 (UTC)[reply]
The issue is the latter – the base map is horrendous Inkscape code and Inkscape lacks functionaliity.
Thanks for the input on local language (yes, I meant language, not dialect – thanks for picking up on that). Maybe should we limit this practice only where the local language uses a Latin script? (unlike OSM's current approach) --SHB2000 (talk | contribs | meta) 11:19, 29 March 2024 (UTC)[reply]
Although the base SVG maps are in English, you can see that there are both English and Bengali (my native language) labels in different layers. I disable the Bengali layer when I upload or update the maps. I use Inkscape to create SVG maps and export PNG maps for use in respective Wikivoyages. However, I have decided to replace those monolingual PNG maps with multilingual (bilingual or trilingual, depending on region) ones soon. Sbb1413 (he) (talkcontribs) 07:11, 30 March 2024 (UTC)[reply]
@LPfi: File:NLR diagram.svg is another example of a horrendous base map compared to the PNG map – it's bad enough where many text elements are hidden beneath the pictograms (namely the light rail and the wheelchair pictograms). --SHB2000 (talk | contribs | meta) 08:03, 4 April 2024 (UTC)[reply]

Random error messages appearing on pages[edit]

On several pages, this message keeps appearing

https://imgur.com/a/Mq3p3UI

I try going to past revisions of pages but the message keeps showing up. How can I remove the message and get the pages to start working again? Matematica6 (talk) 03:46, 30 March 2024 (UTC)[reply]

Looks like someone vandalized a template. And I don't see the error message anymore. OhanaUnitedTalk page 05:12, 30 March 2024 (UTC)[reply]
Yes, Bsadowski1 has taken care of it. --SHB2000 (talk | contribs | meta) 05:56, 30 March 2024 (UTC)[reply]

Central Jersey[edit]

The latest version of the New Jersey Travel Guide designates Central Jersey as a distinct region. Should it be incorporated into the Wikivoyage hierarchy? If not, should it be an extra region? JsfasdF252 (talk) 00:45, 5 April 2024 (UTC)[reply]

I would say that it does not:
New Jersey is commonly divided into two regions: North Jersey (including Bergen, Essex, Hudson, Passaic, Morris, Sussex and Warren counties) and South Jersey (including Camden, Burlington, Gloucester, Cumberland and Salem counties). Sometimes Central Jersey (Middlesex, Mercer, Somerset and Hunterdon counties) is considered as a third region. The trichotomous division is up for debate; for example Union and Ocean counties can be considered to both be part of Central Jersey or as part of North and South respectively. For the purpose of this guide, those two regions are further divided into four areas.
I would say that Central Jersey is an amorphous region that some people think exists, and I doubt it's useful enough to be covered in an extra-region article (Upstate New York similarly would not be a useful article), but if you think it is, what would you add to the single sentence that is the second in the above paragraph? Ikan Kekek (talk) 03:08, 5 April 2024 (UTC)[reply]
I meant the travel guide at visitnj.org, not the Wikivoyage one JsfasdF252 (talk) 05:05, 5 April 2024 (UTC)[reply]
OK, I think their take on what is Central Jersey is debatable. To me, Trenton, as a suburb of Philly, is in South Jersey. There are also towns that I tend to think of as more characterized by being right near Pennsylvania than by being Central or North Jersey (Flemington, Lambertville). But of course all of that is informed by my being a New Yorker. To me, a place like Scotch Plains is in Central Jersey, but it really isn't, geographically. Anyway, there's definitely nothing preventing you from creating an extra-region article if you think it would be helpful. Would you plan to do it for the other New Jersey tourism regions we don't use? Ikan Kekek (talk) 05:51, 5 April 2024 (UTC)[reply]
Wikivoyage uses four regions; visitnj.org uses seven. It would be a big job to re-sort all of NJ along the lines of visitnj, and we risk them changing their minds in five years. If someone has the time and energy to take this on, I wouldn't object to it, but it's not a job for me. Ground Zero (talk) 11:17, 5 April 2024 (UTC)[reply]
We don't need to change our hierarchy to exactly match the one used by visitnj. In particular, the Jersey Shore region should not be altered. JsfasdF252 (talk) 18:27, 7 April 2024 (UTC)[reply]
The Southern Shore, one of visitnj's tourism regions, was part of the Wikivoyage hierarchy until I converted it to an extra region, since it makes much more sense to have the Jersey Shore region extend down to Cape May County. (Visitnj's Shore region only has Monmouth and Ocean Counties, while Atlantic County is represented as a region to itself.) If Central Jersey gets its own region article (extra or hierarchical) then should North and South Jersey get their own region articles, or should they merely be redirects? JsfasdF252 (talk) 18:25, 7 April 2024 (UTC)[reply]

Amber Alert[edit]

The following discussion is closed. Please do not modify it. Subsequent comments should be made elsewhere.
This particular event was an apparently brief parental abduction resulting in no risk to travelers or the general public. It has been fully resolved, and the child is safe and unharmed. If you feel a need to discuss this non-travel-related incident further, please do so at Talk:British_Columbia#Warning -- Amber Alert and not here. Thank you. WhatamIdoing (talk) 05:56, 6 April 2024 (UTC)[reply]

There is a discussion at Talk:British_Columbia#Warning_--_Amber_Alert about whether an "Amber Alert" (a warning about an abducted child) should be included in the article in British Columbia. Ground Zero (talk) 21:54, 5 April 2024 (UTC)[reply]

I think it's important to provide information about safety concerns in travel articles, including Amber Alerts. As travelers, we often visit unfamiliar places and may not be aware of local safety issues. By including this information in the article, we can help travelers make informed decisions and potentially avoid putting themselves at risk. 70.68.168.129 22:10, 5 April 2024 (UTC)[reply]
The discussion is taking place on the Talk:British Columbia page, not here. There is no need abs no value in repeating the same argument over and over. Ground Zero (talk) 22:15, 5 April 2024 (UTC)[reply]
I understand that the discussion is taking place on the Talk:British Columbia page, but I believe it's still relevant to mention safety concerns, including Amber Alerts, in travel articles. As travelers, we should be aware of potential risks and take necessary precautions. Providing information about Amber Alerts can help us make informed decisions and travel more responsibly. 70.68.168.129 22:26, 5 April 2024 (UTC)[reply]
Here's a tip for persuading people: repeating yourself ad nauseum doesn't convince anyone. It just annoys them. And it's boring. Don't be boring. Ground Zero (talk) 22:27, 5 April 2024 (UTC)[reply]
Thank you for the tip. I'll make sure not to repeat myself excessively in the future. However, I still believe that safety concerns, including Amber Alerts, should be mentioned in travel articles. As travelers, we have a responsibility to look out for each other and share important information that could help keep us all safe. 70.68.168.129 22:31, 5 April 2024 (UTC)[reply]
Let's keep the discussion in one place, please – Talk:British Columbia. Having this in two places makes things more confusing and will likely make your chance of successfully persuading others less likely. --SHB2000 (talk | contribs | meta) 22:52, 5 April 2024 (UTC)[reply]
@SHB2000 I apologize for the confusion. I will continue the discussion on the Talk:British Columbia page. As for the Amber Alert specifically, I believe that it is a valid safety concern that should be addressed in travel articles. Travelers often visit unfamiliar areas and may not be aware of local safety issues. By providing information about Amber Alerts, we can help them make informed decisions and travel more responsibly. 70.68.168.129 22:57, 5 April 2024 (UTC)[reply]
So you have said, over and over and over again. You just are not listening to what other members of the Wikivoyage community are saying. Ground Zero (talk) 23:55, 5 April 2024 (UTC)[reply]

AI-"generated" edits[edit]

In a discussion at User talk:70.68.168.129 @Ibaman: wrote:

"AI-generated edits are unneeded and unwanted in this travel guide. Shut down. Turn off."

I agree completely.

Other opinions? Does this need to be added to a policy page? Which one? Pashley (talk) 03:05, 7 April 2024 (UTC)[reply]

Also Wikivoyage:Votes for deletion/December 2023#Car rental in Tashkent. While I haven't used AI to write anything, I have experimented by asking ChatGPT with this prompt: "Write a Wikivoyage article about [insert destination]" to see what would happen. I do appreciate AI in creating a draft by summarizing the destination (which then I could verify and adapt into my own words before creating the page if I had gone through with this). It appears to be quite accurate and I suspect that the LLM used Wikipedia page entries to learn the text for these destinations. I'm not sure where we should draw the line on AI usage in this project. OhanaUnitedTalk page 03:40, 7 April 2024 (UTC)[reply]
Using AI responsibly like you describe it, including changing wordings and checking facts, should be no problem. If you do it like that, probably nobody notices that you used AI. It doesn't differ that much from using encyclopaedias, competing travel guides and other external resources to gather information. In the cases where using AI has been apparent, the text obviously hasn't been checked and rewritten, and not knowing how the used AI has been trained, copyrighted expressions main remain and some of the statements may be hallucinations.
I don't know how to word a guideline so that it does allow responsible use, without encouraging use that is highly problematic. Those who use AI without accounting for the issues, probably aren't prone to follow the spirit nor the wording of such a guideline, but may argue (stubbornly) that it allows their usage of such tools.
LPfi (talk) 06:01, 7 April 2024 (UTC)[reply]
I've used ChatGPT for translating content, but that's about it (since the copyright remains with the original WM authors). It's fine to be used in discussions, but again, only for translations. --SHB2000 (talk | contribs | meta) 07:54, 11 April 2024 (UTC)[reply]
As I see it, these programs are basically plagiarism machines & we already have more than enough problems with plagiarism -- mostly uncredited copying from WP or lumps of text from someone's marketing material. We've also sometimes had problems with machine-generated text, in particular some pretty awful translations.
I conclude that we should ban use of AI-generated text entirely, at least in main space. Pashley (talk) 08:08, 7 April 2024 (UTC)[reply]
I agree with a complete ban. If that is too far, we could add "an individual editor may be allowed to use AI for a specific purpose if there is consensus on that use in the pub". Longer term I would like to see AI running on a WMF server to offer features like an improved InternetArchiveBot which could replace "dead link" with "suspect business closed - see this newspaper report of it closing". AlasdairW (talk) 13:00, 7 April 2024 (UTC)[reply]
Given that you know you've used AI effectively when nobody can tell that you've used AI, I can't see how banning AI would hurt, as it basically implies no obvious AI, which no one wants anyway. Brycehughes (talk) 23:56, 8 April 2024 (UTC)[reply]
For exactly that reason, I can't see how banning AI would help. The options are:
  • You use AI, but the content was good, so nobody objects – no harm, no foul (except perhaps in the opinion of people who believe that scrupulous compliance with rules is a morally good action, rather than a means to an end).
  • You use AI, but the content was bad, so it gets reverted – the "ban" was pointless (we revert bad content no matter how it's generated).
  • You don't use AI to create good content, somebody incorrectly claims you did, so good content gets reverted – we lose good content (and probably good will and time in unpleasant discussions, too).
  • You don't use AI to create bad content, somebody incorrectly claims you did, so bad content gets reverted – the ban was pointless (it would have been reverted for being bad anyway)
  • You want to use AI to create good content , but you're afraid of breaking the rules, so you don't contribute at all – we lose a new contributor.
BTW, I am leery of people who claim that they can tell the difference between a poor writer, an English language learner, and an AI tool. I put some of my Wikipedia articles through an AI detection program, and it had pretty much 50–50 results. I'm told that the accuracy is much worse for shorter content, which is most of what we do here.
If you want rules that can be effectively enforced, I suggest:
  • No high-volume editing by newcomers.
  • Regular patrollers are encouraged to check some of the facts independently.
WhatamIdoing (talk) 03:17, 9 April 2024 (UTC)[reply]
I agree with most of that reasoning. I am one of those who do believe that one shouldn't ignore rules even when they seem counterproductive – the "ignore all rules" rule is about cases where breaking the letter of a rule indeed follows the intended spirit of the rules as a whole.
Rule of Law is an important principle, which I believe is an important factor in the success of the Nordic countries, and being pragmatic about rules can have unforeseen consequences. (Still, the Finnish judicial system has what essentially is an ignore-all-rules rule: the main book of laws quotes Olaus Petri saying that what is not right cannot be law, and judges are allowed to ignore laws they deem unconstitutional – such as violating Human Rights.)
I would certainly not recommend using AI if we forbid it – but unenforceable rules are bad exactly because they undermine the respect for rules in general.
LPfi (talk) 07:59, 9 April 2024 (UTC)[reply]
Don't we need to make remarks about the use of AI in Wikivoyage:Copyleft, at least? "Good" and "bad" is not the only issue; copyright violation is also relevant. Ikan Kekek (talk) 11:17, 9 April 2024 (UTC)[reply]
Copyvio content is always bad content. However, AI generation is not synonymous with copyright violation. Training an AI system on CC-SA content, for example, does not violate anyone's copyrights. WhatamIdoing (talk) 20:47, 9 April 2024 (UTC)[reply]
I'm concerned that inaccurate AI-generated content (which includes most ChatGPT-generated content about reasonably obscure topics, in my experience) may be harder to detect than other bad content. ChatGPT is good at writing things that sound plausible but are actually bogus. In other words, I'm skeptical of the reasoning in User:WhatamIdoing's bullet point that reads "You use AI, but the content was bad, so it gets reverted" – I think AI-generated content may slip through the cracks more easily than other misinformation.
I also think it may be useful to have some kind of warning for good-faith editors who may not realize how unreliable language models are in terms of accuracy. —Granger (talk · contribs) 00:56, 10 April 2024 (UTC)[reply]
We could have a warning in some guideline giving advice on good and bad sources, without explicitly banning or accepting AI-derived content. A warning can hardly be seen as sanctioning it. –LPfi (talk) 07:14, 10 April 2024 (UTC)[reply]
Although I have never used AI in any Wikimedia project, l do use AI to get the solution of a given problem since 2023 (when the CHATGPT revolution took place). However, I always use my own words when I write the solution myself. If I were going to use AI to contribute in English Wikivoyage, I would ask for transport options, list of attractions and activities with details, list of notable hotels and restaurants etc. individually, and then use my own words to describe these. However, I would never ask to write an entire WV article for me. Sbb1413 (he) (talkcontribs) 06:17, 10 April 2024 (UTC)[reply]
For reliability, the things found by AI should always be checked. If you don't find the POI or connection in other sources, confirming the location and other details, then don't list it. –LPfi (talk) 07:17, 10 April 2024 (UTC)[reply]
It's hard to even read the discussion and make sense out of what the user wants to say. "It's important to" is a dead giveaway of ChatGPT. You don't want to spend your time writing your own thoughts down, but expect others to read it? -> you earned a Ban, easy as that. -- andree 09:48, 12 April 2024 (UTC)[reply]
I don't think that phrase is a "dead giveaway". For one thing, that exact phrase appears on 363 pages here, and many of those pre-date ChatGPT's existence. WhatamIdoing (talk) 18:10, 12 April 2024 (UTC)[reply]
YMMV, but 1/2 of answers I get (if I ask non-technical stuff in v3.5) have this condescending tone. I'm allergic to that, so it may be the case that it just triggers me  :-) -- andree 18:46, 12 April 2024 (UTC)[reply]
I'm not surprised; ChatGPT, after all, needed to learn its content from somewhere. --SHB2000 (talk | contribs | meta) 21:41, 12 April 2024 (UTC)[reply]
The sanctimonious tone sounded more like Gemini to me. But that one unhinged comment sounded like the infamous Sydney. Brycehughes (talk) 22:05, 12 April 2024 (UTC)[reply]

Change of Mobile View Watchlist[edit]

Since a few hours I noticed a change in the mobile view of the watchlist. The left side of the list has a grey background and is covering part of the text. FredTC (talk) 10:29, 10 April 2024 (UTC)[reply]

@Jdlrobson, do you know which team is working on the watchlist? I assume this problem was on the current deployment train. WhatamIdoing (talk) 16:44, 10 April 2024 (UTC)[reply]
Looks like a side effect of phab:T358904. I'm currently traveling so would you be able to raise the alarm? Seems like this should be fixed immediately and possibly block train from rolling out further. Jdlrobson (talk) 00:14, 11 April 2024 (UTC)[reply]
It is back to normal now. FredTC (talk) 13:34, 12 April 2024 (UTC)[reply]

Gender-neutral language[edit]

@SHB2000 recently changed some text in Go, replacing "he or she" (which I'd written) with "they". This is fine, though I do not think necessary; certainly either is better than just using "he". In general, we should avoid making any assumption about anyone's gender (traveller, editor, or in this case go player). Should we make such changes elsewhere? Is there other usage we should correct?

The notion that "singular they" is somehow ungrammatical is utterly bogus; using it with an indefinite antecedent ("Has everyone got their passport?") is entirely normal English that has been in the language longer than singular you. One reference. It can also be used in cases where the gender is unknown (most people you interact with on the net), or undefined (some angels & demons, perhaps God?). Recent attempts to extend the usage are more debatable. In general I'd say anyone who announces "My pronouns are ..." should be laughed at, not humoured, but on the net it may be a legitimate way to avoid being labelled.

There are other cases of arguably sexist language. e.g. Great Rift Valley has "Mankind seems to have evolved largely in this valley" and search shows that "mankind" is used in many other places. These could all be replaced with "humanity", but in my opinion that would be silly. Probably there are other phrases that might be changed, but that I have not noticed.

Do we need a policy on this, or some advice in a style guide? Pashley (talk) 01:54, 12 April 2024 (UTC)[reply]

I think "mankind" has evolved to be gender-neutral. I disagree with "In general I'd say anyone who announces "My pronouns are ..." should be laughed at, not humoured, but on the net it may be a legitimate way to avoid being labelled.", but won't delve into it to avoid a rather off-topic discussion on this page. --SHB2000 (talk | contribs | meta) 03:46, 12 April 2024 (UTC)[reply]
MANkind, huMANity, perSON... I'd say if someone wants to search for sexist verbs in a language, they will find it. I'm for equality as the next person, but constantly pushing annoys even the biggest supporters, IMO. Definitely don't make it a policy. If someone wants to spend time thinking about it and fixing it, let them - but don't bother people that don't care. TBH, I wonder more why we have an article, with half of it describing the rules of Go :-))) -- andree 09:42, 12 April 2024 (UTC)[reply]
I also disagree creating a policy on gender neutrality. You can simply recommend the users to use gender-neutral language in WV:MOS. You can also link to the relevant WP policy if necessary. Sbb1413 (he) (talkcontribs) 10:54, 12 April 2024 (UTC)[reply]
I also don't think we need a policy on this. Mankind is not sexist, just like saying "Hey, guys" isn't sexist. People who make those types of arguments are the types with solutions in search of problems. Most of the time we refer to the type of person ("travelers", "backpackers", "hikers", "divers", etc.), so I don't think we generally need to get involved with playing pronoun games. I don't think "his or her" is a problem, because it does cover all humans, despite what the narcissistic fake LGBT "personal pronoun"-types claim (I resent what the "self-identity" movement is doing to real LGBT people, but that's beyond scope), but "their" is also not a problem. In short, I don't think this is an issue. It's fine as it is but was also fine as it was. ChubbyWimbus (talk) 11:07, 12 April 2024 (UTC)[reply]
"because it does cover all humans" – no it doesn't. Neopronouns are used because it reflects the gender identity of non-binary individuals better than conventional pronouns. --SHB2000 (talk | contribs | meta) 11:16, 12 April 2024 (UTC)[reply]
Non-binary is as legitimate as saying you're a turtle or a douvet cover. It makes a mockery out of real LGBT people and their issues. The non-binary mantra of "I say therefore I am" is a false claim, but this discussion is beyond scope and a consensus has been reached, so we can just leave this where it is. ChubbyWimbus (talk) 11:27, 12 April 2024 (UTC)[reply]

──────────────────────────────────────────────────────────────────────────────────────────────────── Let's stick with the question of whether we should have a policy, and avoiding bringing a culture war to the Travellers' Pub. Wikivoyage is written by a collection of people. The language Wikivoyage uses will evolve as the language of its writers evolves. I don't think we need a policy. Sexist, racist, homophobic, transphobic, ablist language has no place in Wikivoyage. Inclusive language is always preferable in an project aiming to appeal to a broad audience. If someone wants to replace non-inclusive language with inclusive language, they should go ahead and do it. Writing a policy, however, is going to lead to a whole bunch of dyspeptic rants and unproductive debates. Let's not spend our energy on that. Ground Zero (talk) 11:37, 12 April 2024 (UTC)[reply]

Agreed. My main issue was with ChubbyWimbus' denialism of non-binary people which has no place on Wikimedia. I don't like closing discussions but can we just close this? I don't think we're going anywhere by continuing it. --SHB2000 (talk | contribs | meta) 11:41, 12 April 2024 (UTC)[reply]
As I said, everyone agrees, so unless someone opposes, consensus has been reached. ChubbyWimbus (talk) 11:42, 12 April 2024 (UTC)[reply]
I agree that ChubbyWimbus' denialism of non-binary people has no place on Wikimedia. Ground Zero (talk) 11:46, 12 April 2024 (UTC)[reply]
He said he despises that stuff (not that he denies existence of such people), and even gave a valid reason, IMO. The non-binary people can call themselves whatever they please. They can't force anyone to like it, though. -- andree 11:58, 12 April 2024 (UTC)[reply]
I think you are misreading CW's comment. See the one at 11:27, 12 April 2024. Ground Zero (talk) 12:01, 12 April 2024 (UTC)[reply]
No, he is right. I didn't say that nobody identifies as non-binary. I said I don't agree with the logic or lack thereof surrounding "non-binary" and that I think it does harm to LGBT people. The referenced policy is specifically about dealing with others users and states that we should identify users how they wish to be identified. Nowhere did I identify anyone in a way that they asked not to be identified nor did I state anywhere that I would refuse to do so. It does not state that users must all have the same religious or ideological beliefs or that they all must state that they believe in all religious or ideological beliefs. ChubbyWimbus (talk) 12:26, 12 April 2024 (UTC)[reply]
It is never constructive to bring a w:Straw man argument into a discussion. No-one argued that users must all have the same religious or ideological beliefs or that they all must state that they believe in all religious or ideological beliefs. No-one claimed that you kick puppies or beat your spouse, either.
It is clear that you are looking to have a fight about this. There are other of places you can fight about this on the internet; you don't have to do it in the Travellers' Pub. This is a forum about building a travel guide.
The comments that "despite what the narcissistic fake LGBT "personal pronoun"-types claim" and "Non-binary is as legitimate as saying you're a turtle or a douvet cover. It makes a mockery out of real LGBT people and their issues. The non-binary mantra of "I say therefore I am" is a false claim" were completely unnecessary, gratuitous, and not germane to the discussion. It makes it clear that you want to have an argument. This is not the place for that.
These comments are insulting and do not meet the Wikimedia Universal Code of Conduct (2.1) "We expect all Wikimedians to show respect for others." They do meet the definition Unacceptable Behaviour (3.1) "Insults: This includes name calling, using slurs or stereotypes, and any attacks based on personal characteristics. Insults may refer to perceived characteristics like... sexual orientation, gender, sex, ... or other characteristics. In some cases, repeated mockery, sarcasm, or aggression constitute insults collectively, even if individual statements would not."
One of the reasons that this behaviour is unacceptable is that it can drive contributors away. The condescending and sarcastic tone taken by CW (and others) in this discussion caused me to take several days off to consider whether I want to spend my time online in a hostile environment. Let's not let this sort of behaviour be tolerated. Ground Zero (talk) 17:06, 12 April 2024 (UTC)[reply]
Not only that, but Chubby's comments are insanely disrespectful, inconsiderate and insensitive to those experiencing gender dysphoria. The WMF knew what they were doing when they created the Universal Code of Conduct, and part of that is to avoid comments like CW's to ensure that communities, including the English Wikivoyage, are "positive, safe and healthy environments". --SHB2000 (talk | contribs | meta) 21:38, 12 April 2024 (UTC)[reply]

This discussion has gone way off the rails. Just stop. Already. Please. Nurg (talk) 23:08, 12 April 2024 (UTC)[reply]

+1. Brycehughes (talk) 23:50, 12 April 2024 (UTC)[reply]
Indeed. Pashley (talk) 01:17, 13 April 2024 (UTC)[reply]
It is sad that the Wikivoyage community has no interest in following Wikimedia's Universal Code of Conduct. It was adopted hy Wikimedia for just this sort of situation. Ground Zero (talk) 01:51, 13 April 2024 (UTC)[reply]
Pashley your framing of a legitimate question was unnecessarily combative, sparked this, to wash your hands now is a bit rich. Whatever. Everyone take a step back. This is a travel guide. Ground Zero you of all people know that this is not Wikipedia and we tend to have a a more cowboy/cowgirl/cowwho approach here. Users want to know where to eat, how to get from A to B. Arguments like these are peripheral to our mission. Brycehughes (talk) 01:59, 13 April 2024 (UTC)[reply]
Wikivoyage is part of Wikimedia. Pashley was out of line; ChubbyWimbus was insulting and looking for a fight. Calling out this toxic behaviour is how we stop Wikivoyage becoming like so many other parts of the Internet. And it is Wikimedia policy. Ground Zero (talk) 02:31, 13 April 2024 (UTC)[reply]
They're opinions that you'd find in any pub around the world including this one. This is a travel website. Brycehughes (talk) 02:48, 13 April 2024 (UTC)[reply]
Wikimedia has a Code of Conduct that requires treating other contributors with respect, and to create a positive, safe environment. ChubbyWimbus is violating that Code of Conduct.
I've created 162 travel articles on the website, so I know it's a travel website. And I think you know you're being condescending in telling me that repeatedly. Being a travel website does not give anyone licence to be insulting, or to use it as a soapbox for their views as Pashley and ChubbyWimbus have done. Ground Zero (talk) 03:10, 13 April 2024 (UTC)[reply]
Ok but I also refuse to believe that you travel around the world asking others abide by the wm code of conduct. So how do you get by? Brycehughes (talk) 03:28, 13 April 2024 (UTC)[reply]
First of all, you're being deliberately insulting and belittling, which is an obvious violation of any code of conduct on a site not known as, like, 4-Chan or Reddit. Second, this is Wikimedia, so you need to either respect the rules, be silent about them, or try to fight them at a much higher level than the Wikivoyage Travellers' pub. What you are doing constitutes harassment, and the high quality of your edits does not give you license to continue such behavior. Ikan Kekek (talk) 06:55, 13 April 2024 (UTC)[reply]
I'm being insulting and belittling... what? Brycehughes (talk) 10:01, 13 April 2024 (UTC)[reply]
@Nurg: No – I would have agreed with you yesterday, but I am not letting ChubbyWimbus' derogatory comments against non-binary people go under the radar and am willing to fight tooth and nail until they retract their comments. --SHB2000 (talk | contribs | meta) 06:58, 13 April 2024 (UTC)[reply]
I do not believe I was at all "out of line", but nor do I think this should be argued here. If you think my rebuttal would be important (I don't), then take the discussion elsewhere — my talk page, a separate thread on this page, a policy talk page, or wherever you like — & I'll give you both barrels. But for heaven's sake either keep this thread for the original question or kill it off since the question is resolved. Pashley (talk) 07:04, 13 April 2024 (UTC)[reply]