The ORES extension runs PHP code that calls ORES for damaging and goodfaith only (but others are supported, see the extension.json file). The function that returns the HTTP URL to hit is:

	/**
	 * @return string Base URL plus your wiki's `scores` API path.
	 */
	public function getUrl() {
		$wikiId = self::getWikiID();
		$prefix = 'v' . self::API_VERSION;
		$baseUrl = self::getBaseUrl();
		$url = "{$baseUrl}{$prefix}/scores/{$wikiId}/";
		return $url;
	}

And ores.wikimedia.org is configured as BaseUrl. So in theory we should just add an option to use LiftWing (that could may be rolled out on a few wikis first) it shouldn't be much harder than extending the above function. Since it is the PHP code that calls ORES we should be able to use our inference.discovery.wmnet internal endpoint. I'll try to follow up with Amir to verify if my understanding is right or not :)

More or less copying over a comment from another task that's more pertinent here though likely beyond scope: the ORES Extension has the two MariaDB tables mentioned in the description. They are obvious important to the functioning of the extension but also serve as a public record* of ORES scores that have been used for research. I doubt there are tools that depend on these tables but it's worth recognizing that if there is a way to create a nice public dataset of ORES scores (or really any LiftWing model) as part of this work, that would have research benefits.

Relevant tasks based on quick search: T209611, T209739, T280107

*A poor public record unfortunately as their scope is very unclear and the data schema is very difficult to understand.

In T312518#8239403, @Isaac wrote:

More or less copying over a comment from another task that's more pertinent here though likely beyond scope: the ORES Extension has the two MariaDB tables mentioned in the description. They are obvious important to the functioning of the extension but also serve as a public record* of ORES scores that have been used for research. I doubt there are tools that depend on these tables but it's worth recognizing that if there is a way to create a nice public dataset of ORES scores (or really any LiftWing model) as part of this work, that would have research benefits.

Relevant tasks based on quick search: T209611, T209739, T280107

*A poor public record unfortunately as their scope is very unclear and the data schema is very difficult to understand.

Hi @Isaac! I have a follow up question on the public datasets - Do you think that we need the Mariadb tables for the dumps, or would it be ok to explore alternatives like the mediawiki.revision-score dataset in Hive/HDFS? If the latter is viable we could partner with Data Engineering and see if we can generate a dump from Hadoop. The ORES extension seems something useful for people patrolling Recent Changes etc.., but it seems a stretch to use it for dumps. What do you think?

Do you think that we need the Mariadb tables for the dumps, or would it be ok to explore alternatives like the mediawiki.revision-score dataset in Hive/HDFS? If the latter is viable we could partner with Data Engineering and see if we can generate a dump from Hadoop.

@elukey yeah, I think that would be a much better strategy than the MariaDB tables. I think it's acceptable to have an e.g., 1-month lag for public large-scale access to revision scores and I have found the format of the MariaDB tables to be particularly opaque so would much rather see the scores packaged up in an interpretable format and merged with some other metadata as they are in events. It also presumably has the benefit of not splitting the data across lots of databases and including all scores (not just ones used by the ORES extension).

I just noticed that the message at ores.wikimedia.org seems to imply we are 2 months away from the classic ORES REST API disappearing and everyone needing to use the LiftWing service. I'm wondering if there is still a plan to hard stop at the end of December 2023.

https://ores.wikimedia.org/docs#/default/list_available_scores_v3_scores_get

"This service will be available to support users transitioning to the new infrastructure until December 2023."

It is unclear to me whether there is a comparable REST API via a GET request for ORES, as the documentation at Liftwing seems to indicate the replacement requires a POST request. Any clarification on this would be appreciated.

Also, there are some related unanswered questions here:
https://wikitech.wikimedia.org/wiki/Talk:Machine_Learning/LiftWing/Usage

Hi @Fuzheado!

In T312518#9313661, @Fuzheado wrote:

I just noticed that the message at ores.wikimedia.org seems to imply we are 2 months away from the classic ORES REST API disappearing and everyone needing to use the LiftWing service. I'm wondering if there is still a plan to hard stop at the end of December 2023.

https://ores.wikimedia.org/docs#/default/list_available_scores_v3_scores_get

"This service will be available to support users transitioning to the new infrastructure until December 2023."

It is unclear to me whether there is a comparable REST API via a GET request for ORES, as the documentation at Liftwing seems to indicate the replacement requires a POST request. Any clarification on this would be appreciated.

Also, there are some related unanswered questions here:
https://wikitech.wikimedia.org/wiki/Talk:Machine_Learning/LiftWing/Usage

We are likely not going to make that deadline, we'll probably rework the deprecation message soon to reflect this. Do you have a specific need currently not satisfied by Lift Wing? The GET vs POST change is due to how KServe, the infrastructure layer to handle ML models on k8s, uses: in order to pass a JSON payload we need to use POSTs, that should be inline also with the REST specs.

Let us know how we can help in migrating to Lift Wing, even if we are not likely going to deprecate the ORES API soon, we urge users to migrate to Lift Wing as soon as possible (and to tell us what's missing so we can work on it!).

Thanks for the pointer of the talk page!