Replying to: vincent @vincent

@vincent Not surprising. I can't really blame browsers for aggressive favicon caching, either.

Manton Reece @manton