Community Author Information is a "Snapshot" rather than live

[mikeacjones]

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.

[mikeacjones]

Updated so that we are not duplicating author information in the mongo table:

Instead we're just storing the authorid for posts AND comments, and then using that to fetch back the current author information.

[mikeacjones]

@piyushroshan proposed method of addressing this: https://github.com/OWASP/crAPI/pull/81