A place to cache linked articles (think custom and personal wayback machine)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

преди 4 години
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350
  1. <!doctype html><!-- This is a valid HTML5 document. -->
  2. <!-- Screen readers, SEO, extensions and so on. -->
  3. <html lang="fr">
  4. <!-- Has to be within the first 1024 bytes, hence before the <title>
  5. See: https://www.w3.org/TR/2012/CR-html5-20121217/document-metadata.html#charset -->
  6. <meta charset="utf-8">
  7. <!-- Why no `X-UA-Compatible` meta: https://stackoverflow.com/a/6771584 -->
  8. <!-- The viewport meta is quite crowded and we are responsible for that.
  9. See: https://codepen.io/tigt/post/meta-viewport-for-2015 -->
  10. <meta name="viewport" content="width=device-width,initial-scale=1">
  11. <!-- Required to make a valid HTML5 document. -->
  12. <title>Hey, your e-mail matters more than hype (archive) — David Larlet</title>
  13. <meta name="description" content="Publication mise en cache pour en conserver une trace.">
  14. <!-- That good ol' feed, subscribe :). -->
  15. <link rel="alternate" type="application/atom+xml" title="Feed" href="/david/log/">
  16. <!-- Generated from https://realfavicongenerator.net/ such a mess. -->
  17. <link rel="apple-touch-icon" sizes="180x180" href="/static/david/icons2/apple-touch-icon.png">
  18. <link rel="icon" type="image/png" sizes="32x32" href="/static/david/icons2/favicon-32x32.png">
  19. <link rel="icon" type="image/png" sizes="16x16" href="/static/david/icons2/favicon-16x16.png">
  20. <link rel="manifest" href="/static/david/icons2/site.webmanifest">
  21. <link rel="mask-icon" href="/static/david/icons2/safari-pinned-tab.svg" color="#07486c">
  22. <link rel="shortcut icon" href="/static/david/icons2/favicon.ico">
  23. <meta name="msapplication-TileColor" content="#f0f0ea">
  24. <meta name="msapplication-config" content="/static/david/icons2/browserconfig.xml">
  25. <meta name="theme-color" content="#f0f0ea">
  26. <!-- Documented, feel free to shoot an email. -->
  27. <link rel="stylesheet" href="/static/david/css/style_2020-06-19.css">
  28. <!-- See https://www.zachleat.com/web/comprehensive-webfonts/ for the trade-off. -->
  29. <link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_regular.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
  30. <link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_bold.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
  31. <link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_italic.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
  32. <link rel="preload" href="/static/david/css/fonts/triplicate_t3_regular.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
  33. <link rel="preload" href="/static/david/css/fonts/triplicate_t3_bold.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
  34. <link rel="preload" href="/static/david/css/fonts/triplicate_t3_italic.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
  35. <script type="text/javascript">
  36. function toggleTheme(themeName) {
  37. document.documentElement.classList.toggle(
  38. 'forced-dark',
  39. themeName === 'dark'
  40. )
  41. document.documentElement.classList.toggle(
  42. 'forced-light',
  43. themeName === 'light'
  44. )
  45. }
  46. const selectedTheme = localStorage.getItem('theme')
  47. if (selectedTheme !== 'undefined') {
  48. toggleTheme(selectedTheme)
  49. }
  50. </script>
  51. <meta name="robots" content="noindex, nofollow">
  52. <meta content="origin-when-cross-origin" name="referrer">
  53. <!-- Canonical URL for SEO purposes -->
  54. <link rel="canonical" href="https://axbom.blog/hey-email-hype/">
  55. <body class="remarkdown h1-underline h2-underline h3-underline hr-center ul-star pre-tick">
  56. <article>
  57. <header>
  58. <h1>Hey, your e-mail matters more than hype</h1>
  59. </header>
  60. <nav>
  61. <p class="center">
  62. <a href="/david/" title="Aller à l’accueil">🏠</a> •
  63. <a href="https://axbom.blog/hey-email-hype/" title="Lien vers le contenu original">Source originale</a>
  64. </p>
  65. </nav>
  66. <hr>
  67. <main>
  68. <p><b>There is a new e-mail provider in town and it’s an excellent opportunity to have a reasoned conversation about how to improve your e-mail management. I do not believe that decisions around your e-mail provider should be made lightly. Your e-mail address is often the hub of your online presence and your inbox is your sanctuary. Well, at least it could be.</b></p>
  69. <p>First, let me break down why there is this nagging feeling of urgency to sign up for the HEY e-mail service and “be saved”. There are a number of biases in play that could be affecting you:</p>
  70. <ul>
  71. <li><b>Authority bias.</b> Basecamp founders are household names in the tech industry, and they also have friends in high places. There is no shortage of prominent advocates who are now buzzing about the HEY e-mail service. This could make the opinions hit closer to your heart.</li>
  72. <li><b>Selective perception.</b> When we favour information that we agree with we may avoid information that could have a negative impact. The ability to choose who can send you e-mail may sound fantastic. So much so that any peripheral concerns about accessibility, lock-in and privacy may pass you by.</li>
  73. <li><b>Scarcity bias.</b> Choosing to initially be invitation-only is a purposeful choice by HEY. It works. Since it targets a human weakness.</li>
  74. <li><b>Bandwagon effect.</b> Many people are talking about it – at least in your circles – and asking for invites. But going along with the crowd, when the choice is not required, can be harmful when it’s not in an individual’s best interest. HEY is not free.</li>
  75. <li><b>Noble-edge effect.</b> Products of caring companies are seen as superior. Basecamp is not just any company. They’ve done a lot of impressive work, often challenge common truthisms and generally contribute in a positive way to concepts of designing and working. This of course does not mean one has to jump when they say jump.</li>
  76. <li><b>Speak-easy effect.</b> Words that are easier to say are more trustworthy and valuable. Hey, I don’t need to explain this one , right?</li>
  77. <li><b>FOMO.</b> Fear of missing out. What if this really is the next big thing? Trust me, then it won’t die.</li>
  78. </ul>
  79. <p>It may truly feel like you need the new shiny thing. And I’ll be honest, when I heard Jason Fried being <a href="https://www.stitcher.com/podcast/vox/recode-decode/e/71072616">interviewed by Kara Swisher on Recode Decode</a>, HEY did sound like the best thing since sliced bread. Kara was noticeably craving for it.</p>
  80. <p>And no one’s wrong to be entranced. The reason many of us are susceptible to the allurement of HEY is because the current state of e-mail really is failing many of us. We live with e-mail that needs fixing. From overload, from disarray, from mass-marketing and more.</p>
  81. <p>But before we decide that HEY is the answer to that fix, I’ll encourage anyone and everyone to stop, reflect and reason. Because getting excited about something before it has proven its worth can too easily led us astray.</p>
  82. <h2 id="A completely new e-mail address">A completely new e-mail address</h2>
  83. <p>Here’s the thing. Signing up for HEY and using it as your main e-mail address really will mean that you have to change your e-mail address. In many places. Or get used to managing yet another e-mail address. While this can solve a lot of things it could also lead to more labor for you.</p>
  84. <ul>
  85. <li>Will you need to maintain two e-mail addresses, and for how long? For many years if you still want that searchable archive.</li>
  86. <li>Will you forward all e-mail from the old account? Then how much have you solved?</li>
  87. <li>Can you migrate all your e-mail from the old account ?-The answer to that is a <a href="https://hey.com/faqs/#can-i-import-my-gmail-outlook-apple-email-into-hey">resounding no</a>. You are starting fresh in this aspect.</li>
  88. </ul>
  89. <p>If you’re prepared to switch e-mail address to solve your current problems with e-mail, and not bring any old e-mail with you, then you are prepared for some major changes in your e-mail management.</p>
  90. <p>Remember, many reviews of HEY are going to be positive in the beginning. Everyone will have vastly less e-mail and it will naturally feel liberating. The primary reason they will have vastly less e-mail is that they are starting a new e-mail address with zero e-mails. Something that could be achieved with just about any service.</p>
  91. <p>If you’re ready for the big change that a new e-mail address sets in motion, maybe you’re ready for decision-making that helps you seize more control over your inbox, rather than blindly trust another actor to know what’s best for you.</p>
  92. <p>Before I walk you through that decision process, let me share som other facts about HEY that may help you stop and think some more:</p>
  93. <h2 id="Locking your e-mails inside HEY">Locking your e-mails inside HEY</h2>
  94. <blockquote><p>HEY treats email in <a href="https://hey.com/faqs/#can-i-check-my-hey-email-with-my-existing-email-app">all sorts of special ways</a>, so off-the-shelf 3rd party email apps won’t work with HEY.<br/>
  95. — <i>from the HEY FAQ</i></p>
  96. </blockquote>
  97. <p>To use HEY you can only use their app and their website. There is no POP/IMAP access from other e-mail clients. If you ‘ve ever moved between accounts before you’ll remember this as a common way to migrate your e-mail, or reach multiple e-mail accounts from the same app.</p>
  98. <p><em>On a sidenote: To get your e-mail out of HEY, if you don’t like it, they offer MBOX as an export format. And as long as you’ve paid for a first year of service your <a href="http://hey.com">hey.com</a> e-mail is yours forever to forward wherever you want. So you could pay $99 for the heck of it, if that ’s how you like to, and can, play the game.</em></p>
  99. <p>More importantly, this closed garden means deviating from e-mail standards of structure, protocols and security. This does not have to be bad through-and-through, but should trigger questions around openness and transparency, and a wish to understand more before committing.</p>
  100. <h2 id="Accessibility">Accessibility</h2>
  101. <p>Some e-mail clients <a href="https://uxpajournal.org/usability-evaluation-of-email-applications-by-blind-users/">are better than others</a> when it comes to making content accessible to people with, for example, variations in visual, sensory and auditive perception. Being able to use <a href="http://www.accessibilitycentral.net/accessible%20email%20client%20mozilla%20thunderbird.html">your own client of choice</a> (software or online service) for e-mail can make all the difference between being able to even read it or not. This is one of several reasons the lack of POP and/or IMAP access can pose a huge problem.</p>
  102. <p>All users, regardless of ability, become reliant on the HEY web client and apps. This means they need to cater to many different needs and abilities. And as it turns out, some concerning lapses in accessibility have already been uncovered:</p>
  103. <blockquote><p>So I’m checking out @dhh’s new HEY email service as I’m keen to get away from Gmail and like what they preach about smaller sustainable business. After a few minutes of looking, there is inexcusable accessibility issues that means I won’t recommend it or subscribe. — <a href="https://twitter.com/NickColley/status/1272986177155538946">@NickColley</a></p>
  104. </blockquote>
  105. <p>When a new tool by design excludes people who are time and time again excluded in society and communities, it’s generally a tool I do not wish to support. Even if I personally could fare well with the service, the way I voice my values is by not supporting tools that reject others – and especially people who are forced into vulnerability by not being listened to enough.</p>
  106. <h2 id="Finding old e-mail">Finding old e-mail</h2>
  107. <p>If you’re anything like me, searching for e-mail with advanced operators is one of the ways I get by with e-mail management and working effectively with e-mail. HEY mentions little about how their search engine helps you do this. Again, remember that their search engine is all you’ve got since you can’t use another e-mail client to access your e-mail.</p>
  108. <h2 id="The rewards of being patient">The rewards of being patient</h2>
  109. <p>HEY does introduce some nifty ideas on threads, subjects lines and notifications. I doubt that these will go unnoticed by other e-mail providers. If proven successful, they will likely be copied in some form. Should this occur, I’ll certainly acknowledge that we have HEY to thank for pushing the envelope.</p>
  110. <p>Some features may already be available with other providers to some extent. In their marketing for the “Reply Later” feature, HEY writes:</p>
  111. <blockquote><p>You often know you need to get back to someone, but you don’t have time <i>right now</i>. Gmail, Outlook, and the rest, force you to come up with kludgy workarounds to deal with this (like marking an email unread so you hopefully remember to deal with it later). <b>That’s ridiculous.</b></p>
  112. </blockquote>
  113. <p>For anyone familiar with Gmail, there is a Snooze feature that allows you to accomplish what “Reply Later” does, and then some. I see people already posting on how much better designed the HEY version is. But hey, the marketing copy wasn’t really true to fact, was it?</p>
  114. <figure id="attachment_9488" align="aligncenter"><a href="https://i2.wp.com/axbom.blog/wp-content/uploads/2020/06/gmail-snooze.png?ssl=1"><img loading="lazy" src="https://i2.wp.com/axbom.blog/wp-content/uploads/2020/06/gmail-snooze.png?resize=300%2C284&amp;ssl=1" class="size-medium wp-image-9488 jetpack-lazy-image" alt="" data-recalc-dims="1" data-lazy-srcset="https://i2.wp.com/axbom.blog/wp-content/uploads/2020/06/gmail-snooze.png?resize=300%2C284&amp;ssl=1 300w, https://i2.wp.com/axbom.blog/wp-content/uploads/2020/06/gmail-snooze.png?w=540&amp;ssl=1 540w" data-lazy-sizes="(max-width: 300px) 100vw, 300px" data-lazy-src="https://i2.wp.com/axbom.blog/wp-content/uploads/2020/06/gmail-snooze.png?resize=300%2C284&amp;is-pending-load=1#038;ssl=1" srcset="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7"/><noscript><img loading="lazy" src="https://i2.wp.com/axbom.blog/wp-content/uploads/2020/06/gmail-snooze.png?resize=300%2C284&amp;ssl=1" class="size-medium wp-image-9488" alt="" srcset="https://i2.wp.com/axbom.blog/wp-content/uploads/2020/06/gmail-snooze.png?resize=300%2C284&amp;ssl=1 300w, https://i2.wp.com/axbom.blog/wp-content/uploads/2020/06/gmail-snooze.png?w=540&amp;ssl=1 540w" sizes="(max-width: 300px) 100vw, 300px" data-recalc-dims="1"/></noscript></a> Screenshot of the Snooze feature in Gmail.</figure>
  115. <p>Remember you’re looking to make your e-mail work for <b>you</b>. Keep your eye on the goal, we’re getting closer to the checklist.</p>
  116. <h2 id="Getting privacy conscious">Getting privacy conscious</h2>
  117. <p>One valid reason to avoid free Gmail is absolutely to avoid having personal data and attention traded as a product, which is often how you pay when you’re not paying with money. HEY underscores how Google’s email service relies on your data and rightfully emphasises how HEY blocks tracking pixels.</p>
  118. <p>On the other hand, if privacy is a primary reason for you to choose HEY, first have a look at the <a href="https://basecamp.com/about/policies/privacy/hey-subprocessors">sub-processors for the HEY e-mail service</a>. A sub-processor is a data processor who, on behalf of HEY, processes the personal data of customers. These are:</p>
  119. <ul>
  120. <li>Amazon Web Services. Cloud services provider.</li>
  121. <li>Braintree. Payment processing services.</li>
  122. <li>Google Cloud Platform. Cloud services provider.</li>
  123. <li>Help Scout. Help desk software.</li>
  124. <li>Mailchimp. Email newsletter service.</li>
  125. <li>Sentry. Error reporting software.</li>
  126. <li>TaxJar. Sales tax calculation.</li>
  127. <li>Zapier. Software integration service.</li>
  128. </ul>
  129. <p>It’s not a (very) long list, but may feel like a damning one depending on the trust you place in the companies on the list, and how much you wish to support them.</p>
  130. <p>I’m not surprised by the list at all, and I’m sure the data processing agreement between HEY and these companies is by the book. It’s just one of those wake-up calls reminding us all of how many companies choose to build online software today. Relying on a network of third-party platforms is often quicker and more cost-efficient in the short term.</p>
  131. <p><em>Note (update): The number of subprocessors does not necessarily affect privacy. This can all be well-managed, and I trust that it is. But complexity (and thus vulnerability) can increase with the number of dependencies – and for someone wishing to avoid certain companies, knowing where those dependencies lie can be important.</em></p>
  132. <p>When it comes to privacy, no service is of course stronger than its weakest link. And remember, there are other services out there blocking trackers as well.</p>
  133. <h2 id="Manage e-mail with care - A checklist for inbox improvement">Manage e-mail with care – A checklist for inbox improvement</h2>
  134. <p>Choosing HEY is a financial decision and you’ll do right by yourself if you set aside time to do your research. What HEY does well is bring to attention the importance of making choices around your e-mail that mitigate frustrations and benefit your well-being.</p>
  135. <h3 id="Decide if changing e-mail address is worth it">Decide if changing e-mail address is worth it</h3>
  136. <p>How much work am I willing to put into changing address where it would need to be changed? Do I send an alert to everyone in my address book and let them know? How long before I’ve just redirected all my e-mail to a new place? What is my exit strategy when I’m locked in and really don’t like it?</p>
  137. <p>And if you are changing e-mail address, which in some contexts very well could prove to be a smart step, are there <i>other services that would suit you better</i>? This is the crucial question before taking the plunge. Because it will likely be some time before you’re prepared to move again.</p>
  138. <p>I’ve listed a few services at the end of the article, most of them with a greater focus on privacy.</p>
  139. <h3 id="Decide who can e-mail you">Decide who can e-mail you</h3>
  140. <p>To be fair, the opt-in feature of HEY sounds hugely appealing. Nobody could send me e-mail without my approval. Whether or not it’s a killer feature remains to be seen. It’s however not unique. Another provider is launching with the same functionality this summer, <a href="https://techcrunch.com/2020/04/07/new-email-service-onmail-will-let-recipients-control-who-can-send-them-mail/">OnMail</a> – built by the team behind Edison Mail.</p>
  141. <p>If it turns out to be a hit, I expect others to follow suit with this option. Meanwhile, your current provider will offer some variant of blocking to give you more control. I encourage you to go ahead and block generously.</p>
  142. <h3 id="Opt-out of seeing things you don’t need to act on or reply to">Opt out of seeing things you don’t need to act on or reply to</h3>
  143. <p>Whether you’re sticking with your current e-mail or changing to a new one you’ll do good to spend time opting out of newsletters, marketing and notifications from social platforms.</p>
  144. <p>I’ve been applying this strategy extensively with all e-mails that arrive over the past six months and the effect is noticeable. Generally there are three things you may want to do:</p>
  145. <ul>
  146. <li>Opt-out of things you do not want. This sounds obvious but you’d be surprised to see how many times I see people delete time and time again instead of unsubscribing.</li>
  147. <li>Filter into a folder if there are senders you never want to see in your inbox but may want to find when you search</li>
  148. <li>Use a separate service for newsletters you may want to read, keeping them out of your inbox. I’ve written about this in a separate post: <a href="https://axbom.blog/newsletters-the-mindful-way/">Subscribing to newsletters the mindful way</a>. This advice is valid even if you do choose to sign up for HEY.</li>
  149. </ul>
  150. <p>Just do not use services like <a href="https://axbom.blog/delete-unroll-me-revoke-access/">unroll-me</a> to unsubscribe.</p>
  151. <h3 id="Who gets to see my e-mail address?">Who gets to see my e-mail address?</h3>
  152. <p>This is where many of us have gone wrong in the past. By sharing and posting and signing up with the same e-mail address all over the place we have set ourselves up for the misuse that we are now experiencing.</p>
  153. <p>Your e-mail address is a thing of great value and more of us should probably start treating it as such.</p>
  154. <p>Are you signing up for a new service that you have no prior relationship with and have no specific reason to trust? You can decide to not give them your real e-mail address. For this very purpose, I use services such as <a href="https://burnermail.io">burnermail</a>*. It will generate an anonymous e-mail and you can sign up with a unique address for every service you use. This allows you to block each address if it’s being misused.</p>
  155. <p>As a bonus, trackers and advertisers will find it harder to follow you online. Your e-mail is a unique identifier that is often used to cross-reference databases to find out more about you from third parties. See what I mean about “thing of great value”?</p>
  156. <p>Think again about who you want to trust with this value.</p>
  157. <p><em>*For variants of burner mail, do an online search for “disposable e-mail” or “temporary e-mail”.</em></p>
  158. <h3 id="Who gets my time?">Who gets my time?</h3>
  159. <p>I get a huge amount of e-mail. Some are really interesting messages from students, podcast listeners, researchers, journalists and junior designers from all over the world. For me, this is why e-mail is awesome and why an opt-in solution may not work for me. It’s not always obvious who I’d want to reject as a sender. And what learnings it could cost me to do that.</p>
  160. <p>Obviously replying to all these e-mails costs me as well. And sometimes there is just no time. For me, acknowledging the impossibility of responding to everyone is important. It allows me to be kinder to myself even when I feel bad about failing to reply promptly.</p>
  161. <p>One thing I’ve done strictly to make myself feel better is to have a short template that I use to respond when my priorities are elsewhere. It’s most often used for e-mails where I get a lot of questions around best ways forward for a design challenge or when being asked to be interviewed for a dissertation.</p>
  162. <blockquote><p>Thanks for your e-mail. I am currently unable to respond to all of the many e-mails that reach me, and I will not be able to respond to yours. This is not a reflection of the content of your e-mail. This is my approach for prioritising my well-being and personal goals during periods where my capacity for attention is scarce.</p>
  163. <p>Thank you again for reaching out and I wish you all the best.</p>
  164. <p>Kind regards,<br/>
  165. /Per</p>
  166. </blockquote>
  167. <p>I reply with this and then I can archive the e-mail. In fairness this usually happens after I’ve snoozed the e-mail several times. Realising your own limits can be painful.</p>
  168. <h2 id="Full disclosure">Full disclosure</h2>
  169. <p><span class="todo-text">I’ve signed up for the HEY e-mail service, gained access and started the trial. I’ve done this out of curiosity getting the better of me, for purposes of understanding the service better and getting enough experience to have an educated opinion on it. In the end it may also be a way for me to protect my brand name on a potentially popular service.</span></p>
  170. <p>The funny things is this: I just don’t know who I would tell about this e-mail address and why I should. It seems I can get a pretty good handle of managing my e-mail without it, in an interface I am already comfortable with.</p>
  171. <p>Furthermore, the seven (7!) e-mails that immediately clutter my “Imbox” (yes, that’s what they call it), with tutorials on how to use the service, seems like a disconnect from any message of simplicity. First impressions leave me… bewildered.</p>
  172. <figure id="attachment_9490" align="aligncenter"><a href="https://i1.wp.com/axbom.blog/wp-content/uploads/2020/06/hey-imbox-emails.png?ssl=1"><img loading="lazy" src="https://i0.wp.com/axbom.blog/wp-content/uploads/2020/06/hey-imbox-emails-1024x489.png?resize=640%2C306&amp;ssl=1" class="size-large wp-image-9490 jetpack-lazy-image" alt="" data-recalc-dims="1" data-lazy-srcset="https://i1.wp.com/axbom.blog/wp-content/uploads/2020/06/hey-imbox-emails.png?resize=1024%2C489&amp;ssl=1 1024w, https://i1.wp.com/axbom.blog/wp-content/uploads/2020/06/hey-imbox-emails.png?resize=300%2C143&amp;ssl=1 300w, https://i1.wp.com/axbom.blog/wp-content/uploads/2020/06/hey-imbox-emails.png?resize=768%2C366&amp;ssl=1 768w, https://i1.wp.com/axbom.blog/wp-content/uploads/2020/06/hey-imbox-emails.png?resize=1536%2C733&amp;ssl=1 1536w, https://i1.wp.com/axbom.blog/wp-content/uploads/2020/06/hey-imbox-emails.png?resize=2048%2C977&amp;ssl=1 2048w, https://i1.wp.com/axbom.blog/wp-content/uploads/2020/06/hey-imbox-emails.png?w=1280&amp;ssl=1 1280w, https://i1.wp.com/axbom.blog/wp-content/uploads/2020/06/hey-imbox-emails.png?w=1920&amp;ssl=1 1920w" data-lazy-sizes="(max-width: 640px) 100vw, 640px" data-lazy-src="https://i0.wp.com/axbom.blog/wp-content/uploads/2020/06/hey-imbox-emails-1024x489.png?resize=640%2C306&amp;is-pending-load=1#038;ssl=1" srcset="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7"/><noscript><img loading="lazy" src="https://i0.wp.com/axbom.blog/wp-content/uploads/2020/06/hey-imbox-emails-1024x489.png?resize=640%2C306&amp;ssl=1" class="size-large wp-image-9490" alt="" srcset="https://i1.wp.com/axbom.blog/wp-content/uploads/2020/06/hey-imbox-emails.png?resize=1024%2C489&amp;ssl=1 1024w, https://i1.wp.com/axbom.blog/wp-content/uploads/2020/06/hey-imbox-emails.png?resize=300%2C143&amp;ssl=1 300w, https://i1.wp.com/axbom.blog/wp-content/uploads/2020/06/hey-imbox-emails.png?resize=768%2C366&amp;ssl=1 768w, https://i1.wp.com/axbom.blog/wp-content/uploads/2020/06/hey-imbox-emails.png?resize=1536%2C733&amp;ssl=1 1536w, https://i1.wp.com/axbom.blog/wp-content/uploads/2020/06/hey-imbox-emails.png?resize=2048%2C977&amp;ssl=1 2048w, https://i1.wp.com/axbom.blog/wp-content/uploads/2020/06/hey-imbox-emails.png?w=1280&amp;ssl=1 1280w, https://i1.wp.com/axbom.blog/wp-content/uploads/2020/06/hey-imbox-emails.png?w=1920&amp;ssl=1 1920w" sizes="(max-width: 640px) 100vw, 640px" data-recalc-dims="1"/></noscript></a> Screenshot of the 7 e-mails in my “Imbox”</figure>
  173. <p>Note that this article is not intended as a takedown of the HEY e-mail service. I’m sure it can provide value to a lot of people. Just not everyone. My text is an emotional response to an explosion of hype over the past week and I’ve made an effort to bring more thoughtfulness to the conversation. I want to highlight shortcomings and the importance of reasoned decisions when jumping on the bandwagon. No service is perfect but a strong ability to listen to reflections and feedback will likely help a company improve its products. I do believe Basecamp to be one such company. And I especially hope for a considered response to the weaknesses in accessibility .</p>
  174. <p>There’s a chance HEY can change our relationship to e-mail. Then again, there’s also a big chance it won’t. But if this made you sit down and think about how you can improve your management of electronic mail, even if you don’t sign up for HEY, then perhaps the hype was worth it.</p>
  175. <p><hr/>
  176. <h3 id="Footnote about custom domains">Footnote about custom domains</h3>
  177. <p><i>Eventually</i> you’ll be able to set up your own domain with <a href="http://hey.com">hey.com</a> but there is no indication of how soon or far off that is. A multi-user option with this feature, targeted at businesses, is said to be ready this year.</p>
  178. <p>Generally, if you own your own domain and can afford the cost of custom domains, moving between e-mail providers is an easier choice, since your e-mail address does not have to change. Obviously, only a small percentage of people enjoy this opportunity,</p>
  179. <h3 id="List of E-mail services">List of E-mail services</h3>
  180. <p>More and more people are waking up to the importance of privacy. Here is a list of small tech e-mail providers that raise the bar on privacy.</p>
  181. <ul>
  182. <li><a href="https://www.fastmail.com">Fastmail</a> (Australia)</li>
  183. <li><a href="https://kolabnow.com">KolabNow</a> (Switzerland)</li>
  184. <li><a href="https://mailbox.org/">Mailbox</a> (Germany)</li>
  185. <li><a href="https://posteo.de/en">Posteo</a> (Germany)</li>
  186. <li><a href="https://protonmail.com">ProtonMail</a> (Switzerland)</li>
  187. </ul></p>
  188. </main>
  189. </article>
  190. <hr>
  191. <footer>
  192. <p>
  193. <a href="/david/" title="Aller à l’accueil">🏠</a> •
  194. <a href="/david/log/" title="Accès au flux RSS">🤖</a> •
  195. <a href="http://larlet.com" title="Go to my English profile" data-instant>🇨🇦</a> •
  196. <a href="mailto:david%40larlet.fr" title="Envoyer un courriel">📮</a> •
  197. <abbr title="Hébergeur : Alwaysdata, 62 rue Tiquetonne 75002 Paris, +33184162340">🧚</abbr>
  198. </p>
  199. <template id="theme-selector">
  200. <form>
  201. <fieldset>
  202. <legend>Thème</legend>
  203. <label>
  204. <input type="radio" value="auto" name="chosen-color-scheme" checked> Auto
  205. </label>
  206. <label>
  207. <input type="radio" value="dark" name="chosen-color-scheme"> Foncé
  208. </label>
  209. <label>
  210. <input type="radio" value="light" name="chosen-color-scheme"> Clair
  211. </label>
  212. </fieldset>
  213. </form>
  214. </template>
  215. </footer>
  216. <script type="text/javascript">
  217. function loadThemeForm(templateName) {
  218. const themeSelectorTemplate = document.querySelector(templateName)
  219. const form = themeSelectorTemplate.content.firstElementChild
  220. themeSelectorTemplate.replaceWith(form)
  221. form.addEventListener('change', (e) => {
  222. const chosenColorScheme = e.target.value
  223. localStorage.setItem('theme', chosenColorScheme)
  224. toggleTheme(chosenColorScheme)
  225. })
  226. const selectedTheme = localStorage.getItem('theme')
  227. if (selectedTheme && selectedTheme !== 'undefined') {
  228. form.querySelector(`[value="${selectedTheme}"]`).checked = true
  229. }
  230. }
  231. const prefersColorSchemeDark = '(prefers-color-scheme: dark)'
  232. window.addEventListener('load', () => {
  233. let hasDarkRules = false
  234. for (const styleSheet of Array.from(document.styleSheets)) {
  235. let mediaRules = []
  236. for (const cssRule of styleSheet.cssRules) {
  237. if (cssRule.type !== CSSRule.MEDIA_RULE) {
  238. continue
  239. }
  240. // WARNING: Safari does not have/supports `conditionText`.
  241. if (cssRule.conditionText) {
  242. if (cssRule.conditionText !== prefersColorSchemeDark) {
  243. continue
  244. }
  245. } else {
  246. if (cssRule.cssText.startsWith(prefersColorSchemeDark)) {
  247. continue
  248. }
  249. }
  250. mediaRules = mediaRules.concat(Array.from(cssRule.cssRules))
  251. }
  252. // WARNING: do not try to insert a Rule to a styleSheet you are
  253. // currently iterating on, otherwise the browser will be stuck
  254. // in a infinite loop…
  255. for (const mediaRule of mediaRules) {
  256. styleSheet.insertRule(mediaRule.cssText)
  257. hasDarkRules = true
  258. }
  259. }
  260. if (hasDarkRules) {
  261. loadThemeForm('#theme-selector')
  262. }
  263. })
  264. </script>
  265. </body>
  266. </html>