performing http requests should signal to the user when the requests time out / are otherwise unavailable

[tinaun]

for example, play.rust-lang.org is down for me as i write this, but when i call the ?eval or ?play commands, there's no user visible feedback that the bot tried to make an http request and failed (it gets logged as an error, but it's not communicated to the end user in any way). without a bot response, the user may think that either the bot is broken or their command syntax is wrong.

ideally, this should be done at a high level and individual commands should be able to make http requests whenever without having to explicitly handle returning a message response to the user on a timeout

[kangalio]

This is a subset of #17

[technetos]

This is a subset of #17

Kinda, error reporting is not uniform across the bot.

[khionu]

That said, I agree that this is an error that can be covered by #17. The centralized error handling can match on the error, censoring ones that don't match safe-to-show errors.