[07:00:35] Does anyone know if CirrusSearch can be set to treat "these" quotation marks the same as the cury marks some wikis use? [07:03:09] Someone brought this up recently on Serbian Wikipedia's village pump. They said they couldn't search for this article https://sr.wikipedia.org/wiki/Библиотека_„Јован_Дучић”_(Барајево) if they used straight quotation marks -- "" -- which are the only ones available on a Serbo-Croatian-Slovene keyboard. [07:03:54] I realize one could just make a redirect, but most editors seem to forget to do that. [07:32:11] Hm, I just remembered that "these" are used for exact strings, so that might not be possible. [14:33:32] I'm stuck looking for a specification of the json v2 format that the /w/api.php returns... Is there a general structure or each query returns a different json structure? [15:01:04] yurb: it depends on the action. The list of actions is here https://en.wikipedia.org/w/api.php and clicking on any of them will lead to a dedicated page, where at the bottom you have Example with a link to a sandbox. In there you can execute the request and see the response in json format. This is the best approach I'm aware of :) [15:20:45] Tonina_home: thanks... I'm writing a very very lightweight python wrapper for the API, and I want it to be agnostic of the different actions, ideally. [15:21:24] (I didn't want to use pywikibot or the other wrappers I looked at because they are either incomplete or too complicated with little documentation.) [15:22:01] Examples are great, but ideally they should not be a substitute for a specification [15:22:15] oh cool [15:25:27] yurb: have you looked at mwbot? It's node.js but it might give you some inspiration :) [15:25:56] Tonina_home: thanks, I will look at it:) [15:27:43] wikitools is already completely agnostic AFAICT [15:28:08] you can put whatever arguments you want and it will only handle continuation, perhaps login if you ask [15:30:08] Nemo_bis: "Python 2.5+. Not compatible with Python 3"... [15:33:25] Right. Excellent opportunity for a fork to fix that. :) [15:34:08] Who needs Python 3 anyway, it came out just 10 years ago. ;) [15:36:16] mmh, maybe which needs a feature only available in python 3 [15:36:32] Nemo_bis: I'll keep that in mind (the idea to port wikitools to py3) [15:37:06] Platonides: anything you want to still be useful and working in (very) near future [15:38:42] I missed a "someone" :P [15:38:52] «mmh, maybe someone which needs a feature only available in python 3» [17:53:29] Hello! I'd like to ask somebody (who doesn't have steward right) to make a test edit on this page: https://hu.wikipedia.org/wiki/Szerkeszt%C5%91vita:OrsolyaVir%C3%A1g [17:54:52] In theory, an abuse filter will not let to save the edit. I cannot test it myself, so I'd like to ask your help. [17:55:15] *let saving [17:55:36] Why have an AF for a user talk page? [17:56:35] The user asked it. [17:58:08] But why? [17:58:18] What's the point if no one but a steward can leave them a message? [17:58:19] Because she/he doesn't want that get messages from users whoam don't have at least autoreview right (I don't know the exact English name of the user group). [17:58:32] semi-protect it? [17:59:25] I told her/him that users from other wikis will not be able to edit it and she/he said that it's fine and she/he will use other contact forms. [18:00:33] It is protected, anons cannot edit it. The next level would be admin-only, which is obviously not applicable. [18:04:43] Seems kinda pointless and inefficient [18:06:46] The point would be that avoiding edits from new or young users I think. [18:07:12] With user_rights, autoreview is a possible solution. [18:10:26] File a task requestion addition of autoreview to wgRestrictionLevels [18:11:31] I see. [18:19:55] Thanks for the advice. [22:08:04] Is there a recommended way to get the list of pages whose corresponding talk pages are members of a certain category (through api.php)? [22:08:37] Getting the talk pages is straightforward with list=categorymembers [22:09:07] Getting the corresponding main namespace pages en-masse is not so straight forward... [22:19:39] Okay, I think I've found a solution: generator=categorymembers in combination with prop=info and inprop=subjectid