Comment 1 for bug 1177945

I've determined this is caused by file access from QML in the avatar cache . It's actually significantly faster using remote URLs for the avatars. Using the remote URLs also means QML will handle local caching of the avatars for us, so we don't need to manage the avatar cache in the backend at all. The only remaining need for a cached version of the avatar is the notify-osd integration, which doesn't support a url to a remote image.

For now we'll drop the avatar caching logic from the friends dispatcher and start storing the URLs in the model. However, the dispatcher will need to cache an avatar long enough for the notification. Perhaps cache in /tmp which will get purged on restart?