Consider the handling of media workers (with separate APIs)

[JacksonChen666]

Synapse media workers also handles admin APIs, and the main Synapse can turn the media repository off, making the admin APIs for media not work. (This is the only thing so far to have a separate admin API separate from the main Synapse)

Ideas:

• Directly query the media worker ourselves, after asking about it in synadm config ("do you use?" followed by "where is it?")
  • Is there an advantage to this, if the sysadmin is going to have to setup the proxy anyways for the media worker?
  • What about multiple media workers? Is querying only one of them enough? (Probably, but untested)
  • Code: Our code doesn't seem like it's set up to handle cases like this
• Don't handle it ourselves, and instead just ask to point synadm to a proxy
  • In theory it's possible to also to also have the former mode with this mode, but then the configuration question would probably have to be worded carefully
  • This would involve more work for the sysadmin (and we'd likely need docs on this to expand on it)
  • When it seems like we're querying the main Synapse that's not handling media requests (which seems to return M_UNRECOGNIZED errors), hint that when a media related command is run

[ricardo-duarte-av]

What about multiple media workers? Is querying only one of them enough? (Probably, but untested)

Only one worker can get those tasks, so the user will have to know the worker ip:port