[03:06:57] Help needed in finding a replacement to the mobile-friendly page content Rest API for my web app [03:06:58] Hello All, [03:06:59] For my website webnomads.in I have been using mobile-friendly page content Rest API for years . Now that it has been stopped I am struggling to find a new suitable API as I was displaying the content in sections . [03:07:01] On various pages I read about making use of parsoids . [03:07:02] While I have explored the different API offerings , I could not find any API which is delivering the text based on sections . I will be very thankful if someone can guide me or point me to any article showing the use of Parsoid or any other way to deliver page content in text form and in sections . [03:07:04] Thanks in advance . [03:07:05] Regards [03:07:07] Harsh [03:20:28] 🛠 Introducing the initial version of ToolWatch - a tool built during Wikimania Hackathon 2023! 🚀 [03:20:28] [03:20:29] ToolWatch checks the health status of tools deployed on ToolForge and presents the information in a visually appealing dashboard. 🎉🔍 No more guessing about tool health – ToolWatch gives you health status at your fingertips! Developed along with Soham. [03:20:31] [03:20:32] 📍Check it out here: https://tool-watch.toolforge.org [03:20:34] [03:20:35] 🌟 Stay tuned for more updates and improvements as we continue to enhance your tool management experience. Your feedback on phab T341379 is valuable in making ToolWatch even better! 🙌 [04:35:16] See https://www.mediawiki.org/wiki/Specs/HTML/2.8.0#Headings_and_Sections (re @pathik410: Help needed in finding a replacement to the mobile-friendly page content Rest API for my web app [04:35:17] Hello All, [04:35:19] For my website webn...) [04:35:37] (from the Parsoid DOM spec) [04:48:08] It is worth noting that sections are somewhat of a hack; MediaWiki allows section headings pretty much anywhere, so there is no guarantee you end up with a DOM which can be neatly split into sections. E.g. https://www.mediawiki.org/wiki/Special:ApiSandbox#action=parse&format=json&text=%3D%3D%20First%20%3D%3D%0A%7B%7C%0A%7C-%0A%7C%0A%3D%3D%20Second%20%3D%3D%0A%7C%7D&parsoid=1&formatversion=2 [04:53:17] <বোধিসত্ত্ব> Something happening with the PAWS? The terminals are unresponsive to commands [08:15:19] Hey there (not too sure where to best ask this): yesterday I directed someone to report a bug regarding a Toolforge against its Gitlab repository − and they hit the roadblock that they needed a Wikimedia developer account. [08:15:19] [08:15:20] I assumed the lack (or impossibility) of SUL has been discussed before, however I could not locate any Phab task for it (whether open or closed) − T274461 makes no mention of SUL I could see ; meanwhile there is T325235 that discusses allowing Github login, so alternative login method do seem to have some merit. [08:15:22] [08:15:23] I would be grateful for a pointer to any relevant decision/discussion/etc. :) [08:17:09] (As for the use-case − it does not feel reasonable to ask editors to sign-up for a Wikimedia developer account just for the sake of filing (or commenting on) a bug-report ; so to me that would rule out using GitLab issue) [08:20:50] I thik the correct venue for filing bugs is to do that on phabricator, Gitlab is only supposed to be for development (AFAIK) [08:36:27] yes, I think we even disable the issues feature on gitlab [08:40:16] Not side-wide, as it seems, per https://gitlab.wikimedia.org/toolforge-repos/multitrack-drafting/-/issues (re @lucaswerkmeister: yes, I think we even disable the issues feature on gitlab) [08:41:10] o_O [08:44:52] apparently you can turn them on in the repo settings [08:45:10] to me that sounds like a bug [08:46:10] T264231 apparently [09:05:33] Thanks ; I rest my case though: where could I find the rationale for not having SUL for GitLab? [09:12:43] I think it is supposed to mirror Gerrit, where you also need a Wikimedia developer account to upload code changes. Additionally, if you really want to contribute, setting up a LDAP account is not very difficult, it's as simple as making a account here https://wikitech.wikimedia.org/w/index.php?title=Special:CreateAccount :) (re @JeanFred: Thanks ; I rest my case though: where cou [09:12:43] ld I find the rationale for not having SUL for GitLab?) [09:19:50] But per T147864, Gerrit not supporting SUL appears to be a limitation rather than a deliberate decision. (re @sohom_datta: I think it is supposed to mirror Gerrit, where you also need a Wikimedia developer account to upload code changes. Additionally,...) [15:28:14] Having bug reports in GitLab is a bug in and of itself. Phabricator handles the SUL + Developer account dual auth problem already. (re @JeanFred: (As for the use-case − it does not feel reasonable to ask editors to sign-up for a Wikimedia developer account just for the sake...) [15:41:09] Any alternatives to https://commons.wikimedia.org/wiki/Data:Wikipedia_statistics/data.tab ? [15:43:58] I can understand why someone wouldn't want to use phabricator for tracking issues in their personal project though. I certainly wouldn't, I've still not worked out how to make the notifications behave sensibly [15:48:50] but it requires providing an email address that will be made public, which seems excessive in general, let alone just for reporting a bug (re @sohom_datta: I think it is supposed to mirror Gerrit, where you also need a Wikimedia developer account to upload code changes. Additionally,...) [16:13:14] Some url's appear mixed up? See for example the Wikiminiatlas (re @gopavasanth: 🛠 Introducing the initial version of ToolWatch - a tool built during Wikimania Hackathon 2023! 🚀 [16:13:16] [16:13:17] ToolWatch checks the health st...) [16:20:57] I'm unsure as to why that happens it seems to be a problem with the tooladmin data that we are pulling, I'mma file a phabricator ticket for it (re @MaartenDammers: Some url's appear mixed up? See for example the Wikiminiatlas) [16:23:47] I personally don't use the notifications feature at all (unless I'm on phabricator at that exact time). I prefer to browse updates on my email client (re @Nikki: I can understand why someone wouldn't want to use phabricator for tracking issues in their personal project though. I certainly ...) [17:47:20] Hi guys, I want a wiki page to be visible only to those with sysop rights, how do I do that? [17:47:39] Don't use MediaWiki? (re @vikipolimer: Hi guys, I want a wiki page to be visible only to those with sysop rights, how do I do that?) [17:48:16] Restricting read access in MediaWiki is quite complicated because it was never designed for it. [17:48:50] Oh wait, delete the page! [17:49:13] I want only sysops to see the page at this link (https://tr.wikipedia.org/wiki/Vikipedi:Konsol_kullanarak_kullan%C4%B1c%C4%B1_taklidi) without the MediaWiki prefix. [17:52:12] Delete it, than it will only be visible for sysops and not normal users (re @vikipolimer: I want only sysops to see the page at this link without the MediaWiki prefix.) [17:53:15] I would like to do that without deletion but anyway thank you! [17:58:21] I don't think it's possible on Wikimedia sites. [18:00:24] I think it's possible to hide all pages from certain users, but not particular pages or namespaces. It may be possible with Some extensions, but they aren't installed on Wikimedia wikis. [18:47:24] Any alternatives to https://commons.wikimedia.org/wiki/Data:Wikipedia_statistics/data.tab ? It does not seem to be updated any longer [23:28:17] https://m.mediawiki.org/wiki/Phabricator/Help/Managing_mail (re @Nikki: I can understand why someone wouldn't want to use phabricator for tracking issues in their personal project though. I certainly ...)