If the mailers follow the proper multipart protocols and also make it easy to hide quoted emails, move to see the original ones, etc (to add incentives to use the protocol), then support for it can grow until everyone will have updated just over time. once you know someone's reader has support for it, because they send you emails using it, you can send to them without the old inline-quoted version.
On 5/6/05, Robert G. Hays <[EMAIL PROTECTED]> wrote: > The problem with this will be getting *all* the email readers updated > with this *entire* feature, -and- getting everyone to update to said > newer versions *or* programs if/When! -their- favorite didn't get > updated for this. > > That said, it sounds like a FINE idea to me. > > Now, where'd I put that blamed crowbar? > > rgh. > > Calvin Spealman wrote: > > >I know I said I was out of this conversation, but this off the > >original topic so I want to make myself clear on what I actually meant > >here. > > > >E-mails have unique identifiers, and replies include information in > >the header as to the identifier(s) of the original messages. Thus, if > >you have the messages (or access to a service archiving them) you > >could reconstruct the entire thread from just a single message. > > > >A protocol or format could even be created to designate where and how > >other messages are quoted, without actually including the content. > >This would be especially useful for very large messages and replying > >to multiple messages at once. > > > >Always there is room to move forward, so find the door that need's > >unlocked and break it down. > > > >On 5/5/05, Robert G. Hays <[EMAIL PROTECTED]> wrote: > > > > > >>Calvin Spealman wrote: > >><snip> > >> > >> > >> > >>>it isn't like the bandwidth is anything at all > >>>compared to the bloated headers and redundant repeating of messages in > >>>every reply. > >>> > >>> > >>> > >>> > >><snip> > >> -- is a good way to control redundancy factor > >> > >>And sometimes someone skips the original(s), and the later msgs become > >>interesting, and "someone" needs to catch up. > >> > >>Sigh, no soution is ever perfect. > >>rgh. > >> > >>-- > >>gentoo-user@gentoo.org mailing list > >> > >> > >> > >> > > > > > > > > -- > gentoo-user@gentoo.org mailing list > > -- gentoo-user@gentoo.org mailing list
