Magnus wrote in comment 34: > Regarding "both" ... from a storage saving perspective it's [neglegible] You'd have to write until your fingers bleed to get > the plain text up to megabytes, on a yearly basis. Then you send someone a picture the next day, and > all the savings is down the drain... +1 Exactly that, particularly the last sentence. > I would not base discussion on the assumption that per-card pref of prefers plaintext would stay, > since it is something that I think should be removed as well. Agreed. > An add-on could then set the per message delivery option based on whatever criteria it sees fit. Nice idea. I think adding an add API for that would be far easier than mainining the current complex code with all its corners.
Bug 1727493 Comment 35 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Magnus wrote in comment 34: > Regarding "both" ... from a storage saving perspective it's [neglegible] You'd have to write until your fingers bleed to get > the plain text up to megabytes, on a yearly basis. Then you send someone a picture the next day, and > all the savings is down the drain... +1 Exactly that, particularly the last sentence. > I would not base discussion on the assumption that per-card pref of prefers plaintext would stay, > since it is something that I think should be removed as well. Agreed. > An add-on could then set the per message delivery option based on whatever criteria it sees fit. Nice idea. I think adding an add-on API for that would be far easier than mainining the current complex code with all its corners.
Magnus wrote in comment 34: > Regarding "both" ... from a storage saving perspective it's [neglegible] You'd have to write until your fingers bleed to get > the plain text up to megabytes, on a yearly basis. Then you send someone a picture the next day, and > all the savings is down the drain... +1 Exactly that, particularly the last sentence. > I would not base discussion on the assumption that per-card pref of prefers plaintext would stay, > since it is something that I think should be removed as well. Agreed. For the sake of this discussion, we should assume that all recipient-centric options are removed. > An add-on could then set the per message delivery option based on whatever criteria it sees fit. Nice idea. I think adding an add-on API for that would be far easier than mainining the current complex code with all its corners.