Wikitext-l January 2016

wikitext-l@lists.wikimedia.org

4 participants
8 discussions

Deprecating rest.wikimedia.org in favor of /api/rest_v1/
by Gabriel Wicke 15 Apr '16

15 Apr '16

We have decided to officially retire the rest.wikimedia.org domain in favor of /api/rest_v1/ at each individual project domain. For example, https://rest.wikimedia.org/en.wikipedia.org/v1/?doc becomes https://en.wikipedia.org/api/rest_v1/?doc Most clients already use the new path, and benefit from better performance from geo-distributed caching, no additional DNS lookups, and sharing of TLS / HTTP2 connections. We intend to shut down the rest.wikimedia.org entry point around March, so please adjust your clients to use /api/rest_v1/ soon. Thank you for your cooperation, Gabriel -- Gabriel Wicke Principal Engineer, Wikimedia Foundation

1 1

Re: [Wikitext-l] [Mediawiki-api] [Engineering] [Wikitech-l] Deprecating rest.wikimedia.org in favor of /api/rest_v1/
by Gabriel Wicke 02 Feb '16

02 Feb '16

Luigi, On Thu, Jan 28, 2016 at 2:09 AM, XDiscovery Team <info(a)xdiscovery.com> wrote: > I tried /rest_v1/ endpoint and it is terribly fast. that is great to hear. A major goal is indeed to provide high volume and low latency access to our content. > @Strainu / @Gabriel , what does 'graph' extension do ? If you refer to https://en.wikipedia.org/api/rest_v1/?doc#!/Page_content/get_page_graph_png…, this is an end point exposing rendered graph images for https://www.mediawiki.org/wiki/Extension:Graph (as linked in the end point documentation). > I have few questions for using proxy cache: > 1# Is it possible to query a page by page_ID and include redirect? We don't currently provide access by page ID. Could you describe your use case a bit to help us understand how access by page id would help you? > /page/title/{title} > allow to get metadata by page, including the pageID , but I would like to > have final page redirect (e.g. dna return 7956 and I would like to fetch > 7955 of redirected 'DNA' ) We are looking into improving our support for redirects: https://phabricator.wikimedia.org/T118548. Your input on this topic would be much appreciated. > /page/html/{title} get the article but page_ID / curid is missing in source > I would like to get the two combined. This information is actually included in the response, both in the `ETag` header and in the <head> of the HTML itself. I have updated the documentation to spell this out more clearly in [1]. The relevant addition is this: The response provides an `ETag` header indicating the revision and render timeuuid separated by a slash (ex: `ETag: 701384379/154d7bca-c264-11e5-8c2f-1b51b33b59fc`). This ETag can be passed to the HTML save end point (as `base_etag` POST parameter), and can also be used to retrieve the exact corresponding data-parsoid metadata, by requesting the specific `revision` and `tid` indicated by the `ETag`. > 2# The rest are experimental: > what could happen if a query fail? > Does it raise an error, return 404 page or what else? The stability markers are primarily about request and response formats, and not about technical availability. Experimental end points can change at any time, which can result in errors (if the request interface changed), or return a different response format. We are currently discussing the use of `Accept` headers for response format versioning at https://www.mediawiki.org/wiki/Talk:API_versioning. This will allow us to more aggressively stabilize end points by giving us the option of tweaking response formats without breaking existing clients. > I am thinking if possible to use api.wikipedia as fallback, and use proxy > cache as primary source any ajax example for doing that to handle possible > failures? Yes, this is certainly possible. However, you can rely on end points currently marked as "unstable" in the REST API. Basically all of them are used by a lot of production clients at this point, and are very reliable. Once we introduce general `Accept` support, basically all of the unstable end points will likely become officially "stable", and several `experimental` end points will graduate to `unstable`. > 3# Does /rest/ endpoint exist also for other languages? Yes, it is available for all 800+ public Wikimedia projects at /api/rest_v1/. [1]: https://github.com/wikimedia/restbase/pull/488/files#diff-2b6b60416eaafdf0a… -- Gabriel Wicke Principal Engineer, Wikimedia Foundation

2 3

Re: [Wikitext-l] [Mediawiki-api-announce] Deprecating rest.wikimedia.org in favor of /api/rest_v1/
by Luigi Assom 29 Jan '16

29 Jan '16

Hi Gabriel! please read below comments, and remaining questions are: - how to extract _ID from ETag in headers: GET /page/title/{title} - how to ensure GET /page/title/{title with different char encoding or old titles are always resolved to last canonical version} [i registered this email after reply, sorry for eventual cross-posting] On Fri, Jan 29, 2016 at 6:42 PM, Gabriel Wicke <gwicke(a)wikimedia.org> wrote: > Luigi, > > On Thu, Jan 28, 2016 at 2:09 AM, XDiscovery Team <info(a)xdiscovery.com> > wrote: > > I tried /rest_v1/ endpoint and it is terribly fast. > > that is great to hear. A major goal is indeed to provide high volume > and low latency access to our content. > > > @Strainu / @Gabriel , what does 'graph' extension do ? > > If you refer to > > https://en.wikipedia.org/api/rest_v1/?doc#!/Page_content/get_page_graph_png… > , > this is an end point exposing rendered graph images for > https://www.mediawiki.org/wiki/Extension:Graph (as linked in the end > point documentation). > Oh very interesting! So basically html markup can be extended ? Would it be possible to share json objects as html5 markup and embed them in wiki pages? > > > I have few questions for using proxy cache: > > 1# Is it possible to query a page by page_ID and include redirect? > > We don't currently provide access by page ID. Could you describe your > use case a bit to help us understand how access by page id would help > you? > > Oh yes! Thank you so much for asking. I've been working with complex networks and knowledge graphs; I can compute a knowledge graph for each dump, and match graph entities with wiki articles. Part of UX goes like this: - a user query my knowledge graph, click on entity A, I prompt the context of A, I query commons to decorate A by _ID(A). If I had to query wiki by title _TITLE(A), I run into these issues: #1 '*my title (could contain brackets or weird chars in other languages or in any case title could change @ any-time! )'* how to ensure is resolved to corresponding canonical page? # 2 *a page is named 'Dna' at time0; changed to 'DeoxRiboAcid' at time1; changed to 'DNA' at time2.* I want to avoid to update my graph just because titles changes: entities are always the same. So, assume I have titles dated at time0, how to ensure that a query will always land to last revisioned article at *timeN*? If I had to keep synced my graph, for how long old wiki titles will be validly resolved and not deleted? In general, for research project working with commons, I think that query by _ID is very much handy (thinking about all cases or oddities for not unicode chars, less exception to handle, portability to localise content..). > > /page/title/{title} > > allow to get metadata by page, including the pageID , but I would like to > > have final page redirect (e.g. dna return 7956 and I would like to fetch > > 7955 of redirected 'DNA' ) > > We are looking into improving our support for redirects: > https://phabricator.wikimedia.org/T118548. Your input on this topic > would be much appreciated. > > just did it! > > /page/html/{title} get the article but page_ID / curid is missing in > source > > I would like to get the two combined. > > This information is actually included in the response, both in the > `ETag` header and in the <head> of the HTML itself. I have updated the > documentation to spell this out more clearly in [1]. The relevant > addition is this: > > The response provides an `ETag` header indicating the revision and > render timeuuid separated by a slash (ex: `ETag: > 701384379/154d7bca-c264-11e5-8c2f-1b51b33b59fc`). This ETag can be > passed to the HTML save end point (as `base_etag` POST parameter), and > can also be used to retrieve the exact corresponding data-parsoid > metadata, by requesting the specific `revision` and `tid` indicated by > the `ETag`. > Sorry not clear to me! I still don't know what parsoid is. Please let me understand, how to I transform the ETag <meta property="mw:TimeUuid" content="56f23674-6252-11e5-a0b4-fd306fc438f5" /> into corresponding page_ID from a client? Should I do a second query? Should I pass another parameter? Is pageID encoded in ETag ? *Could you provide an example...?* > > > 2# The rest are experimental: > > what could happen if a query fail? > > Does it raise an error, return 404 page or what else? > > The stability markers are primarily about request and response > formats, and not about technical availability. Experimental end points > can change at any time, which can result in errors (if the request > interface changed), or return a different response format. > Among the two (end points and response format) I feel it most comfortably if the latter would not change that frequently or abruptly. > We are currently discussing the use of `Accept` headers for response > format versioning at > https://www.mediawiki.org/wiki/Talk:API_versioning. This will allow us > to more aggressively stabilize end points by giving us the option of > tweaking response formats without breaking existing clients. > Ok. > > > I am thinking if possible to use api.wikipedia as fallback, and use proxy > > cache as primary source any ajax example for doing that to handle > possible > > failures? > > Yes, this is certainly possible. However, you can rely on end points > currently marked as "unstable" in the REST API. OK. > Basically all of them > are used by a lot of production clients at this point, and are very > reliable. Once we introduce general `Accept` support, basically all of > the unstable end points will likely become officially "stable", and > several `experimental` end points will graduate to `unstable`. > > > 3# Does /rest/ endpoint exist also for other languages? > > Yes, it is available for all 800+ public Wikimedia projects at > /api/rest_v1/. > > Thank you.

1 0

Parsoid entrypoint http://parsoid-lb.eqiad.wikimedia.org being decommissioned
by Subramanya Sastry 29 Jan '16

29 Jan '16

Hello everyone, The public Parsoid endpoint http://parsoid-lb.eqiad.wikimedia.org is being decommissioned [1] once we migrate over all straggler references to that endpoint [1] possibly as soon as 3 weeks from now. As far as we know, there are very few requests to that endpoint right now, but if you have been using that endpoint, please switch over to using the RESTbase service instead. You can access Parsoid HTML for the wikimedia wikis via their REST API endpoint. For example, https://en.wikipedia.org/api/rest_v1/?doc is the REST API url for English Wikipedia content. Thanks, Subbu. 1. https://phabricator.wikimedia.org/T110474

1 0

query rest endpoint proxy cache
by Luigi Assom 29 Jan '16

29 Jan '16

Hello, I was not aware api.wikipedia are available in cached version ! I tried /rest_v1/ endpoint and it is terribly fast. https://wikimedia.org/api/rest_v1/?doc I have few questions for using proxy cache: *1# Is it possible to query a page by page_ID and return the resulting redirected page if necessary?* e.g.: /page/title/{title} allow to get metadata by page, including the pageID , but I would like to have final page redirect (e.g. dna return 7956 and I would like to fetch 7955 of redirected 'DNA' ) /page/html/{title} get the article but page_ID / curid is missing in source I would like to get the two combined. *2# The rest are experimental:* what could happen if a query fail? Does it raise an error, return 404 page or what else? I am thinking if possible to use api.wikipedia as fallback, and use proxy cache as primary source any ajax example for doing that to handle possible failures? *3# Does /rest/ endpoint exist also for other languages?*

1 0

Re: [Wikitext-l] [Engineering] [Wikitech-l] Deprecating rest.wikimedia.org in favor of /api/rest_v1/
by Gabriel Wicke 25 Jan '16

25 Jan '16

On Mon, Jan 25, 2016 at 11:38 AM, Oliver Keyes <okeyes(a)wikimedia.org> wrote: > Will it apply to the pageviews API as well? It will, but the canonical URL for this has always been https://wikimedia.org/api/rest_v1/?doc, which will continue to work. Are you aware of any pageview users hitting rest.wikimedia.org? In any case, we'll check the logs for remaining rest.wikimedia.org accesses & make an effort to remind remaining users before decommissioning it. Gabriel

1 0

Re: [Wikitext-l] [Wikitech-l] Deprecating rest.wikimedia.org in favor of /api/rest_v1/
by Gabriel Wicke 25 Jan '16

25 Jan '16

Strainu, On Mon, Jan 25, 2016 at 11:01 AM, Strainu <strainu10(a)gmail.com> wrote: > Hi, > > Does this apply to the Graph extension as well? the graph extension has been using /api/rest_v1/ right from the start, so it's likely that no changes are needed for graphs. Gabriel

1 0

CentOs 5 Install
by Bob Cohen 10 Jan '16

10 Jan '16

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Wikitext-l January 2016