Wikivoyage:Travellers' pub

From Wikivoyage
(Redirected from Travellers' Pub)
Latest comment: 9 minutes ago by OhanaUnited in topic Template:Overseasjobscam
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

Commons bot that should warn us about photos nominated for deletion is not working

[edit]

It's important for you all to know about this! See c:Commons:Village pump/Technical#Bot no longer working to warn Wikivoyage about nominations for deletion? It would appear that the only solution at this point is for one of us to monitor c:Commons:Deletion requests at all times. It's a big job, and this is a big problem, because it's a return to the status quo ante, when we had a slew of thumbnails emptied without any notice. I became aware of the problem due to this deletion. I've resumed looking at deletion requests, starting with the earliest date that still has open deletion requests, and I've gotten up to c:Commons:Deletion requests/2024/07/14, but it's a huge job and not one I'll be able to do by myself. If there are other volunteers, maybe we should create an Expedition, so as to keep each other up to date on which days of deletion requests we have already looked through. -- Ikan Kekek (talk) 01:18, 30 August 2024 (UTC)Reply

Oh gosh, not a repeat of 2021 again. A bot for this would be very nice; what exactly happened to it? --SHB2000 (t | c | m) 01:25, 30 August 2024 (UTC)Reply
This is linked from the thread. Ikan Kekek (talk) 01:29, 30 August 2024 (UTC)Reply
@MusikAnimal, is your team working on that Phab task? It's marked as high priority, but nobody's assigned to it. WhatamIdoing (talk) 16:51, 30 August 2024 (UTC)Reply
I'm very sorry for the extremely long delay in reviving this bot! The engineer who wrote it left the Foundation years ago, so we were at a lost when it died last year. Anyway I think at this point there's only a few issues left. I will see what I can get done this week. Thanks for the ping. MusikAnimal talk 19:40, 4 September 2024 (UTC)Reply
Super! Thank you very much. Ikan Kekek (talk) 22:19, 4 September 2024 (UTC)Reply
Thank you! That is very much appreciated, MusikAnimal :-). --SHB2000 (t | c | m) 22:32, 4 September 2024 (UTC)Reply
@MusikAnimal: By any chance, do you have any updates as to how this is going? TIA, --SHB2000 (t | c | m) 07:18, 17 October 2024 (UTC)Reply

Why are our official inserted maps broken?

[edit]

This has been reported to me by some students, and confirmed by me, see my sandbox User:Hanyangprofessor2/sandbox.

The maps inserted from Insert->Map in visual editor do not display location pins.

I.e. this is good code

{{Mapframe|39.95|116.35|zoom=10|width=650|layer=M}}

and this is bad code

<mapframe latitude="39.95" longitude="116.35" zoom="10" width="650" height="418" />

What's wrong? The layer is missing in the bad code, which perhaps could be the answer, but there is no way I can see to enable that parameter. Right now, I am telling my students to copy a map from another article it works in and adjust GPS coordinates manually, but it is a bit annoying that our official, nice, user-friendly way of inserting maps is effectively broken. Hanyangprofessor2 (talk) 05:51, 23 September 2024 (UTC)Reply

Someone with more technical knowledge about the Mapframe template and element can probably add some nuance here, but I'll attempt to explain this issue to the best of my ability.
The element (<mapframe/>) is one of the ingredients for rendering the template ({{Mapframe}}) and its functionality. Other ingredients include Module:map, which adds understanding of GeoJSON data. That processing of GeoJSON data is what makes markers (location pins) render on the map. It's not being called into action through the element - only through the template.
The layer not being defined doesn't play a role here.
On a sidenote, I can't seem to replicate the issue myself - that is, spawning the element instead of the template through the visual editor. As for fixes, you should be able to force the usage of {{Mapframe}} in the visual editor by using Insert → Template and selecting Template:Mapframe through there though.
I hope this helps. Wauteurz (talk) 11:54, 24 September 2024 (UTC)Reply
I assumed something like that, but in my reading of Mediawikiwiki:Help:Extension:Kartographer, the <mapframe> element indeed does render markers, if those are given as geoJSON – and Module:Marker seems to indeed produce geoJSON code. Does the element require the code to be included as content of the element itself? –LPfi (talk) 14:18, 24 September 2024 (UTC)Reply
Anyway, using the template would be the right solution. –LPfi (talk) 14:21, 24 September 2024 (UTC)Reply
@LPfi: That does seem to be the case, yes! If you have a look at #GeoJSON in the source editor, the mapframe element is started, raw GeoJSON data is inserted, and the mapframe is closed again. Using <mapframe/> as in the sandbox above, opens and closes the element without giving it opportunity to look for GeoJSON data to display. From what I can tell, the element also cannot work without being properly closed, and cannot look beyond its own extent for usable GeoJSON data (i.e., all markers have to be embedded within the mapframe element).
In summary: <mapframe/> shouldn't be used in articles, as {{Mapframe}} contains essential parts for gathering map markers that the element itself does not have.
Wauteurz (talk) 21:44, 25 September 2024 (UTC)Reply
Wauteurz, if you use Insert > Map in the visual editor, then it inserts the <mapframe> element directly, rather than the template. WhatamIdoing (talk) 20:01, 25 September 2024 (UTC)Reply
Interesting. I tried both inserting a map and inserting a template through the Visual Editor. When I moved that edit into the source editor, that would convert to {{Mapframe}} in both cases. I didn't publish any edits for my testing though, so that might be a possible lead as to what's going wrong?
Regardless, this bug requires fixing. Having both the element and template used alongside each other in articles will likely just pose problems further down the road, even if it were to work correctly now. I'm not sure where bugs for the Visual Editor should be reported though? Wauteurz (talk) 21:23, 25 September 2024 (UTC)Reply
This would be a feature request, which you can file in phab: Add "VisualEditor" as a tag. WhatamIdoing (talk) 16:35, 26 September 2024 (UTC)Reply
Wouldn't the fix be as simple as having VE insert the template, and not the element? Hanyangprofessor2 (talk) 06:35, 30 September 2024 (UTC)Reply
I think you'd actually have VE make it locally configurable, so that local admins could tell it whether to prefer a template and which template to prefer. But even simple feature requests are still feature requests. WhatamIdoing (talk) 16:36, 30 September 2024 (UTC)Reply

About districts (and students)

[edit]
User:Hanyangprofessor2, I'm sorry I don't know the answer to this question, but while we're waiting for a more technically savvy person to come along and address it, could you please ask your students not to create new district articles for city districts without starting a discussion on the relevant talk (discussion) page and gaining a consensus that they are needed, not to edit pages like Wikivoyage:Small city article template and Template:Smallcity skeleton, and also explain that we don't give articles or redirects titles that are in non-Roman scripts? We all know there's a learning curve and appreciate your students' efforts, but knowing these things will help them avoid hassles. Thanks a lot!
Best,
Ikan Kekek (talk) 08:28, 23 September 2024 (UTC)Reply
@Ikan Kekek Thanks, I will be revising the assignment now to include this. That said, I think we are way too strict on districts. I mean, I live next to Seoul, most of its districts are larger than your average town or city. A lot of my students are puzzled why we don't have articles on them and I can't really explain it to them. Ex. Hyehwa. Not that I am opposed to redirecting and merger, if there is little content. Oh, and as for foreign language redirects, I don't see why we don't like them, but they are just unavoidable accidents - a lot of students use automated translation in their browsers (at least one published article today in Chinese...). I am afraid there is not much I can do except moving the articles to correct names when such an error happens (it should not be too often). Btw, Jinshazhou (K) error was probably due to "Fat finger" and mobile interface (I do require students to bring a laptop, but some still bring tablets, sigh). Piotrus (talk) 08:47, 23 September 2024 (UTC)Reply
Seoul has 11 district articles. If that were to be changed, someone would have to change the map, create new maps for new and changed districts, and a whole lot of listings would need to be moved by someone who knows which of the current and new districts they are in. If we were to allow people to unilaterally change the district structure of articles, it would create a huge mess. Ikan Kekek (talk) 09:37, 23 September 2024 (UTC)Reply
I am not happy with what I think is semi-arbitrary grouping of some districts, but for now I think we can just work on expanding the existing articles and see if and when they get too big and need more splits. Piotrus (talk) 04:11, 24 September 2024 (UTC)Reply
Do feel free to propose a specific new district structure for Seoul in Talk:Seoul. That's how these kinds of things get started in the first place and changed later. Ikan Kekek (talk) 04:16, 24 September 2024 (UTC)Reply
For China in particular, districts are problematic. Chinese users often add articles for the official administrative districts, which in general do not work well as WV districts; see Talk:Fuzhou#Districts? for an example. Also, there's often an ambiguity between city & prefecture; do we need one article, one plus a redirect, or two? I'd say usually just one for the city, but some cases are more complicated; see Talk:Dengfeng for example. Pashley (talk) 12:45, 23 September 2024 (UTC)Reply
@Pashley Yeah, it's confusing for me, I have students write about city, then add listings for some stuff that seems pretty far away. I guess they are confused about city & prefecture issue too, and I am not sure what to do here. Piotrus (talk) 04:12, 24 September 2024 (UTC)Reply
I don't know how to explain it to students, but normally you could check the region article for what articles there are, and check whether the city described in yours or one in an already existing other article would be a more convenient base for visiting an attraction. If some such city is a realistic base, then we include the sight there, regardless of whether it is "in" the city (whatever that's taken to mean).
Of course, sometimes you want to create new articles to accommodate your points of interest, and then the question arises, whether a place is worth an article and what area the new article should cover. That's often tricky if the official boundaries don't make sense for Wikivoyage.
LPfi (talk) 14:33, 24 September 2024 (UTC)Reply

Duplicate IDs

[edit]

Special:LintErrors/duplicate-ids shows many pages on enwikivoyage with duplicate `id` attributes. I think I've tracked this down to Template:Listing, which contains both an explicit invocation of {{anchor|{{{wikidata}}}}} but also includes Template:Marker, which has its own invocation of {{anchor|{{{wikidata}}}}}. I think one of those anchors should be removed, and/or Template:Marker should take a "noanchor" option to have it skip the redundant anchor. I don't have edit rights to those templates, though. Could an admin take a look at fixing those templates? CAnanian (WMF) (talk) 19:27, 25 September 2024 (UTC)Reply

As {{marker}} is also used by itself, I suppose the id code cannot be removed from there without significant breakage. Thus it seems that just removing it from {{listing}} would be the cleanest solution (leave an HTML comment, in case things are changed at some point).
What about the "alt" parameter? I think it used to work as (create an) anchor, but that seems to have been broken at some point. As name and alt often are reversed (typically the native name moved to alt) or name changed (when a different translation is taken into use), having both as anchor is quite important.
LPfi (talk) 07:26, 26 September 2024 (UTC)Reply

FYI: One of the site's co-founders has a new venture

[edit]

User:Evan co-founded Wikitravel and launched the Social Web Foundation yesterday. —Justin (koavf)TCM 22:36, 25 September 2024 (UTC)Reply

He has also written a book on the open social networking software w:ActivityPub. Pashley (talk) 14:07, 10 November 2024 (UTC)Reply
Which (for those of you who aren't going to follow thru the link) is the foundation of the Fediverse (e.g.) Mastodon (social network), etc.). Real Internet Hall of Fame stuff. —Justin (koavf)TCM 14:21, 10 November 2024 (UTC)Reply

FYI: Why Some People Are Paying to Be Left on a Desert Island—Alone

[edit]

https://www.afar.com/magazine/docastaway-sends-travelers-to-deserted-islands-on-purpose

This one is pretty neat and shockingly affordable, all things considered. —Justin (koavf)TCM 06:53, 26 September 2024 (UTC)Reply

The size of the images with thumb and no px is wrong

[edit]

I noticed that the images in an article generated with [[file:filename.jpg|thumb|caption]] (no px value) results in a much bigger result than my 120px preference. However, when I'm viewing the result (Using the "Show preview" button) while editing, the size is correct. FredTC (talk) 07:24, 27 September 2024 (UTC)Reply

I have no experience with Phabricator, so I don't recognize what is done to the problem now. Could someone explain? --FredTC (talk) 01:45, 14 November 2024 (UTC)Reply
Well, on the 3rd of October someone put the ticket in the "Phase 5: Later" category. You can look at the current Parsoid workboard and see what tasks Phases 0-5 contain, and how many of them are resolved... Let's hope they are not working on them in strict phase order. Daggerstab (talk) 07:03, 14 November 2024 (UTC)Reply
@FredTC, in Special:Preferences#mw-prefsection-rendering, what's your skin setting in the first section? And you have 120px set in Special:Preferences#mw-prefsection-rendering-files? Do you have anything set in Special:GlobalPreferences#mw-prefsection-rendering-files ? WhatamIdoing (talk) 19:43, 27 September 2024 (UTC)Reply
@WhatamIdoing, My skin is "Vector legacy (2010)", but for this problem I also tried it with "Vector (2022)". The problem occurred with both skins. I have 120px at "Thumbnail size". The problem also occurred at nl:Wikivoyage, but not at Wikipedia. I have nothing set at "Global preferences". FredTC (talk) 06:56, 28 September 2024 (UTC)Reply
What's the "correct" size? I think it is better that when editing, you see images at the size people with default settings will see. Your personal preferences should not affect what image size you choose when editing. –LPfi (talk) 09:28, 28 September 2024 (UTC)Reply
@LPfi: I think the idea of having image sizes as for users with default settings and not logged-in users (when editing), would be a good idea. So, that is exactly the opposite of the situation now. --FredTC (talk) 04:02, 30 October 2024 (UTC)Reply
When I have this [[file:filename.jpg|thumb|caption]] image, it displays incorrect like a [[file:filename.jpg|thumb|220px|caption]] when I read pages, having "Thumbnail size" set at 120px. When I edit such a page and use the "Show preview" button, [[file:filename.jpg|thumb|caption]], displays correct like a [[file:filename.jpg|thumb|120px|caption]]. Correct displaying also happens when I compare versions using "View history". I think 220px is the size that is used for not logged-in users. The problem started happening just 1 or 2 days ago. --FredTC (talk) 10:12, 28 September 2024 (UTC)Reply
It was probably Wednesday's update. Ladsgroup, do you know what team this would be? (Your work account hasn't been here, so I'm pinging your volunteer one.) WhatamIdoing (talk) 19:39, 28 September 2024 (UTC)Reply
That Wednesday is now 3 weeks ago. It is still not working correct. Using the "Switch to legacy parser" link makes it OK. So, the new Parsoid parser must be the problem. FredTC (talk) 12:03, 16 October 2024 (UTC)Reply
And another 2 weeks later, nothing happened. This cannot be such a great problem that it takes so much time!? FredTC (talk) 01:31, 30 October 2024 (UTC)Reply
@WhatamIdoing and @LPfi This is very very likely because of Parsoid for read project. I'd say create a ticket and tag "content transformers" team and Parsoid. Ladsgroup (talk) 11:28, 29 September 2024 (UTC)Reply
Yes Done Thanks for the advice. WhatamIdoing (talk) 18:25, 29 September 2024 (UTC)Reply
Recall that we agreed to change the default to 300px. This Phabricator request T357943 has stalled. Grahamsands (talk) 20:42, 29 September 2024 (UTC)Reply
Linking phab:T357943 for recordkeeping. --SHB2000 (t | c | m) 22:36, 29 September 2024 (UTC)Reply
[edit]
Apologies for cross-posting in English. Please consider translating this message.

Hello everyone, a small change will soon be coming to the user-interface of your Wikimedia project. The Wikidata item sitelink currently found under the General section of the Tools sidebar menu will move into the In Other Projects section.

We would like the Wiki communities feedback so please let us know or ask questions on the Discussion page before we enable the change which can take place October 4 2024, circa 15:00 UTC+2. More information can be found on the project page.

We welcome your feedback and questions.
MediaWiki message delivery (talk) 18:57, 27 September 2024 (UTC)Reply

Danny Benjafield (WMDE), thanks for this note. This site still uses the old Vector skin. There are currently two links in the sidebar:
  1. "Tools": Wikidata item to d:Special:EntityPage/Q16503
  2. "In other projects": Wikidata to d:Wikidata:Project chat
Will both of those links now be in the same section, or is the plan to remove one of those links? WhatamIdoing (talk) 19:49, 27 September 2024 (UTC)Reply
There hasn't been any link to the wikidata item in "in other projects" on most pages. Project pages are special in that there may be an equivalent on Wikidata, in addition to the item page.
I think "in other projects" for this page should link to the Wikidata project chat, but according to Wikidata policies (cf Commons categories), I assume it will link to the item, unless we get two Wikidata entries in that section.
LPfi (talk) 09:40, 28 September 2024 (UTC)Reply
I think there should be two links on nearly all pages in the mainspace, as well as many templates and help pages. WhatamIdoing (talk) 19:40, 28 September 2024 (UTC)Reply
Hello @WhatamIdoing, both of those links will move into the new section (In Other Projects). A ticket on this topic can be found on our workboard (Phabricator: T372566) and we will be investigating if any further work to differentiate those 2 links is required. -Danny Benjafield (WMDE) (talk) 12:46, 30 September 2024 (UTC)Reply
That sounds okay to me. As long as we've got both links available, I think we'll learn which one does the thing we need. WhatamIdoing (talk) 16:35, 30 September 2024 (UTC)Reply

Redirects

[edit]

What redirects do we want? There is a user (or several, but I think it is the same person) who creates redirects to neighbourhoods, landmarks and POIs in Finland. I cannot find any policy page on the matter and Wikivoyage:How to redirect a page gives little guidance.

Helsinki Central Station and Asematunneli are not in line with what we normally use redirects for, and a high-volume contributor who doesn't discuss such counter-practice actions makes me feel uncomfortable. (Asematunneli doesn't even seem to be mentioned on the target page, only in Helsinki#Buy).

The neighbourhood redirects (Sörnäinen, Vuosaari) are probably useful (although a search for the name should turn up the relevant article), arguable in line with practice, and they cause little harm as long as they are unique. However, if they set a precedent and we get redirects for ambiguous names, possibly to an obscure place instead of the well-known one, we might have a problem.

I think I have seen redirects also to individual attractions (well-known domestically, but not internationally), but I cannot find any such for Finland now.

LPfi (talk) 11:34, 28 September 2024 (UTC)Reply

The Helsinki ones have been added by an anonymous user using different IPs. I left a notice on their talk page a few hours ago, and vaguely remember that someone - possibly you - did the same some time ago.
Redirects can be used for individual sights that are really famous such as the Eiffel Tower, but not for stuff like Helsinki railway station let alone the underground shopping and restaurant area Asematunneli connecting the station to nearby retail buildings. --Ypsilon (talk) 14:01, 28 September 2024 (UTC)Reply
There is some guidance at two places in Wikivoyage:What_is_an_article?:
If an attraction or an event is really famous, and travellers may not know the city or region it is in, then create an article with the attraction name as title, but make it a redirect to the appropriate destination article, and put the actual description of the attraction in the destination article. For example, Taj Mahal redirects to Agra and Burning Man redirects to Black Rock City.
Redirects are also used for extremely well-known attractions; for example The Alhambra redirects to Granada#The Alhambra.
It does not sound to me like the attractions mentioned here merit this sort of redirect. Pashley (talk) 14:46, 28 September 2024 (UTC)Reply
If a redirect might help someone find the relevant article, especially if it points to the correct part of an article (that train station, for example, points to Helsinki/Central#Get in), then I'd be inclined to keep it, and maybe even to encourage their creation. WhatamIdoing (talk) 20:03, 28 September 2024 (UTC)Reply
I'm with WhatamIdoing on this, also per WP:CHEAP. It can't exactly hurt to have redirects for railway stations and major landmarks if it helps travellers. --SHB2000 (t | c | m) 21:35, 28 September 2024 (UTC)Reply
I am hesitant to change long-standing practice without some serious consideration of the effects. Redirects are cheap, but their names might not be – cheap redirects can pollute the namespace. Should Waterloo railway station point to Waterloo#By train or London/South Bank#By rail, or, God forbid, Austin#By train (Austin used to be called Waterloo) or Kitchener#Kitchener Railway Station (close to Waterloo, Ontario). The editor who creates a redirect might not come to think of the more well-known places of the same name. Such a redirect is cheap resource-wise, but may cause harm by leading readers astray. A search on the phrase turns up the four mentioned articles within the first half-dozen results, giving some context for the reader to choose the relevant one.
A search on "Helsinki railway station" or "Asematunneli" gives Helsinki as one of the first three results, and a click on By train or a search for Asematunneli gets you to the right place in that article. Pointing to the right district (Helsinki/Central, not a far-fetched guess) from where the place is mentioned wouldn't be harder than creating the redirect, and would help also those readers who try to navigate via the city article.
LPfi (talk) 14:36, 29 September 2024 (UTC)Reply
When there's genuine opportunity for confusion (e.g., rail stations with identical names), then those should be disambiguation pages, no? WhatamIdoing (talk) 18:18, 29 September 2024 (UTC)Reply
Yes, they should. The problem is that it may take a long time until some established user notices the problem. How often does one of us type "Waterloo" in the search box to find any of those stations? –LPfi (talk) 19:58, 29 September 2024 (UTC)Reply

(indent) No, we should not create disambiguation pages for train stations nor should we be creating redirects for train stations. That's not something that has ever been encouraged. If redirects are "cheap", not creating them at all is even cheaper. The search engine is a feature not a bug, and the search engine proved to work for searching this station. We should not be creating redirects for every station, attraction, restaurant, etc. in every city. That's a lot of time wasted to solve a non-existent problem. In my experience, our redirects are more burdensome than useful and should be used sparingly. Stations, attractions, restaurants, etc searches should be left to the search engine. ChubbyWimbus (talk) 11:00, 30 September 2024 (UTC)Reply

I find the arguments made by LPfi, Pashley and ChubbyWimbus to be the most convincing. Let's not use redirects where the search engine is doing its job. A redirect takes the reader to one article, which may not be the right one; a search gives the reader a list of choices so they can choose the article they are looking for. Ground Zero (talk) 11:51, 30 September 2024 (UTC)Reply
Readers are unlikely to be looking for a train station without having some idea of where it is. Who says "I want to go to Waterloo Station in England" without knowing that it is in London? On the other hand "I want to go to the Taj Mahal in India" is much more likely. So train station redirects are generally not of much use. AlasdairW (talk) 21:57, 30 September 2024 (UTC)Reply
What is important, but often neglected, is to provide links to the appropriate districts (ideally to the listings) in "huge city" articles, for important POIs, such as stations mentioned in Get in and famous sights. Similarly, the appropriate articles should be pointed to where individual attractions are mentioned in region and country articles. Sometimes a search works, but not for "Grand Hotel" or "Notre Dame" (a possible more specific name may not be known by the reader, or not mentioned in the article). –LPfi (talk) 09:41, 1 October 2024 (UTC)Reply
Alasdair, I agree that people will mostly know that Waterloo Station is in London, but:
  • They might want to type "Waterloo Station" in the search bar, and automatically end up in the right place (or on a short dab page instead of a list of 260 search results).
  • They probably won't know that "Waterloo Station in London" means going to London/South Bank#Q795691, which is why we've had a redirect from London Waterloo since 2017.
WhatamIdoing (talk) 18:15, 1 October 2024 (UTC)Reply
If you type "Waterloo Station London", the first result is the district. Users should not expect to "automatically end up in the right place" by searching for random listings. We don't do that for listings. This goes back to the search being a FEATURE and not a bug. The first search result showing the correct article should not be viewed as a "problem". It's the optimal result. ChubbyWimbus (talk) 12:54, 3 October 2024 (UTC)Reply

Invitation to Participate in Wiki Loves Ramadan Community Engagement Survey

[edit]

Dear all,


We are excited to announce the upcoming Wiki Loves Ramadan event, a global initiative aimed at celebrating Ramadan by enriching Wikipedia and its sister projects with content related to this significant time of year. As we plan to organize this event globally, your insights and experiences are crucial in shaping the best possible participation experience for the community.

To ensure that Wiki Loves Ramadan is engaging, inclusive, and impactful, we kindly invite you to participate in our community engagement survey. Your feedback will help us understand the needs of the community, set the event's focus, and guide our strategies for organizing this global event.

Survey link: https://forms.gle/f66MuzjcPpwzVymu5

Please take a few minutes to share your thoughts. Your input will make a difference!

Thank you for being a part of our journey to make Wiki Loves Ramadan a success.


Warm regards,

User:ZI Jony 03:19, 6 October 2024 (UTC)

Wiki Loves Ramadan Organizing Team

Topics chosen and being edited by my students

[edit]

The list should be mostly complete (not all students have chosen the topic, despite the deadline for the choice having passed over a week ago...). Feel free to watchlist those (as they will likely see some newbie mistakes). If you make changes/fixes, it is good to explain them in an edit summary so that the student can learn (I encourage my students to review the history of those pages and read edit summaries).

Hanyangprofessor2 (talk) 07:48, 6 October 2024 (UTC)Reply

謝謝 for the heads up. For those who don't know, you can temporarily add pages to your watchlist, so the watching expires after x days. —Justin (koavf)TCM 11:21, 6 October 2024 (UTC)Reply
@Piotrus: If only we could have timed your students' writing to coincide with the Wikipedia Asian Month - Wikivoyage Special Edition! OhanaUnitedTalk page 02:54, 25 October 2024 (UTC)Reply

@Hanyangprofessor2: I am getting really fed up with your students making the same mistakes over and over again. I am doing my best to coach them on their talk pages, but many of them just ignore what I write. I support using Wikivoyage as a learning tool, but your students must respect other members if the community. It is time for you to have a talk with them, or start paying us to be your teaching assistants. Ground Zero (talk) 03:17, 12 November 2024 (UTC)Reply

Chongqing districting

[edit]

Hi, everyone! I'm not up to pinging a bunch of people right now, so I'm just posting here: we need to discuss districting for that city, and we will need a map that shows the agreed-upon districts. So far, a new user has unilaterally created two more district articles for the city, and that kind of piecemeal districting is not the way this site is supposed to work. There is also ongoing discussion about the best way to district Chengdu. I think it's reasonable to have discussions about any very big Chinese city with lots of things to list and coherent sections, as long as there are knowledgeable people and volunteers who are happy to add useful content. I've been to China twice but not too recently and only to several cities. Ikan Kekek (talk) 06:07, 9 October 2024 (UTC)Reply

I haven't been to China to know how Chongqing should be districted, but if these were unilaterally created, shouldn't we speedy merge them for the time being? --SHB2000 (t | c | m) 06:42, 9 October 2024 (UTC)Reply
Go ahead, if you like. Dazu and Yuzhong, both started by new user User:Wuwenhao19960507. But I would suggest only hiding and not overwriting (=deleting) the content if you do redirects. Ikan Kekek (talk) 06:47, 9 October 2024 (UTC)Reply
If you really want to take this policy to its logical end, though, unilaterally created district articles for Chengdu will also have to be redirected. Ikan Kekek (talk) 06:48, 9 October 2024 (UTC)Reply
Dazu is not a new article. It has existed on this site for almost two decades. Wuwenhao19960507 did not create it. Moreover, it's outside the main urban. area, which is why it is listed on the Chongqing (municipality) page. I oppose merging Dazu but support merging Yuzhong (though I believe central Chongqing should be districtified eventually). STW932 (talk) 07:38, 9 October 2024 (UTC)Reply
You're right. Sorry, I didn't realize I was looking at only the latest page of the history. Dazu shouldn't be merged. Only Yuzhong is new. Ikan Kekek (talk) 08:46, 9 October 2024 (UTC)Reply
I don't know enough about Chongqing to do any of the merges, to be fair. I'd rather abstain. SHB2000 (t | c | m) 09:20, 9 October 2024 (UTC)Reply
Me, too. Besides, this isn't an emergency. If it takes a day (or a week) to figure it out, then that's okay. WhatamIdoing (talk) 16:41, 9 October 2024 (UTC)Reply
It's not an emergency; it just needs discussion and agreement. Ikan Kekek (talk) 17:16, 9 October 2024 (UTC)Reply
I'd say places in the municipality but outside the central urban area -- Qijiang, Qianjiang, Dazu & maybe others later -- are fine as separate articles. We should keep Chongqing (municipality) or (I think better) move it to Chongqing Municipality.
The Chongqing article is a good candidate for districting & Yuzhong looks to me like a good candidate for one of the districts. Pashley (talk) 17:59, 9 October 2024 (UTC)Reply
Please share your thoughts on Talk:Chongqing. Ikan Kekek (talk) 18:35, 9 October 2024 (UTC)Reply
Hello everyone, I was born in Yuzhong District, Chongqing. Initially, I wanted to edit the page about my hometown, Yuzhong District, but I couldn't find it in the administrative divisions. As this is my first time editing on Wikipedia, I thought creating a new page for an area would be simple. However, I quickly realized it was more complex than I expected. So, instead, I decided to edit the existing travel guide for Dazu District.
I would like to share that Chongqing currently has 26 districts, 8 counties, and 4 autonomous counties. Editing every administrative region would involve handling a massive amount of data. While I would love to do that, time and personal capacity limit me. Therefore, I've chosen to focus on Dazu District, particularly highlighting it as a World Heritage site and offering detailed information for visitors from all over the world.
I removed some outdated information about Dazu because it has been six years since the last update, and much of the content was no longer accurate. For example, ticket prices have changed, and transportation methods have evolved with the addition of new stations. Over the next two months, I will devote my efforts to thoroughly editing the page on Dazu. First, I’ve visited this place many times, and second, it truly deserves to be explored by people from every country. Wuwenhao19960507 (talk) 00:37, 16 October 2024 (UTC)Reply
Thank you for work on Dazu. I visited Dazu in October last year and I hope to do some editing on that page myself when I have time. STW932 (talk) 05:44, 16 October 2024 (UTC)Reply
Thank you, Wuwenhao19960507, for your work to update that page. WhatamIdoing (talk) 16:34, 16 October 2024 (UTC)Reply

Yet another merge/redirect needed

[edit]

This one is straightforward, but I really can't handle all this work by myself: Gonjiam is part of Gwangju (Gyeonggi) city and needs to be moved and redirected there. I just merged and redirected Munseom to Seogwipo. A stub about an island that may be misnamed might need deletion, rather than anything else. See User talk:Xisuux#Moon Island for that one. Ikan Kekek (talk) 07:10, 10 October 2024 (UTC)Reply

Looking at Special:LonelyPages, which lists pages with no links from other articles, I find several more that likely need merging & redirecting. Pashley (talk) 21:21, 10 October 2024 (UTC)Reply
Worth looking at. In the meantime, I started Wikivoyage:Votes for deletion#Moon Island. Ikan Kekek (talk) 05:16, 11 October 2024 (UTC)Reply
Meanwhile, I did make the merge from Gonjiam to Gwangju (Gyeonggi). Ikan Kekek (talk) 05:39, 11 October 2024 (UTC)Reply

Durga Puja

[edit]

Although we have mentioned the Durga Puja festival at Hinduism, India, Kolkata#Do, I think it is not enough, as Durga Puja is a large event in Kolkata, and an ICH since 2022. While WV:EA restricts creating event articles that are not international, it gives some exceptions in case-by-case basis, like Vivid Sydney. Even if Durga Puja does not qualify as a separate event article, maybe its notable venues can be listed in individual districts. --Sbb1413 (he) (talkcontribs) 11:16, 13 October 2024 (UTC)Reply

It looks like WV:EA is applicable for events in a given year only, not for event topics. We have Olympic Games and FIFA World Cup articles as travel topics. So we can have Durga Puja as a separate travel topic, especially as it is not limited to one city, although the Kolkata one is the most famous. --Sbb1413 (he) (talkcontribs) 11:28, 13 October 2024 (UTC)Reply
[edit conflict] A UNESCO Intangible Cultural Heritage (I had to look the initialism up). According to the linked Wikivoyage:Event articles, the main criterium is about whether it would overwhelm the city article. I assume this festival could. I also assume that those who want to experience it are better served by an article than having the event split over many district articles. I suppose many of the venues are worth individual listings (read: interesting also at other times), while some aren't. Hoe to handle that without duplicating information or making less important venues stand out in the event article, I don't know. LPfi (talk) 11:29, 13 October 2024 (UTC)Reply
I think WV:EA is applicable for events in a given year only, like Paris 2024 and Los Angeles 2028 (both Olympics), and not for articles like Olympic Games and FIFA World Cup. My proposed article would be similar to the latter, with listings to individual venues in Kolkata, as well as listings to other cities where the festival is notable. Sbb1413 (he) (talkcontribs) 11:34, 13 October 2024 (UTC)Reply
There should also be advice to eat, drink, sleep, stay safe, stay healthy, etc. as the streets to the venues are narrow and can be heavily crowded, especially at night. There are also issues with women's clothing, where you have to avoid revealing dresses while visiting the venues. This can be covered under the Respect section. Sbb1413 (he) (talkcontribs) 11:47, 13 October 2024 (UTC)Reply
I think there is room for more than one travel topic on huge Hindu festivals and pilgrimages. Please go ahead and start the article. Ikan Kekek (talk) 14:10, 13 October 2024 (UTC)Reply
I agree. This would be an excellent travel topic article. I look forward to reading it. Ground Zero (talk) 16:36, 13 October 2024 (UTC)Reply
Thanks a lot. I'll start the article tomorrow, according to my local time. Sbb1413 (he) (talkcontribs) 16:53, 13 October 2024 (UTC)Reply
@LPfi, Ikan Kekek, Ground Zero: I have started Durga Puja for some days, with my experience and the help of Wikipedia articles. Feel free to expand it if you know more about the festival. Sbb1413 (he) (talkcontribs) 15:35, 15 October 2024 (UTC)Reply
Super! I really don't know much about the holiday, myself. Ikan Kekek (talk) 02:03, 16 October 2024 (UTC)Reply

Preliminary results of the 2024 Wikimedia Foundation Board of Trustees elections

[edit]

Hello all,

Thank you to everyone who participated in the 2024 Wikimedia Foundation Board of Trustees election. Close to 6000 community members from more than 180 wiki projects have voted.

The following four candidates were the most voted:

  1. Christel Steigenberger
  2. Maciej Artur Nadzikiewicz
  3. Victoria Doronina
  4. Lorenzo Losa

While these candidates have been ranked through the vote, they still need to be appointed to the Board of Trustees. They need to pass a successful background check and meet the qualifications outlined in the Bylaws. New trustees will be appointed at the next Board meeting in December 2024.

Learn more about the results on Meta-Wiki.

Best regards,

The Elections Committee and Board Selection Working Group

MPossoupe_(WMF) 08:26, 14 October 2024 (UTC)Reply

Seeking volunteers to join several of the movement’s committees

[edit]

Each year, typically from October through December, several of the movement’s committees seek new volunteers.

Read more about the committees on their Meta-wiki pages:

Applications for the committees open on 16 October 2024. Applications for the Affiliations Committee close on 18 November 2024, and applications for the Ombuds commission and the Case Review Committee close on 2 December 2024. Learn how to apply by visiting the appointment page on Meta-wiki. Post to the talk page or email cst@wikimedia.org with any questions you may have.

For the Committee Support team,

-- Keegan (WMF) (talk) 23:08, 16 October 2024 (UTC)Reply

Click for a full screen dynamic map... with the Parsoid parser

[edit]

Clicking the pictogram at the upper right corner of the article, displays a map wit lat=0 and long=0. When switching to the legacy parser, the correct map is shown. FredTC (talk) 10:24, 17 October 2024 (UTC)Reply

Pinging @CAnanian (WMF). WhatamIdoing (talk) 16:09, 17 October 2024 (UTC)Reply
I didn't see any actions taken by the pinged CAnanian (WMF), but maybe I didn't know well enough where to look. --FredTC (talk) 05:00, 27 October 2024 (UTC)Reply
The task is under investigation.--RolandUnger (talk) 10:06, 27 October 2024 (UTC)Reply
I think that the full-screen map is now working again. --RolandUnger (talk) 10:21, 27 October 2024 (UTC)Reply
Yes. It worked for me for pages I haven't visited recently. For those that I have visited [since the bug was discovered?], reloading or pruning doesn't help, editing seems to. –LPfi (talk) 12:06, 27 October 2024 (UTC)Reply
Maybe, the pages are stored in the browser cache. Emptying the cache or the one-time addition of ?action=purge at the url should help. --RolandUnger (talk) 17:54, 27 October 2024 (UTC)Reply
For me it is back to normal now. FredTC (talk) 01:39, 28 October 2024 (UTC)Reply
I tried those two, as I told; they didn't help [oops: I see I didn't write "purge" above, maybe I did the same error in the URL]. Both actions should refresh the browser cache, at least for the page itself (the former explicitly, the latter already by the URL being different). Editing the page helped. I don't know why the purging and editing have different effects on caching server-side – purging doesn't always help. –LPfi (talk) 07:25, 28 October 2024 (UTC)Reply
Anyway: reloading the page does seem to be enough now. –LPfi (talk) 07:27, 28 October 2024 (UTC)Reply
Back as normal for me as well. --SHB2000 (t | c | m) 01:41, 28 October 2024 (UTC)Reply

Destinations not updating

[edit]

I posted a question couple days ago but not hearing anything because presumably it's a low-traffic page. I have created new city/town pages since December 2023 but none of them appears in the dynamic map of the Destinations page. How often does the Destinations dynamic map get updated? And does it require manual update? OhanaUnitedTalk page 15:40, 17 October 2024 (UTC)Reply

It looks like any article since the end of 2021 or the start of 2022 isn't on that map, from what I gather. --SHB2000 (t | c | m) 00:38, 18 October 2024 (UTC)Reply
Pinging Atsirlin and Andyrom75 from the list of tool maintainers for that page. WhatamIdoing (talk) 18:11, 18 October 2024 (UTC)Reply
I think that poimap2 is deprecated and replaced by the Kartographer based maps. -- Alexander (talk) 19:51, 18 October 2024 (UTC)Reply
Last time I took a look at it, I've noticed that the script fail to elaborate the en:voy database, due to its size, while it keep on working on it:voy. Due to lack of time I'm not able to fix it, and also for Listing Editor fix, after it has been rewritten by @Jdlrobson, I rely on his spare time for the support. Andyrom75 (talk) 11:08, 19 October 2024 (UTC)Reply
The places shown on this map are taken from en-articles.js at toolforge.org. For the last time it was updated on 2022/3/1. I do not know if an update of this file would be possible in any future. It means that newer articles will never been shown on this map.
Of course, poimap2 should be replaced by Kartographer. But the feature of showing all places on a world map was removed last year. I think the main reason was to reduce the dependencies on third-party tools. This was the cause that this service is not provided at the German Wikivoyage any longer. --RolandUnger (talk) 06:47, 28 October 2024 (UTC)Reply

Wikivoyage 12 planning

[edit]

Hey everyone! Wikimedia Small Projects and the Wikipedia Asian Month User Group are teaming up again to throw a contest to celebrate Wikivoyage's 12th anniversary with the Wikimedia family. As part of Wikipedia Asian Month, we’re excited to kick off something special called Wikivoyage Asian Month from November 20 to January 20, where we’ll focus on improving or creating content about Asian destinations.

You can find all the contest details on this page. Just like with the Wikivoyage 10 contest, each community needs to have at least three judges and can decide if they want to stick to the global scoring criteria or come up with their own (just keep in mind that local criteria can’t be lower than the global ones). It’d be great to whip up a list of top places to create or enhance.

This year, we also want to include other communities, like frwikivoyage, itwikivoyage, ruwikivoyage, dewikivoyage, jawikivoyage, and zhwikivoyage. If anyone who speaks those languages could help promote this initiative, that would be awesome!

Feel free to hit me up with any questions you have about it. Let’s use this discussion space to figure out what method to go with (WAM usually uses Fontaine, so we might want to stick with that).

Best, Galahad (sasageyo!)(esvoy) 05:39, 18 October 2024 (UTC)Reply

I'll be available this summer (southern) and am more than happy to volunteer as a judge if it's needed. --SHB2000 (t | c | m) 05:40, 18 October 2024 (UTC)Reply
@Galahad, do you have someone lined up to create a CentralNotice banner? As I recall, that was the biggest hurdle last time.
Based on prior experience, especially the amount of time involved for judges, I think that we need to have very few categories, and only automated criteria (e.g., the tools automatically count up the number of edits, and judges manually subtract out any identified bad edits). WhatamIdoing (talk) 18:14, 18 October 2024 (UTC)Reply
Past experience suggests that purely automatic criteria is a bad idea. It is Ok to use automatic qualifying criteria, but prizes should only be given at the judges discretion. We have had contests in past where the same 1000 bytes (eg detailing the mobile phone operators) have been added to tens of articles. We don't want "1 point for each 2000 bytes added to an existing article" to result in loads of articles getting the same boilerplate text. AlasdairW (talk) 22:02, 18 October 2024 (UTC)Reply
I strongly agree with AlasdairW on this. Ikan Kekek (talk) 00:06, 19 October 2024 (UTC)Reply
+2 – most of our problem expeditions stem from a broad automatic criteria. --SHB2000 (t | c | m) 00:19, 19 October 2024 (UTC)Reply
I also don't want to see "1 point for each 2000 bytes added". I would like to see automatic (or nearly automatic) criteria like "Most number of unreverted edits" or "Most number of days edited" or "Most listings updated" (the latter being detectable through the "Updated listing for..." edit summary, though it'd be nice to have the Special:Tags system tag the use of the listing editor).
And I would like the list of criteria to be short, so the judges don't have to check 20 different things. WhatamIdoing (talk) 17:36, 19 October 2024 (UTC)Reply
Merely updating a listing is not necessarily good, if it's done in order to tout, involves adding default address info, makes it more encyclopedic, etc., etc. I oppose any automatic criteria. The judges need to take the time to personally review everything. Ikan Kekek (talk) 19:23, 19 October 2024 (UTC)Reply
I can assist with zhwikivoyage and judge. I think we can use the same criteria as the edit-a-thon in 2018. You can only get 1 point per article, not the "1 point per 2000 bytes added". And disqualify copying & pasting the same content across different pages. These rules should eliminate the boilerplate text problem. Recognizing that some of the contents can be out-of-date, removing inaccurate information should also count (but I am not sure if any tools can be used to count "subtraction" as improvement automatically). OhanaUnitedTalk page 22:15, 19 October 2024 (UTC)Reply
I like the rules for the edit-a-thon 2018. But if it is to be held globally, the byte count should be changed (or removed) for different languages because of both an issue of byte count per character (ex. each Japanese characters have three bytes) and an enrichment issue for existing articles.
Also, I think it would be difficult to count minor corrections and subtractions; it would be easier to judge to focus only on the addition and creation of articles.
BTW: I can help judge on jawikivoyage though it is a small community if the contest is held there as well. It would be exciting if we could attract users from jawiki, where many users participate... Tmv (talk) 13:01, 21 October 2024 (UTC)Reply
@WhatamIdoing: I can ping some admins to prioritize the banner request.
@OhanaUnited & @Tmv thanks! Please can you translate the message I posted and preferably ping me so I can provide assistance.
When it comes to global criteria, each community has the freedom to establish local criteria that suit their unique needs—this flexibility is what makes the contest so great! Ideally, we want to keep the criteria consistent, simply adjusting the requirements as necessary. It’s also crucial to leverage the content gap criterion to help prioritize our efforts; for instance, in eswikivoyage, we’re focusing on boosting our coverage of Japan destinations. Best, Galahad (sasageyo!)(esvoy) 01:00, 22 October 2024 (UTC)Reply
You need someone with translation rights to mark the page eligible for translation. Otherwise we can't translate the message on Meta. OhanaUnitedTalk page 02:06, 22 October 2024 (UTC)Reply
No harm in asking a TA to mark it for translation (even us ordinary Meta admins cannot do this). --SHB2000 (t | c | m) 02:19, 22 October 2024 (UTC)Reply
I think there isn't any major technical problem with the byte count for Japanese: Japanese characters use more bytes but also convey more meaning (Russian would have the problem). Anyway, isn't the competition language specific? The more severe problem of encouraging fluff remains. –LPfi (talk) 10:05, 22 October 2024 (UTC)Reply
Creation of stub articles has been a problem. If article creation is to be counted, then I think there should be a requirement of the article reaching usable status. Adding listings (appropriate ones with sufficient information) to articles seems to be among the most important tasks; although perhaps only those in bottom-level destination articles with a lack of them in the section concerned should be counted. –LPfi (talk) 10:12, 22 October 2024 (UTC)Reply
You're obliquely making an important point: templated listings in non-bottom-level articles are usually problematic and should not be rewarded. That said, I think that any useful listings put in the right place should be appreciated and credited, not only those on otherwise blank pages. Ikan Kekek (talk) 10:16, 22 October 2024 (UTC)Reply
Maybe I could suggest the removal of points for incorrectly formatted articles such as the example you brought up? (e.g., -5 points for each templated listing in a region article where it is not supposed to belong) It would have definitely helped for the Nigeria and Africa Expeditions were this a thing. --SHB2000 (t | c | m) 11:14, 22 October 2024 (UTC)Reply
I think there shouldn't be punishments for good-faith edits; not giving points for possibly problematic edits, good or not, instead directs participants toward those that are easy to judge. By counting only the first listings in a section, we'd avoid long lists in big cities.
If there already are 3, 5 or 9 eat listings, adding another grill kiosk helps little; better add the first or third listing to some badly underdeveloped city article. Whether that grill kiosk is worth listing is a matter of judgement, which takes judges' time and can create frustration for the participant who added it in good faith.
LPfi (talk) 11:51, 22 October 2024 (UTC)Reply
If you're suggesting a full hard-cap on points for listings (such as 9 for cities/parks in buy, eat, drink and sleep), I am all for that, as that avoids the listing copypasta we saw in the Africa Expedition. That said I don't think we should have one for see or do which I think is implied. SHB2000 (t | c | m) 11:54, 22 October 2024 (UTC)Reply
I did think about eat/drink/sleep, and you are right that there can be many more relevant see/do listings. There can still be a problem of long lists: adding all churches in Helsinki (taking info from the congregation pages, where it is readily available) shouldn't give more points than adding three listings to each of a dozen articles. There could be a cap at three similar listings or some such. –LPfi (talk) 15:31, 22 October 2024 (UTC)Reply
Yeah, true; I don't remember which expedition (or if it was with a specific editor), but there was one that added loads of boring municipal parks which would have the same intended consequence. Similarly, we also need to have provisions to ensure that listings such as WV:BORING (fast food joints) don't get additional points unless proven otherwise. --SHB2000 (t | c | m) 21:40, 22 October 2024 (UTC)Reply
I'm in favor of adding a municipal park to pretty much every article; a free place to get some sunshine and exercise is useful for anyone with jetlag, and a playground is good for anyone traveling with little kids. I have fond memories of stopping at little city parks during family road trips when I was a kid. However, I don't think we need "loads of" them in any article, and probably not even three, unless they're very different (e.g., municipal playground vs municipal swimming pool vs municipal bike path). WhatamIdoing (talk) 16:44, 23 October 2024 (UTC)Reply
Sure, and more than one if they're particularly nice. -- Ikan Kekek (talk) 20:57, 23 October 2024 (UTC)Reply
I am too – they're a great place to unwind at the end of a day; I only have an issue with excessive municipal parks. SHB2000 (t | c | m) 02:31, 24 October 2024 (UTC)Reply
Is this possible to be held at Wikimedia Incubator? Veracious (talk) 09:26, 15 November 2024 (UTC)Reply

The global page is already set for translation. With just 25 days to go, it’d be great to get the local pages ready with the judges and local criteria (or decide if you wanna stick with the global criteria). Best, Galahad (sasageyo!)(esvoy) 00:15, 26 October 2024 (UTC)Reply

With just 15 days to go, do we need to set up a registration/sign-up page? OhanaUnitedTalk page 22:08, 4 November 2024 (UTC)Reply
Page on eswikivoyage created! Make a page like the one for every local edition of Wikipedia Asian Month (check out the ones on Wikivoyage 10 for both eswikivoyage and enwikivoyage, for example). Also, set up the boards in Fontaine after we figure out if we're going with the global or local criteria. Galahad (sasageyo!)(esvoy) 05:21, 6 November 2024 (UTC)Reply
enwikivoyage and zhwikivoyage pages are also ready (I relied on your Spanish page as source for translation, so please double check the English version for accuracy). OhanaUnitedTalk page 07:02, 10 November 2024 (UTC)Reply

Can we get someone to be enwikivoyage judge? OhanaUnitedTalk page 06:04, 13 November 2024 (UTC)Reply

@SHB2000 wanted to volunteer as a judge for this edition. Galahad (sasageyo!)(esvoy) 15:54, 13 November 2024 (UTC)Reply
Yep, can confirm. --SHB2000 (t | c | m) 20:36, 13 November 2024 (UTC)Reply

Graffiti wall on Wikivoyage?

[edit]

I know this may not be important, but when will the Graffiti wall page be reopened for experimenting? RockTransport (talk) 17:03, 19 October 2024 (UTC)Reply

Courtesy link: Wikivoyage:Graffiti wallJustin (koavf)TCM 17:14, 19 October 2024 (UTC)Reply
If I read this correctly, it would be in about 15 hours. --Ypsilon (talk) 18:14, 19 October 2024 (UTC)Reply
Thanks! RockTransport (talk) 18:55, 19 October 2024 (UTC)Reply
@RockTransport: You should now be able to edit the graffiti wall (I've given you confirmed perms for a week). --SHB2000 (t | c | m) 21:20, 19 October 2024 (UTC)Reply
Why is the graffiti wall semi-protected? Of all the pages on Wikivoyage, that's probably the one where vandalism matters the least. It's also important for it to be open to edits from new editors, who may want to use it as they're getting the hang of how to edit. —Granger (talk · contribs) 00:39, 20 October 2024 (UTC)Reply
Spam ≠ vandalism. --SHB2000 (t | c | m) 01:06, 20 October 2024 (UTC)Reply
What I can see, there has come spam only from two IP addresses in the last month, and vandalism from a couple more. We should be able to handle that by revert+block. Although the policy doesn't seem to explicitly allow blocking in these cases – I see no evidence that the edits were from bots, and ordinary touts should be handled with {{tout}}, not by blocking – but I think it is consistent with our practice. –LPfi (talk) 06:12, 20 October 2024 (UTC)Reply
I really did not think we needed to be having this discussion, but here we go:
  • Mx Granger claimed that it was semi-protected because of vandalism – yes, vandalism. Most types of vandalism have no issue, but this was an IP user trying very hard to spam their link into their graffiti wall.
  • You claim this could be handled by blocks, but blocking does nothing since they used three (not two as you claimed) IP addresses within a 32-hour period meaning the blocks are useless. The IP then continues under a different address.
And all of this, mind you, was handled by me manually confirming RockTransport for a week meaning they can edit the page while it is still protected. Was this...not an option that came to mind? (even though I brought it up at #c-SHB2000-20241019212000-RockTransport-20241019185500)
I don't think it's worth my time arguing when the two of you bring up deliberately incorrect information because you have an issue with the protections. This seems like you both are looking for a problem in search of a resolved issue. --SHB2000 (t | c | m) 06:49, 20 October 2024 (UTC)Reply
I followed these incidents, rolled back one of the spam edits, I do believe, and fully vouch for SHB2000's account. Out-of-control spam is a good reason to at least temporarily restrict use of the graffiti wall. Ikan Kekek (talk) 08:47, 20 October 2024 (UTC)Reply
[edit conflict] Please! I didn't deliberately bring up false information. I'm sorry if I wasn't careful enough in analysing the history, but I really tried to search for the massive spamming (ah! there were two different .61s!). Still, two or three in 32 hours isn't that big a difference. –LPfi (talk) 08:54, 20 October 2024 (UTC)Reply
If you think this spamming was too intense to be handled by revert-and-block, then I'd expect a discussion on that. Thanks IK for your post. I just have to trust your assessment, it seems. Still, the issue doesn't go away by giving one user the needed rights. Attempts to edit a locked page doesn't show up anywhere that I know, so other newcomers will still be hampered, if any happen to try the Graffiti wall during the locking. –LPfi (talk) 09:00, 20 October 2024 (UTC)Reply
Thanks for being honest and admitting, LPfi. I'll admit I was somewhat frustrated at the time, but glad we cleared things in the air. --SHB2000 (t | c | m) 09:07, 20 October 2024 (UTC)Reply
I don't think we need to permanently restrict edits on that page. Ikan Kekek (talk) 10:02, 20 October 2024 (UTC)Reply
The only reason to would be some unblockable spambot permanently targeting it for frequent edits that cannot be caught by a filter. I see that scenario as quite far-fetched. The question is about the threshold for semi-protecting pages, and whether half-an-hour protections would suffice. –LPfi (talk) 10:31, 20 October 2024 (UTC)Reply
For sure, which is why it's only protected until today. --SHB2000 (t | c | m) 10:46, 20 October 2024 (UTC)Reply

──────────────────────────────────────────────────────────────────────────────────────────────────── I did not "bring up deliberately incorrect information" and would appreciate not being accused of it. Thanks for the answer to my question, but I would prefer if we can keep Wikivoyage fun and tone down the hostility. —Granger (talk · contribs) 22:15, 20 October 2024 (UTC)Reply

It's your responsibility to check what you add is in fact correct in discussion (spam and vandalism are handled very differently); if you can't take responsibility for that, that's frankly your issue, not anyone else's. --SHB2000 (t | c | m) 02:45, 21 October 2024 (UTC)Reply
Curious (don't kill me) why we don't just have WP's per user sandbox? Brycehughes (talk) 03:21, 21 October 2024 (UTC)Reply
@Brycehughes: Do you mean something where a link to your personalised sandbox appears in the top right corner? That's not actually that bad of an idea for new users. --SHB2000 (t | c | m) 03:24, 21 October 2024 (UTC)Reply
Do we have a personalised sandbox to link to?? Brycehughes (talk) 03:29, 21 October 2024 (UTC)Reply
I mean the WP sandbox is just a link to Special:MyPage/sandbox. --SHB2000 (t | c | m) 03:32, 21 October 2024 (UTC)Reply
When I first joined this website years ago from en.wp I thought the weirdest thing was that they don't have a sandbox where I can practice my edits. Yeah I think it'd be really beneficial to have a link to the "sandbox" for new users. I think there is some verbage somewhere however that says we don't have a sandbox – I remember that. Brycehughes (talk) 03:38, 21 October 2024 (UTC)Reply
For sure; for those who don't love a redlink in their header the option to just create it blank always exists. --SHB2000 (t | c | m) 03:58, 21 October 2024 (UTC)Reply
Adding the link might be beneficial, but is spam in userspace any less problematic than spam on the graffiti wall? Neither should turn up unexpectedly in search results – do they? Whether the link would be beneficial for other reasons should be a separate discussion (and no, personally I wouldn't like that bluelink either). –LPfi (talk) 14:29, 21 October 2024 (UTC)Reply
LPfi I'm reasonably sure non-article space on wikis is tagged with norobots (or whatever it is) or flagged as do not scan with the robots.txt (I can't recall the specific lingo but I'm sure you know what I'm talking about). I don't recall ever being able to search non-article space via Google, etc. Brycehughes (talk) 01:33, 10 November 2024 (UTC)Reply
I cannot find "User:" in robots.txt (however, the equivalent "Käyttäjä:", "Användare:" and "Bruker:" are disallowed). Many projects disallow VFD. I cannot find any Wikivoyage-specific entries in the file. I think external links are marked with "nofollow"/"noindex" in all namespaces, which advises search engines not to give any weight to such links (seemingly '<a rel="mw:ExtLink nofollow"…' in article space; I didn't investigate more than superficially). –LPfi (talk) 08:12, 14 November 2024 (UTC)Reply
[edit]

Hello everyone, I previously wrote on the 27th September to advise that the Wikidata item sitelink will change places in the sidebar menu, moving from the General section into the In Other Projects section. The scheduled rollout date of 04.10.2024 was delayed due to a necessary request for Mobile/MinervaNeue skin. I am happy to inform that the global rollout can now proceed and will occur later today, 22.10.2024 at 15:00 UTC-2. Please let us know if you notice any problems or bugs after this change. There should be no need for null-edits or purging cache for the changes to occur. Kind regards, -Danny Benjafield (WMDE) 11:29, 22 October 2024 (UTC)Reply

Kitikmeot Region navigation breadcrumbs

[edit]

I'm trying to get {{IsPartOf}} to work after updating Nunavut regions. The breadcrumbs work on Gjoa Haven, but not Cambridge Bay or Kugluktuk despite all using the same template. Can someone troubleshoot? OhanaUnitedTalk page 13:33, 23 October 2024 (UTC)Reply

Another strange thing is that the breadcrumbs show up correctly in the preview (when using source editing). It might be a parser issue. Anyway, I think I managed to force a workaround by using an underscore (_) instead of a space in the region name in the template. Please check if the issue is resolved for you too. Daggerstab (talk) 14:36, 23 October 2024 (UTC)Reply
Yes that fixes the issue. Very strange indeed. OhanaUnitedTalk page 15:38, 23 October 2024 (UTC)Reply

Wikivoyage at a competition

[edit]

Hello there. Me and my friends are taking part in a science (STEM) competition and we would like to set up a stand for Wikivoyage (and our other project) as part of our whole project during this event. I was thinking how you could help us (ideas etc.) in doing so. Many thanks. -- RockTransport (talk) 15:54, 23 October 2024 (UTC)Reply

Welcome, @RockTransport. I'm not sure what your idea means in practice. Is this an in-person event? WhatamIdoing (talk) 16:20, 23 October 2024 (UTC)Reply
Yes, it is an in-person event, and it is part of outreach, so we can get more contributors. There will be a multitude of well-known people attending this event. RockTransport (talk) 16:22, 23 October 2024 (UTC)Reply
It would be something like this: https://commons.wikimedia.org/wiki/Category:Wikimedia_stands. Additionally, there will also be another project as well that we are exhibiting. RockTransport (talk) 16:23, 23 October 2024 (UTC)Reply
We have had travel guides in the past for events like the Olympic Games and the World Cup, and for conferences like Wikimania, so i think what you are propiding woukd be in scope. Here is one example. If you get it started, and put a link here, experienced editors will assist with formatting and making sure it compares with Wikivoyage policies. You would be responsible for content, however. Ground Zero (talk) 16:41, 24 October 2024 (UTC)Reply
I think a physical stand at an event is being proposed. Does this need a page? What may be useful is a 2-3 paragraph guide to Wikivoyage that can be printed and displayed on the stand. Do we have a page that could be printed as a WV poster? I assume that the "other project" is another WMF wiki and not another venture that we would need to question whether it is compatible. If there is some idea of the location of this event, some improvements could be made to the local pages. AlasdairW (talk) 18:00, 24 October 2024 (UTC)Reply
I'm sorry Ground Zero, but this is not what I am referring to. What I'm referring to is starting up a stand at that event and talking about why you should edit on Wikivoyage etc. RockTransport (talk) 18:20, 24 October 2024 (UTC)Reply
Yes, I misunderstood. Sorry for my interruption. Carry on.... Ground Zero (talk) 18:44, 24 October 2024 (UTC)Reply
Will you be there the whole time? Will you have wifi access? Can you have more than one computer/display screen? WhatamIdoing (talk) 23:52, 24 October 2024 (UTC)Reply
We will be there the whole time and we may have Wi-fi access. I'm not too sure about the display screens though. We are unveiling the technology behind it so it is in line with the technology part. RockTransport (talk) 06:16, 25 October 2024 (UTC)Reply
If you have a display screen (even if it's just a laptop), you can play a slideshow/video that shows how to edit, with occasional messages about why to contribute. (I would suggest making those messages as simple and basic as possible.) The advantage of a slideshow is that it can run even when you're busy with something else.
If you have time to talk to people, you could ask people to suggest changes, and show them how you do it (i.e., in your own account, or in a specially created account for the event that you use). For example, you can ask people "Here's the article for Ourtown. When you have visitors, where do you take them?" or "What have we gotten wrong in this article?"
When is your event? If it's weeks or months from now, we might be able to mail you some stickers to give away. WhatamIdoing (talk) 16:45, 25 October 2024 (UTC)Reply
After making a decision, I have decided to change my mind and I will not use Wikivoyage during this event. Thanks though! RockTransport (talk) 18:07, 25 October 2024 (UTC)Reply
Okay. Watching two stands was sounding like a lot of work and logistics to me. Maybe keep the idea in mind for another year. WhatamIdoing (talk) 18:09, 26 October 2024 (UTC)Reply

Stage stations

[edit]

I'm just putting this out here for a potential travel topic. In the past, when people had to ride horses to travel long distances, there would be places where they could change horses to continue the journey once their horse got tired. With such an article we could cover both the caravanserai of the Middle East and North Africa, and the shukuba of Japan. There are also a few such places in China that have been preserved, and I think the U.S. may have some such sites as well. The dog2 (talk) 02:25, 25 October 2024 (UTC)Reply

The U.S. absolutely had them, and there are some existing stagehouse inns and restaurants at some of the places on stagecoach routes where people and horses got refreshments and rest. Ikan Kekek (talk) 03:38, 25 October 2024 (UTC)Reply
King's Road (Finland) mentions a number of inns that have survived in some form. I suppose they served a role similar to the stage stations (by letting passengers rest), although the system I know about here was a farmhand driving horses of the farm to the next farm in the system – I don't know whether the inns represent the same period. w:Coaching inn says those performed the same functions as the American w:stage stations. w:Stagecoach seems to concentrate on England, but mentions several other countries. Also w:Mail coach is probably relevant. I suppose there is a host of Wikipedia articles also on the eastern systems. –LPfi (talk) 14:30, 25 October 2024 (UTC)Reply
For Japan there is a Wikipedia article on Shukuba (宿場), which was the Japanese equivalent during the Edo Period. In Chinese, they are called 驛站 (yìzhàn), and some of the ones in China have been preserved to the present day. There is not much information on them in English, but there are travel articles in Chinese about some of those you can visit. If we create such an article, we need to think about what to call it. "Stage station" is one name, but you may also encounter "relay station" or "post station". The dog2 (talk) 15:11, 25 October 2024 (UTC)Reply
Lion and Lamb, a former coaching i in Farnham, Surrey
There are many coaching inns throughout Europe. The give-away is usually a large door which lead to a courtyard. In the picture to the right (which shows a former coaching inn that dates back to the sixteenth century, the doorway is below the gable). The Wikipedia article scarcely does justice to the topic. Since coaching inns were used to change horses, they were seldom more than 10 km apart and many market towns had clusters of coching inns. I found an academic article about English coaching inns which gives more information here[1]. From what I have seen in France and Germany, similar coaching inn networks exsist there as well. Today, some of these coaching inns are still hotels where patrons park their cars in the former coachyard. Others, such as the Lion and Lamb in Farnham (see illustration) have been repurposed - in this case, the courtyard is an open pedestrianised precint with a number of coffee shops. Martinvl (talk) 12:44, 28 October 2024 (UTC)Reply
We already have an article about The Tokaido Road and many more could be made, so I don't see an issue with making more in Japan or the equivalent in other countries. Are you suggesting making a parent article that lists similar places worldwide that we don't have articles for? I don't see an issue with that either. I don't know if we have any articles to put in it at the moment outside of Japan (Magome and Tsumago are articles specifically about individual post towns), but it's a legitimate travel topic. In Japan they seem to be consistently translated as "post towns" or "post stations" in English. ChubbyWimbus (talk) 03:55, 29 October 2024 (UTC)Reply
In the United Kingdom, the word "Post Town" has nothing to do with travelling, but is tied up with the postal service. The United Kingdom has about 1500 post towns. When mail is being delivered, it is first delivered to the main postal sorting office in the post town and from there it is either delivered to the recipient or to a subsidiary sorting office in a neighbouring town or village for futher sorting and delivery.
As regards your initial question, I was thinking in terms of an article that described a typical coaching inn, but with your suggestion, such an article could include a list of roads that have many coaching inns. Martinvl (talk) 18:02, 30 October 2024 (UTC)Reply

Final Reminder: Join us in Making Wiki Loves Ramadan Success

[edit]

Dear all,

We’re thrilled to announce the Wiki Loves Ramadan event, a global initiative to celebrate Ramadan by enhancing Wikipedia and its sister projects with valuable content related to this special time of year. As we organize this event globally, we need your valuable input to make it a memorable experience for the community.

Last Call to Participate in Our Survey: To ensure that Wiki Loves Ramadan is inclusive and impactful, we kindly request you to complete our community engagement survey. Your feedback will shape the event’s focus and guide our organizing strategies to better meet community needs.

Please take a few minutes to share your thoughts. Your input will truly make a difference!

Volunteer Opportunity: Join the Wiki Loves Ramadan Team! We’re seeking dedicated volunteers for key team roles essential to the success of this initiative. If you’re interested in volunteer roles, we invite you to apply.

  • Application Link: Apply Here
  • Application Deadline: October 31, 2024

Explore Open Positions: For a detailed list of roles and their responsibilities, please refer to the position descriptions here: Position Descriptions

Thank you for being part of this journey. We look forward to working together to make Wiki Loves Ramadan a success!


Warm regards,
The Wiki Loves Ramadan Organizing Team 05:11, 29 October 2024 (UTC)

Android app for Wikivoyage

[edit]

Hi, is there an Android app for Wikivoyage? How does it work? I have been advised that there is no infrastructure for push notifications for Android apps for sister wikis and I would be interested to know more. Related: phab:T378545. Thanks! Gryllida (talk) 23:16, 29 October 2024 (UTC)Reply

@Gryllida: AFAIK, no, we don't have either an iOS or an Android app for Wikivoyage. --SHB2000 (t | c | m) 23:27, 29 October 2024 (UTC)Reply

Any interface admin around?

[edit]

Could one of you take care of User:Nothing I Can't/common.js – this is a JS page for a username that doesn't exist (never moved when the user was renamed). Thanks. --SHB2000 (t | c | m) 00:50, 3 November 2024 (UTC)Reply

Same with User:Alexlur/common.css. --SHB2000 (t | c | m) 00:51, 3 November 2024 (UTC)Reply
I don't seem to be able to remove those... -- andree 18:37, 3 November 2024 (UTC)Reply
That's interesting – @Andyrom75:, are you able to delete those? I hope it doesn't require a sysadmin. --SHB2000 (t | c | m) 03:05, 4 November 2024 (UTC)Reply
I was able to delete it. —Granger (talk · contribs) 04:24, 4 November 2024 (UTC)Reply
Interesting how I was able to just delete the second one. Must've been some glitch/connection issues on my side earlier. Thanks for deleting the first page. --SHB2000 (t | c | m) 05:01, 4 November 2024 (UTC)Reply

PSA: POI Search gadget

[edit]

We had this conversation in the past few years, that many region articles have empty see/do sections. Behold this tool, which can be enabled in the preferences/gadgets to kickstart these sections:

After setting the language (standard wiki code) + clicking the button, it will search all the articles in the section and gather all see/do listings there (with wikidata/wikipedia reference). Then it retrieves the number of views (of that wikipedia article, in the above language) and finally prints out the 9 most viewed POIs, in the format of WV templates.

You can try it on e.g. North Moravia and Silesia. Some time ago, I filled that area using Wikivoyage:Maptool, and after moving the listings into the cities, this POI search can be used.

Note that if there are too many listings and/or sub-articles, this may fail/trigger some rate-limiting on wikipedia (didn't observe it, but one never knows). Comments are welcome, as usual :-) -- andree 20:40, 3 November 2024 (UTC)Reply

I tried it out. It feels like it would be more useful for articles with little content. I particularly appreciated the tool ranking points of interest according to the number of page views on Wikipedia, as it puts the more obvious sights towards the top. WhatamIdoing (talk) 22:42, 4 November 2024 (UTC)Reply
Indeed, that was the intended use - if the cities are prepared, and the whole area is reasonably covered by wikipedia, it (IMO) works nicely as 'starting content' for the region (esp. if you don't know it personally, what are the most interesting POIs). Thanks for giving it a try! :-) -- andree 06:47, 5 November 2024 (UTC)Reply
I found it useful for Western Iowa, a mostly rural neglected region. I don't know much about that area, and there isn't much there, but by setting the radius to 100 km and looking through its list for things that sounded relevant to tourists (e.g., some lakes, some small airports), I was able to add several things that would be interesting to people outside of individual towns. WhatamIdoing (talk) 19:32, 5 November 2024 (UTC)Reply
Special:Preferences#mw-prefsection-gadgets for reference. --SHB2000 (t | c | m) 22:46, 4 November 2024 (UTC)Reply

FYI: All Travelers are Infiltrators: An Introduction to the Study of Travel Writing

[edit]

https://daily.jstor.org/all-travelers-are-infiltrators-an-introduction-to-the-study-of-travel-writing/ An interesting lens to think of travel writing. Like all lenses, it clarifies some things, distorts others, etc. —Justin (koavf)TCM 09:48, 6 November 2024 (UTC)Reply

Switching to the Vector 2022 skin: the final date

[edit]
A two minute-long video about Vector 2022

Hello everyone, I'm reaching out on behalf of the Wikimedia Foundation Web team responsible for the MediaWiki skins. I'd like to revisit the topic of making Vector 2022 the default here on English Wikivoyage. I did post a message about this two years ago, but we didn't finalize it back then.

What happened in the meantime? We built dark mode and different options for font sizes, and made Vector 2022 the default on most wikis, including all other Wikivoyages. With the not-so-new V22 skin being the default, existing and coming features, like dark mode and temporary accounts respectively, will become available for logged-out users here.

If you're curious about the details on why we need to deploy the skin soon, here's more information

* Due to releases of new features only available in the Vector 2022 skin, our technical ability to support both skins as the default is coming to an end. Keeping more than one skin as the default across different wikis indefinitely is impossible. This is about the architecture of our skins. As the Foundation or the movement in general, we don't have the capability to develop and maintain software working with different skins as default. This means that the longer we keep multiple skins as the default, the higher the likelihood of bugs, regressions, and other things breaking that we do not have the resources to support or fix.  

  • Vector 2022 has been the default on almost all wikis for more than a year. In this time, the skin was proven to provide improvements to readers while also evolving. After we built and deployed on most wikis, we added new features, such as the Appearance menu with the dark mode functionality. We will keep working on this skin, and deployment doesn't mean that existing issues will not be addressed. For example, as part of our work on the Accessibility for Reading project, we built out dark mode, changed the width of the main page back to full (T357706), and solved issues of wide tables overlapping the right-column menus (T330527).
  • Vector legacy's code is not compatible with some of the existing, coming, or future software. Keeping this skin as the default would exclude most users from these improvements. Important examples of features not supported by Vector legacy are: the enriched table of contents on talk pages, dark mode, and also temporary account holder experience which, due to legal reasons, we will have to enable. In other words, the only skin supporting features for temporary account holders (like banners informing "hey, you're using a temp account") is Vector 2022. If you are curious about temporary accounts, read our latest blog post.

So, we will deploy Vector 2022 here in three weeks, in the week of November 25. If you think there are any significant technical issues, let us know. We will talk and may make some changes, most likely after the deployment. Thank you! SGrabarczuk (WMF) (talk) 16:22, 6 November 2024 (UTC)Reply

@SGrabarczuk (WMF), click here: https://en.wikivoyage.org/wiki/Grinnell?useskin=vector-2022 and take a look at the missing page title. WhatamIdoing (talk) 20:35, 6 November 2024 (UTC)Reply
I see it on desktop, it's in the pagebanner. Do you mean the lack of a "floating" page title bar? Using Template:Pagebanner seems to disable it. The issue is probably fundamentally with Extension:WikidataPageBanner and/or its CSS. There's an open bug report since 2022. Either that, or the floating bar hasn't been enabled for the main namespace. Daggerstab (talk) 09:31, 7 November 2024 (UTC)Reply
Screenshot of Vector 2022 skin at Wikivoyage
I'm primarily concerned about the big empty space that I've marked here. It looks odd.
Additionally, while I don't think we necessarily want "wide width", we might want a wider default, and to have these sidebars start off collapsed. WhatamIdoing (talk) 20:52, 7 November 2024 (UTC)Reply
That's an inevitable result of the Pagebanner extension suppressing the article title. And apparently it's made bigger by a placeholder box for the site notice? I don't know if the languages menu can be repositioned via CSS or some skin settings. Daggerstab (talk) 22:23, 7 November 2024 (UTC)Reply
@Daggerstab, WhatamIdoing: I was already writing my thoughts in reply to the Pagebanner-Vector2022 compatibility, but I'll do that separately. The part of it that applies here, is that having the text size set as standard blows a lot of elements, and makes many others (like the pagebanner) considerably smaller in comparison, to where some templates are simply unusable. Setting the text to be 'small' instead, results in a version of Vector2022 that more or less everything we know and love from old-Vector, except styled it's like an early-2020s website instead of a late-1990s website.
Wauteurz (talk) 22:38, 7 November 2024 (UTC)Reply
Reading this back, and Christ does it look like my head was turned off. None of what I said is really relevant to this discussion. My apologies for that.
I think I meant to raise the fact that, yes, MW:Extension:WikipediaPageBanner does conflict with Vector2022's floating title, and that a patch (Phab:T306744) is being worked on, seemingly close to being finalised. That said, I think my note of the small text setting making Vector2022 look more familiar to those still used to old-Vector does hold true. It distorts templates and extensions considerably less, but making the point here was a tad irrelevant. :)
Wauteurz (talk) 22:18, 8 November 2024 (UTC)Reply
That patch was me, BTW. I didn't wait until the weekend. Daggerstab (talk) 06:31, 9 November 2024 (UTC)Reply
I'm still opposed to this change – what exactly has changed for Wikivoyage since. What you seemed to have mentioned in your post doesn't seem to resolve any of the Wikivoyage-specific issues. --SHB2000 (t | c | m) 04:18, 7 November 2024 (UTC)Reply
I looked at the linked old discussion, and there seem to be no site-breaking issues. Some CSS changes might be necessary to preserve pagebanner height, and perhaps the skin's default page width should be set to "wide". The only major issue is the missing floating title bar, and it's mainly an issue because the button for unhiding the side menu goes there when the menu is hidden. (See my other comment about the pagebanner extension bug report.) Daggerstab (talk) 09:49, 7 November 2024 (UTC)Reply
I did some technical investigation of the issue and posted a comment to that bug report. If nobody does anything until the weekend, I can actually go through the whole rigamarole of setting up a MediaWiki development environment and try to submit a fix myself. Daggerstab (talk) 12:18, 7 November 2024 (UTC)Reply
SHB, the question here is what's going to change for Wikivoyage soon. If we don't switch, stuff's going to start breaking, and when we complain, they're going to say "Well, we told you that we weren't going to keep supporting that 15-year-old skin forever. It's your own fault if you decided to use old software after we warned you." WhatamIdoing (talk) 20:54, 7 November 2024 (UTC)Reply
Right, I see – doesn't help that we're considered an afterthought here. --SHB2000 (t | c | m) 21:04, 7 November 2024 (UTC)Reply
No, we're a "first thought"; that's why they're warning us in advance. WhatamIdoing (talk) 03:44, 8 November 2024 (UTC)Reply
If we were truly a first thought, the issues brought up would have been fixed 2 years back, not now. --SHB2000 (t | c | m) 03:53, 8 November 2024 (UTC)Reply
Asking out of curiosity more than anything, but what according to you are the issues that were brought up that haven't yet been fixed? I can't seem to identify ones that haven't yet been mended or at least touched on. The only things that I can see not having been addressed, weren't within Vector2022's scope to begin with.
Wauteurz (talk) 22:11, 8 November 2024 (UTC)Reply
I do prefer Vector2022 over old-Vector, but only once modified. My main grope with Vector2022 as it stands, is that it breaks all of Wikivoyage's UI and layout balance. This is because of two factors: Scaling, and compatibility. Scaling is an issue since Vector2022 blows up the proportions of UI elements to where there's barely any room left to fit content (as @WhatamIdoing's screenshot above demonstrates). Compatibility is an issue as Wikivoyage articles depend on MW:Extension:WikidataPageBanner, and it is not yet updated to be entirely compatible with Vector2022, although a patch fixing the lack of a floating bar is currently being tested. Floating the pagebanner at the top of the page in place of the floating title bar I don't think is a feature that's being worked on, but the TOC is in the sidebar anyway - so that's not much of an issue.
Also, I would implore anyone still against or on the fence about Vector2022 to use, to enable it, customise that scaling so it doesn't break every template's proportions, and use it for a week or two. Yes, it takes some time to find where things have moved, but you'll also find that having, for example, a TOS on the sidebar is a massive quality of life improvement.
I personally would only support Vector2022 being rolled out here once the floating bar is fixed (which shouldn't take that long), and if Wikivoyage's default appearance uses the 'small' text option so we don't have to rethink our whole layout as a result of Vector2022.
The way I see it, Vector2022 definitely is the way forward, and the skin doesn't need anything additional for us that I am aware of. But despite that, other extensions, modules, &c, that we use, are not yet fully compatible with it, so we're not in a position to make the switch yet. Give it a few more months, and we should be there.
Wauteurz (talk) 23:20, 7 November 2024 (UTC)Reply

Excessive whitespace above the (hidden) title

[edit]

The issue noticed by @WhatamIdoing above is partially caused by a placeholder that remains after the sitenotice banner is collapsed. On my display, it's 24 px high, either because it has a fixed height in CSS (which doesn't seem the case), or because it has some kind of actual content, a default banner - a div containing a "<!-- CentralNotice -->" comment. Someone with more user rights than me should look into that.--Daggerstab (talk) 09:28, 10 November 2024 (UTC)Reply

Would like review of Charlton

[edit]

I've recently been working on updating the information for my hometown of Charlton and now think it's relatively complete (at least for a first pass at things). I'd appreciate someone experienced in Wikivoyage to take a look to see if I've done enough to graduate it out of "Outline" status, and please provide any further suggestions for improvements. Thank you! -- PeterCooperJr (talk) 19:32, 6 November 2024 (UTC)Reply

@PeterCooperJr, that's a really nice article. Congratulations!
If you were looking for something else to add, then I like to note an outdoor activity or two that is suitable for wheelchairs/walkers/people with mobility issues, and I like to mention the existence of public restrooms in parks. This can literally be as short as typing "Restrooms." at the end of a description, or by adding a description like "flat, paved" to hiking trails (or the opposite sentiments: "loose dirt" or "climbs 300 ft elevation"). WhatamIdoing (talk) 20:43, 6 November 2024 (UTC)Reply
Hello, PeterCooperJr, I have to echo WhatamIdoing's kind words – great work to the article! Other than what she already mentioned, my only gripe with the article is the "By plane" article – typically we only include airports if they are in that town and more so, information from how to get from the airports to the town needs to be present. I think the two Worcester airports are fine (but you will need to add information on getting from the two airports), but Boston and Bradley seem realistically too far away to be useful for travellers. Otherwise, keep up the great work. --SHB2000 (t | c | m) 04:11, 7 November 2024 (UTC)Reply
I disagree. Logan Airport is the major airport in the area. If you want to get to Charlton from most other places by plane, you are not going to go to some local Worcester airport, when Worcester is 40 miles from Boston. Note this description (emphasis added): "This regional airport is about 20 minutes away from Charlton, and while it only has a few flights daily it's much more convenient to drive to than the larger airports that are further away." Where we agree is that there shouldn't be listings for the bigger airports farther away; instead, Boston Logan International Airport and [[BDL|Bradley International Airport]] should be merely linked. Ikan Kekek (talk) 04:32, 7 November 2024 (UTC)Reply
Yep, the listings should merely be linked, not listified (whereas Worcester seems close enough to be listified). I simply happened to phrase that very poorly. --SHB2000 (t | c | m) 04:35, 7 November 2024 (UTC)Reply

Template:Overseasjobscam

[edit]

Template:Overseasjobscam Does anybody know if this is still relevant? If no one does, at what time threshold do we call this irrelevant? This is currently displayed on: Thailand, Cambodia, Laos, Myanmar, Myawaddy, Northern Myanmar, Sihanoukville, Southeastern Myanmar and Tachileik. At what point do we call this? My plan is that if no one has any further details on this within the next week or two, I'll just mass remove these from the pages, and propose the template for deletion. Brycehughes (talk) 02:33, 10 November 2024 (UTC)Reply

Sounds like a good plan to me.
We do have some warnings at Volunteer_travel#Be_wary, Working_abroad#Stay_safe & Teaching_English#Risks. I think those are all we need, though some other articles might need links to those. Pashley (talk) 05:38, 10 November 2024 (UTC)Reply
Are you suggesting integrating some of the wording into the articles? I could see adding a sentence or two to the work sections of Thailand, Cambodia, Laos and Myanmar. Brycehughes (talk) 06:05, 10 November 2024 (UTC)Reply
The other day I found out that Wikivoyage has mw:Extension:Labeled Section Transclusion enabled, which allows parts of page text to be included into another page without being turned into proper templates. It might be helpful in this case. Daggerstab (talk) 09:34, 10 November 2024 (UTC)Reply
The template is addressing "Chinese speakers", but this is the English Wikivoyage. So, I think the warning should be (and is) given at the Chinese Wikivoyage. FredTC (talk) 11:03, 10 November 2024 (UTC)Reply
Could {{seealso|Working_abroad#Stay_safe}} replace all uses of the template? Pashley (talk) 14:48, 10 November 2024 (UTC)Reply

News sites say the scam is still ongoing. Thailand, Cambodia, Myanmar 1, Myanmar 2, Myanmar 3, Laos. And it's now targetting new countries for scammers to traffick (e.g. Africa, South America and UK) who are fluent in English that they previously have not recruited from. I recommend keeping this note. OhanaUnitedTalk page 15:33, 10 November 2024 (UTC)Reply

I think that's reason enough to keep it. I would only include it in the Work sections of Thailand, Cambodia, Laos and Myanmar though – any objections to removing it from the child articles? Brycehughes (talk) 21:08, 11 November 2024 (UTC)Reply
Any objections going once... going twice... Brycehughes (talk) 23:26, 15 November 2024 (UTC)Reply
It wouldn't hurt to keep the notice in child articles, but to revise the notice to mention that it's targetting both Chinese and English speakers. OhanaUnitedTalk page 05:44, 16 November 2024 (UTC)Reply
[edit]

I have created User:Red link example (confirmation) for use in documentation and testing.

The account is already globally locked, so cannot be used for editing.

It is vital that the user and talk pages are not created. Can an admin kindly protect them both, permanently, with an edit summary noting that they are "for use in documentation and testing"? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:43, 12 November 2024 (UTC)Reply

@Pigsonthewing: Red link example is not registered locally on enwikivoyage. Could you register it locally and then give me a ping? --SHB2000 (t | c | m) 22:19, 12 November 2024 (UTC)Reply
Hang on, it is locked. I'll still go ahead and protect it anyway. --SHB2000 (t | c | m) 22:23, 12 November 2024 (UTC)Reply

Attempting to revert vandalism; keep getting prevented by filters

[edit]

Hello all, when I attempted to revert vandalism on User talk:Count Count, it was blocked by the filters.This has happened to me on multiple occasions, such as trying to revert cross-wiki vandalism on Wuhan and getting prevented by the filters when reporting someone at WV:VIP. Can something be done about this to where I stop getting prevented by the filters when I do counter-vandalism? Thank you. ChrisWx (talk) 03:03, 14 November 2024 (UTC)Reply

Generally most cross-wiki patrollers lack this issue due to the fact that global rollbackers have autopatrol globally, but since I notice your edit matrix x-wiki isn't super extensive (for GR), your best course of action is to just let an admin know for now until we figure out a workaround with the filters. --SHB2000 (t | c | m) 03:09, 14 November 2024 (UTC)Reply
I know this isn't the subject of your question, but I want to again object to VIP standing for something other than the obvious Very Important Person. That said, I don't think the filter should have tripped you up, and I'm confident one of our technical people will fix it, but we wouldn't have known there was a problem if you hadn't told us, so thanks for doing that, and sorry. Ikan Kekek (talk) 03:11, 14 November 2024 (UTC)Reply
Yeah I hate the name of VIP – I'll make a proposal on the talk page. SHB2000 (t | c | m) 03:13, 14 November 2024 (UTC)Reply
Thank you both for the responses! I'll remember to take this approach until the filters are fixed. I hope that the filters can be fixed soon, and will let admins like y'all know about the vandalism if you aren't taking care of it already for the time being. :) ChrisWx (talk) 03:15, 14 November 2024 (UTC)Reply
Sure thing – and in the meantime I've given you autopatroller perms since your primary work here is cross-wiki patrolling (meaning you shouldn't be caught up in such filters anymore). --SHB2000 (t | c | m) 03:17, 14 November 2024 (UTC)Reply
Awesome, thank you very much! ChrisWx (talk) 03:18, 14 November 2024 (UTC)Reply
There were multiple issues, some of which really cannot be resolved other than by giving such rights. I fixed one filter. When disallowing your revert of a talk page edit, the filter was doing exactly what it should do – the filter had no way of knowing it wasn't vandalism. You were also caught by a global filter that seems like very easily causing false positives, with autopatroller no recourse (we cannot edit those filters, just ask for changes, and I couldn't spot the offending expression in it). –LPfi (talk) 10:54, 14 November 2024 (UTC)Reply
See Meta:Talk:Global AbuseFilter#Filter 214. Doing some more edits could help. –LPfi (talk) 11:13, 14 November 2024 (UTC)Reply
The global filter was updated to use the global edit count, so Wikipedians coming here for such edits won't be disallowed by it any more. –LPfi (talk) 21:34, 14 November 2024 (UTC)Reply
That's much better than using local edit count, IMO (and my bad for not noticing and fixing it earlier). --SHB2000 (t | c | m) 21:41, 14 November 2024 (UTC)Reply
We might want to do the same change in some of our own filters, see Special:AbuseFilter/2 for discussion on details. –LPfi (talk) 09:30, 15 November 2024 (UTC)Reply