Is your feature request related to a problem? Please describe.
When you want to show 1500 users at once, each of which has a profile picture, you need to fetch 1500 thumbnails at once. Even worse, most of them are expected to be the default and thus, wasted networking.
Describe the solution you'd like
I would love to have a http forwarding to a "default thumbnail/profile pic endpoint", if the profile pic is not changed.
so /users/{username}/thumbnail => /users/defaultthumbnail
We might want to change the endpoint, but thats the basic idea. The improvement here would be, that you already (?) give us an e-tag for pictures, so after the forwarding, we just check whether the default thumbnail has changed and then resolve the call. We can use the cached image instead.
Describe alternatives you've considered
I think my proposed solution is very smart, perhaps the smartest. My uncle was also very smart. We can make big money, we can make UC4 great again if we implement the solution. Very great.
Is your feature request related to a problem? Please describe. When you want to show 1500 users at once, each of which has a profile picture, you need to fetch 1500 thumbnails at once. Even worse, most of them are expected to be the default and thus, wasted networking.
Describe the solution you'd like I would love to have a http forwarding to a "default thumbnail/profile pic endpoint", if the profile pic is not changed. so /users/{username}/thumbnail => /users/defaultthumbnail
We might want to change the endpoint, but thats the basic idea. The improvement here would be, that you already (?) give us an e-tag for pictures, so after the forwarding, we just check whether the default thumbnail has changed and then resolve the call. We can use the cached image instead.
Describe alternatives you've considered I think my proposed solution is very smart, perhaps the smartest. My uncle was also very smart. We can make big money, we can make UC4 great again if we implement the solution. Very great.