Hi Ken S,
My concern is that some of our users will look at the latest post on aIn what I proposed it would still be shown there.
I proposed consolidating the storage rather than "stripping out" the duplicate.
As a dabbler in software, I would also believe that the code to keepI'm not quite sure what difficulty you're seeing.
Images and attachments already occupy separate storage from the body text of the message. In the web view it would be rather simple to have multiple instances of the displayed image point to the same image file storage. If you're a dabbler in HTML code the storage is pointed to by the URL used in the src attribute of the <img> tag in whatever page or text displays the image.
In messages sent out by email I know that some processing of the content is done by Groups.io, but I don't know the details. However I'm confident that Mark can ensure that consolidating the storage doesn't "break" the content; whether for individual or digest.