User Details
- User Since
- Oct 9 2014, 8:09 PM (492 w, 4 d)
- Availability
- Available
- LDAP User
- Tacsipacsi
- MediaWiki User
- Tacsipacsi [ Global Accounts ]
Yesterday
Sun, Mar 17
This is a Minerva-specific skin style (introduced in 83dccd47636841d9c75f55f6b8a9cbe7de934650), so it should be fairly easy to convert it to LESS and use design tokens? On the other hand, it will only fix Minerva; other skins are even more awful from a design viewpoint (e.g. the same message on Vector 2022, with non-standard background color #eaf3ff and non-standard text color #000 – although, at least, this overrides both the background and text color, so it will be just way too bright in night mode rather than unreadable).
The documentation in mediawiki.page.preview.js appeared during the JSDoc migration, in commit 2d4257305963, so it’s no surprise that it’s not duplicated in JSDuck. And during copying documentation around, it came that both copies are slightly different (minor punctuation and formatting differences), so they cannot automatically be de-duplicated. I see two options:
Fri, Mar 15
Thu, Mar 14
Isn’t this a bit too early? There are wikis that aren’t on Vector 2022 yet, will readers of those wikis never see the hint?
Please make the CM panel more discoverable. I know the CodeEditor panel exists, I use it every now and then, yet I struggle each time recalling/finding out the hotkey.
Wed, Mar 13
I still don’t understand why you changed your minds about how required the edit summary should be, but as long as T359984 will get implemented, I’m fine with it.
I tried a random URL from your stack trace, and it opens correctly in my browser, so it doesn’t sound like 64f44423eedd91160c727f8642c8ebce0dabc3e9 would be the culprit. 6fe410491f1e1f285ef48e7855a984e8d0345674, however, could cause issues. fetch is experimental in Node.js 18 LTS and 20 LTS, becoming stable only in Node.js 21 (non-LTS) and, consequently, in 22 LTS (to be released next month). Which Node.js version do you use?
Tue, Mar 12
This is now unblocked, isn’t it?
Ideally, switching Flow to readonly would happen a few weeks or months after moving all Flow pages away, so that active discussions started with Flow could be finished with Flow (but due to them moved away, new discussions would naturally be started using DiscussionTools/wikitext).
Mon, Mar 11
Why editinterface, why not a configuration variable on LocalSettings.php? The namespaces are also defined through code (LocalSettings.php and extensions), so it seems more logical to also define their use there.
mw.language:getDir() in Lua is often not suitable because […] it's easy to run into the limit on how many times you can use it on a single page.
That’s quite long ago. 🙁 I wish it would be fixed (by using URL escapes), but who knows how many templates were built around this buggy behaviour in the past thirteen years…
Sun, Mar 10
Thu, Mar 7
I’m not sure if this is a good change. With the reminder approach, the user needs to acknowledge the reminder, which a) makes sure that they noticed it and b) makes sure that they can’t accidentally (e.g. by pressing Enter while focusing on the wrong button) submit the edit without the summary. With the helper text approach, neither is true.
I’m okay with displaying the diff on a different screen, as long as it’s a real diff.
Both increasing the minimum number of digits and emptying the repos would break existing links. Couldn’t the above patch work with a bit different syntax?
Wed, Mar 6
Could someone review this patch? It’s been waiting for a +2 for over two years now.
Tue, Mar 5
Looking at the “diff”, it’s everything but a diff – a diff highlights the differences, i.e. both the old and new values. Could this “diff” be modified to show the old values as well?
Thanks for the explanation! So the concern is the amount of outgoing mail, specifically the amount of mail going out from the production mail server (or amount of mail having the sender wiki@wikimedia.org?).
Thanks for noticing it! Fixed. However, I’m not sure if the mistake was really on the wiki page, or {{TRANSLATIONLANGUAGE}} should respect <nowiki> tags. I’d say it should respect them – although it may not be trivial to make it do so.
Why should this exception use the bot flag rather than bot membership? If admins are exempted based on group membership, why should this be changed for bots? As for the window, it’s quite uncommon to add a user to the bot group or remove it from the group in the middle of an editing session. If a user gets added to the bot group, it usually happens after at least a few hours of inactivity after the last test edit, and it also means that it’s generally trusted – both its edits that it makes after being added and the ones that it has made before that. If a bot is malfunctioning or the community doesn’t trust it for some other reason anymore, it’s blocked, not removed from the group. Removal from the group usually happens after months or years of complete inactivity – well, if the jobs haven’t been processed for months, we have bigger problems than whether the edit gets automoderated. 🙂
Mon, Mar 4
Sat, Mar 2
See description.
This means that the documentation is somewhat machine-readable (although there is no machine-readable connection between the command being scrollToCaretPosition and the options being a scrollToCaretPositionCommandOptions object) but still partly duplicated – the content after one of: needs to be copy-pasted from the actual description and thus can get out of sync.
Fri, Mar 1
Thu, Feb 29
A drawback of bundling is that it doesn’t happen when the notifications are delivered by email. It’s not necessarily a bad thing to get separate emails about separate groups, though (it can help e.g. if one uses emails as a todo list or uses filters to put mails about different message groups in different folders).
Wed, Feb 28
I also experienced a long delay when migrating https://commons.wikimedia.org/wiki/Template:PD-Hungary to the Translate extension last Sunday: I marked the page for translation at 14:12 UTC, and Special:Translate became functional around 14:30 UTC. Until then, directly editing the Translations-namespace pages worked (but only because I knew which pages I had to edit, a newbie won’t guess them), although they didn’t show the English text above the edit form.
Tue, Feb 27
Do the two provide the same performance under MariaDB? BETWEEN is more specific and thus feels to be more performant, but I can also imagine that they translate to the exact same query plan.
Mon, Feb 26
I don’t know how the code works, but this is how the boolean parameter type on the API main page is defined, and indeed https://translatewiki.net/w/api.php?action=query&meta=siteinfo&siprop=usergroups doesn’t return group membership counts, while https://translatewiki.net/w/api.php?action=query&meta=siteinfo&siprop=usergroups&sinumberingroup=0 does (sinumberingroup is documented to be boolean).
Sat, Feb 24
Three test articles:
- sr:Č – exists (and redirects to Ч)
- sr:Budimpešta – doesn’t exist, but its Cyrillic equivalent does.
- sr:Budimpešt – doesn’t exist, neither does its Cyrillic equivalent
Thanks for the fix! I can confirm that the article appeared in my reading list in the alpha app.
Thanks, that was quick! The new version doesn’t crash anymore, but I’ve found another issue: T358426: Places: Unable to view article on map if device location access is denied. I really don’t want to allow access to my location. 😀
This may affect more than just the documentation. In JSDuck, these methods, documented as @private, were available (if one clicked on a link in the textSelection() documentation or checked Private in the Show menu) while they were clearly marked as something you shouldn’t (and, in fact, can’t) use directly. In JSDoc, it was decided that private methods don’t appear at all in the documentation. I see three options:
Fri, Feb 23
Actually, this has nothing to do with <languages/>: it appears at the top of the page and highlights outdated translations if and only if there are outdated translations. It appears at the top even if <languages/> is not at the top or it isn’t used at all.
The system could resemble Growth team's Community Configuration.
If it just walks back, shouldn’t it find <a href="/%E7%89%B9%E6%AE%8A:%E7%94%A8%E6%88%B7%E8%B4%A1%E7%8C%AE/BugCatcher" title="特殊:用户贡献/BugCatcher">贡献</a>, a contributions link, before running into the <img> tag?
This varies by user. Probably nobody expects others to use × on talk pages, but there are users (including me) who expect themselves to be precise even on talk pages.
Thu, Feb 22
Widget installation
2. Search 3. Featured article
Does this screenshot mean that the links will be autonumbered external links? These should be avoided if possible: they look ugly and has accessibility issues. I’d write
Tue, Feb 20
Mon, Feb 19
Maybe for performance as well, but not only: if I have to scroll over 15k group names, I feelingly never reach the end of the page, which makes it less helpful for humans.
Yes: if a parameter is boolean, any value (even empty ones) count as true, only omitting the parameter entirely counts as false (in line with the HTTP/HTML/whatever spec). This would be a breaking change, which is what @Reedy meant with “I can understand it may not be able to be one easily, due to the underlying usages”.
There are hundreds of languages (language, sourcelanguage), and on Meta, over 15,000 groups. I don’t think listing all those would make the help page more usable. main:uselang doesn’t list all possible languages either. However, more information on how to find out the list of possible values could be helpful.
@ovasileva Another acceptance criterion was added in T356821#9552036, which hasn’t been confirmed yet – and couldn’t have been, as the patch is currently under review. (I’ve now added a beta cluster link as for that AC as well.)
Okay, thanks for the explanation!
I’ve just realized that $wgEnableEditRecovery is still disabled on all production wikis except for testwiki. Is this intentional? When do you plan to enable it as an opt-in beta (i.e. $wgEnableEditRecovery = true; $wgDefaultUserOptions['editrecovery'] = 0;) on other wikis?
Since the train arrived, I’ve missed
- Wikidata constraint report updates that are done exactly to highlight potential issues that should be handled by humans;
- FuzzyBot edit marking translation as outdated, i.e. in need of human review (fortunately I was the translation administrator triggering the edit, so I knew of it, but updating other languages may take a few years more because of this), due to T62000#1688226;
- InternetArchiveBot edit marking an external link dead and not automatically rescueable, i.e. in need of a human who can find it or an equivalent source at another URL;
- Commons edit request list update, a bot edit whose sole purpose is making the backlog more visible to humans;
- and probably more things, which I haven’t even realized I’ve missed.
Sun, Feb 18
Why was it changed to <a role="button"> rather than a <button>? <a> is for things that go somewhere; this toggle does something.
Feb 16 2024
@ovasileva It took me a while to understand what you mean, so I’ve updated the title and description to make it easier to understand. Is it okay for you? Or did I maybe still not understand correctly what you mean and updated them with a misinterpretation?
There’s already a patch to fix (but at the same time deprecate) this usage at https://gerrit.wikimedia.org/r/c/mediawiki/core/+/985035. Maybe you could weigh in about whether to deprecate on Gerrit.
Feb 13 2024
Then it’s okay. Your message sounded like you want to contradict me.
@dcaro I’m not a maintainer of this tool, but hasn’t it long been migrated away from the grid? https://grid-deprecation.toolforge.org/t/ato lists no grid jobs, even though the bot is running continuously.