While this is working as intended (matches the behaviour on Discord, for example), I recently introduced a new mechanism for avoiding cloning of forwarded attachments for the announcement channels feature. As such, I could make it so that attachments that are deleted from the source message that are too big for your file upload quota also break downstream, but still allows you to forward it. As such, it is not a faithful snapshot, but it arguably matches user expectations better.
I overlooked that – at the time I implemented this feature, it matched Discord. They might've realised they could implement it this way with a non-snapshot recently too. Or they let you take a full snapshot without paying for it now anyway, though that wouldn't be something I would like to do at this time for as long as we do not have content-addressed storage in place. I can look into implementing content-addressed storage for this thing only initially, perhaps.
Thread
Comment by Hampus
Comment by Jackuczys
Comment by Hampus