Tickets :: Comment on [#13051] Emoticon images as mime parts instead of links

* Your Email Address
* Spam protection	Enter the letters below: . .. . __ .__ .__. \|\ \|\|\ \|/ `\| \[__] \| \\|\| \\|\__.\|__/\| \|
Comment	> > The way I see it, once a message is sent, it should be viewable >> without the need for my server to be up or online or available to the >> viewer. Also, the message should be viewed as it was sent today, >> next month or 10 years from now. > > Well... yes and no. It really depends on the use case of the > message. A bulk message (think newsletter, or even a message CCd to > many recipients) is actually much more efficient if sent with http > links, since http is a much more efficient data retrieval protocol > than MIME attachments. > > And i think the whole "message should be viewable 10 years from now" > isn't really that important. We explicit give the option to link > attachments, which most likely won't be available after a certain > period of time. Example: while it would be nice for my bookmarks > from 15 years ago to still work, the amount of effort required to > route http requests to a new web layout is most likely way more > effort than is reasonable for the payoff. > >> Having external links just makes >> that nearly impossible. This is why you provide the option to imbed >> images as attachments! > > Do note that this ability has been removed from IMP 6.2. The > reasoning is that, now we have a way to explicitly indicate we want > to add images to a message (drag/drop; adding via image menu()), any > explicit http links in the message are there for a reason. So images > explicitly linked by an HTTP request will remain that way and will > not be converted.
Attachment
Watch this ticket

Saved Queries