[03:49:00] 10Scoring-platform-team, 10Edit-Review-Improvements-RC-Page, 10MediaWiki-extensions-ORES, 10Collaboration-Team-Triage (Collab-Team-Q1-Jul-Sep-2017), 10Schema-change: Index on oresc_probability, temporarily or permanently - https://phabricator.wikimedia.org/T175778#3634198 (10jmatazzoni) [17:02:50] harej: there? [17:03:07] It’s codezee [17:32:21] ebernhardson: o/ I have a crazy question about Flow. We have some free-form text entry for one of our systems (JADE), where people can post comments critiquing ORES judgments. I’m trying to offload the whole suppression/editing thing to an existing service, and was thinking that we might just post into Flow and only store the post URL. [17:32:47] So something like, https://www.mediawiki.org/wiki/Topic:Ry6o4jowf78f34gp#flow-post-ry6o5niswvf6gpue [17:49:43] awight: plausible i suppose. correctly handing suppression is highly contentious and probably a great idea to figure out before going live [17:50:40] Yeah I’m really interested in not even touching that part. [17:52:30] A few details have me stumped, though—like where these posts would appear on wiki. Many wikis (?) haven’t and won’t enable Flow, so we’ll have to host comments on a central wiki, but with some overlap in the adminships? [17:52:56] Donno what the path would look like, either :-/. or if Flow posts can exist without being anchored to a wiki path? [18:33:39] 10Scoring-platform-team (Current), 10Collaboration-Team-Triage, 10ORES: Make RCFilters compatible with both the old and new thresholds APIs - https://phabricator.wikimedia.org/T175053#3636396 (10awight) [20:34:19] 10Scoring-platform-team, 10User-Zppix: Grant Zppix access to ORES project - https://phabricator.wikimedia.org/T176805#3637079 (10Zppix) [20:34:34] awight: ^^ [20:58:36] awight: flow posts have to be owned by a topic, topics have to be owned by a "topic list" which for all intents and purposes is a wiki page. One plausible solution i suppose would be to create a wiki page and then use that for everything [20:59:25] awight: sadly the flow api is not the most obvious thing ... but everything that can be done in the web ui can be done through the api (underneath its all the same code) [20:59:27] ebernhardson: Do you think there will be bad side-effects if we scale… real big? [20:59:35] ok this is great news. [20:59:55] awight: in theory, an incredibly large topic list shouldn't have any particular problems. In practice not 100% sure [21:00:14] awight: you see my ping? [21:00:30] Zppix: yes, thanks for making that task! [21:00:40] let me know if i did it wrong xD awight [21:00:48] ebernhardson: hehe we’ll put it to the test. [21:01:16] ebernhardson: question? why must it be flow? [21:01:52] Zppix: it doesn't have to, but awight asked above because flow already supports all the suppression/spam/etc stuff that editors will require as minimum viable features of anything that takes arbitrary user input and displays it [21:01:54] Since we probably don’t want to browse the topics, it would be fine to have some arbitrary sharding thing. $rootPage/$wiki/$randoshard [21:02:08] Zppix: ^ ebernhardson has it right [21:02:39] I can’t imagine any other system that would support onwiki administration and ownership of freeform text. [21:02:42] i see... makes since... (i have a strong dislike for flow) [21:02:54] gotta keep them newbies out /s [21:03:04] Wide open to listen to any alternative ideas! [21:03:06] ebernhardson: thats why mw has page protection xD [21:03:28] My main requirement is that I don’t have to rewrite any moderation, auditing/history, or editing code :p [21:03:55] awight: i mean just use a normal non flow page and page protect it [21:04:01] i mean its easier then flow api use [21:05:13] I’m not sure what the benefits are. Why do you dislike Flow? [21:05:55] it feels to forum-like to me [21:09:55] lolol [21:10:00] sorry it makes you feel that way. [21:10:31] halfak still out for awhile awight ? [21:11:27] Haven’t seen him in ages ;) [21:11:41] same, hes always here xD [23:58:38] 10Scoring-platform-team (Current), 10Collaboration-Team-Triage, 10ORES: Make RCFilters compatible with both the old and new thresholds APIs - https://phabricator.wikimedia.org/T175053#3638265 (10awight) Deploying this without a break in service might be tricky. The new API cannot return the old format test_... [23:59:20] (03PS1) 10Awight: [WIP] Support new thresholds API [extensions/ORES] - 10https://gerrit.wikimedia.org/r/380893 (https://phabricator.wikimedia.org/T175053)