Currently, `wttr.in` uses user agent strings to determine response format. User requests an explicit option to render HTML instead of relying on user agent sniffing, especially when `curl` defaults to ANSI and HTML is preferred over low-res PNG.
currently, wttr.in uses user agent strings to determine the best response to return to the client. by default, `curl` gets ANSI in response. but let's say, someone is trying to render the HTML instead of PNG [because it's so low res](700). the only option here is to change the user agent to something else that does not contain the keyword `curl` anywhere in the string of the user agent (not even spaces around `curl` work) proposals (sorted from most preferred to least preferred of personal choice and misc.): - a long argument (similar to `lang` arg) `output_format` or `format` which can `=` to `PNG`, `HTML`, `ANSI`, `plain`, `JSON`, etc. - `H` argument for getting HTML (similar to using `M` for getting meter/s wind speeds) - `_arguments.html` (similar to png format request) all which ignore the user agent and returns HTML anyways.