Mon, May 13
Thu, May 9
Thanks to everyone! :D
Mon, May 6
As I wrote as clarification, this also happen on enwiki, i follows the user language. Just click on the links and wait a few minutes. Most likely the message cache is somehow stuck in an outdated state.
Sun, May 5
@Nikerabbit Could this be an error due to the update being turned off for a short time?
Tried to go to enwiki, which has the timestamp, and then change the English language to Norwegian Bokmål, and the timestamp goes away.
Actually, you did reproduce the bug.
Wed, Apr 24
Apr 19 2019
Per PHP: function die; die doesn't prevent destructors from being run, so the script doesn't exit immediately, it still goes through cleanup routines.
Apr 11 2019
Not sure I agree with @Esanders, this is detected, as it has nowiki added to *not* being linked. It should just be left alone.
Mar 30 2019
I wonder if it would be better to relate analytics tasks to specific metrics on Wikitech or some other site, as a task only description with no links opens a wast array of possible interpretations. I dumped into this while searching for possible ways of analyzing new contributors, and after more than 10 years on Wikipedia I still have trouble figuring out what this is about.
Mar 29 2019
Seems like something is wrong with the local repo, new clone works.
Mar 23 2019
The same behavior observed at nowiki. It is reported as w:no:Wikipedia:Torget#Overvåkingsliste virker ikke.
Mar 22 2019
Seems like the short form is used inside a paragraph, but the first occurrence use the full form. (example)
Mar 19 2019
This should really be solved somehow.
Mar 14 2019
Nice, really nice!
Mar 13 2019
Could it be the final .2 that creates trouble? Even when removed I can't get the correct book, that is the second bind.
Mar 12 2019
Note that there are several options to do PGP/GPG signing and encryption in the browser. One example in Javacript is OpenPGP.js, but it is probably better to use Web Cryptography API if available. (It is almost universally available now, and should be used.)
Sorry, but this is not the way you should do it. This assumes the uploader in fact reads and understands the schema (s)he is signing, but that newer works. It is also insecure as it opens a man in the middle attack.
Note that "click 'sign this' icon next to a statement" imply a fundamentally insecure and broken process. You don't sign something after it is uploaded, you sign it before and while it is still on your own machine. The JSON code snippet should be signed, and then a provenance for the statement including that snippet should be provided.
Mar 10 2019
A press release from W3 and FIDO; W3C and FIDO Alliance Finalize Web Standard for Secure, Passwordless Logins.
Mar 8 2019
This process is completely and utterly broken.
Still not fixed?
I believe this has been fixed…
The target for the first tab is sometimes the special page with whatever arguments to recreate the page as it is in the current context, and sometimes it is just the pagetitle of the investigation.
Mar 5 2019
Mar 3 2019
Feb 18 2019
Feb 16 2019
Ouch, something I wrote a long time ago…
Feb 13 2019
Does this still happen? I wonder if this is gone now…
See also T150581.
Really weird and confusing, but it is unlikely it will ever be changed. "Its someones baby."
Kvensk (fkv) seems to be added, Romani/Romanes (rom) is added as rmy (?), and Scandoromani/Romani rakripa is still missing.
This was on vagrant, and the gadgets2 role is dismissed.
Feb 11 2019
Feb 5 2019
This was implemented by a slight change to Xt/Xm, I have not seen anything similar.
Feb 4 2019
It does not make sense to keep this open. Closing as declined due to the community, I doubt it will change anytime soon.
Feb 2 2019
Bits and pieces of JSON is available, some documented, some not. It is pretty weird.
Probably just "a random debug spew"
Perhaps if someone else does the followup.
Not sure if it is possible to finish this.
I can't see how this will ever be implemented.
Feb 1 2019
Jan 31 2019
Jan 30 2019
In some cases (all?) warning messages and dialogs should sometime beep when they are created or made visible.
The common assumption that programmers in fact knows how the system they create works… ;)
One such message, that could be an example, is the warning message that comes when the console state is cleared in Scribunto. This message is triggered by previous changes in the module code.
A screen reader has no knowledge about what is and what is not a warning message, except for the standard dialog boxes. I'm not sure we use those, perhaps someone should check.
Jan 29 2019
Jan 27 2019
Jan 25 2019
I wonder if this should have higher priority, as it is pretty damaging for the editors. It is already pretty difficult to convince them to add sources, and fixing encoding errors isn't fun at all.
Jan 24 2019
I wonder if anyone at all read this… Probably none.
Jan 22 2019
Then I guess it is sufficient info to identify the issue. People at nowiki want to clean up the article.
Sharing of configurations is an obvious case, reusing localization is another (importing into Mediawiki-space is not always a good idea), and importing data to be reused by Lua scripts.
Jan 21 2019
Jan 20 2019
My bad, it does a cleanup in the get function
Jan 19 2019
I'm pretty sure I saw some related work less that 3.5 years ago, so it can have been moved somewhere else. Not sure about this, it could be me mixing it up with something else.
Good arguments are always appreciated.
T107119#4684407: The naming schema used for Lua is pretty weird and should be revised. As it is now it creates way to long names without any real need. Such names are only necessary in a system where code can be loaded at will from external sites. Within a controlled system it is not necessary.
Not quite sure if it is related, but the path used in the templatecall seems weird. It does not fail on the path though. The same weird path is used while defining a bunch of roles.
This lib still has the problem that it only makes sense when both Lua and Templatedata exist in the environment. It is a fundamental flaw for several extensions, they add some functionality together with some more or less hack-ish code to figure out whether they shall run in the current environment.
Does this still happen?
This is closed for a wrong reason, and blocks proper localization by using json files. It also blocks use of json-based configuration files, forcing such files into other non-related namespaces.