http://www.iamrambling.com/wp-content/uploads/2016/10/image-rendering.jpg

Today talk about image rendering on Steemit being broken was hot and heavy. Here's [just one example](https://steemit.com/steemit/@thecryptofiend/image-issue-there-is-currently-an-issue-with-images-not-being-displayed-on-steemit-all-image-hosts-please-read) of the many posts hitting most user's feeds. It was validating to know it wasn't just on my end. It wasn't my browser or my ISP. It wasn't my router or the image server(s) in question.

It wasn't a flashback to using AOL on dial-up in my college days. God, I should have been dropping LSD. That would have been better for my health than that mess!

So who's awaiting an official explanation of what was broken? There was talk that any images under 31.75 kilobytes would render fine but larger images broke after surpassing that amount. I'm sure I could dust off a collection of animated GIFs from 1996 that would have served fine.
http://rs317.pbsrc.com/albums/mm387/mikayla619_4/Pixels/tinicat-n-yarn.gif~c200
Outside of that **we need bandwidth!**

If you're wondering about Steemit's security or centralized nature of the web portal you've been instructed to place your head into a metal pail and yodel. It will garner better answers than you'll receive from up top.

Tongue firmly-in-cheek,

The Everyday Geek on Steemit
EGOS.live
[Image credit](http://media.photobucket.com/user/mikayla619_4/media/Pixels/tinicat-n-yarn.gif.html?filters[term]=cat%20pixels&filters[primary]=images&filters[secondary]=videos&sort=1&o=6)