Store hashes of avatar photos to avoid spurious updates #66
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When the bridge is restarted, Google Chat sends different
URLs for the avatar images for every participant in every room.
This happens even if the images have not changed, but sending
'avatar change' events into the Matrix rooms can be costly.
This patch computes a SHA256 hash of the image to see if the
image has actually changed; if not, the new URL is stored but no
Matrix event is sent.
This includes a database schema upgrade to v4.