4 ms·
Why shouldn't they? There's plenty of scenarios where you might want to swap images after a period of time has elapsed, or to fix a mistake.
by iamacyborg 8mo ago
Why shouldn't they? There's plenty of scenarios where you might want to swap images after a period of time has elapsed, or to fix a mistake.
- londons_explore 8mo agoThe ability to swap images but not text seems arbitrary. You could imagine a system more like the notification tray on iOS/Android where at any time a notification can appear, be edited, timeout, or be deleted. Your email inbox could be like that. The email saying "Your parcel has been dispatched" could be edited to say "Your parcel has been delivered". When you refund something you've bought, the original purchase receipt could be crossed out or hidden. When you get invited to a wedding but then the wedding is cancelled, the original invite could be deleted, etc.
- afavour 8mo agoIt's counter to the principle of what e-mail is. It's supposed to be static. Just because you can doesn't mean you should.
- iamacyborg 8mo ago> It's supposed to be static. Says who? It's not in the original RFC as far as I'm aware.
- SahAssar 8mo agoI'm pretty sure the original RFC (RFC 821) does not include remote resources and it was written far before HTML or HTTP was invented. It was text delivered over SMTP.
- Tagbert 8mo agospecifically to prevent this kind of tracking