MCS decommission
 | This page is currently a draft. More information and discussion about changes to this draft on the talk page. |
Reasoning task T264671
We are in the middle of a big effort to sunset RESTBase (the underlying proxy between all services), including mobile content service (MCS). It's a multi-year effort with multiple teams and work-streams the final push to deprecate MCS and remove it from our infrastructure, a plan we had before this project started.
Moving forward this committed work will be prioritised and the Content Transform Team won't plan any new APIs or endpoints (JSON or not) unless it overlaps with the work for the Parser Unification (not related with the scope of interest of this topic).
Timelines
Currently there's an active allowed list that won't receive any new additions. The allowed list will stop working soon (tentatively end of September) and the service fully removed from our servers. This allowed list is a temporary compromise for projects that already started migrating away from MCS and reached out before the deadline.
Alternatives
A good candidate for extraction section information is a combination of these Action API requests:
- Get section information for page <PAGE> - https://en.wikipedia.org/w/api.php?action=parse&page=<PAGE>&prop=sections
- Render the output only for the specific section identifier <ID> - https://en.wikipedia.org/w/api.php?action=parse&page=<PAGE>§ion=<ID>