[09:24:57] MediaWiki 1.35+ should come with RESTbase bundled, right? [09:25:49] I'm trying to figure out how to get it set up correctly, since VisualEditor fails to contact parsoid. [09:28:45] I thought maybe I had to install it from source with git, but that fails at npm install due to insufficient permissions, so I'm guessing that's probably supposed to be for development. [13:10:45] It's been a few hours, so I'll ask this again. I'm trying to install the MediaWiki RESTbase server via instructions here: https://www.mediawiki.org/wiki/RESTBase/Installation, but I'm hitting a snag with npm install giving a permissions error on the github.com/wikimedia/content-type repository, even when I'm able to git clone it outside the script. [13:11:11] I made sure to set up a key and link it to my account, and I was able to even use that key to clone private repos. [13:14:47] sorry, i don't know how to help, but can i ask why you're trying to install it? at the WMF we're currently struggling to deprecate and uninstall it ;) [13:15:29] What's the current supported API, then? [13:15:35] We need one for a mobile app. [13:15:41] I thought RESTbase was replacing the PCS [13:16:24] Plus we need Parsoid for the VE, and I've been under the impression that that was a part of RESTbase. [13:16:31] (We're behind a proxy) [13:16:35] https://www.mediawiki.org/wiki/API [13:16:55] i don't know about mobile apps, but VE has not required RESTBase for a while now [13:17:18] the good parts of RESTBase have been integrated into the MediaWiki REST API, and VE uses that now [13:18:14] i don't remember exactly, but i think 1.35 was the first version that didn't need it, and in 1.41 it finally worked well out of the box [13:24:21] Really? We had trouble with it complaining about parsoid not being found [13:24:28] When we upgraded to 1.35 anyway [13:28:42] is there a reason you aren't updating to 1.39 (LTS) or newer? [13:35:31] I'm doing that right now [13:36:01] The 1.35 upgrade was a year or two ago [14:23:35] What is the current preferred mobile API solution? I know MobileContentService was removed from the extension. Should we just transition to the REST API? [14:23:53] Just trying to figure out if we need another service on top of REST or not [14:57:43] Okay, I keep losing internet but I just want to know more about how Page Content Service replaces the Mobile Content View. https://www.mediawiki.org/w/index.php?title=Page_Content_Service does not offer any information about what provides the service, how to start it, etc. [15:02:22] jfolv_: are you really using those services for anything? [23:12:59] Dreamy_Jazz: I think we could try getting our both globalblocks schema changes in one task for dba to apply to prod (my change: https://gerrit.wikimedia.org/r/c/mediawiki/extensions/GlobalBlocking/+/998583)