Description
Will need a UI for it, and the ability to store it in the DB or a ProtoBuf object.
Might be cool if we could automatically resize/compress it to avoid the "must be of size X" hurdle when selecting it, but still keep bandwidth low while sending the images around with the profile update messages.
Alternately, maybe the profile update object can either have the image or a hash of the current image,
which the client can use to see if their image is out of date and request the up to date one. This is more complex but prevents sending images around when not needed, or when like just the username is being updated. Some cases would contain the image by default, like if the MeshID has never been seen before, or the user has just updated their image and is sending the first update out to everyone.