Pppery

Talk page changes

If you're wondering why I deleted or created your talk page, see Structured Discussions/Deprecation. I've been reviewing all Flow boards with only a header and no actual posts, and deleting them or converting them to wikitext. * Pppery * _{it has begun} 01:24, 9 December 2024 (UTC)

Translations:Help:Templates/18/sk

To answer your question, I had reverted that IP edit due to the extraneous trailing "$1" and pointless nowiki pair they added and left behind. Cleaned up (as in your revision) it might well be a better translation, but the IP's previous edit (probably) to a translation unit was to add 2 pairs of useless code tags to the end, giving me low confidence in their translations. Clump (talk) 18:58, 10 December 2024 (UTC)

Yeah, sure, that makes sense. But the version you reverted to was a translation of the older version of the source text, and the "outdated" bit marking that was lost by your reverts (this is a software bug that will be fixed soon). So I was going to restore the outdated bit, and then noticed that there seemed to be a valid update buried in the noise. * Pppery * _{it has begun} 19:01, 10 December 2024 (UTC)

FlaggedRevsConnector extension

I can see that you made some changes on this extension page, I just open a topic about things I found about it. Maybe can you help ? Mahabarata73 (talk) 14:40, 11 December 2024 (UTC)

No idea, sorry. Try asking MLRodrigue instead. * Pppery * _{it has begun} 16:52, 11 December 2024 (UTC)

Ok, thank. Mahabarata73 (talk) 13:24, 12 December 2024 (UTC)

Thanks

Thanks for your change on MWStakeCommonUIRegisterSkinSlotComponents extensions: I saw my error, wanted to cancel it but you did it before me. Mahabarata73 (talk) 21:59, 15 December 2024 (UTC)

Inconsistency

The hook MWStakeRunJobsTriggerRegisterHandlers is visible on this page. This link is visible on this page Category:MWStakeRunJobsTriggerRegisterHandlers extensions — MediaWiki with only one category at the bottom.

The hook MWStakeAlertBannersRegisterProviders is visible on this page hallowelt/mwstake-mediawiki-component-alertbanners. But the link is not visible on this page Category:MWStakeAlertBannersRegisterProviders extensions — MediaWiki (probably better to add it?) and there are 3 categories at the bottom of the page.

I don't know if there are missing categories for the first hook or if there are too many categories for the second one. What needs to be improved ? Mahabarata73 (talk) 22:55, 15 December 2024 (UTC)

Thanks, I've cleaned up a bit. My intention for the category structure here:

Category:Undocumented MediaWiki hooks is for hooks defined by MediaWiki core that nobody has written a documentation page on.

Hooks defined by extensions that exist on MediaWiki.org should have a the hook documentation as a subpage of the extension, like Extension:AbuseFilter/Hooks/AbuseFilter-builder. If no documentation page exists that can either be left red or added to Category:Undocumented extension hooks but since there's no systematic process involving that category creating an empty stub doesn't help anything IMO.

For hooks defined by extensions that don't have standard documentation pages on MediaWiki.org the hook page should just be red. That is Manual:Hooks/MWStakeAlertBannersRegisterProviders shouldn't exist. The category should exist always (because redlinked categories are bad) and should be manually added to Category:Extensions using unrecognized hooks and unlinked. If the external codebase is known a link can be added, but doesn't have to be. I think I must not have been able to find the alertbanners repo when I created that category years ago.

Category:Extensions using redlinked hooks is auto-generated if the hook page doesn't exist. It should be identical to Category:Extensions using unrecognized hooks

* Pppery * _{it has begun} 23:04, 15 December 2024 (UTC)

Ok, thanks. Mahabarata73 (talk) 12:28, 16 December 2024 (UTC)

Hello

Hello Abduvaitov Sherzod 56 (talk) 19:46, 2 January 2025 (UTC)

Yes? * Pppery * _{it has begun} 19:54, 2 January 2025 (UTC)

Autopatrol

Hi there, I got notified you gave me the autopatrol permission. I did not request it formally, was there any reason why? Sorry just checking. Waddie96 (talk) 18:04, 5 January 2025 (UTC)

I give autopatrolled to any editor whose been reasonably active and seems to know what they're doing. * Pppery * _{it has begun} 18:08, 5 January 2025 (UTC)

Ah, thanks for the trust! Waddie96 (talk) 19:23, 5 January 2025 (UTC)

preventing access

Just FYI, but I reverted and fixed your edit at "Preventing_access#Removing_the_Login_link_from_all_pages".  Regarding your comment why would you even want to do this?, removing the public login prompt is very helpful for a single-user private wiki to prevent confusion for people who are viewing the wiki and are presented with a prompt in the corner to log into the wiki which of course doesn't work if user account creation has been disabled. Nicole Sharp (talk) 09:13, 15 January 2025 (UTC)

Noted. * Pppery * _{it has begun} 17:10, 15 January 2025 (UTC)

My rollback on Project:Support desk

Hi Pppery, you're right: I didn't exactly center the message that I left to the User. Thanks for the clarification you've left them, and please accept my apologies for not being clear. The content anyway referred to something that is entirely out of WMF and dev's control and therefore I've decided to remove it. Thanks for your message. --M7 (talk) 16:29, 23 January 2025 (UTC)

Thank you!

Thank you for running recheck for me on gerrit:c/mediawiki/core/+/1113723! :) MolecularPilot (talk) 01:18, 24 January 2025 (UTC)

You're welcome. I've been trying to recheck everyone's patches that need it for a while, but have so many tasks to do and can only keep up with some of them so I'm not perfect at it. * Pppery * _{it has begun} 01:19, 24 January 2025 (UTC)

A barnstar for you!

	The Tireless Contributor Barnstar
	Thank you for your outstanding contributions and dedication to improving the wiki and helping fellow editors! Your work makes a real difference. [[kgh]] (talk) 09:19, 29 January 2025 (UTC)

Add translate tag to the protected page

Hello Pppery! Please, wrap the last paragraph of the protected Parsoid/Parser Unification/Migration page with <translate/> tag for it to may be translated into other languages. Jenesdude (talk) 12:39, 5 March 2025 (UTC)

Done Sorry for the delay in getting to this. * Pppery * _{it has begun} 05:24, 6 March 2025 (UTC)

Thanks! Jenesdude (talk) 05:58, 6 March 2025 (UTC)

Autopatrolled

Hi there, I got notified you give me the autopatrolled permission. I did not requested it formally yet, was there any reason why? Sorry just checking. Also i completed the translation pages such as Extension:AntiSpoof/es, Template:Strong support/es, Template:Strong oppose/es, Template:Support/es, and Template:Oppose/es. USB4215 (talk) 19:12, 6 March 2025 (UTC)

I did not give you the autopatrolled permission. And in my opinion you're closer to getting blocked for messing around then being granted autopatrolled right now. What on earth are you talking about? * Pppery * _{it has begun} 19:14, 6 March 2025 (UTC)

Flow cleanup bot (posting here to avoid accidentally cluttering the thread at the Village Pump)

Firstly, thank you for coding & running Flow cleanup bot :)

I only mention this because I don't think they're currently listed on the bot's userpage as known issues, but there are a couple of differences between Extension talk:Elastica#h-Composer_Install_Failed?-2018-06-03T12:13:00.000Z & Extension talk:Elastica#Composer Install Failed? (imported diff): there's an image in the Flow topic that doesn't seem to have made it into the wikitext version; and there are a bunch of � characters that've been added within the <pre> tags in the wikitext version. (Although, thinking about it, would the latter issue fall under Old posts with <pre> tags get garbled?)

All the best, ‍—‍a smart kitten_[meow] 21:51, 11 March 2025 (UTC)

No, that's not a known issue. The specific <pre> tags getting garbled bug I know about has to do with them being replaced with &lt;pre&gt;, which I now just postprocess the wikitext to undo. Something went direly wrong there that I've not seen before. Unfortunately it's not a bug in the bot code, but instead in the upstream Parsoid API, so there's nothing I can do (which you can see at Special:ApiSandbox#action=flow&format=json&submodule=view-topic&page=Topic:Uecl7etmvwe4tg5x&formatversion=2&vtformat=wikitext). Feel free to report it on Phabricator, though. As long as it's a one-off I'm inclined to let the bot keep running and just fix that page's current revision manually. * Pppery * _{it has begun} 21:55, 11 March 2025 (UTC)

It is still running right now, despite appearing to be silent - it is churning through the support desk, which is eventually going to fail based on its sheer size, but it has to realize that first. When I eventually export the support desk I'm going to have to export each month's worth of topics to a separate archive page in order to keep things a reasonable size! * Pppery * _{it has begun} 22:00, 11 March 2025 (UTC)

That actually touches on one of the things I was curious about - does the bot have a defined maximum wikitext-byte-size that an export should be? Or is it limited by another factor? ‍—‍a smart kitten_[meow] 22:07, 11 March 2025 (UTC)

The current bot run punts if any one revision is more than 100,000 bytes of wikitext or if the total size of the XML to import is >10MB. I plan to process the skipped pages in a later supervised run once the easy bits are done. * Pppery * _{it has begun} 22:10, 11 March 2025 (UTC)

Thanks -- I might report it on Phabricator tomorrow if I remember (& if I work out the actual underlying issue to report!). Looking at the HTML format, it appears that it's converting the \b backspace character to the � character when formatting the topic as wikitext. Interestingly, data about the image also seems to survive when the topic is formatted as HTML. ‍—‍a smart kitten_[meow] 22:05, 11 March 2025 (UTC)

Missing image issue filed as T388687. I’ll file the other one later if I get a chance. Best, ‍—‍a smart kitten_[meow] 15:30, 12 March 2025 (UTC)

I've added the missing image to that specific page. I don't have the motivation to try to find any other examples right now, but anyone else is welcome to. * Pppery * _{it has begun} 17:30, 15 March 2025 (UTC)

Out of interest, do you know off the top of your head any way in which pages/topics with missing images could be found/detected? Don't worry if not. Best, ‍—‍a smart kitten_[meow] 13:32, 21 March 2025 (UTC)

My first thought was to use Quarry to look for all images linked in Flow boards, expecting there to be relatively few of them. Instead there were over 10,000 (quarry:history/85009/987617/957891). But not all of them are missing in the wikitext export. Another idea would be to use Quarry to find images used only in topic namespace (unfortunately no way to get the title of the board from a topic namespace title exists other than screen-scraping or downloading the Flow dumps (!)), but then import is known to not always populate pagelinks tables due to another bug, so ... shrug. * Pppery * _{it has begun} 16:30, 21 March 2025 (UTC)

Continued at phab:T388687, where I found a much better way to detect the missing images. * Pppery * _{it has begun} 00:25, 25 March 2025 (UTC)

A couple more things, just FYI

Just posting here to let you know a couple more things I've noticed, as a courtesy FYI (to be clear, there is no subtext to this! I just thought you might be interested in knowing about these):

• In this imported edit (Flow permalink), the ending </pre> tags were exported as </pre>. (I know this is a known issue, but I just wanted to let you know about this anyway; as - given that I believe the bot fixes these tags in the majority of instances - this may be an edge case.)
• In this imported edit (Flow topic), a link to m:Template:Translatable template is rendered using syntax that (apparently) causes the MediaWiki parser to link to the URL for Template:Translatable+template instead. (Though, thinking out loud, I wonder if that may be more of an issue with the MediaWiki parser than one with the Flow export? IIUC,   is the HTML code for a space, so shouldn't the MW parser be URL-encoding it as %20, rather than +?)

Best wishes, ‍—‍a smart kitten_[meow] 13:31, 21 March 2025 (UTC)

Also, it doesn't seem like <syntaxhighlight> plays well with <translate> - compare [1] with [2] - but I don't know whether that's a bug with Extension:SyntaxHighlight/Extension:Translate or not. Best, ‍—‍a smart kitten_[meow] 14:20, 21 March 2025 (UTC)

I was aware of the first issue already, and did some manual cleanup on a bunch of pages when they came to my attention. It's technically a bot code issue, not a Parsoid bug - I do the hackiest fix possible of string replacing &lt;pre&gt; with <pre> and the same for closing tags in certain circumstances (and I also convert multiline <pre> in indented posts to <syntxhighlight>, which sometimes magnifies the original error), which sometimes matches the opening tag but not the closing tag. The second issue is a legitimate Parsoid bug, probably caused by my patch for T385132 not considering this edge case, but it's probably fairly low-priority for the parsoid team since it only affects converting some wikitext to HTML, changing the config of the wiki in a specific way, and then trying to convert it back to wikitext - the original Flow board probably had [[:m:Template:Translatable template]] and was written before gerrit:298693 so the HTML had a protocol-relative URL which no longer matched the current definition of the interwiki, originally this produced the broken wikitext [:m:foo bar], and I wrote a patch to fix that to produce a working external link in most cases, but apparently not this one.

For the <translate> issue, see Help:Extension:Translate/Page translation administration#Segmentation -

Parsing order. Beware, the ‎<translate>tags work differently from other tags, because they do not go through the parser. This should not cause problems usually, but may if you are trying something fancy. In more detail, they are parsed before any other tags like ‎<pre> or ‎<source>, except for ‎<nowiki> which is recognized by the Translate extension.

I decided several weeks ago that it wasn't a worthwhile use of my time to chase down the infinite long tail of wikitext conversion issues, and what I had was good enough. That may have been a mistake, especially since gerrit:1123696 probably made the wikitext decoding issues worse, but I can't really go back now. * Pppery * _{it has begun} 16:30, 21 March 2025 (UTC)

'Hidden' topics

Apologies if this is already known about (posting here as I can't see it on the bot's userpage) -- Flow topics that have been 'hidden' by a non-admin may not have been exported in pages' histories (e.g., compare [3] with [4]; [5] with [6]). At a (potentially incorrect) first look, it seems like hidden topic(s) might not be appearing in the view-topiclist API response(?)

(By the way, please genuinely tell me if you'd rather I didn't let you know about any more of these that I end up finding - I am very conscious that I've been editing your talk page about this a lot recently.) Best, ‍—‍a smart kitten_[meow] 16:35, 26 March 2025 (UTC)

I checked for hidden posts - I guess I didn't check for hidden topics. There's nothing I can really do about it now, though, as I don't think there's any way of finding them other than digging through dumps. Please don't be discouraged from posting here, even though there's obviously a limit to problems I can realistically fix now that I ran the script weeks ago. (But of course, if I hadn't run the script, these issues couldn't have been found). * Pppery * _{it has begun} 16:38, 26 March 2025 (UTC)

That is I appreciate knowing about these issues, but unless it's something that affects a small number of boards, is easy to fix, and there's a non-awful way of finding all boards affected by them then I won't do anything about it other than note it on the bot's userpage. * Pppery * _{it has begun} 16:45, 26 March 2025 (UTC)

Understood :) ‍—‍a smart kitten_[meow] 16:53, 26 March 2025 (UTC)