Honestly, we should really propose killing LQT on mediawiki.org - it's going to be replaced by Flow in the (hopefully) not-too-long term anyway...

LQT can't go until someone comes up with a way to extract LQT conversations and either put them in a format Flow can understand or output as a normal talk page.

Currently the response for:
https://m.mediawiki.org/w/api.php?format=json&action=mobileview&page=Talk%3ARequests+for+comment%2FScoping+site+CSS&variant=en&redirect=yes&prop=sections%7Ctext&noheadings=yes&sectionprop=level%7Cline%7Canchor&sections=all

is:
{"warnings":{"main":{"*":"Unrecognized parameter: 'redirects'"}},"mobileview":{"sections":[{"id":0,"text":""}]}}

Could the api return something different when liquid threads is being used?

Poke.. anyway to find out when a page has LiquidThreads enabled?

LiquidThread invokes onAPIQueryAfterExecute and seems to add a parameter. Could we somehow incorporate this in the above api response?

https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FLiquidThreads/4f2fbead90ac9f8373d2766c6460919b8f4bffce/classes%2FHooks.php#L888

(Question aimed at Max)

If we can, I suggest we just display a message saying "talk not currently available on this page".

https://gerrit.wikimedia.org/r/81580 kicks this off

My api seems to always say it is not LQT enabled so not sure if this patch worked correctly..

Change 84466 had a related patch set uploaded by Jdlrobson:
Redirect to talk page when liquid threads enabled

https://gerrit.wikimedia.org/r/84466

Change 84466 merged by jenkins-bot:
Redirect to talk page when liquid threads enabled

https://gerrit.wikimedia.org/r/84466