I decided not to allow URLs for image inlining in iTerm2 because of possible security issues. Have you thought about that? I didn't have a clearcut risk in mind, but giving someone else (e.g., root on an outside machine you're sshed to) the ability to fetch URLs within your network (even without cookies) expands the attack surface of corporate networks.

We proxy all external URL's through: https://github.com/atmos/camo

Here's a similar blog post I wrote just a few days ago: http://blog.neax.de/console/

Very nice. Can't wait to try it out in our builds.

Easy to remember, it's ANSI escape 1337 +1