<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Il 06/04/2015 08:27, Golden Ring ha scritto:<br>
<blockquote
cite="mid:CAKaDXE5138u5txxZw4pZP20CgSdO4UkqL-8a66R3GjLDTvF13Q@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On 6 April 2015 at 14:03,
Ricordisamoa <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:ricordisamoa@openmailbox.org"
target="_blank">ricordisamoa@openmailbox.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"><span class=""> Il
06/04/2015 02:18, Golden Ring ha scritto:<br>
<blockquote type="cite">
<pre>I've been thinking recently about how to do recent changes patrol
better. I've prototyped a tool, which you can see at
<a moz-do-not-send="true" href="http://recent-changes.appspot.com/" target="_blank">http://recent-changes.appspot.com/</a>.</pre>
</blockquote>
<br>
</span> Nice. It reminds me of <a
moz-do-not-send="true"
href="https://tools.wmflabs.org/pltools/rech/"
target="_blank">rech</a>...<span class=""><br>
<br>
</span></div>
</blockquote>
<div><br>
</div>
<div>Yes, very similar concept. Is there a reason that
rech is wikidata only?</div>
</div>
</div>
</div>
</blockquote>
<br>
I guess that is because its author, <a
href="https://www.wikidata.org/wiki/User:Pasleim">Pasleim</a>, is
mainly active there and didn't think it may have been useful to
other projects. Or maybe it's supposed to implement some
Wikidata-specific features in the future.<br>
<br>
<blockquote
cite="mid:CAKaDXE5138u5txxZw4pZP20CgSdO4UkqL-8a66R3GjLDTvF13Q@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"><span class="">
<blockquote type="cite">
<pre>This is currently implemented on Google AppEngine, basically
becausethat's what I had to hand when I set out and already knew
something about using. It uses the MediaWiki API to retrieve diffs.
This is not ideal for a few reasons, not least because it wouldn't
take very heavy use of the tool before I'd have to start paying for
it, which would probably mean putting ads on it. I can't be dealing
with all that.</pre>
</blockquote>
<br>
</span> I suppose the cost is related to Google charging
for bandwidth use beyond a threshold?<br>
Since the app needs JavaScript anyway, you could simply
retrieve recent changes on the client, thus avoiding
much of the server-side traffic.<span class=""><br>
<br>
</span></div>
</blockquote>
<div><br>
</div>
<div>Yes, Google charges for both CPU time and bandwidth use
beyond the free quota (1GB bandwidth either way + 28
instance-hours per day).<br>
</div>
<div><br>
</div>
<div>Retrieving changes from the client side was what I
attempted first, but of course it has to be hosted
somewhere, and unless that's on the wiki concerned, then
you have to deal with the cross-site nature of the API
requests. My impression is that this requires the wiki to
be configured to explicitly allow requests from the domain
serving the page.</div>
</div>
</div>
</div>
</blockquote>
<br>
Just pass dataType: "jsonp" to $.ajax(), it will magically work! (<a
href="https://www.mediawiki.org/wiki/Manual:Ajax#Limitations">background</a>)<br>
<br>
<blockquote
cite="mid:CAKaDXE5138u5txxZw4pZP20CgSdO4UkqL-8a66R3GjLDTvF13Q@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div><br>
</div>
<div>[snip] </div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"><span class=""></span>
Labs is precisely for external tools, and I'd say Tool
Labs best fits your needs.<br>
To enhance MediaWiki's built-in patrolling
functionality, you should read <a
moz-do-not-send="true"
href="https://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker"
target="_blank">this</a> instead.<br>
<a moz-do-not-send="true"
href="https://lists.wikimedia.org/pipermail/wikimedia-l/2014-October/075137.html"
target="_blank">Use your judgement and common sense</a>
to decide whether it's better to develop your tool on
Tool Labs or as part of MediaWiki (either core or an
extension).<span class=""><br>
<br>
</span></div>
</blockquote>
<div><br>
</div>
<div>I'm not absolutely clear on the best choice here. On
one hand, I'd like the tool to end up something like <a
moz-do-not-send="true"
href="https://en.wikipedia.org/wiki/Special:NewPagesFeed">Special:NewPagesFeed</a>.
I guess this points towards developing it as built-in
mediawiki functionality, rather than an external tool. On
the other hand, I've developed it because I actually want
to use it; my impression is that getting changes into
mediawiki, and then deployed onto en wikipedia, is not
easy. Probably for pretty good reasons, but still not
easy.</div>
</div>
</div>
</div>
</blockquote>
<br>
Only you know how your tool will look like :-)<br>
Special:NewPagesFeed is provided by the <a
href="https://www.mediawiki.org/wiki/Extension:PageTriage">PageTriage
extension</a>, so if your goal is to improve it or build upon it
tightly, here you go.<br>
If you're still undecided, I advise you to install
MediaWiki+PageTriage on your device and have a look at the code
while experimenting with Tool Labs.<br>
<br>
<blockquote
cite="mid:CAKaDXE5138u5txxZw4pZP20CgSdO4UkqL-8a66R3GjLDTvF13Q@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div><br>
</div>
<div>If I go down the external tool route, then I guess the
tool gets hosted at eg. <a moz-do-not-send="true"
href="http://tools.wmflabs.org">tools.wmflabs.org</a>;
is that right? On the other hand, an external tool hosted
there doesn't have access to the production wikipedia
databases and would have to continue getting data through
the mediawiki API; is that right?</div>
</div>
</div>
</div>
</blockquote>
<br>
#1: yes. Follow the links at <a href="https://tools.wmflabs.org">tools.wmflabs.org</a>
to create a Labs account (if you don't have one yet), request access
to the Tools project and create a new tool. It will be hosted at
tools.wmflabs.org/<yourtoolname>.<br>
#2: no. Tools accounts have access to replicas of the production
databases with private data redacted: read <a
href="https://wikitech.wikimedia.org/wiki/Help:Tool_Labs/Database#Connecting_to_the_database_replicas">Connecting
to the database replicas</a> for access. However, some data are
only exposed via the API, and (my understanding is that) databases
are generally only used directly in performance-critical
applications which benefit from the power of SQL.<br>
<br>
<blockquote
cite="mid:CAKaDXE5138u5txxZw4pZP20CgSdO4UkqL-8a66R3GjLDTvF13Q@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div><br>
</div>
<div>TBH I'm not sure I've got a lot of clue about the
architecture of MediaWiki; is it described anywhere,
beyond, "It uses PHP, MySQL and jQuery"?</div>
</div>
</div>
</div>
</blockquote>
<br>
It seems you're asking for the <a
href="https://www.mediawiki.org/wiki/Developer_hub">Developer hub</a>,
though it may be hard to grasp for a 'newb' ;-)<br>
<br>
<blockquote
cite="mid:CAKaDXE5138u5txxZw4pZP20CgSdO4UkqL-8a66R3GjLDTvF13Q@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div><br>
</div>
<div>Sorry for having so many questions!</div>
</div>
</div>
</div>
</blockquote>
<br>
You're welcome!<br>
<br>
<blockquote
cite="mid:CAKaDXE5138u5txxZw4pZP20CgSdO4UkqL-8a66R3GjLDTvF13Q@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div><br>
</div>
<div>Regards,</div>
<div>GoldenRing</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"><span class=""> </span></div>
</blockquote>
</div>
<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Labs-l mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Labs-l@lists.wikimedia.org">Labs-l@lists.wikimedia.org</a>
<a class="moz-txt-link-freetext" href="https://lists.wikimedia.org/mailman/listinfo/labs-l">https://lists.wikimedia.org/mailman/listinfo/labs-l</a>
</pre>
</blockquote>
<br>
</body>
</html>