When Casey Newton (author of the article) first launched his Substack newsletter, he was alarmed that the full posts were not displayed for gmail users - instead there was a "jump" (that many users probably don't see, because it's formatted as "... [Message clipped] View Entire Message"). The issue is that gmail clips emails at 102k, and the substack emails easily hit that limit when posts contain lots of urls due to 1) inline styling on links, and 2) the ballooning hyperlinks due to the tracking strings.
This person found that substack was ballooning a 59 character url to over 400 characters.
I was hoping this incident would cause substack and others to pull back on the reins a little bit. The urls on these emails are redonk, and clearly the authors aren't happy about users missing out on content.
I wrote the story on the size limit issue you linked and have thoughts on the issue listed here. (Long story short: This whole issue is a byproduct of the lack of standardization in the email space, something highlighted by the use of tables in emails, which are another reason why emails are so large. Long story short, email is in need of modernization, which could lead to better options for tracking than tracking pixels, which are not anonymized enough for publisher use cases.)
I agree that the amount of tracking going on in the Substack links is a bit aggressive, but I want to be careful to not put too much of the blame on them for the long links. Part of the problem is the service that Substack is using, Mailgun, is intended for transactional emails, rather than the newsletters that Substack is sending. My feeling is that Substack ramped up using Mailgun but probably needs to start building their own tech for doing this, because it’s clearly not suited for the Substack use case.
Thanks for sending the link—it is super-relevant to this issue.
Indeed, tables and in-line styles are industry standard email coding practices, and the main reasons email character count balloons. Tracking links are a tiny factor, unless maybe the email is stuffed with links. (I doubt Casey’s are.)
Thank you for figuring out that character limit. We redesigned and recoded a template to get under it.
And tables and in-line styling are industry standard for one reason: Microsoft Outlook. It still uses the ancient and horrible HTML rendering engine from MS Word, instead of a modern HTML engine like literally everybody else uses. And a ton of senders care about Outlook because so many high-value subscribers use it (e.g. corporate staff at big companies).
The other factor is that the use of email to send long-form content is pretty recent. For a long time before, emails were either personal, marketing, or publishing with “click to read full article.” All pretty short.
When I started my newsletter, I was seemingly the only person using email for long-form. Now everyone’s doing it.
The situation with Outlook should hopefully improve in the next year, as Microsoft is planning to make different versions of Outlook work basically the same, with the web version as the baseline: https://www.techradar.com/news/microsoft-wants-to-unite-all-...
The downside of this whole saga with Apple is that other than this Apple basically renders emails better than just about every other service—rendering essentially using the Safari engine. Gmail has improved but inlining CSS is still required because of it.
If everyone was working to a unified standard life would be easier for email senders … possibly even recipients.
Casey’s are fairly stuffed with links. The format is generally: main article; multiple sets of links to other articles; funny tweets. He might be more mindful these days of how many links he includes, because at the beginning he seemed quite alarmed that many readers couldn’t see the whole email without a jump.
This person found that substack was ballooning a 59 character url to over 400 characters.
https://tedium.co/2020/12/22/gmail-102kb-email-size-limit-hi... (same author, more detail): https://twitter.com/ShortFormErnie/status/133992146683031961...
I was hoping this incident would cause substack and others to pull back on the reins a little bit. The urls on these emails are redonk, and clearly the authors aren't happy about users missing out on content.