notrheadagain

Re:Ask HN: Plain text emails in 2017? on Wednesday August 30, 2017 @10:04AM (#15132210)

However, the rule of thumb, especially for drip campaigns, is that you do get some marketing content with almost every email. This could be a specific sign off and such.

Re:Ask HN: Plain text emails in 2017? on Wednesday August 30, 2017 @10:02AM (#15132200)

The plain text versions I was talking about are those well-formatted and structured ones. Where you get the minimalistic beauty of simple formatting. Markdown-style, maybe.

Re:Ask HN: Plain text emails in 2017? on Wednesday August 30, 2017 @10:01AM (#15132187)

Well, I agree here. However, it's pretty hard to include click tracking into plain text emails. So it may be complicating attributing revenue to those. The way out here would be utms or stuff like bit.ly

Re:Ask HN: Plain text emails in 2017? on Wednesday August 30, 2017 @04:59AM (#15130674)

Personally, I agree emails should be sent in two versions. However, there's a trend of sending just HTML. This article was written some time ago https://litmus.com/blog/best-practices-for-plain-text-emails... and latest comments will also promote the idea of dumping plain text.

Regarding marketing emails, I mean every automated email sequence. Like, you definitely get receipts and stuff over email. And those aren't written by hand.

Ask HN: Plain text emails in 2017?

Posted by notrheadagain on Wednesday August 30, 2017 @03:51AM
from the ask-hn dept.

Hi, guys. From day to day, we send lots of emails and a huge fraction of those are of marketing nature. We're used to actionable HTML stuff in our inbox, and there are very few clients that don't support HTML email layouts. Still, we usually send two versions. HTML and plain text. Do we really need to send plain versions or it's just a second system syndrome of doing everything "right"?

( Read More... | 10 comments | 4 points | on HN )

Re:How Uploadcare Built a Stack That Handles 350M File API Requests pe... on Monday August 28, 2017 @02:53PM (#15119072)

AWS is an infrastructure. It could be Google Cloud or something else. When writing the article, we wanted to convey how frameworks are interconnected and try and estimate the number of "Moving Parts" (I liked this one) :)

Re:How Uploadcare Built a Stack That Handles 350M File API Requests pe... on Monday August 28, 2017 @02:42PM (#15118987)

I just got wind of it, we at Uploadcare will soon be releasing an article with more info about the early days :) And, I believe, a podcast or two. Thanks for this question, btw. Would you elaborate on what you would like to know? It'll help us compile a great article, thanks :)

Re:How Uploadcare Built a Stack That Handles 350M File API Requests pe... on Monday August 28, 2017 @11:58AM (#15117479)

Uploadcare contributes to open source, however. For instance, the fast and production-ready Pillow-SIMD fork is a great example. You can search for "Pillow-SIMD" here for the discussion or check out the original article: https://blog.uploadcare.com/the-fastest-production-ready-ima...

Re:Show HN: Dynamic image size generator on Wednesday August 16, 2017 @01:00PM (#15029088)

There are SaaS for that, Uploadcare offers that for free, for instance