Yeah, we could do that.
nostr:npub1yaul8k059377u9lsu67de7y637w4jtgeuwcmh5n7788l6xnlnrgs3tvjmf would it be possible to reduce the favicon cache from 60 days to 7/14 days on Damus?
Discussion
And the option of custom favicons for NIP-05?
I guess we could standardize a path /.well-known/nostr/nip05-favicon.jpg.
I want to show a custom favicon for NIP-05s compared to the website. Currently I could do that with user agent matching but that is messy.
We could, but then it restricts the file path / extension. Could the path be defined by /.well-known/nostr.json?
GET /.well-known/nostr.json
```
{
"names": {
"bob": “...“
},
"relays": {
"...": [ "wss://relay.example.com"]
},
icon: “https://path/to/icon%E2%80%9D
}
```
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://…"}}
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.
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