# Update Avatar Image Serving - Remove Proxy Method **URL:** \ **Category:** Feature\ **Created:** [February 5, 2025, 8:05pm UTC](https://meta.discourse.org/t/update-avatar-image-serving-remove-proxy-method/350715 "2025-02-05T20:05:27Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![LotusJeff](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lotusjeff/32/477888_2.png) [@LotusJeff](https://meta.discourse.org/u/LotusJeff)\ **Post date:** [February 6, 2025, 3:12pm UTC](https://meta.discourse.org/t/update-avatar-image-serving-remove-proxy-method/350715/4 "2025-02-06T15:12:13Z")
None of the abovementioned options are feasible or preferred in my current environment. I would love to help solve this convoluted part of the application, but I am very new to this tech stack. The only assistance I can provide now is using my old BA and Dev Mgt skills. So, in the spirit of feeling like I am helping, these are my thoughts. When I look at any technical conundrum, I first look at possible assumptions that would make a solution more difficult. One assumption is to save an updated avatar image as a new filename. The person only has one avatar. We don’t keep a record of avatar names. I would suggest that when a person updates their avatar image, it is saved using the same filename as the existing avatar. This is basically what the /user-avatar/ link is doing. Instead of having a workaround, perform this logic during avatar creation/update. This would solve the historic posts’ concerns for future baked posts. Is this a big-bang change? No, this change could be implemented over months, slowly improving site performance. My dev teams always had an opportunistic code list for every code block. We wanted to make these improvements, but they were not critical to be done individually. When the code was opened for development for some other reason, the developer also made opportunistic changes. This minimized our testing and errors by reducing the times the code was opened and updated. I would break this project into the following phases: 1. Update avatar image saving logic to replace any image updates using the current filename. 2. Replace all uses of avatar images with a standard function that utilizes the discourse’s preferred file storage/delivery system. These could be implemented over months, slowly moving to the new avatar image presentation logic. 3. Once the first two are completed, provide the community with the steps and code snippets to change out and rebake historical avatar images in baked HTML to their preferred filesystem. This would be up to the individual discourse site owners’ choice to implement. (This code instructions and snippets would be useful for making raw HTML changes) I am sure you have considered all of this. I also know that fixing older code never makes it up the priority list. If there is anything I can do to assist in this effort, please let me know. ps. I do appreciate the offer of a PR for a global header setting. Let me do some additional research and follow-up with a more defined requirements. thank you for your assistance. --- _[View the full topic](https://meta.discourse.org/t/update-avatar-image-serving-remove-proxy-method/350715)._