Freshness isn't something I actively manage. Logos are cached, treated as static, and failed domains stay skipped.Memory first, then disk, then network. If a fetch fails, the badge shows and nothing retries.Stale logos are fine. A flickering UI isn't.
Archit Mittal
I Automate Chaos — AI workflows, n8n, Claude, and open-source automation for businesses. Turning repetitive work into one-click systems.
Logo fetching is one of those deceptively hard problems — you think it's just an image URL until you deal with favicons, SVG fallbacks, CDN redirects, and companies that change their brand assets monthly. Smart approach building a dedicated service for this. I've run into similar challenges when building client dashboards that display partner logos — ended up using a multi-source fallback chain (Clearbit, Google favicon API, then scraping og:image as a last resort). How do you handle logo freshness and cache invalidation?