[03:03:49] <legoktm>	  08:41:41 <taavi> do we consider changes to external dependencies "breaking changes" in semver speak? <-- personally no, because it's all transparently handled by composer. If that external dependency is part of that library's API, then yeah
[03:04:42] <legoktm>	 in this case I don't see any breaking change since any attempts to catch CriticalSectionMismatchException or LogicException will still work
[20:16:10] <addshore>	 Hmm, if I have a title and am doing $title->getCanonicalURL() is there a way to ensure that namespaces like Special: are canonical rather than localized?
[20:17:35] <addshore>	 i guess making the title always be "external" might work
[21:30:14] <Krinkle>	 addshore: localised is canonical. It redirects otherwise.
[21:30:25] <Krinkle>	 You mean English namespace prefix. Why?
[21:47:20] <addshore>	 Its for the TTL / rdf output of wikibase. We want concept URIs to be consistent, even if a user changed the language of the wiki.
[21:47:25] <addshore>	 ie, We always want Special:
[21:47:57] <addshore>	 my current evil hack thought https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Wikibase/+/761711/1/data-access/src/MediaWiki/EntitySourceDocumentUrlProvider.php
[21:48:30] <Krinkle>	 addshore: okay but this is within a given wiki right? Site lang is English
[21:48:47] <addshore>	 I dont follow
[21:49:20] <Krinkle>	 We don't localise URL to user language, it's site lang
[21:49:41] <addshore>	 sorry, yes, I meant site lang when saying "language of the wiki"
[21:51:01] <Krinkle>	 Well. The namespace prefix will be local, but you could disable translation of the page name by removing the I18n values.
[21:53:24] <Krinkle>	 If prefix must be pinned as well, then I'm not sure how. But also if it was possible that's seems likely to cause more confusion in the long term, going back to "why". If it's discovery, maybe an API can be used to discover the data. If the url itself needs to be parser externally by third parties, then maybe it shouldn't be a special page, or you can choose to mint it consistently your own way through some custom link formatting. What 
[21:53:24] <Krinkle>	 about rest.php?
[21:54:22] <Krinkle>	 If it's for formatting externally, special will work everywhere.
[21:55:21] * Krinkle has to go
[22:36:32] <addshore>	 `mint it consistently your own way through some custom link formatting` I think thats what we will be needing
[23:10:49] <Krinkle>	 addshore: ack, so what we do in central auth when formatting such link is WikiMap->getFullUrl( 'Special:CentralAutoLogin/start' );
[23:10:56] <Krinkle>	 which basically only considers wgArticlePath
[23:10:59] <Krinkle>	 and nothing else
[23:11:28] <Krinkle>	 it's very discouraged/hidden away but still doesn't really duplicate code which seems a good middleground (e.g. we wouldn't want to promote it in Title I think)
[23:11:57] <Krinkle>	 although this one seems also like one we could migrate to rest.php