Code review comment for lp://staging/~stephen-stewart/snapweb/default-package-icon

o/

Just to fill out the reasoning behind this a little:

If the store mandates a default icon it's mandating a visual style to all clients, Canonical or otherwise, and making it harder for clients to know if an icon is default, user submitted or otherwise (v1 of the default versus v2 of the default?).

By using null in CPI responses, clients can adapt the visual style of a default icon to their own whim, and `null` is much simpler for clients.

Canonical only has a handful of locations to update the default icon, and can do so at a pace that suits the project in hand (for example webdm may not like a v2 default icon until certain updates have been made, visually or otherwise).

I'll not make the bandwidth argument since it's negligible.