Skip to content
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

Using Wikipedia APIs mobile-sections endpoint is deprecated #1664

Closed
johngian opened this issue Oct 13, 2022 · 7 comments · Fixed by #1903
Closed

Using Wikipedia APIs mobile-sections endpoint is deprecated #1664

johngian opened this issue Oct 13, 2022 · 7 comments · Fixed by #1903
Assignees
Milestone

Comments

@johngian
Copy link

Related to: https://phabricator.wikimedia.org/T319303

It looks like kiwix is using the mobile-sections endpoint served by Wikipedia REST API:
https://en.wikipedia.org/api/rest_v1/#/Mobile

This endpoint is considered deprecated and we are working towards sunsetting it.
Instead of mobile-sections its suggested to use the page content for mobile and specifically:
https://en.wikipedia.org/api/rest_v1/#/Page%20content/getContent-mobile-html

@johngian johngian changed the title Using wikipedia APIs mobile-sections endpoint is deprecated Using Wikipedia APIs mobile-sections endpoint is deprecated Oct 13, 2022
@kelson42
Copy link
Collaborator

@johngian Good to know, nee to read more about the rationals behind this. Hopefully the new end-points are not too different.

@kelson42 kelson42 added this to the 1.13.0 milestone Oct 16, 2022
@kelson42
Copy link
Collaborator

@johngian It seems the old is deprecated, but I wonder that you recommend to use a new API end-point which is effectively tagged as « experimental » and therefore not productionreqdy!? See https://de.wikipedia.org/api/rest_v1/#/Page%20content/getContent-mobile-html

@Jaifroid
Copy link
Collaborator

Jaifroid commented Jan 1, 2023

Given some outdated information as reported in #1397 is caused by using the deprecated mobile-sections API, and that this is only going to get more urgent, we need to work out what is needed to make this switch. I don't know these APIs well, but from what I can see, the mobile-sections endpoint produces JSON or something similar, whereas mobile-html produces (evidently) html.

@kelson42 kelson42 modified the milestones: 1.14.0, 1.13.0 Jan 1, 2023
@Exponent4806
Copy link

Exponent4806 commented Jan 1, 2023

this is only going to get more urgent.

@kelson42 Using the deprecated mobile-sections API is a really severe issue. It is really frustrating for users and editors.

For example:

In 2021, I added more than 500 photos in the German Wiktionary. Not a single of those photos appear on the .zim version of the Wiktionary. Also, many translations and definitions are missing. Every month the issue is worse !

By the way, @johngian thanks for opening this issue on GitHub. I am the author of the "Bug report" on Phabricator.

@kelson42
Copy link
Collaborator

kelson42 commented Jan 1, 2023

for the moment I'm a bit puzzled:

  • new endpoint is still experimental
  • reference links don't work in both directions
  • I see strange edit icon at the right of each section title
  • Sections are not collapsable (strange for a mobile output)

It seems simply not really ready to me.

On the top of this, I don't understand and I'm not informed about the high level plan and rationals:

  • why changing of end-points? What are the differences between the old and the new end-points.
  • why shoukd we move if there is already a plan to deprecate Restbase?

Do we have any document allowing to better unterstand what is going on at Wikimedia APIs?

@Jaifroid
Copy link
Collaborator

Jaifroid commented Jan 2, 2023

@kelson42 It looks like mwoffliner can get the scripts and styles needed for the mobile view by using this part of the API:

https://en.wikipedia.org/api/rest_v1/#/Page%20content/get_page_mobile_html_offline_resources__title___revision_

@stale
Copy link

stale bot commented May 26, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be now be reviewed manually. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants