User talk:Wrh2 Voyage Tips and guide

Contents

I've deleted one of the two templates, and converted the other over to replace the infobox that's been added to various country articles. See Wikivoyage:Travellers' pub‎‎#Currencies, again for more details. -- Ryan • (talk) • 22:13, 4 January 2017 (UTC)Reply

Thank you muchly. I will use the template instead. Unless I run into resistance for the changes I have made to the Central American articles, I will apply this to other countries with the aim of making it a standard place in countries articles for readers to find this information. Ground Zero (talk) 22:29, 4 January 2017 (UTC)Reply

I like having the currencies optional. Thanks. I had tried removing the USD line, but that didn't work. I have also thought about adding one or two regional currencies for some countries where there may be a larger share of readers, e.g., Cdn $ for USA, Mexico; Aus$ for NZ, Indonesia; and SA rand for southern Africa. I guess I can copy the code down to create additional optional cornices, can i? Ground Zero (talk) 16:06, 5 January 2017 (UTC)Reply

As noted in the pub, the current template is just a quick-and-dirty version that was meant to immediately replace the infoboxes. Feel free to add more currencies to the template, although if the template starts to get overly complex then some refactoring may be required. -- Ryan • (talk) • 16:09, 5 January 2017 (UTC)Reply

I've added CAD to USA and Mexico, but not to others. When I get to Caribbean nations, I will probably add CAD there too.

I really appreciate your assistance on this.

Can I ask your opinion on a template for the eurozone? Should it show just USD and GBP, or should I add CAD and AUD too? I'm Canadian, so I don't trust my own instincts on this one. Thanks. Ground Zero (talk) 19:36, 5 January 2017 (UTC)Reply

Re: currencies to show: that's probably a better question for the pub - I can help with the implementation, but can't provide much expertise on the subject matter. -- Ryan • (talk) • 19:50, 5 January 2017 (UTC)Reply

Template:Exchange rate euros is another failed experiment. It should be deleted. I'm just not getting the hang of templates, unfortunately. Sorry to cause extra bother. Ground Zero (talk) 21:16, 7 January 2017 (UTC)Reply

What is the goal with the new template? I assumed you were just trying to create something that could be used for all Eurozone countries, and tweaked it slightly to promote re-use of {{exchange rates}}. Is there something else it is supposed to do? -- Ryan • (talk) • 21:22, 7 January 2017 (UTC)Reply

I see now that your tweaks made it work, and do exactly what it was supposed to do. Thanks. I can use that also for UKP, USD, CFA francs, and Eastern Caribbean dollars. Ground Zero (talk) 21:44, 7 January 2017 (UTC)Reply

I have started a documentation page Template:Exchange rate euros/doc. As there are not really any parameters on this one, I have not added that. Please let me know if there is more I should do, or if there is somewhere I can read up on using templates. Ground Zero (talk) 22:52, 7 January 2017 (UTC)Reply

mw:Help:Templates provides an overview of templates, although if you are stuck you can always just as in the Pub and plenty of people should be able to help. -- Ryan • (talk) • 23:06, 7 January 2017 (UTC)Reply

Ryan, I am happy with whatever coding solution you think works best, and am willing to apply the template to articles when it is ready. I do get a bit frustrated, though, that some editors drop in on a discussion to indicate vaguely how something should be done differently, but dont seem to be willing to either provide specifics, or to assist you and me in doing the work. In updating exchange rates, I have found rates in articles that date as far back as 2007, although 2011 and after is more common. Meanwhile, there has been talk on the Currency talk page since 2011 about how to go about fixing it. My aim is to have all country articles updated to Jan 2017 by the end of the month, except for war zones, of course. Will I be around next January to update them again? Maybe. Be at least now there are links in the country articles to make updating the rates much easier should someone else be willing to take it on. And someday, I hope, Wikivoyage will reach the El Dorado of an automated solution that will render updating unnecessary, by in the meantime, we won't have lists of rates from 2013 that make WV look like a dead site. Thank you again for your help. <endrant> Ground Zero (talk) 21:09, 16 January 2017 (UTC)Reply

@Ground Zero: I think anyone who contributes to a wiki regularly gets frustrated at times - since there isn't any authority hierarchy it can be very tough to make decisions and get things done, but it helps to remember that everyone contributing means well. I'll revisit {{exchange rates}} sometime soon and see what can be done to consolidate things further.

It's also worth noting that historically, most people who propose something like an exchange rate template tend to not follow through, thus I tend to be skeptical of those sorts of proposals. In this case I was skeptical when you started the discussion, but I've been pleasantly surprised to see you implement it in most of the country articles - you've proven to be a true exception. Thanks for your efforts! -- Ryan • (talk) • 03:49, 17 January 2017 (UTC)Reply

Your skepticism is entirely warranted: wikis are littered with projects that have been started and abandoned. I think we've seen why nothing has happened with exchange rates for five years: there are a lot of people who want to direct the work, and so discussion goes on for a while until it grinds down and nothing is done, then a while later someone else takes a run at it and the cycle repeats. I guess I've been willing to step on toes to get this done, so now the only countries remaining are the 14 CFA and 8 EC countries. I'll look forward to seeing what you can do with the template. Thanks again for your work and support. Ground Zero (talk) 13:29, 17 January 2017 (UTC)Reply

Hi, Ryan. Can I ask why your bot changes the ellipsis character to three periods? Powers ^(talk) 21:48, 8 January 2017 (UTC)Reply

Replacing the non-ASCII ellipsis symbol with the ASCII equivalent of three dots is fairly standard practice (see w:MOS:ELLIPSIS) so I assumed that it would not be a controversial change. I've reverted the edit in question and removed that rule from the bot. -- Ryan • (talk) • 22:49, 8 January 2017 (UTC)Reply

I wasn't asking for a reversion; I was just curious what the rationale was. I'm not sure I agree with Wikipedia's analysis of the character's drawbacks but I'm willing to use periods if it's considered better. Powers ^(talk) 01:32, 9 January 2017 (UTC)Reply

I disagree with this edit to Wikivoyage_talk:Internal_links. The original comment, left by another user, was "[[Mos]], while actually one of the few useful shortcuts we have, is a town in Spain. [[Apt]] is a town and canton in France. [[As]] are towns in Belgium, Norway, Finland and the Czech Republic. [[Tone]] is a town in Japan. [[IL]], I'd say it should redirect to either Illinois or Israel, but no, it goes to this page." The whole point of that comment is that the original poster dislikes policy shortcuts in mainspace where they can be mistaken for geographic place names. Change [[IL]] to [[WV:IL]] and that meaning is lost. In any case, changing comments left by others is a bad idea if there's any risk that an edit (or even a refactoring) will change the meaning of the text. I haven't reverted your edit, but you may want to look at the text and see if it still makes any sense? Thanks. K7L (talk) 05:10, 15 January 2017 (UTC)Reply

I've reverted that edit - it was done while updating links prior to deleting a redirect, so I hadn't read through the discussions in question. -- Ryan • (talk) • 06:41, 15 January 2017 (UTC)Reply

why? --Garvysolaz (talk) 22:14, 27 January 2017 (UTC)Reply

Altfish (talk) 11:03, 30 January 2017 (UTC) I think I've sorted all the dead links on the Altrincham pageReply

Hi Ryan,

I found a link which was marked as a dead link by your bot, but actually wasn't. Since you asked to know about any such cases, I thought I'd point it out to you. It's in Zarma phrasebook and it concerns the last link Zarma-French-English dictionary.Drat70 (talk) 03:07, 8 February 2017 (UTC)Reply

I found another one at Fischland-Darß-Zingst which links to http://www.bunte-stube.de/ Drat70 (talk) 06:08, 8 February 2017 (UTC)Reply

Frankly I am more concerned about false negatives than false positives, but it's good to know about both. Hobbitschuster (talk) 20:54, 8 February 2017 (UTC)Reply

From here, bisharat.net looks dead (its whois lists ns11.bravehost.com and ns12.bravehost.com as DNS, but neither is responding); www.bunte-stube.de looks to be up. Dunno. K7L (talk) 05:08, 9 February 2017 (UTC)Reply

Hi.

I recently had a debate on de-WV here where I said, I could ask you whether the dead weblink bot can be changed for the German language. It appears that there is interest to have that bot there. So this is me asking you whether that would be possible and if so, how. Hobbitschuster (talk) 22:14, 1 March 2017 (UTC)Reply

Hey Ryan, Russian WV has the same request as de-WV. (Its discussion can be found here). Is it possible for you to run this bot on voy:ru: or share its code? Thanks! --Kiaora (talk) 12:23, 9 June 2017 (UTC)Reply

@Kiaora: At this time I have chosen to retire from Wikivoyage. If you would like I can provide you the code for the dead-links bot (it is written in java using the wiki-java framework), but it isn't well-tested on a non-English site so you may be better off working with some of the bot authors on Wikipedia to re-use one of their dead link bots. -- Ryan • (talk) • 17:39, 12 June 2017 (UTC)Reply

Thanks for taking time to answer this. And yes, if possible, post the source code somewhere please. This way I'll have one more option to choose from. And just to mention, I already had a look at a few other scripts on wikipedia but I was reluctant to use them as I was hoping your one will be easier to adapt. Thanks again! --Kiaora (talk) 17:47, 12 June 2017 (UTC)Reply

@Kiaora: I've uploaded the code to [1]. -- Ryan • (talk) • 04:28, 29 June 2017 (UTC)Reply

Fantastic, thanks! I just tried to run it in ru-WV and it worked. Much appreciated for providing it! --Kiaora (talk) 16:58, 6 July 2017 (UTC)Reply

Wrh2, please do not block me because I am editing Wikivoyage. I will not stop editing until your calm. 70.71.90.6 03:23, 23 April 2017 (UTC)Reply

I don't know what in the world you're talking about, but thanks for linking to your contribution history because you're most definitely going to be blocked now that I've seen it. -- AndreCarrotflower (talk) 06:24, 23 April 2017 (UTC)Reply

Of course, it took some time to have a listing editor (we name it vCard editor) at the German Wikivoyage because the [wv/de] vCard template is more complex then the [wv/en] template and DerFussi and me are the only one who are programmers, too. We will activate it on next Wednesday.

I would propose the following changes in the listing editors script:

From (i18n)

		var _wikidataLabel = function(jsonObj, value) {
			var entityObj = _wikidataEntity(jsonObj, value);
			if (!entityObj || !entityObj.labels || !entityObj.labels.en) {
				return null;
			}
			return entityObj.labels.en.value;
		};

to

		var _wikidataLabel = function(jsonObj, value) {
			var entityObj = _wikidataEntity(jsonObj, value);
			if (!entityObj || !entityObj.labels || !entityObj.labels[ListingEditor.Config.LANG]) { /* mod */
				return null;
			}
			return entityObj.labels[ListingEditor.Config.LANG].value;
		};

And from (Do not perform listing validations when deleting a listing)

					{
						text: ListingEditor.Config.TRANSLATIONS.submit, click: function() {
							if (validateForm()) {
								formToText(mode, listingTemplateWikiSyntax, listingTemplateAsMap, sectionNumber);
								$(this).dialog('close');
							}
						}
					},

to

					{
						text: ListingEditor.Config.TRANSLATIONS.submit,
						title: ListingEditor.Config.TRANSLATIONS.submitTitle,
						click: function() {
							if ($(ListingEditor.Config.EDITOR_CLOSED_SELECTOR).is(':checked')) {
								// no validation
								formToText(mode, listingTemplateWikiSyntax, listingTemplateAsMap, sectionNumber);
								$(this).dialog('close');
							}
							else if (validateForm()) {
								formToText(mode, listingTemplateWikiSyntax, listingTemplateAsMap, sectionNumber);
								$(this).dialog('close');
							}
						}
					},

And from (Add mouse cursor back to price after clicking currency sign)

		var initCurrencySymbolFormFields = function(form, mode) {
			var CURRENCY_SIGNS_SELECTOR = '.currency-signs';
			$(CURRENCY_SIGNS_SELECTOR, form).click(function() {
				var priceInput = $('#input-price');
				var caretPos = priceInput[0].selectionStart;
				var oldPrice = priceInput.val();
				var currencySymbol = $(this).find('a').text();
				var newPrice = oldPrice.substring(0, caretPos) + currencySymbol + oldPrice.substring(caretPos);
				priceInput.val(newPrice);
			});
		};

to

		var initCurrencySymbolFormFields = function(form, mode) {
			var CURRENCY_SIGNS_SELECTOR = '.currency-signs';
			$(CURRENCY_SIGNS_SELECTOR, form).click(function() {
				var priceInput = $('#input-price');
				var caretPos = priceInput[0].selectionStart;
				var oldPrice = priceInput.val();
				var currencySymbol = $(this).find('a').text();
				var newPrice = oldPrice.substring(0, caretPos) + currencySymbol + oldPrice.substring(caretPos);
				priceInput.val(newPrice);
				priceInput.select();
				// now setting the cursor behind the currency symbol inserted
				priceInput[0].setSelectionRange(caretPos + 1, caretPos + 1);
			});
		};

Now I am not really sure if a mobile version could be possible because I do no know if ajax, jquery.ui.dialog, and jquery.ui.autocomplete will work. --RolandUnger (talk) 11:27, 25 June 2017 (UTC)Reply

Thanks for the suggestions @RolandUnger:. I am no longer actively maintaining the listing editor, but @Andyrom75: has been very active in editing the code and may be able to assist. -- Ryan • (talk) • 04:30, 29 June 2017 (UTC)Reply

Thanks for your answer. I will contact @Andyrom75:. The biggest challenge would be the adaption to the mobile version because the Jquery UI modules are deprecated and not working. --RolandUnger (talk) 04:34, 29 June 2017 (UTC)Reply

First of all I'd like to spend few seconds on thanking Ryan for all his great contributions, not only to listing editor, and I was sorry to read that he's about to quit (or at least to reduce significantly) his Wikivoyage presence. Ryan is a great person and technical expert.

That said, let's come to Roland 3 points.

1. If I remember correctly, I've tested your changes in it:voy but I've left entityObj.labels.en because in various cases existed the English label and not the Italian one. By the way we can modify the code to use the local one if exists and if not the English one.
2. Since the body of the two if is the same and considering that if the first variable of an or operator is true the second one won't be tested, we can just modify as follow: "$(ListingEditor.Config.EDITOR_CLOSED_SELECTOR).is(':checked') || validateForm()"
3. I haven't tested it (now I'm in rush ... sorry) but I think it's fine and useful, although I would extend the possibility of adding symbols to all the field with a custom set of chars. --Andyrom75 (talk) 17:39, 29 June 2017 (UTC)Reply

I made all this as a proposal. These proposals were derived from our Listing Editor fork.

By the way, yesterday Jon Robson from WMF told me that there is no way to load jquery.ui.dialog and jquery.ui.autocomplete in the Minerva mobile skin. In the current state the Listing Editor will never run in that skin. Also the people making the ResourceLoader could not help because they are not familiar with the MobileFrontend. Yesterday I started to replace the appropriate calls. --RolandUnger (talk) 04:29, 30 June 2017 (UTC)Reply

Roland, the purpose of my comment is to find a common solution suitable for all the language versions, in order to avoid to have different script. Please share your thoughts about the comments above. --Andyrom75 (talk) 05:52, 30 June 2017 (UTC)Reply

Hi Wrh2, User:Wrh2Bot has been removing dead link templates from links that are still dead, in articles such as Barbuda and Charlotte. I think it might be better to leave the templates there for a human to review rather than removing them by bot, to avoid errors like this. —Granger (talk · contribs) 21:03, 23 September 2017 (UTC)Reply

The Barbuda & Charlotte links you cited are not dead - to cite one example, [2] returns a 200 and redirects to advertising. The bot can only determine if a link is dead, but if it is active there is no way to determine whether the content at the other end of the link is actually relevant or not. -- Ryan • (talk) • 21:08, 23 September 2017 (UTC)Reply

Maybe my phrasing was unclear, but that's exactly my point. Once a link has been marked as dead, if a new website appears at the same URL, there's a good chance that it's a domain squatter rather than the original website. Because the bot can't tell the difference, I think it should leave the templates there for human review rather than removing them. —Granger (talk · contribs) 21:18, 23 September 2017 (UTC)Reply

I appreciate the feedback, but when this was discussed previously people raised concerns about sites that were down temporarily, and wanted assurance that if a site came back online that the bot would no longer mark it as dead. If this is a major concern let me know and I can halt the bot - it is running now only because of the request at Wikivoyage:Collaboration of the month#Category:Articles with dead external links. -- Ryan • (talk) • 21:20, 23 September 2017 (UTC)Reply

Hmm, I only see one user raising a concern like that in the discussion you linked, and their original suggestion was checking links a few days apart (which I think is not a bad idea), not months later. Meanwhile, at Category talk:Articles with dead external links#Dead links bot, at least two other users seem to have raised the same concern I have. I think it is much worse to remove a "dead link" template from a link that goes to a domain squatter than to leave a "dead link" template on a site that has come back to life, because the second case can easily be detected and fixed by someone going through the dead link category whereas the first is more difficult to detect. Moreover, I suspect that domain squatters are more common than sites that come back to life. If you're not willing to make the change, I think it would be better to halt the bot, pending discussion of this issue. I'd be happy to start such a discussion in the pub. —Granger (talk · contribs) 21:29, 23 September 2017 (UTC)Reply

I've disabled the bot. -- Ryan • (talk) • 21:32, 23 September 2017 (UTC)Reply

Thanks! I've started a discussion in the pub. —Granger (talk · contribs) 21:45, 23 September 2017 (UTC)Reply

Swept in from the pub

User:Wrh2 has started running Wrh2Bot again to tag new dead links, and I'm sure I speak for everyone in saying this work is much appreciated. I have a concern, though, which is that the bot removes the "dead link" templates from links if they no longer appear to be dead. Apparently this is to address the case where a website is temporarily down but later comes back online, but the problem is that often these links go to domain squatters, as in Charlotte and Barbuda. I think it would be better for the bot to leave the templates there for human review rather than removing them. What do other people think? Past discussions: 1, 2, 3. —Granger (talk · contribs) 21:44, 23 September 2017 (UTC)Reply

I tend to agree, as that exact thing happened on one of the Buffalo district articles. -- AndreCarrotflower (talk) 22:59, 23 September 2017 (UTC)Reply

There's a 3rd option, one that might get us the best of both worlds. Add a parameter to the template, so that the bot can say "I don't know if the site's back up, or if a squatter took it". Emmette Hernandez Coleman (talk) 02:35, 24 September 2017 (UTC)Reply

This is a very useful bot for keeping this site up to date. Also agree that it should not remove the template automatically if link works on second test. I have also come across a good number of domain squatters on testing. Either do not remove or if not too much effort a separate parameter or category. --Traveler100 (talk) 05:28, 24 September 2017 (UTC)Reply

@Wrh2: Ryan, understand you want to take a break from WV (although you are being missed). Would it be possible to make the code available on the site (in your user area maybe) and some instructions on how it should be run? --Traveler100 (talk) 07:29, 1 October 2017 (UTC)Reply

Hi Ryan, thanks for running the dead links bot again! Unfortunately, it seems to be removing dead link templates again. I recall you had a way to modify the bot to flag them as formerly dead links instead. Can you run that version instead please? —Granger (talk · contribs) 20:10, 31 May 2020 (UTC)Reply

Upon further examination, it seems to be doing that correctly in some articles like this. Is the problem that the template in Bad Bergzabern didn't have a date listed? —Granger (talk · contribs) 20:14, 31 May 2020 (UTC)Reply

(edit conflict) It's running the same version that ran last time, but the code requires a date to know when the link was previously marked as dead; the example you provided was manually added and didn't have a date, so the bot didn't recognize it as one that it had checked before.

I've stopped the bot from continuing its run to avoid any further issues. -- Ryan • (talk) • 20:20, 31 May 2020 (UTC)Reply

Thanks for the clarification. I think manually added dead link templates should be rare enough to be a minor concern, outweighed by the benefit of running the bot, so I encourage you to start running it again regardless. —Granger (talk · contribs) 20:24, 31 May 2020 (UTC)Reply

I've modified the code to insert unknown as the previous date in cases where no date is present in the old template: Special:Diff/3982822/3982823. -- Ryan • (talk) • 21:36, 31 May 2020 (UTC)Reply

Looks great—thanks! —Granger (talk · contribs) 23:10, 31 May 2020 (UTC)Reply

Hi Ryan, how did you implement jCarousel because I copied the code to my MediaWiki:Common.js and the pictures just show up next to each other with no sliding motion.

Ryan, I think it is about time we had another run of the external link check bot. Are you in a position to do this at some point? --Traveler100 (talk) 11:05, 2 August 2018 (UTC)Reply

I ran the bot for a few hours this morning, and got through about 5000 articles before I had to leave the house. Over the coming week I'll run it when I've got reliable internet access, and will leave a note here when it has processed all articles on the site. -- Ryan • (talk) • 22:48, 5 August 2018 (UTC)Reply

The bot is done - all articles have been processed. -- Ryan • (talk) • 05:07, 13 August 2018 (UTC)Reply

Thank you! Hobbitschuster (talk) 14:41, 13 August 2018 (UTC)Reply

Hi Wrh2. I decided to ask you this question since I noticed that you are one of the major contributors to MediaWiki:Gadget-ListingEditor.js.

Ever since we started using listings on the Hebrew Wikivoyage (a long time ago) we had a major bug with the listings that has never been fixed - there is no edit button to any of the listings on the Hebrew Wikivoyage (see example here). The bug prevents users from editing listing in a visual input window (as is possible on the English Wikivoyage).

Would you by any chance be able to fix this bug? ויקיג'אנקי (talk) 10:03, 17 August 2018 (UTC)Reply

Hi Ryan, I tried to import Version 2.1 of the Listing Editor to hewikivoyage (here is the js file). As you can see (if your import the script to your own common.js page), the editor works fine, except one thing. The only problem with the new editor is when you click "edit" to edit an existing listing - the editor doesn't load and nothing happens. However, when you try to add a new listing, the editor does load. Can you please have a look? Thanks for your help (and sorry if you don't understand my English), DL3222 (talk) 16:17, 18 August 2018 (UTC)Reply

? DL3222 (talk) 15:08, 31 August 2018 (UTC)Reply

Hi Wrh2. would you by any chance be able to help us out at Hebvoy by getting your bot to run on the entire content of hebvoy so that all the dead links would be either flagged or removed? ויקיג'אנקי (talk) 19:51, 9 August 2019 (UTC)Reply

Thank you, Ryan. Ground Zero (talk) 20:06, 21 March 2020 (UTC)Reply

I saw that the dead link bot marked many Facebook links as dead links, but in fact they are not dead. E.g. Budapest/Csepel contains link to Magyaros Étekbár which is redirected to [3]; Marcsi Kifőzde which is redirected to [4]. I think these shortenings shouldn't be treated as dead links.--City-busz (talk) 20:59, 1 June 2020 (UTC)Reply

Hi, I put a note about why Facebook links show up as dead links at Category talk:Articles with dead external links#A note on false positives - in every case I've looked at the Facebook page in question is a non-public page, so for anyone who is not logged into Facebook (like a bot) the page returns "not available". -- Ryan • (talk) • 21:25, 1 June 2020 (UTC)Reply

Just to provide a bit more info, Facebook returned a 404 (Not Found) response for three links on the page you cited when the bot attempted to validate that the links were still alive:

2020-05-31 17:59:47,749 WARN - Budapest/Csepel: HTTP 404 processing https://www.facebook.com/1589487017994038/

2020-05-31 17:59:48,810 ERROR - Budapest/Csepel: 2 failures for http://nagylevin.hu/ (java.net.UnknownHostException: nagylevin.hu)

2020-05-31 17:59:49,273 WARN - Budapest/Csepel: HTTP 404 processing https://www.facebook.com/1198894673505729/

2020-05-31 17:59:49,571 WARN - Budapest/Csepel: HTTP 404 processing https://www.facebook.com/2141915062805401/

-- Ryan • (talk) • 21:30, 1 June 2020 (UTC)Reply

That's strange, because I get 301 (Moved Permanently) for these links even if I not logged into Facebook. Maybe it's a special restriction for the bots? Of course I can replace these links for the longer version if it's necessarily. --City-busz (talk) 22:02, 1 June 2020 (UTC)Reply

I'll follow-up after work to see if this was a one-off issue or if it's something specific to how Facebook sees the bot, but when I looked at it yesterday for other pages I was seeing 404 responses. Hitting your link just now with curl I can verify your finding that the response is currently a 301:

$ curl -v https://www.facebook.com/1589487017994038/
* Trying 157.240.11.35...
< HTTP/1.1 301 Moved Permanently

-- Ryan • (talk) • 22:24, 1 June 2020 (UTC)Reply

Also, FWIW, I just spot checked a half dozen other links in the bot logs that were 404 responses from Facebook, and all of those links are still giving me a 404 when I check them today with curl, for example https://www.facebook.com/pages/Kuppers-Bakery-Restaurant/132090783477682, so I'm not entirely sure why the links you cited are problematic. -- Ryan • (talk) • 22:30, 1 June 2020 (UTC)Reply

I'm not sure what it is specifically about those links, but I just re-ran the bot against that article and Facebook still returns 404 errors when the bot hits them; other Facebook links return success/error codes that would be expected when the bot hits them. I assume it has to be some sort of request analyzer on Facebook's side that chooses to give a different response to the bot traffic vs a curl or browser request, but since it seems to affect a very small number of URLs hopefully these can just be cleaned up after manual review for now. -- Ryan • (talk) • 00:38, 2 June 2020 (UTC)Reply

Hi Ryan, do you think that would be easy and quick for you to scan it:voy searching for dead links? I think that a tool like this is so useful that could worth to think how to make available to any wiki. Thanks for your reply. --Andyrom75 (talk) 07:21, 24 July 2020 (UTC)Reply

@Andyrom75: Can you export Template:Dead link to Italian Wikivoyage and also export the ErrorHighlighter gadget and make it available on Italian Wikivoyage (Special:Gadgets/export/ErrorHighligter)? I want to do a few tests to make sure the bot will work in a non-English language, but it will first need the dead links template and the ErrorHighlighter gadget so that when the bot tags a dead link things will render correctly. Thanks! -- Ryan • (talk) • 00:21, 25 July 2020 (UTC)Reply

Done. Thanks for your time. --Andyrom75 (talk) 06:50, 25 July 2020 (UTC)Reply

@Andyrom75: One more thing (sorry, it's been a while since I've worked with Mediawiki) - can you add the following CSS to the Italian Mediawiki:Common.css file? It will cause the dead link tag to be hidden by default, and to only display for users who have enabled the Linkinfo gadget:

/* BEGIN: CSS for Template:Dead link (display managed via the ErrorHighlighter gadget) */
.error-deadlink {
   color: red;
   background: yellow;
   display: none;
   white-space: nowrap;
}
/* END: CSS for Template:Dead link */

-- Ryan • (talk) • 14:37, 25 July 2020 (UTC)Reply

Actually I've done it on purpose, because all the "*info" gadget are used by maintainers that are willing to work on clean up activities. Is it an issue for you? --Andyrom75 (talk) 14:42, 25 July 2020 (UTC)Reply

I just want to confirm that you're OK with all users seeing the "[link non funzionante]" message next to dead links (if I open https://it.wikivoyage.org/wiki/Utente:Wrh2/Sandbox in an incognito window I see the message, so that means everyone will see it). On English Wikivoyage the consensus was to hide that text from normal users and only show it to editors who enabled the "Error highlighter" gadget. Once I run the bot it will appear in a lot of articles, so I want to be sure it's OK for all users to see that before I start tagging links. -- Ryan • (talk) • 15:50, 25 July 2020 (UTC)Reply

Thanks for highlighting it. I forgot to apply a style inside the template. I haven't noticed it because I've turned on all the debug gadgets :-P

Now, if as I supposed, you don't see anymore the links as un registered user, you can proceed with the bot. --Andyrom75 (talk) 16:34, 25 July 2020 (UTC)Reply

Thanks, the bot is now running. I used an auto-translate for messages, please let me know if I need to update anything, or if you notice any issues. -- Ryan • (talk) • 16:55, 25 July 2020 (UTC)Reply

@Andyrom75: There is something wrong with the it:Alta Normandia article - the bot can't edit it, and I get [8f2dfbe0-ff38-41d1-af82-13b28564e083] 2020-07-25 17:30:15: Fatal exception of type "WMFTimeoutException" when I try to load the page in a browser. I'm skipping it in the bot execution, but I've never seen this error before so wanted to bring it to your attention. -- Ryan • (talk) • 17:33, 25 July 2020 (UTC)Reply

I suppose that the bot look for "https?:\/\/" sequence. That said, from these point of view it's a quite standard article. The only two things that I can highlight are:

1. <!--http://-->
2. La regione e i dipartimenti dell'Eure (sud) e Senna Marittima (nord) gestiscono diverse linee di autobus.

Where 1 is just a comment and 2 is a sequence of 3 ext links in the same line. I don't know if it can help. --Andyrom75 (talk) 17:44, 25 July 2020 (UTC)Reply

It looks like the problem is the large mapmask that was added on 14-February. I can load the revision prior to that edit, but every revision after that one fails in my browser with a "gateway timeout" error. -- Ryan • (talk) • 18:12, 25 July 2020 (UTC)Reply

┌────────────────────────────────────────────────────────────────────────────────────────────────────┘ Ok. We have few articles with mapmask, removing them could help the bot? --Andyrom75 (talk) 21:09, 25 July 2020 (UTC)Reply

it:Alta Normandia is likely to fail to load for most users, it is not a problem for just the bot; I cannot view that page at all in my browser. A 300kb mapmask is extremely large, and is probably the cause; if you use a smaller mapmask (remove some of the coordinates) then it will likely fix the issue. -- Ryan • (talk) • 21:46, 25 July 2020 (UTC)Reply

it:Piccardia has the same error. The mapmask for that article is over 500kb and trying to view it in my browser generates an error page. -- Ryan • (talk) • 03:50, 26 July 2020 (UTC)Reply

Ok, I've removed both mapmask. If you find similar issue just let me know and I'll take care about it. --Andyrom75 (talk) 06:56, 26 July 2020 (UTC)Reply

The bot has finished updating all articles on Italian Wikivoyage. If you find any mistakes please let me know. -- Ryan • (talk) • 17:11, 26 July 2020 (UTC)Reply

Thanks a lot Ryan, you are always a great support! As far as you know, is it possible to create a webtool that an admin can launch without disturbing you personally? Or maybe a monthly scheduled tool? --Andyrom75 (talk) 17:43, 26 July 2020 (UTC)Reply

It would take some work to expose the bot as a web tool, but having it run on a monthly basis might not be too difficult. I will investigate and get back to you. -- Ryan • (talk) • 18:34, 26 July 2020 (UTC)Reply

I've foudn and removed very long mapmasks from the following articles: it:Regione del lago di Costanza, it:Okayama and it:Distretto della Svevia. Since I haven't found any trace of your bot in these article there are two scenarios: all the links are fine or bot crashes because of the previous issue. Could you re-run it on these 3 instances? --Andyrom75 (talk) 07:49, 27 July 2020 (UTC)Reply

Those three articles were originally processed successfully, so they should be fine:

2020-07-25 21:48:04,467 [main] INFO - Regione del lago di Costanza: 0 dead links found

2020-07-25 19:22:08,370 [main] INFO - Okayama: 0 dead links found

2020-07-25 14:18:49,917 [main] INFO - Distretto della Svevia: 0 dead links found

For the articles with large mapmasks, the bot was able to retrieve and analyze article text successfully, but it failed when trying to edit the article. These articles also appeared to fail to render in a browser - the two I mentioned earlier generated a "gateway timeout error" message in my browser when I looked at them, so using smaller mapmasks across the site is likely a good idea. -- Ryan • (talk) • 14:31, 27 July 2020 (UTC)Reply

┌────────────────────────────────────────────────────────────────────────────────────────────────────┘ @Andyrom75: "As far as you know, is it possible to create a webtool that an admin can launch without disturbing you personally? Or maybe a monthly scheduled tool?" The bot is re-running now, but it isn't finding a lot of new dead links. Let me know if you would prefer that I schedule it to run less often than once a month so that it doesn't create a lot of clutter in article history - maybe once every three months? -- Ryan • (talk) • 22:58, 30 August 2020 (UTC)Reply

What about running monthly but updating the name of the month only after 6 months? In this way we can catch the "new entries" without affecting too much the page history. What do you think? --Andyrom75 (talk) 17:56, 1 September 2020 (UTC)Reply

I'll try to make that change before running it again. -- Ryan • (talk) • 01:20, 3 September 2020 (UTC)Reply

Hi Ryan, have you got some spare time to look into it? --Andyrom75 (talk) 10:40, 3 December 2020 (UTC)Reply

I haven't had a chance to make any changes to the bot, but since it's been several months since it last ran I'm re-running it now on Italian Wikivoyage. -- Ryan • (talk) • 00:22, 4 December 2020 (UTC)Reply

Hi Ryan, I'm sure that the update of your script has been the last of your thoughts :-P however, I'm pinging you to know if, on top on rerunning the current script, you can modify it in a way that if the status doesn't change no text will be changed in the article. I mean, there's no added value on updating the month where the link was found broken, but it's ok to change the notifing template when the link restart to work. Let me know, --Andyrom75 (talk) 18:25, 5 October 2021 (UTC)Reply

@Andyrom75: I can't promise that I'll be modifying the deadlink bot code anytime soon, but if I get a chance to make the changes you want I'll be sure to re-run it against Italian Wikivoyage. Ryan • (talk) • 03:26, 27 October 2021 (UTC)Reply

Welcome back :-) if you think it can help if you share me the code I can try to have a look at it to try to apply those changes. Let me know, --Andyrom75 (talk) 07:42, 27 October 2021 (UTC)Reply

However, since last time has passed 1 year, could you run again the script? But again, please evaluate the possibility to share the source to avoid to disturb you in the future. Thanks, --Andyrom75 (talk) 07:02, 13 November 2021 (UTC)Reply

@Andyrom75: I've posted a copy of the code at mountaininterval.org/downloads/wikivoyage.zip. There is a README file with basic instructions for running it, but I never took the time to clean it up enough to make it usable for others so you may need to do some trial-and-error to get it fully functional. -- Ryan • (talk) • 16:27, 5 December 2021 (UTC)Reply

Thanks a lot to remember about the code. I was expecting 1 script or ok, maybe few more, not 217 files and 95 folders :-DDD It will take me more time than expected but sooner or later I'll take care about it. Thanks again. --Andyrom75 (talk) 17:51, 5 December 2021 (UTC)Reply

Since you are one of the best contributor to this tool, I'd like to have your point of view on one change that has been applied here in en:voy: the conversion of each listing from, (for example) "{{see" to "{{listing | type=see".

The only benefit I see is to create potentially an endless series of listings without creating the relevant templates, because type is just a parameter, but since the set of listing is almost constant over the time, I can't get the added value that should compensate this more "verbose title".

In Wikivoyage:Listing_editor#Bugs_and_feedback I've seen your note for the "go" template, that maybe originated this new approach. I've made a test on the first listing in Cleveland#By_plane and now "go" works (I don't know if it's because of v2.4 but that's the way it is), so I would tend to restore the original behaviour.

Let me know your thoughts, --Andyrom75 (talk) 10:50, 28 July 2020 (UTC)Reply

I don't know the background behind the change from "{{see" to "{{listing | type=see", but @ARR8: made that change and might be able to provide more info. There is a discussion about it at Wikivoyage talk:Listing editor#New changes (scroll down to comments left on 5-December-2018). -- Ryan • (talk) • 04:23, 29 July 2020 (UTC)Reply

Thanks, I've just the conversation.I'm afraid that ARR8 won't jump soon into this conversation because I've noticed that he miss from en:voy since 2019 and his last edit on any wiki was march 2020 on en:w.

Maybe I'll drop a post in the pub pinging him there too to let the community decide. --Andyrom75 (talk) 06:27, 29 July 2020 (UTC)Reply

If you have some spare time, could you help to understand why the function fix99() in it:MediaWiki:Common.js recently stop working when it's called on ready or load event?

If I launch it from debugger it works correctly. A test page for example is it:Mantova. --Andyrom75 (talk) 22:40, 2 September 2020 (UTC)Reply

When I looked at it just now the function is commented out in it:MediaWiki:Common.js and not running. Can you send me the error, or whatever problem you were seeing, when it was enabled? -- Ryan • (talk) • 01:17, 3 September 2020 (UTC)Reply

I've disabled the call in MediaWiki:Common.js because all the pages like Mantova will stuck for any user without showing any error. Is like when there is an infinite loop that consume CPU &memory. 99% of the times is enough to close the browser tab.

If you want to experience that behaviour you can copy this code in your personal script page. --Andyrom75 (talk) 19:24, 3 September 2020 (UTC)Reply

@Andyrom75: Try changing the while loop so that instead of looping infinitely it just retries after a specified amount of time. I think that solves the problem in my testing. Change:

            while( typeof $(this).attr('href').split('maplink/')[1] === "undefined" ){}

... to something like:

            while ( typeof $(this).attr('href').split('maplink/')[1] === "undefined" ) {
                // maplink not yet loaded, try again in one second
                setTimeout(fix99, 1000);
                return;
            }

Please let me know if that solves the problem for you or if you still see issues. -- Ryan • (talk) • 17:48, 6 September 2020 (UTC)Reply

Solved! Thanks! :-) --Andyrom75 (talk) 19:30, 6 September 2020 (UTC)Reply

Hello Wrh2,

Really sorry for the inconvenience. This is a gentle note to request that you check your email. We sent you a message titled "The Community Insights survey is coming!". If you have questions, email [email protected].

You can see my explanation here.

MediaWiki message delivery (talk) 18:48, 25 September 2020 (UTC)Reply

Hi Ryan, for an idea that I had I'd like to have your opinion and support if possible.

In it:voy we use a quite rigid template for the phrasebooks. Inside the template there are few sections whose purpose is to translate single words (no sentences).

My idea is to create a draft of each phrasebook that currently not exist, finding those words over internet (e.g. google translator).

If you think that would be feasible and if you are interested to support I can add few more details. Let me know, --Andyrom75 (talk) 23:05, 28 September 2020 (UTC)Reply

Today I've made some tests and basically the problem I'm facing is download via script the redenred HTML of https://translate.google.com/#it%7Cen%7Cprova What I get in the variable is the structure of the page without the word "prova" and without the translated word "test" (the part that I need). I have the same problem with similar tools. Any idea? --Andyrom75 (talk) 17:12, 3 October 2020 (UTC)Reply

Are the translators reliable? I could imagine words that have more than one meaning, where the machine translating guesses at the wrong one. I suppose we should have some way to check how frequent this is before using such translations. This, of course, varies between languages, so just testing for three big languages one happens to know is not enough.

I also wonder whether this, if found reliable enough, should be done for individual words missing or for completely new phrasebooks. I think we shouldn't do it for the latter. There is too big a risk that there are some bad translations, the intro, choice if words to list (in cases where there is no sensible translation because the phrase isn't used) and explanations would be lacking, and the chance some of us will find bad translations is smaller. And if we just have machine translations, the odds are the traveller can use the same translator as needed.

If just filling gaps, the risks and the need for the traveller to resort to a translator is smaller, but on the other hand it is possible that the gaps are there because there are issues with the translation, such that somebody knowing the language only superficially did not not dare to add the word.

–LPfi (talk) 17:55, 3 October 2020 (UTC)Reply

@Andyrom75: There are likely going to be some technical challenges with parsing HTML (for example, the structure might change in the future), as well as potential licensing concerns (use of Google translate in this way may not be allowed by Google). If you are just doing this translation one-time for new articles and do not need to expose your code publicly, you are probably better off using the Google Translation API, which is free for the first 500,000 bytes and returns JSON, which is easier to parse and won't have the issue where a change in HTML structure breaks your code. The downside is that you will need to register with Google to create an API key, and you must keep that API key secure - if someone were to get a copy of it they could use it for their own purposes and potentially generate significant charges against your account. -- Ryan • (talk) • 18:47, 3 October 2020 (UTC)Reply

Ryan, my porpuse is just to create the first draft of the missing phrasebook so the interface change is not a problem. In one of my test I've created the API key, but to link the Google translate application I needed to provide my CC so I stop :-P so I come back to the initial issue of parsing an HTML page.

LPfi, I know the translation risk you are talking of, in fact I was thinking (as you described) to approach the problem in a statistical way (e.g. if 3 out of 4 different language return the same translated word, I can reasonably choose it). Let consider that any user contribute in any wiki page has a probability of being wrong, so I considered this tollerance acceptable. ...but all this castle is founded on the feasibility of this parsing.

In the meanwhile I can only test the approach in a semi-automatic way, hence to translate the set of words manually for each source language then to elaborate the results automatically to generate the draft phrasebook. Clearly I can do it for few languages but not for all :-) --Andyrom75 (talk) 19:12, 3 October 2020 (UTC)Reply

Hi. It's nice to see you here and active lately, and I hope life has treated you decently during this very difficult period. I removed the map here while blithely forgetting that it was you who just added it. Sorry for what has to be an annoying edit, but I don't think it's a great idea, as I stated in the edit summary, so let's talk about it. Ikan Kekek (talk) 00:59, 3 May 2021 (UTC)Reply

I just looked at WV:Small city article template, and maps aren't mentioned, so I checked and found this:

Item: maps; Where you can stick it: the Get around or Understand section; if there's a list of Regions, Cities or Districts place the map there Ikan Kekek (talk) 02:35, 3 May 2021 (UTC)Reply

Special:WhatLinksHere/Template:Mapgroup has the full list of pages that have had these maps added to them over the past several years if they need to be removed, although not all of them were added by me. Assuming these maps are disallowed, I'll also take down the tool used to generate the map wikitext. -- Ryan • (talk) • 20:38, 3 May 2021 (UTC)Reply

It's the first time I see a Go next map. For me it fits nicely next to the list and the routebox. In many articles there is little space there, as one wants to use it for photos. In this article there are none, but Commons has quite a few in the associated categories. I have no firm opinion on these maps, but in most cases I suppose the Get in map of the article, or of the articles on the Go next destinations, would make them redundant. –LPfi (talk) 20:52, 3 May 2021 (UTC)Reply

Maybe we should have a discussion about this somewhere. Where do you think the best place would be to do that? Wikivoyage talk:Where you can stick it? For the record, if the map didn't extend below the end of the article on my browser, I'd have less of a problem with it, but I think that's a risk in many articles. Ikan Kekek (talk) 20:59, 3 May 2021 (UTC)Reply

@Ikan Kekek: Are maps in the "Go next" section still something that should no longer be used in articles? There hasn't been any engagement on Template talk:Mapgroup, and policy debate is likely to boil down to "some people like them and some don't". Obviously I think they're extremely useful for trip planning, but I'll leave it to others to decide what to do in this particular instance. -- Ryan • (talk) • 16:37, 29 October 2022 (UTC)Reply

I am not Ikan here, but all I wanted to say is I find such maps super useful. Thank you for making this template, Wrh2 :-). SHB2000 (talk | contribs | meta) 21:29, 29 October 2022 (UTC)Reply

Nice to see you here, Ryan. The same risk of it extending beyond the end of the article still exists. I think we should discuss them somewhere and see if we can come to a consensus. Ikan Kekek (talk) 21:47, 29 October 2022 (UTC)Reply

Thank you for the quick replies. I'll continue to keep an eye on the discussion at Template talk:Mapgroup. -- Ryan • (talk) • 00:21, 30 October 2022 (UTC)Reply

Hi!

You get this message because you are an admin on a Wikimedia wiki.

When someone edits a Wikimedia wiki without being logged in today, we show their IP address. As you may already know, we will not be able to do this in the future. This is a decision by the Wikimedia Foundation Legal department, because norms and regulations for privacy online have changed.

Instead of the IP we will show a masked identity. You as an admin will still be able to access the IP. There will also be a new user right for those who need to see the full IPs of unregistered users to fight vandalism, harassment and spam without being admins. Patrollers will also see part of the IP even without this user right. We are also working on better tools to help.

If you have not seen it before, you can read more on Meta. If you want to make sure you don’t miss technical changes on the Wikimedia wikis, you can subscribe to the weekly technical newsletter.

We have two suggested ways this identity could work. We would appreciate your feedback on which way you think would work best for you and your wiki, now and in the future. You can let us know on the talk page. You can write in your language. The suggestions were posted in October and we will decide after 17 January.

Thank you. /Johan (WMF)

18:14, 4 January 2022 (UTC)

Hello there, and cc:@Tmv,

I am thrilled to inform you that Dead_link extension is requested at Japanese Wikivoyage that we'd like to apply that extension you have offered to the wider population of Wikivoyage.

As per consensus built on Wikivoyage:Village_Pump/ja since 14:59, 14 June 2023 (UTC), could we, or Wikivoyage/ja users, have Template:Dead_link implemented on Wikivoyage/ja please?

Please be reminded. It possible to change date/month order the users will be displayed for the dead_date? For localization or linguistic specifications:

• In ja language, we scribe in the order of YYYYMMDD, which Latin script adopts as DDMMYYYY.
• If yes, I will adjust the documentation page: in Template:Dead_link/doc, the lines where dates are desribed, I will change from MMYYYY to YYYYMM.

So appreciating that as we are a small group of 200+ active editors, and Dead_link extension is so valuable for us, as we are trying to catch up with the global peers by translating pages from other languages. Well, at the back of my brain, I imagine it is not in near future when you notice the bot administrating tasks for our language version hits many times. (;

Kindly ping me if I have left anything unclear, with best, --Omotecho (talk) 11:40, 25 June 2023 (UTC)Reply