@Esor: md@home is a p2p-service. As far as I understood it, the difference is, that instead of using a commercial image-hosting service (for which MD has to pay for), it creates MD's own "virtual" image-host by using servers, that are provided by its own community, which is doing it for free. So if you load a chapter, your browser is redirected to one of those servers, which is providing you with the needed images via direct connection. And voilà, MD's server only has to deal with the much smaller datapackages for the page itself and it's services (reader, comments, forum, aso...) and the main bulk of cost-intensive data-transfers (the images) has been taken from its shoulders. If just told BS, feel free to correct me.
My own issue:
Sadly md@home doesn't work out for me right now. My Load image "bug" seems to be the opposite of OP's problem. The normal servers work fine, but md@home's connections seem to malfunction. I was greeted with a pink wall'o'fail (tap to reload, tap to reload, tap...) for around 3/4 of all chapters I tried to read. The issue isn't concentrated on single mangas. In a manga-series some lower chapter didn't work, while the next one did. So I assume an important peer (important for me at least) in the MD@h-network is either blocking me, is malfunctioning or the connection gets disturbed. As far as I can tell I have no obstacle set up on my side (e.g. firewall-rules), that would block it. Turning MD@h off and falling back on the mainservers solved my problem....at least for now.
