How do you primarily read email? HTML? With it without images? Plaintext only? Asking for research on a new project.

Thanks, everyone, for the feedback thus far! If you want to learn more about what I'm doing and why I wanted to know, feel free to sign up at Details to follow later this month ;-)

Show thread

Plaintext heavily preferred, sometime simple HTML without remote content if not otherwise possible

Plain text preferred.
If html, pure good old v3.
If pictures, give additional description/links, for not forcing to waste bandwidth.

@ericmann plaintext mostly, HTML in a very small number of cases.

@ericmann mutt at home, notmuch mail with emacs frontend at work.

HTML gets rendered as needed. images are shown on demand.

@ericmann If it comes in as HTML with embedded images, I'll read it in that format.

I don't care, I'll happily take plain text too.

@ericmann I prefer plain text, but customers tend to include formatting and screenshots and stuff.

@ericmann Plaintext, without inline images. If it sounds like the pictures are important, I'll open them as attachments.

On remote shell server with mutt and lynx for html mails. I don't really receive image files, but in such I download them to view them locally.

@ericmann Plain text preferred, HTML exported to a file and viewed in browser if necessary.

FWIW, I read mail in Rmail in Emacs, which can render HTML using the SHR library, but it's somewhere between rich & plain text, like w3m or lynx.

@ericmann plaintext and only from a few trustworthy hosts like in html with loaded ressources (uh oh). ;)

read and write only plaintext.

Unfortunately some "services" send html mail and I really hate it.

@ericmann primarily UTF-8 in a text terminal - Debian's packaged mutt inside GNU screen.

Second most common is probably the Android Gmail client, third most common is the Gmail web UI, but those are distant - not more than 10% of my reading.

@ericmann I don't.

I've largely abandoned it due to privacy/surveillance issues.

@ericmann For personal mail, plain text only, though I have infrastructure in place to deal with received HTML mail and images. I only send plain text with the occasional attachment.

At work it's Outlook and almost everyone in the business world sends HTML mail. For sending mail, I have plain text preselected, in parts to annoy the marketing department with their footers that have mandated HTML text formatting (unless you use plain text).

@galaxis @ericmann you could up the game by pasting the footer HTML in the plaintext mail

* Write only plaintext
* Load in plaintext
* occasionally load HTML from senders of interest.

@ericmann HTML, with images. I set images to not load by default, but after I whitelist the sender.

@ericmann I don't use text-only e-mail clients these days, so HTML without images, I guess. Although I tend to ignore e-mails with pictures as unlikely informative.

@ericmann Ideally plaintext only. I'll flip on HTML if it's really important. If I'm greeted by a big wall of HTML in the message pane and it's not important, I'm unsubscribing.

If the unsubscribe link isn't functional in the plaintext version (sadly common) and I'm not using an HTML-capable client at the time, it's getting marked as spam.

@ericmann I default to having HTML off in my email, but I have to turn it on for at least half of the emails that I get to actually read them 😔 I also have images turned off by default.

I have been using Fastmail as my provider for the past 3-4 months, after trying for a month, after using GSuite for years. I am overall liking it, and mainly just have the negative of everything defaulting to Google to contend with.

@ericmann For the last few years, plaintext with HTML rendering (i.e. pipe through lynx). But these days it's full HTML webclient (gmail) for $dayjob purposes.

But all the webclient does is remind me that most email would be better off as plaintext (perhaps markdown) because the formatting and quoting and font choices and so on always waste time

@ericmann HTML/RTF, but images loaded on-demand for tracking reasons. Would consider a simpler format (e.g. Markdown) if it were widely supported for e-mail, but it’s not, so the HTML hate strikes me as misdirected.

Mutt on my side ... HTML mails are processed with lynx ... But usually I have an auto reply to HTML mails. I hate them especially those who say in their signature "act for the planet ! print only if needed" and then put a lot of images at the bottom of their signature without considering the co2 amount generated by each email sent with large images ... The worst being those who reply above the mail including 1200 lines from previous - 1/2

mails. I always point them to the rfc-1855 aka the netiquette. @ericmann - 2/2

@ericmann Thunderbird, prefer plaintext, almost always send plain text. Images off by default.

@ericmann Most commonly in plaintext without images, because that's how I've set email on my phone and I probably scan most email on my phone before dealing with complicated ones with a computer with a keyboard.

Sure reminds me to unsubscribe from advertising -- no distraction, without the HTML and images.

Sign in to participate in the conversation

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!