Comment 8 for bug 963805

Yes that's correct and a weird way to provide an icon it is indeed.
Yet I see only two other possibilities: either chromify-osd should generate a different icon filename (then it should work correctly with caching mechanism which isn't the one I think needs to be disabled); or notification daemons and recent-notifications should use any urls (local or remote) transparently which is not the case now I suppose and never will be.
I'm not an expert though. Maybe you could think of another more correct alternative?