Context Navigation

Changes between Initial Version and Version 1 of Ticket #17025, comment 11

-                      initial
+                      v1
 wp_list_authors() is low-priority to me since it's not called by core. But inevitably some plugins and themes use it in a way that doesn't mesh with per-user inclusion/exclusion I do with WP_Query filters.  Then I'll have to filter '''every''' query and use strpos() and preg_match() to determine if it is the wp_list_authors() query.  Now '''that's''' not fun.  So basically, the significance of this ticket is in setting a precedent for whether the API fully supports external modification of content and user queries, or whether it presumes to anticipate and regulate all implementations.
 In this case, caching the results of the default query is not sufficient since it is built on query clauses that do not account for post types other than 'post' nor visibility statuses other than 'private':
+In this case, caching the "all objects" results of the default query is not sufficient since it is built on query clauses that do not account for post types other than 'post' nor visibility statuses other than 'private':
 {{{
 …
 }}}
+A filter on the results would be better than nothing, but it has the disadvantage of forcing an additional query.
+So a filter on the results would be better than nothing, but it has the disadvantage of forcing an additional query, which makes plugins look bad ;)