Hacker News Reader

I think I would go with a class called Image, which provides a method called download().

This class is now over 4000 lines long.

ImageDownloadDispatcher, ImageDownloadScheduler, Image DownloadQueueManager... basically, the fix for "FooManager" names is to ask which aspect(s) of Foo the manager manages. Lifetime, storage, execution order (and according to which criteria), resource limits, uniqueness, exclusive access, efficient search, ...

All of those hint of functionality that is not present here. The code is just managing image downloads, not dispatching them, scheduling them, or even touching the queue (which is handled on a higher level).

ImageDownloadManager manages image downloads. Why use a name that makes less sense?

ImageDownloadPreparer?

ImageDownloadManager also communicates with the frontend about its state, so it’s not a completely preparatory process.

How about ImageDownloader?