@legoktm wrote:

I've been thinking about this in the context of https://github.com/Krinkle/pywiki-fileprotectionsync/

That use case is to hit sibling wikis' APIs to query data and then make edits on the primary wiki.

One API could be Bot::get_sibling_wiki(), where you just need to provide the domain name and it constructs a new Bot instance, but shares the underlying HTTP client (note that we likely need to have mwapi allow creating a new client using an existing HTTP client.

@legoktm wrote:

And for wikis with Extension:SiteMatrix, we could have a get_sibling_via_sitematrix(a_different_identifier).

@legoktm wrote:

The concurrency lock should probably be shared across wikis.

@legoktm wrote:

Another idea, partially inspired by MZ:

In mwbot.toml

[sites.default]
api_url = "..."
rest_url = "..."

[sites.enwiki]
api_url = "..."
rest_url = "..."

[sites.commonswiki]
api_url = "..."
rest_url = "..."

Not exactly sure what it should look like in Rust. Maybe:

let config = Config::from_default().unwrap();
let bot = config.default();
let bot_commons = config.get("commons").unwrap();

mirrorkt opened https://gitlab.wikimedia.org/repos/mwbot-rs/eventstreams/-/merge_requests/1

Draft: Rewrite and support streams other than RecentChange

In T319104#9376816, @CodeReviewBot wrote:

mirrorkt opened https://gitlab.wikimedia.org/repos/mwbot-rs/eventstreams/-/merge_requests/1

Draft: Rewrite and support streams other than RecentChange

miss

xtex opened https://gitlab.wikimedia.org/repos/mwbot-rs/mwbot/-/merge_requests/110

mwapi: allow setting custom HTTP client

xtex merged https://gitlab.wikimedia.org/repos/mwbot-rs/mwbot/-/merge_requests/110

mwapi: allow reusing HTTP client from a previously built client

legoktm opened https://gitlab.wikimedia.org/repos/mwbot-rs/mwbot/-/merge_requests/139

Add Bot::clone_for_family()

legoktm merged https://gitlab.wikimedia.org/repos/mwbot-rs/mwbot/-/merge_requests/139

Add Bot::clone_for_family()