#REDIRECTen:User talk:Anomie
This page is a soft redirect.

Central auth talk pageEdit

Hi on centralauth talk page you undid my edit I made it because LiquidThread is easer to do and shows more recents posts at the top. I would like to undo the edit I have created an archive for that page so it is saved on another page. 90.192.240.127 14:58, 12 May 2014 (UTC)

A bowl of strawberries for you!Edit

  Thanks for your quick response to the problems in bug 67805. I really appreciate it. Whatamidoing (WMF) (talk) 17:09, 15 July 2014 (UTC)

Some baklava for you!Edit

  thanks
Jessica ann faith cutcher (talk) 19:00, 22 August 2015 (UTC)

A barnstar for you!Edit

  The Original Barnstar
For the great TemplateSandbox, it makes working with templates so much more easier! Thanks! :) Florianschmidtwelzow (talk) 12:18, 26 October 2015 (UTC)

Please provide feedback on suggested improvements to the Code of ConductEdit

Thanks to everyone who’s helped work on the Code of Conduct so far.

People have brought up issues they feel were missed when working on "Unacceptable behavior" and "Report a problem". Consultants have also suggested changes in these same sections.

These are important sections, so please take a look at the proposed changes. I apologize that this feedback arrived later than planned, but I think this will create a better document.

If you prefer to give your opinion privately, feedback via e-mail is welcome at conduct-discussion wikimedia.org.

Thanks. Mattflaschen-WMF via MediaWiki message delivery (talk) 04:18, 24 February 2016 (UTC)

Please participate in discussion on updated "Marginalized and underrepresented groups" textEdit

Thanks for participating in the earlier discussion on Talk:Code of Conduct/Draft#Marginalized and underrepresented groups. There was some support and some issues were raised. I've attempted to propose a better draft to address the issues.

Please participate at Talk:Code of Conduct/Draft#New proposed wording. Thanks. User:Mattflaschen-WMF via MediaWiki message delivery (talk) 01:40, 17 March 2016 (UTC)

Just curiousEdit

What country do you live in? Gettysburg guru (talk) 20:09, 22 April 2016 (UTC)

frame functions in LuaEdit

Despite your attempts to explain while reverting my "clarify" tags, I still do not quite understand what all these frame functions do or what they would be used for, and would really appreciate some more explanation on the page, perhaps by means of examples. I am trying to figure out how to create an array from the parameters supplied to the {{#invoke:}} thingy, and I cannot figure out which of the functions on the page would do this. Erutuon (talk) 22:48, 11 October 2016 (UTC)

The frame object passed into the invoked function (which is also typically the one available via mw.getCurrentFrame()) contains the parameters passed to the {{#invoke:}} as the args subtable. You should be able to create your array from that. Anomie (talk) 12:07, 12 October 2016 (UTC)
I finally realized the problem was that I was not distinguishing between the first frame (if that's the correct term) and the parent frame. I think I had used getParent() when I should have used frame or mw.getCurrentFrame(). I kind of wish there were a clearer explanation on the Lua page or somewhere else, with an example. Erutuon (talk) 01:40, 19 October 2016 (UTC)

rcexcludeuserEdit

Hi! The fact that rcexcludeuser only accepts one name, is that for performance reasons? It would be nice for anti-vandalism purposes if several users – or perhaps a whole user group – could be excluded. Nirmos (talk) 16:41, 11 January 2017 (UTC)

Maybe, or it might have just been intended to implement "hide my edits". Anomie (talk) 22:43, 11 January 2017 (UTC)
Ok. Is there someone else I should ask who knows more closely, or should I file a Phabricator task directly? Nirmos (talk) 23:35, 11 January 2017 (UTC)


MsuploadEdit

Hello! Are you https://phabricator.wikimedia.org/p/Anomie/ ?

I see you worked on Extension:MsUpload I loved loved loved Extension:MsUpload. It is the best extension ever made. Now it is a terrible worthless aberration that has so many major bugs in it to make it worthless.

Whoever redesigned this extension should be reprimanded.

  1. The extension no longer works at all for 1.27.
  2. It no longer works without WikiEditor
  3. If you have mediawiki 1.25 or before, the extension no longer works.

I hope these issues can be fixed. it is a worthless extension now.

I upgraded from mediawiki 1.19 just to use this extension, unbeknownst to me, it is now a steaming pile of dog shit. :-( Moscowamerican (talk) 14:47, 21 July 2017 (UTC)

The only thing I've ever done to that extension is update some of its API modules for changes in MediaWiki core. I don't know anything about how it might have worked in the ancient 1.19 version nor how it might have changed since. You might try using the REL_1.27 branch with MediaWiki 1.27; if that too doesn't work, then you can file bug reports in Phabricator, although if you do so I recommend sticking to objective descriptions of the actual problems rather than "it is now a steaming pile of dog shit". Anomie (talk) 16:46, 21 July 2017 (UTC)

Central recursive Test casesEdit

I would permit to Mediawiki to launch groups of tests already running in Central recursive Test cases
Where to find an efficient example? Thanks in advance. --Rical (talk) 18:23, 3 August 2017 (UTC)

Combining characters and mw.ustring.charEdit

Regarding this edit, we (English Wiktionarians) actually do not often concatenate combining characters. It is more common to use them as variables in substitutions, for instance when generating sortkeys in Module:languages, as it is almost impossible to tell what the combining character is otherwise. However, generating the pattern for mw.ustring.gsub does sometimes require concatenation (for instance here). It's a necessary evil. I think it should be mentioned in the Lua manual. — Eru·tuon 19:47, 26 September 2017 (UTC)

mw.ustring.char is mentioned in the manual. But the manual isn't a how-to guide and doesn't need to detail every possible way of doing anything everywhere. Anomie (talk) 21:14, 26 September 2017 (UTC)
Perhaps you are right that mentioning mw.ustring.char in the context of how to generate UTF-8 strings is only appropriate for a how-to guide. I think that makes that section of the manual less helpful. That section does mention using bytecodes, but those are not intuitive and make it difficult to determine what the character is when they are used in modules, as they have no simple correspondence to the Unicode number. They are only understandable for the rare person who can, for instance, convert decimal to binary in your head and calculate the codepoint from the sequence of bits, or who has access to some kind of tool. I encountered various modules using bytecodes for combining characters, and had no idea how to figure out the Unicode number, as I hadn't learned how UTF-8 works and (perhaps like most newbies) hadn't realized somehow that Unicode numbers were different from byte encodings. The best practice for representing characters that do not print well in the text box is probably to use mw.ustring.char with a hexadecimal number, as you can look up the Unicode number and figure out what the character is. — Eru·tuon 20:18, 28 September 2017 (UTC)
Byte codes are mentioned first because that's the paragraph that says that they exist and second to make it clear that there is no Unicode escape. Anomie (talk) 13:36, 29 September 2017 (UTC)
If that is the purpose of the paragraph, perhaps mw.ustring.char should be mentioned in that same context, as it is the approximation of Unicode escapes in Scribunto, though a function and not a syntactic feature. — Eru·tuon 23:31, 5 October 2017 (UTC)

Disabling ScribuntoEdit

Hi Anomie, you reverted my edit on how to remove Scribunto [1]. I understand your concern about giving people instructions to "mangle" their database. I would prefer either a properly programmed removal tool, or a mediawiki that is more resilient to the problem, but those don't exist right now, so when you suggested the implementation of a phabricator suggestion as the solution, that really doesn't address the issue. Put yourself into the shoes of a user who is stuck supporting a wiki that they need to remove scribunto from. Is it better for them to have to kludge together instructions from several talk page entries? At least if it is on the page then any errors can also be fixed, as it should be on a wiki. Maybe flag it with a caution or something, but unless you have a better solution for an affected mediawiki installation, I think deleting the entry was not right. I suppose part of the problem could be addressed with a strongly worded warning to not install this extension since it makes changes to the database that can not be reverted with existing approved tools. It might stop some people from painting themselves into a corner. If I were to add something like that near the beginning of the page, would you be OK with that? Tenbergen (talk) 20:08, 21 September 2019 (UTC)
No, I would not be ok with "a strongly worded warning to not install this extension". If you try to add any such thing you will quickly be reverted. Anomie (talk) 23:11, 21 September 2019 (UTC)
OK, I take back the strongly worded part. How about a neutrally worded warning, then? Disabling Scribunto breaks mediawiki installations to the point of just giving a white page. It does not fail gracefully. Not warning people about that seems against the interests of potential users of this extension. Tenbergen (talk) 19:56, 22 September 2019 (UTC)
Still no. Anomie (talk) 23:36, 22 September 2019 (UTC)

OAuth administratorEdit

Hi. I noticed that you are listed as an OAuth administrator here, but that group was migrated to meta wiki, and no longer has any user rights associated with it here. Any objections to removal? Thanks, --DannyS712 (talk) 05:46, 19 December 2019 (UTC)

recent revertEdit

Your reason for the revert on Extension:Scribunto/Lua reference manual isn't really valid - it might not be strictly a built-in object, but that doesn't change the fact that it doesn't work when used in the loadData case but does when it isn't - it's a minor point of semantics you're trying to bring up, but it still has to be mentioned because you have to change the module code from what is considered "normal use" to get it to work. DSquirrelGM𝓣𝓟𝓒 15:09, 5 February 2020 (UTC)

It's not a "minor point of semantics". No method parameter exists outside of the context of a method. The note at Extension:Scribunto/Lua reference manual#Frame object should suffice. Calling out frame there would just confuse matters for other contexts where it also doesn't exist. Anomie (talk) 17:12, 5 February 2020 (UTC)