Community Author Information is a "Snapshot" rather than live
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.6k
- Forks
- 645
- Avg merge
- 37m
- Merged PRs (30d)
- 1
Description
Is your feature request related to a problem? Please describe.
If you make a post in the community, your current avatar, email address, nickname, etc are all saved in Mongo at that moment. This causes a few issues:
- If the author modifies any of their information, this isn't reflect in the community
- Saving the image data in mongo creates overhead + the UI is less responsive when returning base64encoded image data.
Describe the solution you'd like
Change author information to be return dynamically. Additionally, don't save any image information in mongo or return image data as base64encoded info. Instead add a new endpoint that dynamically returns the correct user's avatar. Less overhead, less storage, plus caching rules can be set up for the images that the browser can handle.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how community post authors are persisted and returned through the API, including where MongoDB stores author and image data. Done means author details are returned dynamically, image data is no longer stored or base64-encoded in responses, and a user-avatar endpoint exists with browser-cacheable responses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, mongodb
- Domain
- backend-api-design, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100