Last modified: 2009-10-22 14:56:50 UTC
Currently LiquidThreads is integrated with the API in a read-only manner. There needs to be an additional API mechanism for creating and replying to threads, as otherwise external tools will have to do this by screen-scraping, which is undesirable. (API support for WMF-deployed features of this magnitude should really be a requirement, not a nice extra. It would be best to avoid a repeat of what's happened with change tagging.)
These bugs block full-scale roll-out of LiquidThreads (batch-change).
Done.