This user name is for dewiki blocked and suppressed, but the line in Special:Users is not crossed out. When you have suppress user rights (oversight) then you can read the line crossed out. Here the line is not crossed out. What is wrong? What did I understand wrong?

But otherwise the software isn't doing what I expect. If I suppress a user name locally then I expect, that the user name can't be reading publicly locally by any users any more. That's the result of a suppression and should work. And some years ago, I don't have the exact date, it worked properly. We have a big bunch of suppressed user names from some years ago that cannot be read publicly.

Who of WMF I have to contact to wipe those user names entirely? In dewiki it's unfortunately not very rarely, to suppress such harmful user names.

@Urbanecm: Isn't it the easiest and fastest way to change the wiki software like:

@Tacsipacsi: This is one more indenting error using DiscussionTools, see this diff https://en.wikipedia.org/w/index.php?title=Wikipedia:WikiProject_Resource_Exchange/Resource_Request&diff=prev&oldid=1185375661

I would be glad about an outage report in next TechNews, thank you.

They're increasing for now: https://replag.toolforge.org/

But these are thoughts about alternative solutions (?)

One question in mind: Why do we really need a PNG rendering of SVG files? Let's use SVG as SVG and all will be happy. When we need thumbnails or gallery pictures of SVG files we should show minimized SVG (you can minimize and maximize SVG without to produce pixel sludge).

step 2: coding talk pages call to database (wkat1)

thanks for this very fast reaction on it

okay, seems to be repaired, it's working now

a screenshot

others have equal problem, see https://en.wikipedia.org/wiki/Wikipedia:WikiProject_Resource_Exchange/Resource_Request#A_Had_Day%27s_%27Night%27

the URL is https://wikipedialibrary.wmflabs.org/

The database basics for this job by TaxonBota are already well developed. The job will be done with the daily bot run.

reassigned

unassigned as Aklapper wanted

Looks good now, thank you!

In T315893#9118097, @Esanders wrote:

In T315893#9118084, @DLynch wrote:

action=history winds up using a completely different path to generating the title

See also:
https://en.wikipedia.org/w/index.php?title=IPhone&action=history
vs
https://en.wikipedia.org/wiki/IPhone

I'm missing this colon space in discussion page histories like https://de.wikipedia.org/w/index.php?title=Diskussion:DocMorris&action=history

In T315893#9109017, @XanonymusX wrote:

In T315893#9108971, @doctaxon wrote:

No, I disagree but you are wrong too. The words within the page title name indeed should be spelt orthographically. But the colon is not an orthographically colon but a namespace separator within the title database item, and with this it's programming language but not German language with its orthography. In spite of this the page name title is written in the URL without blank or separator, too. Why do we need such differences.

As I said, once it is presented prominently to our readers, text needs to comply with spelling rules. Most readers are completely unaware of namespaces. It would never be acceptable to have such a technical use of punctuation in page titles in ns-0; in other namespaces it is less dramatic, but still not great. Another idea I had in mind for quite some time would be to distinguish the namespace through a different colour (something grey, I guess) or font. The way it used to be written is definitely not what should be aimed for in the long run …

In T315893#9108949, @Aklapper wrote:

In T315893#9108853, @doctaxon wrote:

Where is the discussion, done before this change, where communities had the possibilities or the opportunities to agree or disagree with this.

@doctaxon: Offtopic, see https://www.mediawiki.org/wiki/Bug_management/Development_prioritization#Why_wasn't_I_consulted_about_these_changes%3f

In T315893#9108902, @XanonymusX wrote:

In T315893#9108778, @doctaxon wrote:

This has nothing to do with German spelling but with namespace separation. So the blank style is a programming language spelling mistake. I never saw this spelling within any other programming using namespaces.

Text that is presented to our readers necessarily needs to comply with spelling and typography rules. So imo it makes a lot of sense to differentiate between what is used internally (URL etc.) and what is displayed to everyone. I have long proposed a similar thing for subpages; however, in that case it is more complex, as the slash needs to be distinguished from the title itself first.

Where is the discussion, done before this change, where communities had the possibilities or the opportunities to agree or disagree with this.

In T315893#9108838, @Nardog wrote:

Any reference to a page that does not match what the top heading looks like on the page itself is going to be perceived as a mistake. If communities can override it then it shouldn't be imposed on them in the first place, because they didn't ask for it.

This has nothing to do with German spelling but with namespace separation. So the blank style is a programming language spelling mistake. I never saw this spelling within any other programming using namespaces.

I agree to @Nardog s comment above and I am not convinced that we really need this separator style, Nardog has explained his reason, and this is my reason too.

@Samwalton9 : I reinstalled Chrome now. JSTOR is working fine now.

@Esanders : isn't it possible to avoid the text intending colons at the beginning of the gallery lines when publishing the reply? Isn't it programmable maybe?

@Samwalton9 : But I already deleted the cookies! When JSTOR is working again, it leads to the same error in short time when trying to search anything with JSTOR.

@Aklapper But what then is the reason that this png rendering does work, and without any problems:

@ssastry : Another solution is, to except .js pages from being categorized by syntaxhighlight-source-category. What do you think about this?

That's what I mean, so let's give wikitext parsing knowledge about both methods of JS comment syntax. There's no reason that tags within commented out lines should be handled like real working tags.

You know such things better than me, thanks!

I got these spaces too, and the same if using safemode, also with both legacy Vector and Vector 2022 - but also under the tab Structured Data.

@matmarex Thanks a lot

@cscott @matmarex The bug isn't resolved, see https://de.wikipedia.org/wiki/Spezial:ApiSandbox#action=parse&format=json&page=user%20talk%3ADoc%20Taxon%2FTest&prop=sections&formatversion=2

Please can we get a statement in Tech News about what happened here?

okay, feel free to update tcl/tk

Why 8.6? There's already tcl/tk 8.7 out.

Hi @cscott : I'm pretty sure, you're still working on a fix. But there are still bots and LUA templates down because of missing sections content. Is it possible to give this task more priority? Thank you and kind regards.

Like I could determine action=purge on file description page has a visible result in 40% of all usages, not more. And this is very little. And it doesn't help to purge this more than once.

Sorry, it was a misclick. I removed the tag.

Thanks a lot! Can we make a user notice in the TechNews about it?

But you can't change the size, if the thumbnail is listed on category pages or in the Commons file version list. You can't change all the thumbnails, if the new uploaded file version is already linked in hundreds of articles globally.

I also think it's important to know. Please publish it in Tech News.

In T332650#8770440, @doctaxon wrote:

@Tgr Trying to login to Wikipedia Library I and a fellow Wikipedian get "Access token generation failed, please try logging in again." meaning to "See T332650 for more information". Can you help?

@Tgr Trying to login to Wikipedia Library I and a fellow Wikipedian get "Access token generation failed, please try logging in again." meaning to "See T332650 for more information". Can you help?

Thank you very much ...

@Andrew @bd808 Since ToolsDB change the tool https://toolsadmin.wikimedia.org/tools/id/stimmberechtigung gives https://stimmberechtigung.toolforge.org/ 504 Gateway Time-out.

I tried a forcerecursivelinkupdate purge once more, without success