[00:00:04] [HUGGLEBUILDER] Building a nightly build 20150528 x64 debian package [00:08:41] [HUGGLEBUILDER] huggle_20150528-nightly_amd64.deb is ready for download at http://huggle.wmflabs.org/builds/huggle_20150528-nightly_amd64.deb [00:12:03] [HUGGLEBUILDER] Win32 huggle version is ready for download at http://huggle.wmflabs.org/builds/windows/huggle.zip [01:15:01] Change on 12en.wikipedia.org a page Wikipedia:Huggle/Users was modified, changed by Radon210 link https://en.wikipedia.org/w/index.php?diff=664352288 edit summary: Adding [[Special:Contributions/Radon210|Radon210]] ([[WP:HG|HG]]) [06:52:42] magioladitis: hello! [08:00:01] GitHub [8huggle/huggle3-qt-lx] benapetr pushed 1 commits into branch master: https://github.com/huggle/huggle3-qt-lx/compare/fac81d18f0ee...15f0ef279d83 [08:00:01] GitHub [8huggle/huggle3-qt-lx] commit by benapetr (Petr Bena) https://github.com/huggle/huggle3-qt-lx/commit/15f0ef279d837be6f14cda4a81f50fe2a1151122 show version for every change [08:15:03] halfak: can you send me a link to that revision score thing on labs? [08:15:12] I found only source code so far [08:15:29] Sure! [08:15:46] http://ores.wmflabs.org/scores/enwiki/?models=reverted&revids=4567890 [08:16:12] Note that we're not guaranteeing stability yet, but it should be good for testing. [08:16:15] where can I find the interface where someone can pick what score edit should have [08:16:37] https://en.wikipedia.org/wiki/Wikipedia:Labels [08:16:49] For english. The interwiki links will bring you to local wikis. [08:16:55] ok [08:17:48] so this interface basically sends data to your scoring system which then use them to self-learn how to classify future edits? [08:18:32] which means, if I incorporate this into huggle, people can use this interface to tell huggle (indirectly) which edits are more likely vandalism? [08:22:40] halfak: one more thing, that interface you made at "ores" how do I figure out the wiki name, eg /scores/WIKINAME/ is there some table of all wikis? does this feature work for every wiki we have now? [08:23:14] for example what would be english wikiversity and what about commons? [08:24:32] petan, we use dbnames, you can check the available dbnames by dropping the dbname from the url. [08:24:39] ok [08:24:42] e.g. http://ores.wmflabs.org/scores/ [08:24:56] Right now, we only have 4 models loaded, but we have 10 models built and tested. [08:25:07] So, we'll be standing up a bunch more soon. [08:25:21] We've been focusing on performance improvements in the meantime. [08:26:00] Also, re giving us data, we'll probably want to do it separate from Wikilabels. Wikilabels is more designed for curated samples (i.e. random). [08:26:06] what is "prediction" http://ores.wmflabs.org/scores/enwiki/?models=reverted&revids=664387741 I suppose this score means true for "yes this is vandalism"? [08:26:18] But I can make an endpoint to send huggle evals to so we can use it to check against our predictions. [08:26:48] The 'reverted' model predicts whether or not the edit should be reverted -- not necessarily vandalism. [08:27:06] right [08:27:07] Once we complete our enwiki campaign in wikilabels, we'll load up a model for 'vandalism'. [08:27:20] We're 85% done [08:27:32] Other wikis are farther behind. [08:27:54] But the 'reverted' model seems to be quite useful assuming we have a human in the loop. [08:28:11] well, huggle can be used to revert edits only as well (it has AGF reverting) it's just that it basically filters out everyone who is at least a little bit trusted, so it happens rarely that you see an edit made by regular contributor in huggle's queue [08:28:30] so it can be used for other stuff than just reverting vandals :) [08:28:45] Oh! One more thing. You'll get better performance if you ask for scores for many revisions at a time. [08:28:50] Use "|" to separate. [08:28:56] Multiples of 50 work best. [08:29:11] e.g. http://ores.wmflabs.org/scores/enwiki/?models=reverted&revids=664387741|456789 [08:29:58] given the way how huggle fetches edits from its providers that is not easy to implement, it literally fetches them one by one, and queuing them somewhere just to get a single-query here probably would hurt performance [08:30:37] petan, OK. No worries. We're working agressively towards being performant for that use too. [08:30:46] It's good to know that this is what you are looking for. [08:40:17] GitHub [8huggle/huggle3-qt-lx] benapetr pushed 1 commits into branch master: https://github.com/huggle/huggle3-qt-lx/compare/15f0ef279d83...bf1640f2d06d [08:40:17] GitHub [8huggle/huggle3-qt-lx] commit by benapetr (Petr Bena) https://github.com/huggle/huggle3-qt-lx/commit/bf1640f2d06d49a58cc50e9c0f941c6cfe7daf0f no more instant reverts by default Now the instant reverts need to be explicitly enabled in configuration, this makes it possible to cancel reverts by default. It will make huggle slower by 6 seconds per revert but it might help lower down the amount of reverts that were caused by misclicks and so on. Basically now when you hit the revert button, huggle will wait for few seconds before it actually performs the revert. We had this feature all time, but it wasn't enabled by default. This will affect new huggle installations only. [09:55:06] 10Huggle: Huggle crash, with system log info. - https://phabricator.wikimedia.org/T100631#1317076 (10Aklapper) (For future reference, please associate a [[ https://phabricator.wikimedia.org/project/query/active/ | project ]] to tasks. Thank you a lot!) [11:15:06] GitHub [8huggle/huggle3-qt-lx] benapetr pushed 1 commits into branch master: https://github.com/huggle/huggle3-qt-lx/compare/bf1640f2d06d...4c53ab49f9f9 [11:15:06] GitHub [8huggle/huggle3-qt-lx] commit by benapetr (Petr Bena) https://github.com/huggle/huggle3-qt-lx/commit/4c53ab49f9f949706ae5770b8361e339adaac1e5 mutex fixes There was a problem with Q_ASSERT condition probably caused by missing lock [11:16:57] GitHub [8huggle/huggle3-qt-lx] benapetr pushed 1 commits into branch master: https://github.com/huggle/huggle3-qt-lx/compare/4c53ab49f9f9...c2235e16f6cc [11:16:58] GitHub [8huggle/huggle3-qt-lx] commit by benapetr (Petr Bena) https://github.com/huggle/huggle3-qt-lx/commit/c2235e16f6cc70dc23faf1247b6205af8d8bce29 exception fix