Considering icons that are no longer used (mostly because users choose another one) are removed from your media server, it’s easy to get “broken” URLs.
Currently I run a script daily to refresh icons that are either no longer accessible or if users have chosen a default icon (that never disappear) and might choose an own one later.
Of course if a user changes the icon in the meantime the URL is still wrong, so I’m contemplating caching all user icons in my service, so there’s something sensible shown while the icon hasn’t been updated yet.
Another solution would be to trigger on failing icon accesses on the spot and refresh if needed.
That said: What’s your recommendation for handling user icons for best performance and least API load?
Is there a way to detect mentioned changes via the API without rate limit penalty?
Thanks in advance,