User talk:Gary

From Wikipedia, the free encyclopedia
  (Redirected from User talk:Gary King)
Jump to navigation Jump to search
Featured article Article contributions (210) · Did You Know? Did you know? (108) · Good article reviews (232) · Barnstar Barnstars (55) · Scripts Scripts (31)

ArbCom 2018 election voter message[edit]

Scale of justice 2.svgHello, Gary. 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)

Precious anniversary[edit]

Cornflower blue Yogo sapphire.jpg
Six years!

--Gerda Arendt (talk) 08:12, 2 March 2019 (UTC)

... and ten years awesome today! --Gerda Arendt (talk) 20:54, 14 March 2019 (UTC)

Comments in Local Time[edit]

Very odd. I was just reading the humor piece in today's Signpost (at WP:Wikipedia Signpost/2019-03-31/From the editors). I live in New Jersey, and the gadget converted the UTC times in the piece to ... "UTC‑4.933333333333334" (and no summer adjustment). I presume this has something to do with the reality of life in 1876, but I couldn't figure it out from the code. What's up with it? With admiration, StevenJ81 (talk) 15:20, 12 April 2019 (UTC)

The relevant code is:
    utcOffset = (-1 * time.getTimezoneOffset()) / 60;
    utcOffset = utcOffset >= 0 ? '+' + utcOffset : '−' + Math.abs(utcOffset);
So the timezone offset is retrieved from your browser. If it happens again, you can try checking the value of your browser's timezone offset with the following code in your JavaScript Console: (new Date()).getTimezoneOffset() Gary (talk · scripts) 18:30, 12 April 2019 (UTC)
Didn't help, as on the current date, that correctly returns "240" (or UTC-4, EDT). (Ordinary posts work fine, both when I'm in UTC-4 and when I'm in UTC-5, and even when I've traveled a few times.)
No, the year in which this behavior starts to take place (going backwards from now) is 1883, the year before the International Meridian Conference. So I'm guessing that by design or by accident you're calling something that doesn't recognize time zones before then ... and uses my meridian, somehow, to try to guess my time. (Since I'm actually west of 75degW, I'm not quite sure it works right.) StevenJ81 (talk) 19:38, 12 April 2019 (UTC)
Can you point me to exactly which timestamp you are saying that this happens? I briefly skimmed the linked article but couldn't find a timestamp in it, let alone one that's in the 19th century. Or a screenshot of the problem would be even better. Thanks. Gary (talk · scripts) 20:07, 12 April 2019 (UTC)
Okay I see what you are referring to now. You linked to a different page. This is the one you meant, I assume: Wikipedia:Wikipedia Signpost/2019-03-31/Humour. Gary (talk · scripts) 20:51, 12 April 2019 (UTC)
I'll see what I can do with it, but it isn't really a high priority. It'll probably be a problem for timestamps that are before 1970 and after 2038, which happens very rarely. Gary (talk · scripts) 20:57, 12 April 2019 (UTC)
@StevenJ81: I've re-written the script and fixed the original bug you mentioned. Please check it, and let me know if you find any other bugs, since new ones may have appeared since the major overhaul I just made. Gary (talk · scripts) 02:34, 13 April 2019 (UTC)
Thanks. The time zone stuff seems to be working now. It seems to handle DST correctly from 1918 on, and suppresses it before then. Pre-1884, it's assuming I'm at UTC-4.9; assuming that's a rounded version of -4.993, it's assuming I'm in New York, because my time zone setting is America/New York, and New York is at 44°W (whose mean solar time zone would be "UTC"-4.993).
The date interval calculations aren't right, the farther back in time you go. Picking the same date—say, September 10—should always give the same number of "months" and "days" ago, with only years changing. But that's not actually the case. Question is how much you want to fiddle with this; I'd understand if it's not your biggest priority now. StevenJ81 (talk) 20:14, 15 April 2019 (UTC)
Yeah the date calculations are not completely accurate. It can be improved. But it would take time. I may do it later. Gary (talk · scripts) 21:47, 15 April 2019 (UTC)

Doesn't work in modern or cologneblue[edit]

I was away for a bit and noticed this stopped working. I think it's related to the changing use of bodyContent; both the modern and cologneblue skins don't use #bodyContent. I think mw_contentholder is roughly the parallel for modern and article is for cologneblue, but I think mw-content-text can fill in for everything if tweaked. ~ Amory (utc) 17:39, 15 April 2019 (UTC)

I'll use .mw-parser-output, which should work well. Gary (talk · scripts) 18:58, 15 April 2019 (UTC)
Looks great, thanks for the prompt fix! ~ Amory (utc) 19:34, 15 April 2019 (UTC)