User talk:Quiddity

From Meta, a Wikimedia project coordination wiki
Jump to navigation Jump to search

Hi, you're welcome to leave a message for me here,
or at w:User talk:Quiddity on the English Wikipedia. Thanks!

JS[edit]

Did it work or not? (Please don't use the CSS, it's borked. The JS works for me, but not the CSS.) PiRSquared17 (talk) 00:05, 15 September 2013 (UTC)

@PiRSquared17: It worked so well, that I have 15 tabs open (starting from w:WP:User scripts), and I was looking to see (a) what else I want to experiment with, and (b) whether your script was already included in there, or if I needed to suggest that you add it! (w:Wikipedia:WikiProject User scripts/Scripts#Watchlist is where it belongs ;)
I assume the JS code works identically at En.wiki? (no cleanchanges there, so nope). How would I/we achieve the same thing at En.wiki?
The CSS does work for me, and whilst I do not forsee myself ever needing to collapse the individual items, I guess there might be a heavy-activity day at some forum/rfc/etc, so I'll reset to just using the JS.
[Also, I'm not familiar with JS, so I wasn't sure how to interpret your "eval is evil" comment - is that like "tables are evil (html layout wise)" or more like "This is madness (and could make my processor lose it's magic smoke)" ? (I assume the former, and am mostly joking with the latter ;) ]
Maybe I can finally start using "expand my watchlist" on En.Wiki, after 8 years of avoiding it! Thank you! Quiddity (talk) 00:25, 15 September 2013 (UTC)
@PiRSquared17: Oh, I've found w:user:js/watchlist which claims to do the same thing (amongst other things) - However, the "±" doesn't appear for me, so that feature seems to be broken (Everything else works well). Possibly that code-method is either fixable, or replaceable with your own eval method? (Utterly beyond my code comfort zone). It might make a lot of people happy, to have that feature back! Quiddity (talk) 01:18, 15 September 2013 (UTC)
Hello! I actually just wrote that, after you suggested it. I could probably improve it, but the user won't notice a difference. It should work on any wiki using enhanced RecentChanges. Currently it's just a one-line mess of JavaScript. eval is not always "evil", but it's not good to use it on untrusted input, and it can be slow (but it shouldn't be in this case). Basically, eval is a feature of a programming language that evaluates code in that language. In this case, the JS code in located in a link address (javascript:... "URL"), and I ran it by removing the "javascript:" (11 characters - that's where the 11 comes from) and evaluating the rest.[1] There are better ways, probably, but it was only a quick fix.
I was not aware of the other script. Are you sure it doesn't work? I can try to fix it, but I can't guarantee that I will succeed. I've also promised to help angwiki and gotwiki with technical matters... for a year. PiRSquared17 (talk) 01:25, 15 September 2013 (UTC)
@PiRSquared17: Your JS code doesn't work at En.Wiki - there's no "toggleVisibilityE" in the html source, which I assume is the problem?
The w:user:js/watchlist definitely doesn't work (to toggle the collapsed sections) at En.wiki - I tried purging cache. (However, I much prefer the way that your code doesn't require any interaction from me, and just auto-opens everything on load. So just a fix your code, on En.wiki, is my preference.) Thanks again, and thanks for the explanation of eval; eventually I'll fill a bucket with all the drops of programming knowledge I'm slowly collecting. :) Quiddity (talk) 01:37, 15 September 2013 (UTC)
Try
$(window).load(function() { $('.mw-enhancedchanges-arrow').click(); });
I assume you know a bit about HTML and/or CSS selectors. On Meta, the arrows aren't in any specific class, but can only be identified by the fact that they are links beginning with "javascript:toggleVisibilityE". On enwiki, the arrows are in the class "mw-enhancedchanges-arrow", which makes it much easier to fake-click them via jQuery. ;) I don't know why there is a difference, but I assume it has to do with CleanChanges vs enhanced RC (I honestly didn't realize there was a difference until just now.) Note: this code is untested. PiRSquared17 (talk) 01:47, 15 September 2013 (UTC)
@PiRSquared17: Tested and works, at En.wiki. Fantastico!
I do know HTML and CSS, circa 2005 (i kept uptodate from 1998 till original CSS Zen Garden era). I can copy and occasionally hack apart javascript and other languages, but I don't readily take to it. Similarly, I've used Ubuntu for (8?) years now, but I still have to look up the man pages every time I do anything in the console. I've read numerous books and used a handful of tutorials (tryruby being the best), but it refuses to sink in past the surface, and every language variant just muddles the bits that do stick in my memory (I've tried to put DOS commands in the Bash terminal soooo many times). So yes, I can basically understand what your code is doing, but I definitely couldn't have written it! Much thanks again.
If you haven't already, I'd recommend adding your code somewhere at that User scripts page. Quiddity (talk) 04:09, 15 September 2013 (UTC)
I will do this later today or tomorrow and I'll see what I can do with the ± on that other script. PiRSquared17 (talk) 04:27, 15 September 2013 (UTC)
For Meta/CleanChanges:
  1. To expand the user talk/contributions, and expand each entry, use the code currently on my common.js here. I made it look a little nicer.
    Note that the $(...) now has a comma with two separate selectors. You may remove either, if you want to disable either the auto-expand edits or the auto-expand user links.
    I made a fancier version with a button to expand/collapse. Try that.
For EnWiki/enhanced RC: [2]
I will work on the other script that you said is broken. PiRSquared17 (talk) 17:55, 15 September 2013 (UTC)
@PiRSquared17: Fancier version almost works - the userlinks don't auto-expand. (But the manual toggle does work). That's "good enough" for me, so it's your call whether or not to spend time fixing it. Quiddity (talk) 18:06, 15 September 2013 (UTC)
Fixed. The non-fancy version also does this now. PiRSquared17 (talk) 18:08, 15 September 2013 (UTC)
@PiRSquared17: Much <3 !! Quiddity (talk) 18:14, 15 September 2013 (UTC)

Upcoming IdeaLab Events: IEG Proposal Clinics[edit]

Idea Lab
Idea Lab

Hello, Quiddity! We've added Events to IdeaLab, and you're invited :)

Upcoming events focus on turning ideas into Individual Engagement Grant proposals before the March 31 deadline. Need help or have questions about IEG? Join us at a Hangout:

  • Thursday, 13 March 2014, 1600 UTC
  • Wednesday, 19 March 2014, 1700 UTC
  • Saturday, 29 March 2014, 1700 UTC

Hope to see you there!

This message was delivered automatically to IEG and IdeaLab participants. To unsubscribe from any future IEG reminders, remove your name from this list

Barnstar and a request for feedback[edit]

IEG barnstar 2.png Individual Engagement Grant Barnstar
Thank you for commenting on Individual Engagement Grant proposals during this recent round! We really appreciate that you took the time to share your thoughts.

To help us improve the IEG program for future participants, would you mind taking this quick 3-question survey?

Thanks again for your help,

--Siko and Haitham, Wikimedia Foundation Grantmaking

Re: GLAMs value analytics/metrics[edit]

Did you check outreachwiki:GLAM/Case_studies? Nemo 08:56, 23 January 2016 (UTC)

@Nemo bis: I did, and I even got as far as outreach:GLAM/Indicators_of_Success#Indicators_related_to_visitors, but I couldn't find the specific example that I fuzzily-remember. :-(
I'm trying to find details, in order to help explain the value of analytics to Goldzahn over at Talk:2016_Strategy/Knowledge#Bluerasberry (and how analytics help organizations to rationalize putting dedicated/ongoing resources into the work/donations over many years, instead of just a one-time experiment). I was hoping to include a great example or two, if you can think of any specifically. If not, I'll just explain the abstract benefits, in a few days. Cheers! Quiddity (talk) 22:41, 26 January 2016 (UTC)

mw:Mobile Gateway/Mobile homepage formatting[edit]

Hi, do you know if this is still the best/only help page on how to configure/style a Wikimedia project main page for MobileFrontend? Perhaps it should be moved to Help or Manual namespace, the basepage makes little sense nowadays. --Nemo 20:15, 23 May 2016 (UTC)

@Melamrawy (WMF): might be able to answer that. I'm not familiar with MF. Quiddity (WMF) (talk) 02:42, 24 May 2016 (UTC)

Translation administrator[edit]

Hi. I assume that Echo has already notified you. In any case, I've closed your request as successful and granted the translation adminship toolkit on this account. Enjoy :-) —MarcoAurelio (talk) 11:02, 16 July 2017 (UTC)

Bug in our user group page?[edit]

Hi Quiddity! I come over to you because I have seen you fixed a syntax problem in the Basque Wikimedians User Group. The issue lies with a link in this section: Activities 2017. That link should direct to this page, still it brings you to 2016. I wonder if you could help with this. --Iñaki LL (talk) 22:26, 25 February 2018 (UTC)

@Iñaki LL: fixed. :) (All tvars on a page should be unique). Cheers, Quiddity (talk) 22:33, 25 February 2018 (UTC)
Wow Quiddity, that is actually fast... and great:) Thank you! --Iñaki LL (talk) 22:36, 25 February 2018 (UTC)

Timeless Newsletter • Issue 2[edit]

Wikimedia beetle.svg

The second issue of the Timeless newsletter is out.

The news: Themes are coming to Timeless! Your infobox and navbox templates in particular are probably going to look absolutely horrible in the new built-in night mode.


For more information, background, plans and progress updates, please see the full issue on Meta, complete with a ridiculous list of phabricator task links, gratuitous mention of other skins, and me complaining about the current state of MediaWiki skinning in general.

-— Isarra 01:48, 30 August 2018 (UTC)

Thanks for your benevolent spontaneity ...[edit]

Thank you. I didn't know the utility of <pre></pre>.
At least one utility in Windows— the centralised Help files in .chm format— works far better. Wikipedia/Wikimedia -'s Help pages appear scattered. Or perhaps, there is an utility in Wikipedia to peruse the help pages centrally, of which I am oblivious.
But everything in Wikipedia is very verbose. I liked your The_source_of_many_disagreements.png file. Far better spoken visually/symbolically than that would have been possible in words. Generally applicable in most cases to reduce verbosity.
I have already sent you Thanks messages. But on hindsight they were not good enough gesture.
Thanks once again.
Bkpsusmitaa (talk) 08:14, 13 December 2018 (UTC)

@Bkpsusmitaa: Thank you very much! I sometimes enjoy wikifying things I find in RecentChanges. I agree, our documentation has many problems - that is what 17 years of organic growth from thousands of volunteers and some paid staff can end up with! Eventually it will improve. I also appreciate brevity and obviously infographics. Best wishes, Quiddity (talk) 08:29, 13 December 2018 (UTC)

Timeless Newsletter • Issue 3[edit]

Wikimedia beetle.svg
Newsletter • December 2018

Welcome to the third issue of the Timeless newsletter, complete with a somewhat dubious explanation of where I've been all this time.

Somewhat dubious explanation of where I've been all this time:

I suffered a rather bad concussion in October, which knocked me pretty much completely out of commission through November, and I'm still recovering even now. One person = bus factor of one, even though it wasn't actually a bus but a very short flight of stairs.

Updates:

  • Random bugs have been fixed. More bugs have been found. For a full list of horrors, see the workboard.
  • Implementing themes (T131991: the dark/night mode and winter variants of the skin) has proven far more complicated than initially thought, lacking either the extension, or preferably, some core support for this functionality. Thus:
    • I have submitted a Request for Comment proposing to merge Extension:Theme into core - this will enable skins to specify style variants as distinct options for users to select in their preferences by letting the skin specify the styles separately for each, a much neater way of implementing this than some of the existing hacks.
    • Jack Phoenix has already submitted a patch to do this. We simply need the buy-in and consensus to merge it, and to resolve whatever issues may arise from this wider review.

Comments on the RfC (MediaWiki wiki RfC page, task) or bugs, or further reports, are always appreciated.

Until next time, hopefully with no further injuries,

-— Isarra 22:35, 20 December 2018 (UTC)

Thanks![edit]

Thanks, Quiddity, for reading and correcting this page. It's very appreciated, and I changed the related Commons file accordingly. -- Have a good new year! Johanna Strodt (WMDE) (talk) 09:34, 7 January 2019 (UTC)

Wiki Project Medicine Foundation Membership[edit]

Membership renewal

Dear Wiki Project Med Supporter, you are receiving this message as you have shown interest in supporting Wiki Project Med in the past. As our organization grows and evolves, we want to be able to verify peoples ongoing interest in being involved. To that end, the board has decided to require renew of membership every two years. So -- whether you are a current member or not, please fill out our updated membership form, to ensure your membership till the end of 2020. Please note -- We ask that you fill out the form by Feb 3rd, as we are close to elections and only members can nominate themselves for the board and vote!

Best, Shani & Doc James. 01:57, 28 January 2019 (UTC)

thanks[edit]

Background helps. Personal opinion is that is not needed, though a decision doesn't come from personal opinion.

Timeless Newsletter • Issue 4[edit]

Timeless logo.svg
Newsletter • April 2019

Welcome to the fourth issue of the Timeless newsletter, with a cat! Or maybe not.

Un chat qui miaule???

It's true! The angry cat, a fundamental part of Timeless, has resulted in confusion and bug reports all across the projects and phabricator. And now it shall be immortalised forever in the new, shiny Timeless logo.

Updates:

After putting off the project for three months because I got hit in the head with a flight of stairs, and then putting off the project for another two months while working out what the status of the grant was, I have now put off the project even more in order to focus on my other project for a bit. So progress lately has been a bit whims-based as a result:

Radar:

  • The French Wiktionary voted to set Timeless as their default skin, with results possibly as you might expect: I ran away and hid, and the WMF said no. A bit of discussion later and we largely agreed that all else aside, this is a bit of a branding issue, but we love the enthusiasm! Also the bug reports that inevitably come out of such a discussion. I'm still working on properly going through those.
  • Theme support is still stuck in limbo, but now we have another skinning RfC. tl;dr, we wanna replace the entire skinning system, and Skizzerz'll write a prototype later.

I will be fully resuming work on Timeless next week, or maybe the week after, depending on what madness (or illness) comes out of the Hackathon in Prague. Please come talk to me there to discuss strategy!

-— Isarra 16:51, 14 May 2019 (UTC)