Spawned from T114777: Add Flow contributions to GUC
Flow contributions are not currently included in XTools, e.g.
Spawned from T114777: Add Flow contributions to GUC
Flow contributions are not currently included in XTools, e.g.
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Stalled | None | T136950 Add Flow contributions to XTools | |||
Open | None | T69397 Make Flow database available / accessible on Labs/Tools |
Unfortunately, this is currently completely blocked, since there is neither T69397: Make Flow database available / accessible on Labs/Tools nor T88753: Support Flow changes in Usercontribs API.
@Mattflaschen-WMF Thanks for the pointer - I was in the process of trying to dig into the "tags" system. I'll keep an eye on those tasks and introduce flow contribs to XTools when one or both are resolved.
@Matthewrbowker There are dumps, but you'd currently have to maintain your own DB imported from the XML.
I wonder if that's a good approach to solve T69397: Make Flow database available / accessible on Labs/Tools, though, due to Flow's unique moderation (deletion, etc.) model.
@Mattflaschen-WMF I don't think maintaining our own databases would be a very good use of time or resources. There hasn't been much demand for Flow analysis on XTools.
What is the sticking point of T69397? I confess I'm not very familiar with how Flow functions.
Yeah, I wasn't really advocating it, just mentioning the dumps for completeness. For the second part, I meant that our team could potentially use the dumps to solve T69397 (creating a properly redacted replica everyone could use).
What is the sticking point of T69397? I confess I'm not very familiar with how Flow functions.
Properly redacting private data. The model is different from how wiki content is normally moderated.
We're blocked until T69397 happens, unless there's a way to access flow data via API.