Update: I intend to migrate it but it might take some more time. (I was not the original maintainer and still don't know how the code is organized well.)

Can the MinMT suggestion be converted into something like a beta feature, in which MinT results will be shown to users who explicitly have agreed to test it?

I largely agree. I tried https://translate.wmcloud.org/ and encountered the same pattern of errors including weird puctuation and spacing in Japanese. (All English commas and periods seem to be left untranslated, and would need to be revised by human.) Here is the result for the pre-filled text about Jazz:

My 'brute-force' method was pretty simple. I manually tried different images one by one and eventually found one that doesn't say logrotate is not found when executing "logrotate --version". Maybe I just got lucky when I hit it fairly soon. "Find an image that doesn't fail at command X" could perhaps be made as a script, though.

There were some problems but I think I sorted them out.

I am struggling to find an image containing logrotate (or its alternative). I have been using /usr/sbin/logrotate to rotate log files daily.

This might be a tangent but

I didn't migrate it because I couldn't figure out how to use venv inside kubernetes properly. I think I now know how.

@Esanders Thanks for the pointer. I believe the CSS solution would allow [[トーク:あ]] to be stylized as "トーク：あ" (or very similar to that). However, I would also want [[トーク：あ]] (in wikitext) to be an alias of or a redirect to [[トーク:あ]] and I don't think that's possible with CSS. Perhaps it was unclear with the description I wrote 10 years ago (!). I will try revising it later.

@Xqt You are right, the patch works as described in this task's description. I only skimmed the code and misunderstood how it works. (I should have tested it at least before commenting, sorry.)

Is this the same as T312773?

@MPhamWMF If the Search team doesn't want to keep owning the task, I think we can just remove the "Discovery-Search" tag. In fact, it looks like this task was only added to "Discovery-Search" in 2021, after 10 years.

You are right, saying the current behavior is to sort by the last post is wrong. I will change the description and the title.

FYI: https://www.mediawiki.org/wiki/Talk:Reading/Web/Desktop_Improvements#Jawiki_has_NOT_reached_consensus_on_implementing_Vector_2022_yet

(For future reference) T301649 changed the URL of the pageview service. The change of the URL had to be reflected on an allowlist used by popular ad blockers and privacy plugins: https://github.com/easylist/easylist/pull/11049

Is this different from T12268?

https://ticket.wikimedia.org/ redirects to https://ticket.wikimedia.org/otrs/index.pl which contains "otrs". Does this have to be changed, too?

This seems to overlap with T124841.

Yes, let's close. It might have been slightly better if we made the bahavior configurable, but after 4+ years, I guess the benefit of doing so now is little to none. (Most people would not be using the older versions of MediaWiki any more.)

If no, are there any reasons we could not run WHOIS commands from Clouds machines and cache them in a database?

There might be a common cause, but I think the old task was about edits. My problem here is about bot actions, not bot edits.

In T276613#6887916, @MisterSynergy wrote:

Just for the sake of completeness, I added some of the log items in concern into the description.

whois.toolforge.org is now using ST47's patch. (Thanks again.) @ST47, are you going to send a pull request and get it merged to the upstream repository? That would be better for long-term maintainability.

Ah, that's right. Then there is no reason to withhold it, at least as a short term fix. I'll think about things like highlighting missing information later. Thank you for your help.

In T265784#6565219, @ST47 wrote:

I tried using ST47's version of ipwhois on a test instance, while not changing the original tool yet. However, it looks like currently the block is lifted? I see no difference in the results - both work.

Is the problem larger than the current title and description of this task suggest? The title of this task only mentions mailing list descriptions. Yet the two comments on Oct 18 say that we have a problem in body text of individual emails, at least more recently, too.

• I'm wondering if the whois tool at toolforge should have some mechanism of throttling, if it was the culprit.
• Was there a large amount of automated access to RIPE via the the whois tool? I cannot verify because as a tool maintainer I don't seem to be able to see recent access logs.

In the case of Japanese, the encoding set by the server was euc-jp, not ascii. When I manually override the encoding in the browser side, it is fixed until I reload. (Tested on Mozilla Firefox 81.0)

@Tacsipacsi
The description says "to all Wikipedia talk pages and potentially, other projects." :) I suppose Wikipedia must be supported for this task to be resolved while others might be optionally supported along the way.

Thanks, it looks good to me. :)

In T251693#6109510, @alexhollender wrote:

As far as I can tell they are quite similar. I think the appropriate process here might be to start a discussion on the Talk page of the logo itself? https://commons.wikimedia.org/wiki/File:Wikipedia-logo-v2-ja.svg

Resolved by https://github.com/whym/whois-gateway/pull/15, thanks to @QEDK.

Was there anything you can share from your private correspondence? I don't always ask this, but the public discussion here and on-wiki seem to be pending on what you might have been discussing privately.

Note to @Jeff_G: you might still see the bug on Commons, but that's expected. It might take some time before I update ArchiverBot@Commons to reflect the bug fix. (Maybe next weekend.)

Which URL should I use instead? There is https://afrinic.net/whois/ but I'm not sure I can directly link to a search result there. (It's a dynamic tool.)

Sorry, the link in the description was not adequate - it was done before I updated Pywikibot. I replaced it with newer examples.

@Dvorapa in which commit was it fixed?

For the record, the problem seems to have been resolved before I do anything. Ideally I'd like to know the reason in order to prevent similar issues in future, but I'm not really sure.

If the two time scales are still needed, I would suggest using longer forms ('600min' and '2mon'') or full spells ('600minute' and '2month', not sure if it should be plural or we should support both). The only problem for me was that it was confusing to have to distinguish minutes and months using lowercase 'm' and uppercase 'M'.

I think so, unless there are still plans/needs for supporting minute and month.

@Tacsipacsi Do you think T191901 addresses that? Allowing to set a wiki-wide default setting sounds like a good idea, but a separate one.

Description edited - hopefully this is now more discoverable by keywords like 'Mobile.css'.

Thanks - the workaround suggested there seems to work for me for the moment.