In T3886#59810, @Bawolff wrote:

Note, there is now interwiki stuff in the api:

All links to wikibooks using b prefix: https://en.wikipedia.org/w/api.php?action=query&list=iwbacklinks&iwblprefix=b

All interwikis on main page:
https://en.wikipedia.org/w/api.php?action=query&prop=iwlinks&titles=Main%20Page

There's not really any special page web interface to this though that i am aware of...

Of course doing this in a cross wiki fashion (anything that links to this specific page from any other wiki) is much harder.

In T47514#3612154, @Seb35 wrote:

@jcrespo Wow. It sounds like the documentation for temporary tables needs a gigantic "Pitfalls" section describing shortcomings in the implementation(s). And the semantics seemed *perfect* for use with read-only replicas, too :-(.

In T179628#3762918, @Marostegui wrote:

@Dispenser but on that missing_entries.sql there are tons of things that wouldn't work with the current and new replicas if I am not missing something.
You are basically using your user (I assume yours) database, which will no longer be there as these hosts are RO.

In T66721#1411737, @ori wrote:

In T66721#1411731, @SamB wrote:

So, um, any tips on how to manually clean up the MediaWikiModuleStore keys from all of the wikipedias on Firefox/Iceweasel, including 31.7.0esr as included in Debian Jessie?

It should not be possible to fill it up now that the patch above has been pushed. You must have gotten into some weird state. Clear localStorage (either by nuking your browser history or by using https://addons.mozilla.org/en-US/firefox/addon/volatile-storage/?src=cb-dl-updated) and see if the problem recurs.

So, um, any tips on how to manually clean up the MediaWikiModuleStore keys from all of the wikipedias on Firefox/Iceweasel, including 31.7.0esr as included in Debian Jessie?

In T66721#1340106, @matmarex wrote:

While the last patch may be helpful, it still does not prevent the cache from taking up all available localStorage space.

There should be no need for anyone to upload .ogg versions of MODs; it's easy enough to render them server-side, if not in client-side JavaScript. (Is render the right word for this?)

From https://commons.wikimedia.org/wiki/File:Kitten-stare.jpg

Something like http://quarry.wmflabs.org/query/3610 could be useful to find pages like this on any given wiki; unfortunately, quarry doesn't support just running the same query against a different wiki.

In T54564#836125, @Jane023 wrote:

It would be more constructive if the complainers here would just go and create those articles instead of trying to create interlanguage redirects.

Which is to say, it seems kind of silly to have T89598: Convert Template:Authority_control to Lua and use Wikidata waiting on T89002: multi-lingual label usage [Tracking].

@Lydia_Pinscher: does commons really need to use the labels right off the bat anyway? For example, authority control stuff shouldn't be affected by the whole multilingual label tracking thing, should it?

So, um, I'm seeing these deprecation warnings (for importScript) on Wikidata ... that doesn't seem very resolved.

It would preferably be possible for this to just magically work on Institution and Creator pages that already supply the wikidata parameter to the respective template, whether they explicitly invoke {{authority control}} or not. Is that a thing that can be done?

Well, it seems to mostly work all of a sudden (any idea why?); it just needs to include the label/aliases and work also on links in main/property namespaces. (Yes, sometimes the label will be redundant, but not always.)

The hovercards seem to actually mostly work now, so I guess this should be closed if someone can explain how that happened?

In T52372#544516, @SalixAlba wrote:

What would be nice is if action=purge would force templatedata updates, like null edits do. This is necessary as many templates are protected so only admins can do null edits. Any editor can do an action=purge (I believe).

In T65549#954394, @Krinkle wrote:

Closing as the Typography Refresh is over. The remaining issues that were marked as blocking this weren't blocking this as they were filed after the implementation landed. Some of them are regressions, other are ideas for further enhancements. They've been updated accordingly to be their own task.

Oh, okay ... I kind of thought the day I go to bugzilla. and get here had to be >= day one ...

Isn't it a bit late to be announcing day 1?