[01:41:03] Default link prefix. Links from this namespace to other pages which do not have a prefix will be treated as if they were prefixed with this text. For example, if this was set to "User", a link in the given namespace [[Dogmaster3000]] would be rendered as if it was written [[User:Dogmaster3000|Dogmaster3000]]. The most common use for this is [01:41:03] https://meta.miraheze.org/wiki/Dogmaster3000 https://meta.miraheze.org/wiki/User:Dogmaster3000 [01:41:03] namespace-internal linking. For example, it could be assumed that any unprefixed link in the "Cookbook" namespace points to another recipe, rather than a page in the Main Namespace. [01:41:04] https://www.mediawiki.org/wiki/Namespace_manager [01:41:04] [url] Namespace manager - MediaWiki | www.mediawiki.org [01:41:04] How can enable this feature on my newly defined namespace on my miraheze instance? [01:41:04] [url] Dogmaster3000 - Miraheze Meta | meta.miraheze.org [01:41:06] [url] User:Dogmaster3000 - Miraheze Meta | meta.miraheze.org [01:42:33] https://pustaka.miraheze.org/wiki/abc:Def [01:42:34] It keeps linking to the main namespace. [01:42:34] [url] abc:Def - Pustaka | pustaka.miraheze.org [01:49:07] I don't believe this feature exists in MediaWiki [01:54:14] Oh, Rtnf, I just replied to you on community noticeboard. I'm not quite sure what you're trying to do, though [01:55:44] Rtnf, oh note the note at the top, that was a potential idea for a future MediaWiki release. The page has been tagged for archival purposes [01:56:31] We basically have something very similar with Special:ManageWiki/namespaces, though [01:58:27] I'm looking for easier way to do namespace-internal linking. [01:58:27] We at the Bluepages community have a discussion regarding how to split the project for each country. https://www.bluepageswiki.org/wiki/User_talk:Reschultzed#Local_Language? [01:58:28] The consensus is : split this wiki to several "sub-wiki" by using namespace. [01:58:28] [url] User talk:Reschultzed - Bluepages | www.bluepageswiki.org [02:23:20] Rtnf, yeah, but why can't you have the prefix as part of the wikilinks? I mean, potentially you could use interwiki prefixes here [02:24:04] It's a bit unconventional in terms of using interwiki but, essentially, you'd create a `prefix` for each of your namespaces, then link to `[[prefix:page name|optional displayed text]]`? [02:24:04] https://meta.miraheze.org/wiki/prefix:page_name [02:24:11] [url] Prefix:page name - Miraheze Meta | meta.miraheze.org [07:50:26] Namespace manager sounds interesting [13:49:31] Made a task here: https://phabricator.miraheze.org/T7516 [13:49:32] [url] ⚓ T7516 Run deleteArchivedRevisions.php | phabricator.miraheze.org [16:34:10] What's the word on this? https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/YR3X4L2CPSEJVSY543AWEO65TD6APXHP/ [16:34:11] [url] Security and maintenance release: 1.31.15 / 1.35.3 / 1.36.1 - Wikitech-l - lists.wikimedia.org | lists.wikimedia.org [16:57:04] @Blackwolfe it's being worked on as we speak :) [16:57:09] see the -sre relay channel :) [17:02:10] MediaWiki should have a built in system for minor updates like this [17:05:16] what do you mean by built in? I don't see how that would work since we need to pull the Git changes [17:09:53] @Lake: git pull https://github.com/wikimedia/mediawiki 1.36.1 && git push [17:09:54] [url] GitHub - wikimedia/mediawiki: 🌻 The collaborative editing software that runs Wikipedia. Mirror from https://gerrit.wikimedia.org/g/mediawiki/core. See https://mediawiki.org/wiki/Developer_access for c | github.com [17:10:03] that would have been all needed [17:13:39] Reception123 I mean, would be nicer if these things could be changed separately. Because I imagine this is going to look like installing MW over again [17:13:53] no [17:14:06] this is one of the simplest i've seen tbh [17:14:39] (but in any case, I think updates should be less frequent, unless it's an emergency security update) [17:15:00] this is a security update [17:15:18] CVE-2021-35197) SECURITY: Prevent blocked users from purging pages. [17:15:38] yeah, I've seen that, but I mean only emergency security things [17:15:57] yeah no we'd rather quicker security fixes [17:16:03] not slower [17:17:55] Can I point out though that the issue did cause a live incident [18:08:46] How did a blocked user purging pages cause an incident? [18:10:18] I hope it wasn't DefenderPlate. Void already locked the account anyway [18:17:18] Upstream incident [18:17:23] Read the task [18:19:35] Alright. I'll have a look. [18:21:59] For some reason, I can't seem to find that specific task. [18:25:30] DarkMaggerMan4500: https://phabricator.wikimedia.org/T280232 [18:25:31] [url] ⚓ T280232 Uncached wiki requests partially unavailable due to excessive request rates from a bot | phabricator.wikimedia.org [18:25:36] uup, typo [18:25:43] DarkMatterMan4500: ^ [18:26:08] Okay, I'll look there. [18:27:35] Oh, so it was just a bot? [18:29:15] @Voidwalker [18:34:48] Would a xml dump ever need to be cut into two in order to import it to a mediawiki instll? [18:36:20] Or could a say 1 GB xml be inported just fine? (or even a 5 GB or 10 GB xml) [18:39:35] I believe it would be imported fine, but you would absolutely need to do the import server-side (importDump.php) [18:51:31] Thanks, as I kinda think cutting the dump might damage it [18:52:03] Would a 10 GB dump import fine? [19:27:35] Ah, that makes it more clear, Thanks. So the issue was twofold, the bot at the time doing more than could be handled at that time (even if the rates should normally be supported) and also that blocking the bot did not stop it from purging. [21:19:00] hi [22:02:37] Would User:! ! ! ! ! ! ! ! ! ! ! ! ! ! coochie be against the username policy or no? [22:30:51] Not necessarily against the letter, IMO, but it could certainly be seen as disruptive and/or trolling. Also, I'm not bothered about policing old accounts with no edits. [22:31:59] Alright