Thread:Talk:Echo (Notifications)/Buckets/reply (3)

Revisiting this old thread: Our API framework may need an upgrade here. The idea of single wikis living in a vacuum was very simple, and specifically ignored the common cases -- more common now -- of clusters of related wikis. However, most wikis come in clusters:
 * Some are groups of wikis that are really about the same content (but arbitrarily split into multiple 'different wikis' by language ).
 * Others are groups of wikis on related topics, used by the same group of people. Here often a 'new wiki' rather than a 'new namespace' was chosen to make it easier to have different main pages, or different policies per topic.  None of this technically requires a separate wiki; these clusters of wikis often share 90% of their templates, policies, categories.

The difference between a namespace and a new wiki, for a cluster with shared userpool, is only semantic. And we should offer APIs that let developers ignore that semantic difference. Wikimedia isn't the only group with a cluster of many wikis; most organizations I know that use wikis have a cluster of at least 2 or 3. And all of them need cross-wiki tools, notification, change-tracking.