Leave me a message. --Yair rand (talk)

Add this userbox to your userpage to advertise your opposition to WP:Pending Changes, and tell 10 like-minded users to do the same and vote!--Gniniv (talk) 07:28, 1 September 2010 (UTC)Reply[reply]

This user is against the implementation of flagged revisions in the form of pending changes.

I saw your response to the current Pending changes/Straw poll and thought you might find it interesting to join the Anonymous User Protection Squad (AUPS)‎. Thanks, Maysara (talk) 02:43, 3 September 2010 (UTC)Reply[reply]

Hi. As you recently commented in the straw poll regarding the ongoing usage and trial of Pending changes, this is to notify you that there is an interim straw poll with regard to keeping the tool switched on or switching it off while improvements are worked on and due for release on November 9, 2010. This new poll is only in regard to this issue and sets no precedent for any future usage. Your input on this issue is greatly appreciated. Off2riorob (talk) 23:54, 20 September 2010 (UTC)Reply[reply]

Hi, I reverted your edits considering etymologies, per Wikipedia:WikiProject Etymology. A Macedonian, a Greek. (talk) 12:50, 14 December 2010 (UTC)Reply[reply]

What? I don't see how Wikiproject Etymology somehow allows additions of etymology sections completely irrelevant to the topic of the article. Could you please explain? --Yair rand (talk) 21:50, 14 December 2010 (UTC)Reply[reply]

I'm sorry but I don't understand... how can etymology of the article title be irrelevant to the topic of the article?? A Macedonian, a Greek. (talk) 21:58, 14 December 2010 (UTC)Reply[reply]

The article title itself is irrelevant to the topic of the article. The article title is the English word that represents the topic of the article. On Wiktionary, pages deal with words, and thus give etymologies, pronunciation, etc. on those pages. On Wikipedia, articles deal with the actual concepts/things that the word represents. This distinction is pretty important. (On Wiktionary, my home project, the distinction is really important :). ) Furthermore, the etymology sections specifically dealt with the English word, ignoring all the other thousands of words in other languages that equally represent the concept, which is basically giving an English-speaking point of view. I know you've spent quite a lot of time on these etymologies, but they are really out of the scope of the articles and the project at large. Most of them should be simply deleted, and those that aren't redundant to Wiktionary's content should be transwikied. --Yair rand (talk) 22:06, 14 December 2010 (UTC)Reply[reply]

On the contrary, Wikipedia:WikiProject Etymology states: The scope of this project includes articles about etymology itself and related topics (e.g. etymology, loanword), articles about the origins of particular words (e.g. List of U.S. state name etymologies, names of the Greeks), and etymology sections within articles on other topics (e.g. Ginkgo biloba#Etymology)... A Macedonian, a Greek. (talk) 22:19, 14 December 2010 (UTC)Reply[reply]

Wikipedia:WikiProject Etymology is not policy. Certain articles may have a name or a word as their subject, or have information related to the name that is distinctly notable, and information about the words themselves could be in the article. Most articles are not about names or words. Leaving aside for a second the issue of whether information about words of languages that represent the relevant topic are closely related enough and notable to be included, I don't see how etymologies can be in articles. Assuming that the etymologies wouldn't put forward an Anglo-centric viewpoint by excluding any information related to non-English words that represent the subject of the article, the etymology simply wouldn't fit. After a few dozen languages, the section would be larger than the entire rest of the article, and would have to be split off into something like "Etymology of (subject)", which clearly isn't something that is needed on Wikipedia for every single word. In addition, there is no real benefit of duplicating massive amounts of Wiktionary content for every word that has an article on a project which doesn't have a lexicographic focus. Do you disagree with any of these points individually? Perhaps the issue should be taken to the Village Pump? --Yair rand (talk) 23:19, 14 December 2010 (UTC)Reply[reply]

I think better to take it to Wikipedia:WikiProject Etymology talk-page and see the opinion of project's members. A Macedonian, a Greek. (talk) 07:38, 15 December 2010 (UTC)Reply[reply]

Sure. Taken to Wikipedia talk:WikiProject Etymology#Etymologies not related to article subject. --Yair rand (talk) 06:28, 16 December 2010 (UTC)Reply[reply]

Apologies, my fingers are too fat for my iPhone! I've reverted myself. Stephen 10:01, 31 January 2011 (UTC)Reply[reply]

With all due respect, I will refer to Wikipedia however I see fit depending on context. "Wiki" is as much acceptable shorthand as "US" for the country inbetween Canada and Mexico. doktorb _words^deeds 19:04, 7 February 2011 (UTC)Reply[reply]

Because I have noticed you commenting at the current RfC regarding Pending Changes, I wanted to invite you to the IRC channel for pending changes. If you are not customarily logged into the IRC, use this link. This under used resource can allow real time discussion at this particularly timely venture of the trial known as Pending Changes. Even if nothing can come from debating points there, at least this invitation is delivered with the best of intentions and good faith expectations. Kind regards. My76Strat 08:45, 2 March 2011 (UTC)Reply[reply]

Hello, Yair rand. You have new messages at Jorm (WMF)'s talk page.
You can remove this notice at any time by removing the ((Talkback)) or ((Tb)) template.

Replied there.--Jorm (WMF) (talk) 01:28, 6 May 2011 (UTC)Reply[reply]

Hello, Yair rand. You have new messages at User talk:Yair rand/interwikiwatchlist.js.
You can remove this notice at any time by removing the ((Talkback)) or ((Tb)) template.

--Timeshifter (talk) 10:53, 20 May 2011 (UTC)Reply[reply]

I really appreciate the thought behind the comment you made about the Sticky notes idea. Those are exactly the kind of issues I do not know enough to bring up! That is also the sort of stuff that would need to be discussed to get this idea ready for the proposal page of the idea lab. So, thanks for that.-Tesseract²(talk) 19:45, 27 July 2011 (UTC)Reply[reply]

Template:Wikisaurus has been nominated for deletion. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. The Evil IP address (talk) 10:56, 19 August 2011 (UTC)Reply[reply]

Why did you remove the Handster Inc. acquisition section from Opera Software wikipage.

http://en.wikipedia.org/w/index.php?title=Opera_Software&diff=453842949&oldid=451487063

What sort of copyright violation was that? — Preceding unsigned comment added by Swapnil99pro (talk • contribs) 15:24, 27 October 2011 (UTC)Reply[reply]

That text was copied directly from http://www.opera.com/press/releases/2011/09/19/ , which says at the bottom "Copyright © 2011 Opera Software ASA. All rights reserved.". --Yair rand (talk) 15:28, 27 October 2011 (UTC)Reply[reply]

Nice work on the Reference Tooltips script. I have one suggestion. It would be nice if the pop-up had a slight delay so that rapidly moving the cursor across a reference didn't trigger it. Kaldari (talk) 00:36, 7 December 2011 (UTC)Reply[reply]

Oops sorry about the million milliseconds :) I was testing something and forgot to change it back. Kaldari (talk) 00:49, 7 December 2011 (UTC)Reply[reply]

Regarding the namespace, I was just trying to cut down js bloat for other pages. I've added the Project namespace as well. Are references ever used in other namespaces besides those? Kaldari (talk) 00:52, 7 December 2011 (UTC)Reply[reply]

In the Help namespace occasionally, I think. --Yair rand (talk) 00:55, 7 December 2011 (UTC)Reply[reply]

Is there any documentation on how to use it on another wiki? Is it the one used for example here --Spiros71 (talk) 21:58, 12 December 2011 (UTC)Reply[reply]

No, it is not. By using it on another wiki, do you mean for one user to use it, or for it to be enabled for the entire wiki? If the former, one could just add importScriptURI("//en.wikipedia.org/w/index.php?title=User:Yair_rand/ReferenceTooltips.js&action=raw&ctype=text/javascript");importStylesheetURI("//en.wikipedia.org/w/index.php?action=raw&ctype=text/css&title=User%3AYair_rand%2FReferenceTooltips.css"); to their common.js on that wiki. --Yair rand (talk) 00:25, 13 December 2011 (UTC)Reply[reply]

Hey, if you want help pushing this forward, let me know. It's of interest to us as part of our list of potential experiments here at the WMF (it might eventually be a good tool for prompting people take some kind of action to improve the reference). Steven Walling (WMF) • talk 22:29, 2 April 2012 (UTC)Reply[reply]

Hey,

I've noticed that you have removed a number of political cartoons from articles relating to the Arab Spring, but I didn't see an explanation in the edit summary. So I'm writing here to ask you for the reason of removing them. (if this have been discussed, please redirect me to the discussion) Bahraini Activist ^{Talk to me} 09:51, 17 February 2012 (UTC)Reply[reply]

I thought this was a pretty clear situation. Political cartoons, by their very nature, characterize events and issues in certain ways, and are thus non-neutral explanations of events. Wikipedia strives to provide a completely neutral point of view in articles. We can explain points of views in articles (X holds this view of these events, Y holds this view), but we can't have it as though the article itself has that view. Thus, there are only two ways that I can think of that would make the political cartoons acceptable to have in the article:

• If the specific cartoon is a major element of the protest itself then the article could describe how it was used. It would probably be better to have a photo of it actually in use in that case, though. If that's not possible, then the caption should explain exactly how the cartoon was used, and how the cartoon is a notable element of the event.
• If a section of the article describes certain views of the events, then it might make sense to include a well-known political cartoon in that section to help readers understand a certain popular viewpoint. In that case, the surrounding text should be also about views, and again, the caption should explain the cartoon and how it is relevant. (In this particular case, it would probably also be useful to get an image conveying an opposing viewpoint; perhaps a piece of government propaganda, if one is available, with surrounding text explaining how the event is being characterized by opposition to the protests.)

As far as I can tell, the political cartoons I removed did not fit either of these situations, and was displayed as though the cartoons were the article's representation of those events. Do you disagree with these points? If so, we should probably bring this to the article's talk page (if you disagree on how the cartoons were being used in the article) or perhaps a more general discussion page (if you disagree with the general principle that political cartoons are non-neutral representations of topics). --Yair rand (talk) 15:25, 19 February 2012 (UTC)Reply[reply]

I just remembered about this just now. I guess I understand the reason for removing. But what about this cartoon? Also, some cartoons were used in protests, how would you suggest adding them? Mohamed CJ ^(talk) 04:50, 13 March 2012 (UTC)Reply[reply]

For cartoons that were used in the protests, we could have photographs of people using the cartoons in protests. That would immediately supply the reader with much of the relevant information/context. (Sorry, I'm not completely sure what you're asking.) I'm not aware of how the cartoon File:Ali_Jawad_al-Sheikh_by_Ahmad_Nady.jpg is particularly significant, or what role it played, so I don't know about that. (There is an actual photograph of Ali Jawad al-Sheikh available.) --Yair rand (talk) 01:43, 14 March 2012 (UTC)Reply[reply]

I love your reference tooltips script; however, I have noticed that when hovering over a reference a tooltip does not always appear. It seems to happen near the bottom of articles, so perhaps it's a bug in the code that detects whether the intended reference is already visible or not and decides whether to display a tooltip or highlight the existing ref? It might make sense to make a tooltip show even if the intended reference is visible. Thanks! —danhash (talk) 18:28, 4 April 2012 (UTC)Reply[reply]

When the reference footnote is already visible on the screen, it's supposed to just add a border around the footnote. Is this not working correctly? --Yair rand (talk) 18:32, 4 April 2012 (UTC)Reply[reply]

No. What I suspect is happening is that there's a bug in the footnote detection code and that the border is being added around the footnote but I can't see it since it isn't on the screen. My window is often not maximized, if that makes a difference. —danhash (talk) 18:46, 4 April 2012 (UTC)Reply[reply]

Is it fixed now? --Yair rand (talk) 19:02, 4 April 2012 (UTC)Reply[reply]

Yes. Thank you! —danhash (talk) 19:13, 4 April 2012 (UTC)Reply[reply]

Great. Thank you for telling me about the bug. :) --Yair rand (talk) 19:16, 4 April 2012 (UTC)Reply[reply]

Shalom. I'm wondering if you could have reference tooltips check for a variable set by popups, and if detected, disable itself. I'm assuming yours will get loaded after popups. If not, maybe the popups author could also insert code to check for a variable set in reference tooltips, and disable them if detected. What do you think? Equazcion ^(talk) 11:55, 19 Apr 2012 (UTC)

I added window.pg || to the beginning of the script, which should work, assuming that popups loads before Reference Tooltips. I still need to wait for an admin to synchronize the page in the Mediawiki namespace with the page in my userspace. --Yair rand (talk) 21:50, 19 April 2012 (UTC)Reply[reply]

so i just saw your reference tooltip tool. please compare with he:Mediawiki:Gadget-CiteTooltip.js. my tool use tipsy, which is a jquery extension to do tooltips. currently, tipsy lacks the syntax "please stay on while mouse hovers over tooltip", so it's a little bit more tricky to click a link in the reference. hopefully, sooner or later we'll take over tipsy, and then it's a very simple matter to add this syntax.

peace, קיפודנחש (talk) 21:03, 19 April 2012 (UTC)Reply[reply]

added later: just saw the discussion in village pump, and these people are correct about the fact that gadget popup makes reftooltip redundant, and together they can be annoying. i suggest you add at the first line of the function show(), the following line or something similar:

if (mw.user.options.get('gadget-Navigation_popups')) return;

please note that if you want to handle it differently, e.g. to skip the initialization if popup is enabled, you can't just use this, because the "user" object is not guaranteed to be initialized as soon as the page loads. in this case, you want to add dependency in "mediawiki.user" to the gadget-definitions page.

peace - קיפודנחש (talk) 21:40, 19 April 2012 (UTC)Reply[reply]

I added window.pg || to the beginning of the script, which should work, assuming that popups loads before Reference Tooltips. I still need to wait for an admin to synchronize the page in the Mediawiki namespace with the page in my userspace. --Yair rand (talk) 21:50, 19 April 2012 (UTC)Reply[reply]

The code suggested above would seem to work whether or not popups loads first, so wouldn't that be better? Equazcion ^(talk) 22:06, 19 Apr 2012 (UTC)

Seems like a bit of a waste. The script would go through all the processes of attaching all the events and creating the tooltip whenever one hovers over a reference, and just not display them. I think (though I'm not completely sure about this) that gadgets are reliably loaded in the order they're listed in the gadgets list, so it's not really an issue. If this isn't correct, than yeah, I'll need to use קיפודנחש's method. --Yair rand (talk) 22:24, 19 April 2012 (UTC)Reply[reply]

Couldn't you add if (mw.user.options.get('gadget-Navigation_popups')) to the very beginning of the script then, before any of that stuff is done? It just seems more reliable than assuming the script load order will stay the same, that's all. Equazcion ^(talk) 22:30, 19 Apr 2012 (UTC)

As קיפודנחש mentioned, the mw.user object is not guaranteed to be initialized as soon as the page loads, so no, not unless the script is specifically delayed to not run until after that point, which I'd rather not do. (Another option, by the way, would be to simply add .referencetooltips{display:none;} to MediaWiki:Gadget-navpop.css, popups' CSS file.) --Yair rand (talk) 22:40, 19 April 2012 (UTC)Reply[reply]

I've requested this at Wikipedia_talk:Tools/Navigation_popups#Disable_a_conflicting_gadget. Equazcion ^(talk) 23:17, 19 Apr 2012 (UTC)

no, no, no - if you want to prevent initialization if navpop is used, you do not have to modify navpop itself - all is required is to edit Mediawiki:Gadgets-definition and change

• ReferenceTooltips|ReferenceTooltips.js|ReferenceTooltips.css

to

• ReferenceTooltips|[ResourceLoader|dependencies=mediawiki.user]|ReferenceTooltips.js|ReferenceTooltips.css

this way, it's guaranteed that the user object is ready by the time your code is run. this code does not care which gadget loads first - it just looks at the setup and sees whether or not popup is *configured* to run. personally, i wouldn't be so worried about "efficiency" as you seem to be. this code runs on the user's browser, not on the server, and normally it takes microseconds (or in the worst case miliseconds, if the user has a very old system) to complete, so IMO it should be good enough just to suppress the popups themselves, through the "show" function. if you are worried about performance, the real optimization would be to *generate* the content of the popup from within the "show", rather than creating all of them at load time (and it shouldn't be that difficult - again, look at my code in hewiki). peace - קיפודנחש (talk) 00:00, 20 April 2012 (UTC)Reply[reply]

The content of the tooltip is not generated at load time, it's generated per-reference when the user hovers over the reference link the first time, just before show() is called. I suppose that the check for whether popups is loaded could occur on activation of the hover, though that would still have all the events attached to the reference links by that point (2 milliseconds or so of waste). (By the way, your estimates of the time it takes JS to create a bunch of DOM is off by a lot; the tooltip takes 2-5 milliseconds to create on Chrome on Windows 7 by my tests.) --Yair rand (talk) 00:28, 20 April 2012 (UTC)Reply[reply]

you are correct, of course, but on the UI level, 5, 10 and even 150 milliseconds are not crucial. personally, unless performance is really atrocious, i go with code clarity and brevity every time. again, if you add the dependency on "mediawiki.user" in the MediaWiki:Gadgets-definition, you can then examine mw.user.options.get('gadget-Navigation_popups') at the very first line of your script, and the result is guaranteed to be correct. peace - קיפודנחש (talk) 16:09, 21 April 2012 (UTC)Reply[reply]

Sorry about that. The edit was an accident. I was testing code at User:Kaldari/ReferenceTooltips.js and accidentally edited the wrong page. My apologies. Kaldari (talk) 08:16, 26 April 2012 (UTC)Reply[reply]

Regarding the delay feature in general, I've been using ReferenceTooltips ever since it was proposed as a gadget, and I think it is a much needed (and well-implemented) feature. The only problem I've had with it, is that I commonly accidentally mouse over a ref and then leave the cursor sitting in the resulting pop-up, thus obscuring the text. Your comment on my talk page suggests that you view the accidental triggering as a feature rather than a bug (i.e. otherwise newbies won't discover it), however, given the prominence of tooltips on the web these days (almost all of which are delayed) I think you might be surprised at how many newbies actually would try hovering over the refs. Perhaps a very short delay could be implemented such as 300 or 200 milliseconds. The Hebrew Wikipedia uses 300 for their reference tooltips. Kaldari (talk) 08:28, 26 April 2012 (UTC)Reply[reply]

I suspect that many of our users aren't actually even familiar with the concept of "hovering" to get something at all. Not all that many of our readers are technically literate. Of those that are, I don't think many would try it. Given that the Reference Tooltips idea has never come up in discussion before afaik, I think it would be a reasonable assumption that even our core community never had the immediate idea "maybe hovering over these little links will do something?". Thus, if it doesn't get at some point accidentally activated, it's not going to be useful. It will probably result in a bit of annoyance for some users, but since it goes away as soon as one's cursor is no longer in that little spot, I think the annoyance will be very mild. (The accidental light flicker of reference content might actually be helpful even for users that know about the tool, if something there were to catch someone's eye resulting in them being suddenly interested in the reference, but that's a minor point.) So I suppose the accidental triggering is a mixed bug/feature, where the benefits of the feature outweigh the bug aspects enough that it makes sense to keep it, at least in my opinion. --Yair rand (talk) 08:47, 26 April 2012 (UTC)Reply[reply]

A delay of 300 milliseconds isn't much, if any, of a "hover". It's less than a third of a second, and will "accidentally" happen anyway to those who don't realize the feature might exist. The delay would, though, allow those who are aware of it enough of a buffer to control when they see them. Thus I think the delay is a good idea, and might help gain a stronger consensus for implementation. Equazcion ^(talk) 14:05, 26 Apr 2012 (UTC)

FWIW, in hewiki we use a similar (homegrown) gadget that uses jquery.tipsy as backend to show the tooltips, and we *do* use 300 ms delayIn (as mentioned above, this is almost "industry standard" for tooltips). we also use "fade" for the tooltips. the way tipsy implements it is not 100% trivial, and you might be interested to scan the code if you want to get some ideas (you can't just start a timer naively - you want to verify at the end of the timeslice that the mouse is still above the control). you can read tipsy code to see how it does it here: https://github.com/jaz303/tipsy/blob/master/src/javascripts/jquery.tipsy.js

peace - קיפודנחש (talk) 23:18, 26 April 2012 (UTC)Reply[reply]

Yes, delays on tooltip-style pop-ups are pretty standard, although there doesn't seem to be a standard for the delay time. Google Maps has a delay of about 200 milliseconds, while gMail is a full second. If referenceTooltips didn't have a hide delay, the show delay wouldn't be that important. But delaying hiding without delaying showing is especially annoying. Kaldari (talk) 22:30, 27 April 2012 (UTC)Reply[reply]

Look like Cite has tooltips in development.[1] (Search for tooltips and popups). No clue if this works or when it would go live. ---— Gadget850 (Ed) ^talk 15:59, 4 May 2012 (UTC)Reply[reply]

Hello. You have a new message at Accedie's talk page. Accedie^{talk to me} 22:51, 22 May 2012 (UTC)Reply[reply]

Great work on improving ReferenceTooltips. It seems really solid now. I made a small code tweak to the test version to reduce the footprint a little and insure future compatibility with our jQuery UI skin: http://en.wikipedia.org/w/index.php?title=User%3AYair_rand%2FReferenceTooltips.js&diff=500739549&oldid=500406057

(The button() function is what normally adds all of those css classes and the internal span, so there's no need to do it manually.)

I'm not sure what's going on with Cite.php currently, but I'd still love to see this turned on by default (especially now that it has a configuration interface). Kaldari (talk) 02:47, 5 July 2012 (UTC)Reply[reply]

I'm getting SyntaxErrors from that, so reverted for now. By the way, are you sure that jquery.ui.button is always available when jquery.ui.dialog has been loaded? (Or is it always available, maybe?) Is there a list of dependencies and defaults and such for these things anywhere? If ui.button can be depended upon, then the change makes sense.

Re RT on by default: I'm still much more in favor of it being community handled than having it as a non-community-editable extension. I'm hoping it will be enabled as a gadget soon. Relevant discussion: WP:VPM#ReferenceTooltips. --Yair rand (talk) 03:06, 5 July 2012 (UTC)Reply[reply]

Ah, it was an extra ) that was the issue. --Yair rand (talk) 03:09, 5 July 2012 (UTC)Reply[reply]

jquery.ui.button is always available (since about mediawiki 1.19 I think). Sorry for my sloppy coding :) You'll probably also want to do a blur() on the disable button at the end of openSettingsMenu(), since jQuery UI likes to activate the first dialog form element by default (which is usually OK since it's almost never a button). Kaldari (talk) 03:13, 5 July 2012 (UTC)Reply[reply]

Blurring the button seems to kill tab navigation (or whatever that's called), so I'm leaving that out for now. I re-added your edit, minus the extra ). Thanks. :) --Yair rand (talk) 03:30, 5 July 2012 (UTC)Reply[reply]

So is ReferenceTooltips getting enabled by default? David1217 ^{What I've done} 04:48, 6 July 2012 (UTC)Reply[reply]

I guess that probably depends on the result of the discussion in VPM. Enabling a gadget by default can only be done by an admin, and I don't have admin rights on this wiki, and it probably wouldn't be appropriate for me to decide the result of a discussion I started anyway. --Yair rand (talk) 05:14, 6 July 2012 (UTC)Reply[reply]

	The Technical Barnstar
	For your fine work and persistence with Reference Tooltips, a great way to enhance Wikipedia for editors and readers alike. Steven Walling (WMF) • talk 01:37, 17 July 2012 (UTC)Reply[reply]

Thanks! :) --Yair rand (talk) 01:44, 17 July 2012 (UTC)Reply[reply]

Hi! I'm contacting you because you have participated or discussed The Wikipedia Adventure learning tutorial/game idea. I think you should know about a current Community Fellowship proposal to create the game with some Wikimedia Foundation support. Your feedback on the proposal would be very much appreciated. I should note that the feedback is for the proposal, not the proposer, and even if the Fellowship goes forward it might be undertaken by presently not-mentioned editors. Thanks again for your consideration.

Proposal: http://meta.wikimedia.org/wiki/Wikimedia_Fellowships/Project_Ideas/The_Wikipedia_Adventure

Cheers, User:Ocaasi 16:42, 27 July 2012 (UTC)Reply[reply]

Hello,

You may be interested in this discussion about the reference bubble.

Cheers,

--Nnemo (talk) 18:26, 6 August 2012 (UTC)Reply[reply]

The problem that this user is reporting is that when a citation is near the top of a page, the tooltip isn't visible (it goes off the top). That is something that should be fixed, if you have time. David1217 ^{What I've done} 22:12, 8 August 2012 (UTC)Reply[reply]

Not only the top of the page. My ref link was at the top of the view. Look at the screen photo. --Nnemo (talk) 07:14, 9 August 2012 (UTC)Reply[reply]

Sorry for taking so long to get to this. I've been mostly without internet access for the past week.

So my personal opinion on this is that the tooltip should only be below the citation when otherwise there would be content that would be completely inaccessible, not when the user would just have to scroll up a bit to see it. I think general consistency of direction and clear visibility of content after the citation are more important than making it so the user doesn't have to scroll a bit to see the reference content. However, it looks like my view is the minority.

One complication in making the change: I'm not sure how often the script should check if all of the reference content is on-screen, to see if it should flip it. If a user is reading through a reference's content and scrolls enough that part of the reference is off-screen, it would be annoying if the tooltip instantly jerked out of the way so that it's below the citation, causing the reader to lose their place. I think it also wouldn't be best for it to check only once, and ignore whether it's entirely visible any later time. Maybe it should only check every time it goes from not visible at all to visible? --Yair rand (talk) 19:05, 9 August 2012 (UTC)Reply[reply]

Don't be sorry. :-)

I had not thought about keeping part of the main text visible. The part that may be hidden by the ref bubble. But I think this point gives another good reason to my proposal. It is more important to keep the text before the ref link visible than the text after the ref link. So it is better to hatch the ref bubble downwards rather than upwards, even in the general case. Why ? We have this :

Some lines of text about apples. Bla bla bla bla bla. Apples apples apples apples apples apples apples apples apples apples apples apples apples apples apples apples apples apples apples apples apples apples apples apples apples apples apples apples apples apples apples apples. Apples apples apples apples apples apples apples apples apples apples apples apples apples apples apples apples apples apples apples apples apples. [1] Some lines of text about bananas. Bla bla bla bla bla. Bananas bananas bananas bananas bananas bananas bananas bananas bananas bananas bananas bananas bananas bananas. Bananas bananas bananas bananas bananas bananas bananas bananas bananas bananas bananas bananas bananas bananas bananas bananas bananas bananas bananas bananas bananas bananas bananas bananas bananas bananas.

The ref [1] is about apples. So let's make it hide the bananas, not the apples.

This is the general case. But, if the ref bubble comes below the view, then put it in the view, so that the user does not have to scroll : in this special case, hatch the bubble upwards, or rightwards if there is room…

Having the bubble jumping here and there would be annoying. I think the best way to handle this is this one : as soon as you put the bubble on screen, don't move it.

Thank you !

--Nnemo (talk) 08:07, 10 August 2012 (UTC)Reply[reply]

Okay, so I've made the change at User:Yair rand/ReferenceTooltips.js, but I'm going to hold off on requesting it be deployed across the whole site until I've done enough testing to be pretty sure the change didn't introduce any new bugs. If you'd like to participate in testing the modified version of ReferenceTooltips, you could disable the currently in use version by unchecking ReferenceTooltips at Special:Preferences#mw-prefsection-gadgets and then turn on the modified version by adding importScript("User:Yair rand/ReferenceTooltips.js");importStylesheet("User:Yair rand/ReferenceTooltips.css"); to Special:Mypage/common.js. --Yair rand (talk) 02:01, 13 August 2012 (UTC)Reply[reply]

Thank you. One little thing to change : instead of writing "<br>" and "<hr>" : the correct forms are "<br/>" and "<hr/>". --Nnemo (talk) 10:09, 13 August 2012 (UTC)Reply[reply]

Huh, I didn't know that $.fn.append actually built the DOM straight from the string. I figured it used the /^<(\w+)\s*\/?>(?:<\/\1>|)$/ regexp and then built simple elements through createElement, like jQuery does when one just puts $("<tag>"). I've changed the instances of "<br>" and "<hr>" to $("<br>") and $("<hr>") which, besides for fixing the invalid XHTML, will probably make it faster, I think. Thanks. --Yair rand (talk) 04:03, 14 August 2012 (UTC)Reply[reply]

FYI. I have closed the discussion at Wikipedia:Village pump (proposals)#Simplified_move_proposal_process, noting near unanimous support for this proposal, but also possible need for further testing. --BrownHairedGirl (talk) • (contribs) 18:01, 18 September 2012 (UTC)Reply[reply]

Has there been any followup to your comment on Jimbo Wales' talk page and your proposal? As per David1217's comment in that discussion "Did the script actually work when someone tried it? Because when I tried it, it didn't do anything..." (see diff), I copied your javascript to User:Wbm1058/ControversialMoves.js and that did not seem to have an effect. Is there a way for me to test it in my own account—if so, how do I do that?

Oh, I see. Your followup message at Wikipedia:Gadget/proposals heard only chirping crickets. I'd like to help you test if that's possible. Have you been able to test your script yourself? Thanks, Wbm1058 (talk) 14:30, 2 August 2013 (UTC)Reply[reply]

@Wbm1058: You can test the script by adding the line importScript("User:Yair rand/ControversialMoves.js"); to User:Wbm1058/common.js.

I've only done the most basic testing on it, and only on one browser. It's a fairly simple script, though, so there probably won't be all that many bugs to deal with.

In retrospect, I probably should have linked to the gadget proposal from VPR or something. --Yair rand (talk) 15:30, 4 August 2013 (UTC)Reply[reply]

Cool! I wonder why that didn't work for David1217. Does it make any difference whether "User:Yair rand/ControversialMoves.js" is enclosed in single quotes or double quotes?

I used it to make this edit. Notice that it copied all of the templates from the top of the talk page, and signed the edit twice, which it shouldn't have. My browser is Google Chrome. Wbm1058 (talk) 22:34, 4 August 2013 (UTC)Reply[reply]

Note that, after you wrote your script, I modified ((requested move)) to auto-sign, so your script doesn't need to sign anymore. Wbm1058 (talk) 22:43, 4 August 2013 (UTC)Reply[reply]

Thanks, I removed the extra autosigning from the script. It doesn't make any difference whether the "User:Yair rand/ControversialMoves.js" is enclosed in double or single quotes. I don't know what's with the duplication of all the templates at the top; I suspect it's probably a backend issue. I've filed Bug 52538 on Bugzilla. --Yair rand (talk) 01:24, 5 August 2013 (UTC)Reply[reply]

Hey, it appears that they fixed the bug, and the new version with the patch will be fully deployed on Thursday, August 22, 2013. I'll resume testing after that. Wbm1058 (talk) 11:23, 7 August 2013 (UTC)Reply[reply]

The issue you filed Bug 52538 on seems fixed, per the test I just ran. But I found another issue. The reason I entered in the "Move page" reason box wasn't transferred to the Template:Requested move reason parameter. Best to use the named parameter to avoid Bug 14235, as the template documentation explains. And a favor to ask. Can you change it to create a section header in the format Requested move 25 February 2024, as Template:RMtalk does by default? This ensures that the section header will be unique in the event multiple move requests are made on the same page.

On a related but different matter: I was wondering if you could use your tech wizardry skills to solve the issue discussed here. Consensus seems to want to leave behind, for example,

#REDIRECT [[Le Réveil de Flore]] ((R from move)) rather than just

#REDIRECT [[Le Réveil de Flore]], to minimize the need for a second edit that removes the possibility of later non-admin moves over the redirect. Can you do that, or is it something that requires help from the Wikimedia Foundation? Thanks again, Wbm1058 (talk) 23:15, 12 September 2013 (UTC)Reply[reply]

Re the reason= parameter and the date in headers: Done and done.

Re the redirects text: If there's a way to do that from the wiki side, I don't know what it is. I would guess it probably requires help from the Foundation. --Yair rand (talk) 15:49, 15 September 2013 (UTC)Reply[reply]

Super! Looks good. The edit summary says "‎(→‎Requested move ((subst:#time: d F Y | ((subst:CURRENTTIMESTAMP)) )): new section)" which is OK, but maybe you could change it to say something like (Requested move auto-submitted from Special:MovePage) so we can better track usage. And a minor issue – there are two blank lines between the section header and the Requested move/dated template, if you can remove one of them that would be nice. I'll announce your move proposal solution at Wikipedia talk:Requested moves to give it more exposure and solicit more testing and feedback. – Wbm1058 (talk) 16:00, 18 September 2013 (UTC)Reply[reply]

Hi, is there any reason why the tooltips are not loaded trough resourceloader ? I'm asking because currently this is a default gadget, and because it's not Resourceloader enabled in the gadgets definition, it requires an extra request for every user to the server. If added to resourceloader, it will be compacted into the same request as most of the other gadgets and user specific javascript. I think that would be beneficial. —TheDJ (talk • contribs) 14:59, 7 October 2012 (UTC)Reply[reply]

ReferenceTooltips needs to be loaded after NavigationPopups if both gadgets are enabled in order to avoid conflicts, and NP is not loaded through ResourceLoader. I notice that HotCat, which is loaded through ResourceLoader, is loaded earlier than RT, despite being listed later in the gadget list, so I assume that if RT was loaded through RL, and NavPopups wasn't, then RT would be loaded before NavPopups, causing problems. --Yair rand (talk) 12:27, 14 October 2012 (UTC)Reply[reply]

as an alternative to the way you do it now (testing for "window.pg"), you can test for mw.user.options.get('gadget-Navigation_popups'). this will require adding a dependency in gadgets-definition (mediawiki.user), but once you do add the dependency and change the testing for navpop, you can use resourceloader.

theoretically this will mess up users who load navpop not through the gadgets mechanism (e.g., directly through their common.js or something), but in practice you should not be concerned about these cases.

if you choose to do it this way, remember to add this dependency as a comment.

peace - קיפודנחש (talk) —Preceding undated comment added 16:04, 18 October 2012 (UTC)Reply[reply]

Thanks for replying at User talk:Yair rand/ReferenceTooltips. I have no experience filing bug reports at Bugzilla, but I'd be happy to file one if that's what it takes. I'm not sure I would file it correctly though. The issue at village pump technical isn't getting much discussion.[2] And in June, I submitted a comment, which was escalated to a Bugzilla report, and for months has gone unresolved. Perhaps that is on purpose. The last comment on Bugzilla was made in September. Is sort of thing common? Is it WMF responsibility to make bug fixes? Sorry to unload on you with questions, but I'm trying to figure this place out a little bit. Thanks. Biosthmors (talk) 17:55, 15 October 2012 (UTC)Reply[reply]

It should probably be filed under Mediawiki extensions > MobileFrontend. It is, unfortunately, rather common for bugs to go unresolved for months or even years. The WMF can only afford to hire so many developers, and the volunteer developer community isn't generally able to handle everything that comes in either. However, I think something as severe as the mobile site actually crashing every time an Android user clicks on a citation is likely to be dealt with much faster than the average bug. --Yair rand (talk) 20:36, 15 October 2012 (UTC)Reply[reply]

Interesting. Could you perhaps link me to some relevant commentary/analysis on WMF funding and where people think it should go in relation to this development backlog? Thanks. Biosthmors (talk) 22:56, 15 October 2012 (UTC)Reply[reply]

Sorry, I have no idea where I would find stuff on that topic. Maybe on Meta. --Yair rand (talk) 23:08, 15 October 2012 (UTC)Reply[reply]

No problem, and thanks again. Happy editing. Biosthmors (talk) 23:19, 15 October 2012 (UTC)Reply[reply]

The labs instance we're using is http://piramido.wmflabs.org/wiki/Main_Page (you have to use the full url). Steven Walling (WMF) • talk 22:49, 17 October 2012 (UTC)Reply[reply]

Thank you. I've posted the user CSS to hide the edit confirmation message on the VPT. --Yair rand (talk) 22:57, 17 October 2012 (UTC)Reply[reply]

I can't get that CSS to work at piramido. (See RecentChanges for my stab at it.) Steven Walling (WMF) • talk 23:09, 17 October 2012 (UTC)Reply[reply]

Okay, I just registered an account over there to figure out the problem. That Labs instance simply isn't loading any user styling at all. Try putting #mw-content-text::before{content:'The CSS was loaded'} in your CSS. Nothing. The source shows complete absence of the normal modules=user link element that's normally in the head. The CSS code I gave will work perfectly here on enwiki, there's just a bug in the Labs wiki. --Yair rand (talk) 00:01, 18 October 2012 (UTC)Reply[reply]

Facepalm I knew we should have checked that. Good news then. I'll update the VPT thread accordingly. Steven Walling (WMF) • talk 04:42, 18 October 2012 (UTC)Reply[reply]

If only there were a production-ish configuration for a single MediaWiki test instance instead of copying & pasting out of 14,000(!) lines of cluster setup. Anyway, I changed piramido config to $wgAllowUserJs = true. Yair rand's CSS seemed to work for me, thanks! (I also added Extension:Vector for other preferences.) -- S Page (WMF) (talk) 08:42, 18 October 2012 (UTC)Reply[reply]

There is a broken extension http://www.mediawiki.org/wiki/Extension:Tooltip that seems to be a basis for providing tooltips. I'd like to use popups in my extension as well, to display some context dependent links and very few textual information. However I don't want to reinvent the wheel. It would be nice to have the opportunity to provide some wikitext that is displayed as popup information based on the users preferences. Do you have a suggestion which is the best way to display popups from an extension? --Schubi87 (talk) 12:50, 13 November 2012 (UTC)Reply[reply]

current implementation of mediawiki includes the jQuery plugin "tipsy" as a tooltip infrastructure. to use it, you need to declare "jquery.tipsy" as a dependency (e.g. in the "resourceloader" part of the gadget, or if it is not a gadget, then wrap your script with "mw.loader.using('jquery.tipsy')". you can find some general instruction how to use tipsy here: http://onehackoranother.com/projects/jquery/tipsy .

peace - קיפודנחש (talk) 23:33, 13 November 2012 (UTC)Reply[reply]

If the point is to have links in the tooltip, tipsy might need to be extended a bit, I think. Maybe some of the ReferenceTooltips code could be reused, but it wasn't really built for that, so I don't know if that's a good idea. --Yair rand (talk) 04:30, 14 November 2012 (UTC)Reply[reply]

tipsy happily supports links (or any other html actually - lists, fonts, colors, images and all) in the tooltip. you just need to set {html: true} in the options. peace - קיפודנחש (talk) 06:09, 14 November 2012 (UTC)Reply[reply]

Yes, but it needs to be possible to click them... --Yair rand (talk) 06:25, 14 November 2012 (UTC)Reply[reply]

i 100% agree that once bugzilla:35212 is solved this will be better. in the meantime, we use "delayOut" to enable clicking (value of 1500 or so seems to be enough for most purposes). it is also possible to use {trigger: 'manual'} and deal with the on/off yourself. this is much less attractive, of course, but still much less code than you would need to implement the whole functionality (you can see an example in he:ויקיפדיה:סקריפטים/67: there are ~ 18 lines that deal with triggering tipsy because we use trigger:"manual". look for "tipsy", "mouseover", "mouseout" and "timer" to see the tipsy-related code), which would have been reduced (or "will be reduced") to 0 once bugzilla:35212 is solved. peace - קיפודנחש (talk) 14:49, 14 November 2012 (UTC)Reply[reply]

Thanks for the hit. I tried to use the navpop.js as a first solution. But it seems not to work out of the box with Special Pages. The Reference Tooltips are a good example. I'm working on a soulution to enable MathML for Mathematical Formula in Wikipedia. For debugging I want to display additional technical information on mathematical formula (e.g klick on any formula on that page). In a further step (maybe next year) I want to display something like "m: mass units kg" when hovering over the varibale m. As you can imagine my main focus is to derive the information that should be displayed rather than the techniqual process of displaying. --Schubi87 (talk) 09:26, 20 November 2012 (UTC)Reply[reply]

(after your comment in hewiki WP:VP): where can one get FF 3.6? is if for the windoze system or some other platform? do i have to uninstall FF 16 in order to install 3.6? are there enough users of 3.6 to warrant any action to solve this issue?

peace - קיפודנחש (talk) 14:17, 20 November 2012 (UTC)Reply[reply]

0.83% of all Wikipedia traffic comes from FF 3.6 users, and Hebrew Wikipedia probably gets more than most Wikipedias, based on statcounters stats. I don't know where one can get old versions of Firefox, and I don't know whether one has to uninstall the current version to install an older version. The operating system is Windows 7. --Yair rand (talk) 14:43, 20 November 2012 (UTC)Reply[reply]

i take it you have 3.6 installed. can you help debug it? i.e., can you help find where the call to empty the content of "body" is coming from? thanks, peace - קיפודנחש (talk) 16:40, 20 November 2012 (UTC)Reply[reply]

so i bit the bullet and downgraded (somewhat painful - upgrading back requires a reboot! i would not have downgraded if i knew this ahead of time). no cigar - hewiki loaded and looked just fine on ff 3.6 until further notice i'll treat this as "unreproducible". peace. קיפודנחש (talk) 00:13, 21 November 2012 (UTC)Reply[reply]

Hi there, hope you're doing well. This is just a ping about https://bugzilla.wikimedia.org/show_bug.cgi?id=50843 just in case the email I CC'd in Bugzilla is not actually you. Steven Walling (WMF) • talk 00:23, 6 July 2013 (UTC)Reply[reply]

Per "Oppose. This would result in the histories of over 1.2 billion people and nearly 30 million square kilometers not being covered by anything more specific than 'History of the world'."

That's not accurate. Take another look at the discussion comments, and also the actual list. You'll see that the point of the proposal was to reduce overlap/redundancy, not create an uncovered gap. There are already listed articles that cover History of East Asia, History of India, and History of the Middle East. GabeMc ^{(talk|contribs)} 23:31, 15 December 2013 (UTC)Reply[reply]

My comment was accurate. I was already taking those articles into account. --Yair rand (talk) 00:52, 16 December 2013 (UTC)Reply[reply]

Hello Yair! The code you provided for the redesigned NavPopups is being moved to a betafeature on this patch: https://gerrit.wikimedia.org/r/#/c/109878/. There is the question of if you are okay with licensing that code as GPLv2 or later that needs clarification - it would be wonderful if you could just respond here (or on Gerrit) saying if it is okay with you. Thanks! YuviPanda (talk) 08:33, 30 January 2014 (UTC)Reply[reply]

@Yuvipanda: Um, that was a bit unexpected. I didn't realize that it was going to be created as a beta feature that quickly. There are several bugs that I've fixed since the version that was used was made, including a pretty serious one for IE, and one that causes the box to be very misplaced in links at the beginning of a line. And there were still a few things that really needed to be added, that I'd planned to ask the designers about.

(Also, the version on Gerrit seems to have removed the watch feature? And removed the "Read more" button. And changed the display of the date text to something different than what the design document suggested. And introduced some new bugs, such as having the "tall" version not behave correctly as none of the classes relating to that are ever removed after use.)

Regarding your actual question: Yes, that license is fine. I recommend against turning this on as a beta feature without adding those bugfixes, though. --Yair rand (talk) 13:30, 30 January 2014 (UTC)Reply[reply]

Thanks! And yeah, they will be added in future patches (watchlist, read more, etc). The timestamp formatting I suggested be removed in this patch and be added as a separate library/feature, since I think we already have code that formats timestamps similarly in some other extension. And if you look closely, this entire feature is disabled by default now with a feature flag - this won't go on Betafeatures without all those issues being fixed. Thanks! YuviPanda (talk) 14:09, 30 January 2014 (UTC)Reply[reply]

I can't seem to find any reference in the electoral law changes that state the Knesset will have a fixed term (perhaps because all the focus is on raising the threshold). Could you point me to somewhere where the changes are detailed for my peace of mind (and so I can add some info to the article)? Thanks, Number 57 19:53, 11 March 2014 (UTC)Reply[reply]

@Number 57: Finding English language explanations of the electoral reform is annoyingly difficult. The best sources I've found are this article on Times of Israel and this page on the Knesset website.

Both pages seem to say that the system of votes of no confidence has been modified, such that instead of proposing that the government fall and new elections are called, the opposition proposes an alternative government (new prime minister, cabinet, and all) which, if the vote passes, takes the place of the old government without going to new elections.

I'm not all that knowledgeable about how these things work, but that does imply that the elections won't happen until the four-year Knesset term is completed, right? Is there another way for new elections to happen? --Yair rand (talk) 21:05, 11 March 2014 (UTC)Reply[reply]

Yeah, I know. The Times article (which I think I found earlier) kind of says it in a roundabout way, but I was really hoping to have a clear source that I could use to state that there were now effectively fixed term Knessets. Oh well, I might wait a couple of days to see if anything clearer appears, then just use the Times one. Thanks for looking though. Number 57 21:44, 11 March 2014 (UTC)Reply[reply]

I moved the article back to it's previous title before noting this discussion (thanks to N57 referring me to it). It's important to note that the bill does not limit the knesset's ability (via law) nor the prime ministers ability (via writ) to call early elections. All early elections have been the result of one of these. Only once was a government toppled via a motion of no confidence (The dirty trick), and never due a budget not passing. While it's possible that there will be less cases of the government calling early elections, there is no conclusive evidence; personally, I highly doubt it. Rami R 16:52, 21 March 2014 (UTC)Reply[reply]

I see. Thanks for the information, and for fixing my mistake. --Yair rand (talk) 01:34, 24 March 2014 (UTC)Reply[reply]

Thanks for correcting my mistake on Template:UKEUparties, my bad! =0) --Filastin (talk) 16:12, 22 May 2014 (UTC)Reply[reply]

Hi Yair rand, I was talking with James F earlier today, and we'd like to "extension-ify" your reference tooltips into the mw:Extension:Cite. Would you be willing to re-license your code as GPL v2 or later? See gerrit:145041. Thanks, Legoktm (talk) 19:11, 9 July 2014 (UTC)Reply[reply]

@Legoktm: A few things:

• The version at Mediawiki:Gadget-ReferenceTooltips.js/Mediawiki:Gadget-ReferenceTooltips.css is not the most recent version. User:Yair rand/ReferenceTooltips.js/User:Yair rand/ReferenceTooltips.css have several fixes (including dealing with nested refs) that I haven't gotten around to doing an editprotected request for.
• IIRC, certain wiki(s) have discussed whether to enable this gadget and decided not to, so turning this on by default everywhere might upset certain communities.
• I personally do not know how to use Gerrit, so extensionifying RT would make me unable to continue helping with it.
• There is an open bug about how the gear icon used by RT doesn't match with those used by ULS and Echo. If RT is made into an extension, I recommend changing the image.
• I just changed the JS to use mw.msg in order to have easier localization, and I've added a comment at the top of the script and CSS licensing it "under GPLv2+, CC-BY-SA 3.0, GFDL, and anything else the WMF might find useful". That okay for dealing with the licensing issues?

--Yair rand (talk) 02:50, 10 July 2014 (UTC)Reply[reply]

i claim modest credit for suggesting to use RT in the extension (see Bugzilla:67282#c1) :)

this is not why i butted in here: the reason is a small suggestion: when dealing with licences, i found the most permissive to be the most convenient, i.e., public domain/PD license. you might consider to use this one, and squash all such future inquiries.

btw - love your script. more powerful and nicer than the stub-like thing we use in hewiki, which depends on tipsy, and which i wrote (see he:Mediawiki:Gadget-CiteTooltip.js). maybe one of these days i'll translate your script and migrate it to hewiki. of course, if it'll be sucked into the extension, i won't have to.

peace - קיפודנחש (aka kipod) (talk) 18:19, 10 July 2014 (UTC)Reply[reply]

An editor has asked for a discussion to address the redirect Rights Alliance. Since you had some involvement with the Rights Alliance redirect, you might want to participate in the redirect discussion if you have not already done so. Avono (talk) 18:45, 22 December 2014 (UTC)Reply[reply]

Hi Yair, have a question, could you please contact me? calidrago [at] gmail.com Calidrago (talk) 08:10, 9 September 2015 (UTC)Reply[reply]

@Calidrago: A question regarding what? If it's about something on Wikipedia, I'd prefer to use a talk page. --Yair rand (talk) 08:24, 9 September 2015 (UTC)Reply[reply]

Not something on Wikipedia, but rather a separate, private project. Please be so kind, if you mail me your number - we can chat - worst case if you are not the right person I'm looking for - maybe you can direct me.Calidrago (talk) 09:02, 9 September 2015 (UTC)Reply[reply]

Hi,
You appear to be eligible to vote in the current Arbitration Committee election. The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to enact binding solutions for disputes between editors, primarily related to serious behavioural issues that the community has been unable to resolve. This includes the ability to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail. If you wish to participate, you are welcome to review the candidates' statements and submit your choices on the voting page. For the Election committee, MediaWiki message delivery (talk) 17:33, 23 November 2015 (UTC)Reply[reply]

I would love the chance to further explain why I think this would be the best solution, at least for the time being.

I am referring to this conversation goo.gl/NfcPMR

Would you welcome the chance to do so?

Nikodraca (talk) 23:19, 24 February 2016 (UTC)Reply[reply]

I recommend that you state your case for it on the proposals thread. --Yair rand (talk) 00:33, 25 February 2016 (UTC)Reply[reply]

I have posted in the proposals thread with my case, as well as spoken about how integration would look. Is there anything else I can do? Thank you. 174.92.117.20 (talk) 04:45, 25 February 2016 (UTC)Reply[reply]

Hey Yair, you may want to participate and help publicize the voting for preferences here. Thanks!--Melamrawy (WMF) (talk) 18:27, 19 May 2016 (UTC)Reply[reply]

Albanians and Kosovars are Very Hostile towards Homosexuality and Homosexuals. :(

Read all these Articles:

Homophobia in Albania and Kosovo. :(

http://www.balkaninsight.com/en/article/albania-is-the-most-homophobic-country-in-europe-survey-says

http://www.globalgayz.com/gay-life-in-albania/

http://www.refworld.org/docid/4dd10e342.html

https://www.civilrightsdefenders.org/country-reports/human-rights-in-albania/

http://www.kosovotwopointzero.com/en/article/665/kosovos-homophobia

http://www.kosovotwopointzero.com/en/article/883/public-violence-against-lgbt-people-in-kosovo-the-numbers

http://madikazemi.blogspot.com/2009/09/secret-life-of-kosovos-gay-community.html

Another Article:

Albanian Youth is Homophobic. :(

http://www.kaosgl.com/page.php?id=13271

Albanians are Very Homophobic. They Very Hostile towards LGBT Community and Homosexuality. :(

Hello, Yair rand. Voting in the 2016 Arbitration Committee elections is open from Monday, 00:00, 21 November through Sunday, 23:59, 4 December to all unblocked users who have registered an account before Wednesday, 00:00, 28 October 2016 and have made at least 150 mainspace edits before Sunday, 00:00, 1 November 2016.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2016 election, please review the candidates' statements and submit your choices on the voting page. MediaWiki message delivery (talk) 22:08, 21 November 2016 (UTC)Reply[reply]

Hello, could you please create documentation pages for your scripts? That would be really helpful. They don't have to be long - they just need to state what the script is doing (it doesn't matter if that's already in a comment in the script or not).

--Fixuture (talk) 19:07, 14 January 2017 (UTC)Reply[reply]

An editor has asked for a discussion to address the redirect Nannetticafruit. Since you had some involvement with the Nannetticafruit redirect, you might want to participate in the redirect discussion if you have not already done so. Steel1943 (talk) 01:17, 28 September 2017 (UTC)Reply[reply]

An editor has asked for a discussion to address the redirect Nanettikafruit. Since you had some involvement with the Nanettikafruit redirect, you might want to participate in the redirect discussion if you have not already done so. Steel1943 (talk) 01:17, 28 September 2017 (UTC)Reply[reply]

Hello, Yair rand. Voting in the 2017 Arbitration Committee elections is now open until 23.59 on Sunday, 10 December. All users who registered an account before Saturday, 28 October 2017, made at least 150 mainspace edits before Wednesday, 1 November 2017 and are not currently blocked are eligible to vote. Users with alternate accounts may only vote once.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2017 election, please review the candidates and submit your choices on the voting page. MediaWiki message delivery (talk) 18:42, 3 December 2017 (UTC)Reply[reply]

I was trying to add this to my watchlist, User:Yair_rand/interwikiwatchlist.js does it still work/am I doing something wrong w/ respect to enabling it? thanks--Ozzie10aaaa (talk) 17:01, 26 March 2018 (UTC)Reply[reply]

@Ozzie10aaaa: Hi, sorry for taking so long on this. Should be fixed now, I think. --Yair rand (talk) 18:13, 28 March 2018 (UTC)Reply[reply]

1.per the instructions I added the script...importScript ("User:Yair rand/interwikiwatchlist.js");

2.then I purged cache....don't see the import watchlist in upper right hand...:-(--Ozzie10aaaa (talk) 18:39, 28 March 2018 (UTC)Reply[reply]

@Ozzie10aaaa: Hm... The button is supposed to appear all on the line with the "Watchlist" header, next to the "Help" button all the way on the right. I'm not sure why it's not showing up; the JS that was in your /common.js worked for me. What browser and operating system are you using? Are any errors appearing in the JS console? --Yair rand (talk) 22:00, 28 March 2018 (UTC)Reply[reply]

IE 11/ windows 10 ......this is my .js[3]--Ozzie10aaaa (talk) 22:04, 28 March 2018 (UTC)Reply[reply]

OMG it works but I had to create a page and do this User:Ozzie10aaaa/vector.js, thank you very very much, --Ozzie10aaaa (talk) 23:36, 28 March 2018 (UTC)Reply[reply]

BTW

every year we do Wikipedia:WikiProject_Medicine/Stats/Top_medical_editors_2016_(all) however Wikipedia:WikiProject_Medicine hasn't been able to do 2017 list (and x tools is too busy this time[4])is this something you might be familiar with? thanks--Ozzie10aaaa (talk) 18:17, 1 April 2018 (UTC)Reply[reply]

@Ozzie10aaaa: Hm, takes a lot of API requests, but seems doable. User:Yair rand/TopEditors.js generates the list, which takes quite a while to run. The result for 2017 is here: User:Yair rand/TopMed. It doesn't have the "Main Wiki" column or the bots filtered out, though. --Yair rand (talk) 21:10, 3 April 2018 (UTC)Reply[reply]

Seppi333, Doc James , RexxS I think this is it--Ozzie10aaaa (talk) 22:25, 3 April 2018 (UTC)Reply[reply]

thank you from WP:MED

		The Medicine Barnstar
		to Yair rand from all of us at WikiProject Medicine, thank you Ozzie10aaaa (talk) 22:19, 3 April 2018 (UTC)Reply[reply]

Thanks for the barnstar :) . To be clear, the list I supplied is only for medical articles on the English Wikipedia. I didn't notice beforehand that the previous lists were for all Wikipedias, and I'm not sure how I would get the results from all Wikipedias. --Yair rand (talk) 22:47, 3 April 2018 (UTC)Reply[reply]

its a start, we didn't have anything till now--Ozzie10aaaa (talk) 22:49, 3 April 2018 (UTC)Reply[reply]

Agree great work. To get other languages what was done was EN WP was assumed to have all the medical articles (not off course true but an approximation). The corresponding articles were than found in all the other languages (some might not be tagged so realize that these could also go missing). The edits to these articles are than looked at. Doc James (talk · contribs · email) 03:11, 4 April 2018 (UTC)Reply[reply]

Can you explain through the process you used to calculate these results? Best Doc James (talk · contribs · email) 03:16, 4 April 2018 (UTC)Reply[reply]

@Doc James: The script grabs all the links on Wikipedia:WikiProject_Medicine/Lists_of_pages/Articles, then asks the API for lists of all edits done to each of them from January 1 through December 31 of 2017, then just counts up the number of times each editor appears in the user field of one of the edits. I left it running for a while (maybe an hour?) as the script retrieved all the lists of edits article by article, one after another, and then formatted the final results into a table. This is probably not the best way to do it, but it's the first I thought of. --Yair rand (talk) 06:07, 4 April 2018 (UTC)Reply[reply]

Perfect thanks :-) What do you think about using the Wikidata interlanguage links to find the medical articles in other languages? Could also produce a list of the number of medical articles by language. Not sure if that could be done at a specific point in time or whether it would be as of the date the tool was run. Doc James (talk · contribs · email) 17:57, 4 April 2018 (UTC)Reply[reply]

	The Technical Barnstar
	Brilliant work :-) Hats off to you. Doc James (talk · contribs · email) 03:08, 4 April 2018 (UTC)Reply[reply]

Hello, I'm Waddie96. I noticed that you recently removed content from Pesach Sheni without adequately explaining why. In the future, it would be helpful to others if you described your changes to Wikipedia with an accurate edit summary. If this was a mistake, don't worry; the removed content has been restored. If you would like to experiment, please use the sandbox. If you think I made a mistake, or if you have any questions, you can leave me a message on my talk page. Please explain why, in future, you removed content. Waddie96 (talk) 20:12, 29 April 2018 (UTC)Reply[reply]

You're right, sorry, I should have properly explained my revert. I see that another editor has since re-removed the problematic content, helpfully adding that the removed content was unsourced and inaccurate. --Yair rand (talk) 21:38, 29 April 2018 (UTC)Reply[reply]

for some reason User:Ozzie10aaaa/vector.js the cross-watchlist isn't working, any ideas(I copied it from yours)...--Ozzie10aaaa (talk) 22:26, 30 May 2018 (UTC)Reply[reply]

@Ozzie10aaaa: Are the relevant buttons still showing up? "(+new watchlist)", etc? If so, it's probably the issue with the watchlist tokens. Some of the tokens for accessing watchlists seem to have broken somehow; see phab:T184278 for an instance of this breaking things. Resetting the watchlist tokens in Special:Preferences and then removing and re-adding the watchlists in the script should fix it. --Yair rand (talk) 23:41, 30 May 2018 (UTC)Reply[reply]

no "(+new watchlist)" isn't showing up? what can I do?--Ozzie10aaaa (talk) 23:43, 30 May 2018 (UTC)Reply[reply]

@Ozzie10aaaa: Hm, confusing. Does the Javascript console show any error messages? (Instructions on opening JS console in different browsers). --Yair rand (talk) 00:39, 1 June 2018 (UTC)Reply[reply]

[5] ... it says the following....

HTML1300: Navigation occurred.

how-do-i-open-the-javascript-console-in-different-browsers (1,1)

5 HTML1500: Tag cannot be self-closing. Use an explicit closing tag. how-do-i-open-the-javascript-console-in-different-browsers (98,141)

2 SEC7131: Security of a sandboxed iframe is potentially compromised by allowing script and same origin access.

2 CONSOLE1810304: console.memory is not implemented and will return 0 for all attributes. Please use the memory profiler to monitor memory utilization.

--Ozzie10aaaa (talk) 14:12, 1 June 2018 (UTC)Reply[reply]

(apologies for the interference): the problem stems from line 220: var v=document.getElementById("mw-watchlist-options"); and later code which uses v without testing for nullness: the new watchlist does not have an element with ID mw-watchlist-options anymore. peace - קיפודנחש (aka kipod) (talk) 22:12, 1 June 2018 (UTC)Reply[reply]

Thank you very much, קיפודנחש. I wasn't aware of the changes in the new watchlist interface beta feature. @Ozzie10aaaa: If you copy the modified version of User:Yair rand/interwikiwatchlist2.js, the issue should be fixed. (The automatic sorting is unfortunately still broken for those with the beta feature enabled, due to changes in the list structure.) --Yair rand (talk) 23:24, 3 June 2018 (UTC)Reply[reply]

it works, your the best thanks Yair--Ozzie10aaaa (talk) 01:09, 4 June 2018 (UTC)Reply[reply]

Hi YR. I just installed User:Yair rand/HistoryView.js and that looks interesting. I am looking forward to testing it out, but my first impression is that so much thought has been put into it. One little detail I notice is, that when mousing over one edit by a user, other edits by the same user will have the username bolded. Clever! Thank you, Sam Sailor 22:07, 17 July 2018 (UTC)Reply[reply]

@Sam Sailor: Great to hear! Thank you for the helpful feedback. :) --Yair rand (talk) 22:51, 17 July 2018 (UTC)Reply[reply]

Is there anyplace that shows what it does? Thanks... Smarkflea (talk) 12:38, 1 August 2018 (UTC)Reply[reply]

@Smarkflea: Quiddity helpfully uploaded a screencast here. Does that help? --Yair rand (talk) 19:49, 1 August 2018 (UTC)Reply[reply]

Thanks... Smarkflea (talk) 20:47, 1 August 2018 (UTC)Reply[reply]

I've added that to User:Yair rand/HistoryView so that people can find it a bit more easily. (That page is auto-linked from the top of User:Yair rand/HistoryView.js). HTH! :) Quiddity (talk) 02:01, 29 August 2018 (UTC)Reply[reply]

Just following up on this. Do you have anything further to add to Talk:Main Page#Portal links broken? — Martin (MSGJ · talk) 15:39, 31 October 2018 (UTC)Reply[reply]

Hello, Yair rand. Voting in the 2018 Arbitration Committee elections is now open until 23.59 on Sunday, 3 December. All users who registered an account before Sunday, 28 October 2018, made at least 150 mainspace edits before Thursday, 1 November 2018 and are not currently blocked are eligible to vote. Users with alternate accounts may only vote once.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2018 election, please review the candidates and submit your choices on the voting page. MediaWiki message delivery (talk) 18:42, 19 November 2018 (UTC)Reply[reply]

Hi, I noticed you did some work on Template:Main_Page/styles.css. I'm trying to implement the opposite of a "nomobile" css class over at wikiversity to make some links show up only on the mobile version (to compensate for dropdown menus the not appearing on mobile). I've so far been using a workaround at v:Template:WikiJMed_top_menu taking advantage of the way mobile h2 headings are rendered, but I want to do something a bit more robust! Would you be able to advise me on what could be added to v:MediaWiki:Common.css and v:MediaWiki:Mobile.css to make something like that work? Thanks in advance for any advice! T.Shafee(Evo&Evo)^talk 05:58, 12 December 2018 (UTC)Reply[reply]

@Evolution and evolvability: .onlymobile { display: none; } in Common.css and .mw-parser-output .onlymobile { display: block; } in Mobile.css should work. --Yair rand (talk) 06:42, 12 December 2018 (UTC)Reply[reply]

Brilliant, thankyou! T.Shafee(Evo&Evo)^talk 10:50, 12 December 2018 (UTC)Reply[reply]

this works, but i think only the first part is needed - ttbomk, mobile simply does not load common.css, so not adding the class to mobile.css is prolly better than forcing block display. peace - קיפודנחש (aka kipod) (talk) 07:03, 13 December 2018 (UTC)Reply[reply]

(Checks whether mobile loads Common.css.) Huh, good to know. You are quite correct. --Yair rand (talk) 07:10, 13 December 2018 (UTC)Reply[reply]

Thank you both! You can see the main fruits of your advice in this template on desktop and on mobile. T.Shafee(Evo&Evo)^talk 12:08, 13 December 2018 (UTC)Reply[reply]

@קיפודנחש: Just a note in case it's relevant later - It seems that wikiversity's v:MediaWiki:Mobile.css does load common.css, so I think in that case it may be necessary to use both (@import url("/w/index.php?title=MediaWiki:Common.css&action=raw&ctype=text/css") screen;). I don't know which is more commmon on other wikis though. T.Shafee(Evo&Evo)^talk 22:51, 13 December 2018 (UTC)Reply[reply]

@Evolution and evolvability: - i think you are right. i think i read somewhere arguments against using @import, but i'm no authority on the matter - you may want to poke around and see the pros, cons, and alternatives. as to the "override", in this case, i think the conventional "undo" for css display rule is not "block", which may pervert the display of an element in some cases, but rather "inherit". if Yair disagrees, you should probably listen to him rather than me... peace - קיפודנחש (aka kipod) (talk) 14:59, 28 December 2018 (UTC)Reply[reply]

It looks like you got consensus to enact TemplateStyles on the main page. I think MSGJ implemented it a month later but reverted himself. Do you know why, or the status of that effort in general? --Izno (talk) 16:05, 2 September 2019 (UTC)Reply[reply]

Looks like Talk:Main_Page/Archive_192#Portal_links_broken? and the query by MSGJ above. Could you support further implementation if I were to implement it? --Izno (talk) 16:08, 2 September 2019 (UTC)Reply[reply]

@Izno: So, um, having accidentally broken the main page twice was a rather nerve-racking experience. What would "support" entail here? I'd rather not have the responsibility for urgently fixing things if something goes wrong again. (Non-urgently would be fine.) I don't particularly think it will break again, but...

(See also Wikipedia:Village_pump_(technical)/Archive_170#Main_Page_responsive_design.) --Yair rand (talk) 16:44, 2 September 2019 (UTC)Reply[reply]

Looks like TheDJ accurately predicted your reaction. :) Yes, I was kind of envisioning at least non-urgently, but maybe we can make a sandbox and spin it through browsershots.org at least? Or are there other websites that can take care of some of the archaic or niche browsers? --Izno (talk) 16:48, 2 September 2019 (UTC)Reply[reply]

@Izno: Note that the version previously deployed had bugs in the portal list display even on IE8< (~1.5% of desktop views), which doesn't support a lot of modern CSS, including some things Mediawiki relies on for basic stuff. (If we weren't trying to support really old browsers, we might even use proper CSS columns for the portal list instead of manually absolute-positioning them...) Anyway, I made some changes to User:Yair rand/MPSandbox for supporting all the way back to IE5. If there are particular bugs that are noticed, I can help with fixing them.

I don't know of any free sites for testing archaic/niche browsers. There are some paid systems I think, which the WMF might have access to, but I doubt there's a way to use that. I've been having a hard time using browsershots itself recently, as it keeps expiring... --Yair rand (talk) 02:43, 4 September 2019 (UTC)Reply[reply]

Module:IPAc has been nominated for deletion. You are invited to comment on the discussion at the module's entry on the Templates for discussion page. * Pppery * _{it has begun...} 04:19, 17 November 2019 (UTC)Reply[reply]

Hello! Voting in the 2019 Arbitration Committee elections is now open until 23:59 on Monday, 2 December 2019. All eligible users are allowed to vote. Users with alternate accounts may only vote once. The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail. If you wish to participate in the 2019 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add ((NoACEMM)) to your user talk page. MediaWiki message delivery (talk) 00:09, 19 November 2019 (UTC)Reply[reply]

Since you participated in the discussion on Wikipedia Books I herewith inform you that a decision has been taken.

See Wikipedia:Village_pump_(technical)/Archive_176#Suppress_rendering_of_Template:Wikipedia_books Dirk Hünniger (talk) 20:29, 31 December 2019 (UTC)Reply[reply]

PLS SEE Wikipedia:Village pump (proposals)#Introduction page.--Moxy 🍁 11:25, 12 June 2020 (UTC)Reply[reply]

Thanks for nominating me. I am not sure the candidacy would go through, but if it does I will do whatever I can to do a proper job.--Ymblanter (talk) 09:30, 22 June 2020 (UTC)Reply[reply]

	"Sunflower Award"
	Your work as an admin is not being graded, But it certainly is much appreciated, To know that you see with vision that's clear, A shining light of integrity we tend to hold dear. Yair rand, thank you for all you do! Atsme 💬 📧 13:47, 13 November 2020 (UTC)Reply[reply]

Thank you. (I'm not actually an admin on this project, by the way.) --Yair rand (talk) 04:18, 23 November 2020 (UTC)Reply[reply]

Hello! Voting in the 2020 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 7 December 2020. All eligible users are allowed to vote. Users with alternate accounts may only vote once. The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail. If you wish to participate in the 2020 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add ((NoACEMM)) to your user talk page. MediaWiki message delivery (talk) 01:42, 24 November 2020 (UTC)Reply[reply]

I just came across Wikipedia:Arbitration/Index/Principles 2 – I'm really impressed. Is there a tool that you used to help generate this? Best, KevinL (aka L235 · t · c) 01:50, 8 December 2020 (UTC)Reply[reply]

@L235: I wrote a script to generate it. Source code posted here. --Yair rand (talk) 06:09, 8 December 2020 (UTC)Reply[reply]

Thanks for this KevinL (aka L235 · t · c) 22:12, 8 December 2020 (UTC)Reply[reply]

See Wikipedia talk:Arbitration/Index/Principles 2 – RM to move it to /Principles, over the old, defunct page.  — SMcCandlish ☏ ¢ 😼  03:24, 8 December 2020 (UTC)Reply[reply]

Hey Yair, it looks like you've got some user scripts in use by others that have bare javascript global wg-style variables. These are phab:T72470 deprecated, and while I don't think there's a timeline for their removal, it's been that way for a while. It's usually a straightforward fix, all uses need to use mw.config.get, such as converting wgTitle to mw.config.get('wgTitle'). There's some more info at mw:ResourceLoader/Migration guide (users)#Global wg variables. they are:

• User:Yair rand/interwikiwatchlist.js
• User:Yair rand/interwikiwatchlist2.js
• User:Yair rand/watchlistnotifications.js

I can take care of cleaning them up for you if you like, just let me know! ~ Amory (u • t • c) 11:58, 29 January 2021 (UTC)Reply[reply]

@Amorymeltzer: Fixed, thanks for the note. (Completely unimportant, but how come my username is the only one to somehow not get inserted into the "USERNAME" token above? It doesn't even have any special unicode or quotes or anything.) --Yair rand (talk) 00:57, 1 February 2021 (UTC)Reply[reply]

Thanks, but sorry! I must've had a copy-paste fail. ~ Amory (u • t • c) 01:16, 1 February 2021 (UTC)Reply[reply]

Oh, I was hoping for some amusing technical glitch. :) --Yair rand (talk) 01:24, 1 February 2021 (UTC)Reply[reply]

Hi, are you around? If so, would you be able to do again what you did for 2017 if it's not too much trouble? Thanks very much :) Dr. Vogel (talk) 18:28, 16 April 2021 (UTC)Reply[reply]

@DrVogel: So, the script that created that relied on Wikipedia:WikiProject_Medicine/Lists_of_pages/Articles (warning: large page) to have a list of all the WPMED articles for tracking things, but that list hasn't been updated since 2017. Three options:

• Find someone who can reupdate the list of WPMED articles, and then I can run the script. User:CFCF was the last to update it. @CFCF: Would you be able to update Wikipedia:WikiProject_Medicine/Lists_of_pages/Articles? Otherwise:
• Perhaps there's alternative list of the Wikiproject's articles available somewhere?
• Failing at that, I could just run the script based off the 2017 list, generating a list of the top editors to WPMED articles that existed as of 2017.

--Yair rand (talk) 07:13, 19 April 2021 (UTC)Reply[reply]

Hi, thanks for replying. I think CFCF seems to have sadly left the project. I was sorry to learn about that. Is there anyone else you know who would have the knowledge to generate an up-to-date list of articles? Dr. Vogel (talk) 08:57, 19 April 2021 (UTC)Reply[reply]

maybe All Wikiproject Medicine articles--Ozzie10aaaa (talk) 23:47, 22 April 2021 (UTC)Reply[reply]

great! Dr. Vogel (talk) 13:06, 23 April 2021 (UTC)Reply[reply]

@DrVogel and Ozzie10aaaa: Done, see User:Yair rand/TopMed 2020. --Yair rand (talk) 01:04, 26 April 2021 (UTC)Reply[reply]

• Yair rand, thank you 😊 so much its been a difficult year, hopefully our editors will see the bright side when they see their contributions, ...thank you again--Ozzie10aaaa (talk) 01:40, 26 April 2021 (UTC)Reply[reply]
• Thank you! Dr. Vogel (talk) 08:10, 26 April 2021 (UTC)Reply[reply]

Hi Yair,
I've sent you a question on your meta talk page. As we're moving from Transition towards Implementation of Movement Strategy, I'm about to create a new "Implementation space" on Meta, where we would like to unify/centralize conversations and discussions around the initiatives that are being worked on. To avoid confusion, I wanted to ask you, if we may adopt the meta:Hubs page you have created, rename it to meta:Wikimedia 2030/Implementation/Hubs, and add all important information regarding it. Would that be okay for you? Best regards, --CKibelka (WMF) (talk) 16:58, 23 April 2021 (UTC)Reply[reply]

Hello! Voting in the 2021 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 6 December 2021. All eligible users are allowed to vote. Users with alternate accounts may only vote once. The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail. If you wish to participate in the 2021 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add ((NoACEMM)) to your user talk page. MediaWiki message delivery (talk) 00:23, 23 November 2021 (UTC)Reply[reply]

Hi, could you give me some tips about copying Template:Graph:Chart code to another wiki? How can I access the code? Wolfmartyn (talk) 22:07, 28 November 2021 (UTC)Reply[reply]

@Wolfmartyn: The Lua code is at Module:Graph. If you have the relevant userrights locally, you could use Special:Import from the other wiki, which preserves the history. (See Help:Import.) --Yair rand (talk) 06:34, 29 November 2021 (UTC)Reply[reply]

thanks Wolfmartyn (talk) 01:05, 30 November 2021 (UTC)Reply[reply]

Hello! Voting in the 2022 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 12 December 2022. All eligible users are allowed to vote. Users with alternate accounts may only vote once.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2022 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add ((NoACEMM)) to your user talk page. MediaWiki message delivery (talk) 00:33, 29 November 2022 (UTC)Reply[reply]

Hello Yair, I have some questions to you:

Regarding Google dictionuary and Britannica Dictionuary (both are in sinilar circulation as related to Marian Merriam-Webster ans Oxford University Press)

1. Keep=start/change redirect from Ab (Semitic) to Av
2. Keep=start new separate article called (Abba (religion)
3. Keep=start new separate article called Abu (arabic word)
4. Finally, remove/endorse ABBA primary topic for pop music group and change primary topic to disambiguation. Although the group is primary topic for 21 years, then things can change, especially that was no discussion about it (Just as we changed name of article History of World to Human History -level 1 article). Music group is not part of any dictionuary definition + even ABBA (capital letters) still does not sway in google books dominately results about the group. Group has weaker google trends than some Divine concepts (as for disambiguation or possible compromises compare also Nirvana vs Nirvana, Sting vs Stinging etc).

On Wikidata all wikipedias (except the English) describe Abu and Abba as separste topics.

What do do you think? Warmest regards. Dawid2009 (talk) 03:52, 8 October 2023 (UTC)Reply[reply]

Hello! Voting in the 2023 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 11 December 2023. All eligible users are allowed to vote. Users with alternate accounts may only vote once.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2023 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add ((NoACEMM)) to your user talk page. MediaWiki message delivery (talk) 00:27, 28 November 2023 (UTC)Reply[reply]