-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add annotations for ORES revision scores #43
Conversation
1cb7d96
to
b8c8760
Compare
@Krinkle: just checking if you noticed this proposal. |
|
||
// Find all revids names inside the feed | ||
revids = []; | ||
$feedContent.filter('.mw-rtrc-item').each(function () { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Using $.map()
would simplify this code:
revids = $.map($feedContent.filter('.mw-rtrc-item'), function (node) {
return $(node).attr('data-diff');
});
map() automatically filters out undefined/null from attr().
// Todo: reduce this once ores has better performance | ||
// https://meta.wikimedia.org/wiki/Research_talk:Revision_scoring_as_a_service#ORES_performance_improvements | ||
timeout: 30000, | ||
dataType: 'jsonp', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Using JSONP means cache will still be broken because of the callback parameter. I've filed an issue upstream (https://github.com/wiki-ai/ores/issues/45) to support CORS/JSON instead.
BTW, ORES now supports CORS from Wikimedia sites. |
fa3621d
to
129c7c0
Compare
The probabilities are obtained from ORES server. For details, see: * https://meta.wikimedia.org/wiki/Objective_Revision_Evaluation_Service * https://meta.wikimedia.org/wiki/Research:Revision_scoring_as_a_service
Updated to not use 'jsonp'. |
Thanks! |
The probabilities are obtained from ores server. For details, see: