The bugfix comments says: > The TL;DR is that if someone had conversation trimming on, it could create a rare situation where a database ID was re-used in a wa

The bugfix comments says: > The TL;DR is that if someone had conversation trimming on, it could create a rare situation where a database ID was re-used in a way that could result in this behavior. How is this bug even possible with E2E encryption? If picture.png exists on user A's phone and gets sent to user B, shouldn't it be client-side encrypted in such a way that user C, even if they receive it via some database ID screwup, are unable to view it (because it was encrypted with user B's public key)?