Files
zeekay 33c15584a2 the tab shows our mark, not upstream's hedgehog
Every brand icon we serve was upstream's, byte for byte. The favicon at
/static/icons/favicon-32x32.png hashed identical to
upstream/master's copy, and so did the other seven: both android-chrome
sizes, apple-touch-icon, both favicon pngs, favicon.ico, favicon-dev.ico and
safari-pinned-tab.svg. The manifest and the page titles were debranded long
ago, so the only thing still saying PostHog was the picture — which is the
one part a person actually looks at.

Regenerated from the mark this app already draws: the five-path 67x67 svg
inline in insights/templates/landing.html, which is the canonical Hanzo logo
and was sitting in the same repo the whole time.

The cache-buster moves with them. head.html and site.webmanifest reference
these by literal path with a ?v= query rather than a hashed name, so a browser
that has been to insights.hanzo.ai keeps showing the old icon until that
string changes — which is exactly how this got noticed in a tab today.

Third-party logos under browser_logos/ and coming-soon-destinations/ are
untouched on purpose: those are Chrome's and Datadog's marks, and they are
supposed to match upstream.
2026-08-08 15:14:42 -07:00

19 lines
487 B
JSON

{
"name": "Insights",
"short_name": "Insights",
"icons": [
{
"src": "/static/icons/android-chrome-192x192.png?v=2026-08-08-hanzo-mark",
"sizes": "192x192",
"type": "image/png"
},
{
"src": "/static/icons/android-chrome-512x512.png?v=2026-08-08-hanzo-mark",
"sizes": "512x512",
"type": "image/png"
}
],
"theme_color": "#ffffff",
"background_color": "#ffffff"
}