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

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/13051
------------------------------------------------------------------------------
  Ticket             | 13051
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Emoticon images as mime parts instead of links
  Queue              | IMP
  Version            | Git master
  Type               | Enhancement
  State              | Accepted
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Slusarz
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2014-03-18 15:37) wrote:

  > 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.