Oh yeah, that could work. And if it’s a paid NIP-05 service, a different icon could be provided for different tiers of paid subscriptions. I still think it makes sense to have a general icon though. Maybe we can do both.
Actually, what if the icons were per-name? And the favicons could be cached by URL instead.
This means:
- Any icon changes show up quickly (after NIP-05 validation, aka restart of app)
- Custom icons can be awarded to different users (like team members, contributors, etc. for Damus)
- Icons can still be cached
otherwise, LGTM.
{"icons":{"semisol":"https://…"}}
Discussion
A general icon would be the favicon, imo, or provided per entry manually.
This would be the handling:
1. If the icon parameter for that user is an empty string, show no icon
2. If there is an icon, show it
3. Otherwise show the website favicon