Example query: https://quarry.wmflabs.org/query/49456

Hi @Aklapper this is not a bug, but a question regarding whether such API exist.

Boolean is rarely useful for actually modeling information.

Thank you this is important work~ Kudos to the team.
Can we make https://docs.google.com/document/d/1IacO1l5Y0uGrVnOZQ-3JskZaRqtiwqvpAffmAlJZquQ/edit accessible to general reader? I am interested in reading it.

Hi team, am I doing it right? And are you expecting/waiting any additional input along with this request?

That was very helpful, we are now able to create a web service at http://wikiloop-battlefield-dev.wmflabs.org, pointing to http://172.16.0.129:8000 (instace name = wikiloop3)

Problem: can't ssh into the machine.
Following https://wikitech.wikimedia.org/wiki/Help:Accessing_Cloud_VPS_instances

1. created and launched an instance.
2. uploaded public ssh keys to both wikitech
3. try to do

ssh -J zzn_google@primary.bastion.wmflabs.org zzn_google@wikiloop3.wikiloop.eqiad.wmflabs

Thank you @JHedden , do you know if I need to apply for a floating IP addresses?

Thank you all for the approval.

Thank you @bd808 .

@aborrero thank you. While we are waiting for @bd808 to follow up with the VPS creation question, can we discuss the IP forwarding option? Shall I open a new ticket or we can discuss it here?

Thank you @aborrero

It could also work if we do a IP forwarding from WFM Cloud IP range to a GoogleCloud static IP. as per Global IP exempt application the admins has agreed that static IP is policy-wise ok, it's just technically they can't do it on the mediawiki software. Is that something feasible? That way you don't need to allocate additional VPS machines

@bd808 is there any other aspects of the request you expect from us? I can supply other information if that helps~ thank you!

@bd808 Yes, thank you for asking.

Thank you @bd808 for reopen it. Please feel free to ask any clarifying questions.

Great! Thank you @bd808

@bd808 thank you! I can run it now, but now do I need to change anything to wire the new HTTP proxy to node10 instead of nodejs?
I can visit https://tools.wmflabs.org/wikiloop when using nodejs but it shows 502 bad gateway when using node10

Oh, I thought ores.wmflabs.org was the production API. I didn't know the existence of ores.wikimedia.org.

Update: 2019-08-16 C Scot gave a talk in Wikimania2019 and says we will have javascript support in Scribunto engine.
https://upload.wikimedia.org/wikipedia/commons/b/b2/Wikimania_2019_-_Let%27s_Completely_Change_How_Templates_Work%21.pdf

+1

Thank you all, in particular, @daniel for a long explanation.

Yes for EN, and ideally, global , just like tag:HG for Huggle

@CCicalese_WMF could you kindly elaborate? I presume a solution will be a to use the SQL database's text subpattern directly?

Hi @Aklapper, or other dear friends on this task, is it good to proceed to create the tags of {#wikiloop, #wikiloop-battlefield} for us. We start to see usage of our tools and we hope to track the usage and also allow researcher to query and filter them directly.

Side comment: is there a way for developers (who are not WMF staff) to use them in beta?

@Aklapper Hi, could you see if I answered your question?

Waiting for the K8s to be upgraded to modern version.

Oh, Thank you! I was referring to https://meta.wikimedia.org/wiki/WikiProject_WikiLoop, the exact app (early stage) is WikiLoop Battlefield in http://battlefield.wikiloop.org

Slides:

This feature will be helpful (every single revision ):

Hello from 2019!

In T61101#1224049, @Esanders wrote:

I think having to learn Lua is a huge barrier to entry that is preventing wider participation. JavaScript is not just "likely more familiar to our users than Lua", it is, by most measures[1][2], orders of magnitude more popular. By using such an unpopular language we are limiting ourselves to a fraction of potential contributors. I think this runs counter to our mission to "empower a global volunteer community", and I hope this can be made a higher priority in the future.

1. http://githut.info/
2. http://langpop.com/

Here are a few more rationales why this would be helpful:

1. Traffic: it will allow many more editors to see the feature to mark a commit as vandalism in their regular workflow.
2. Expertise: editors usually specialize in certain way(topics, type of edits, etc.), by putting the vandalism labeling in their workflow, this also helps editors who are best to determine vandalism on this article to label it.
3. Real-time: Anti-vandalism is similar to security and anti-abuse technology, the attackers are going to exploit the detection mechanism until the guards are able to find a way to prevent it from happening, so being able to detect new ways of vandalism as they come is critical to prevent new vandalism approaches. Since the commit history are displayed latest first, it allows editors to label the latest commits as vandalisms first, thus greatly enhance the chance a new way of vandalism being detected by real human and then get into training data pipe-line
4. Vandalizer Filtering: by putting it into the history it increases the chance a legit editor seeing it(feature to label vandalism), while reduce a random vandalism who are not super familiar with entire wikipedia edit flow.
5. Awareness: making more editor knows there is an effort fighting vandalism and they have a way to help.