Since its inception, Let’s Encrypt has been sending expiration notification emails to subscribers that have provided an email address to us. We will be ending this service on June 4, 2025. The decision to end this service is the result of the following factors:

  • Over the past 10 years more and more of our subscribers have been able to put reliable automation into place for certificate renewal.
  • Providing expiration notification emails means that we have to retain millions of email addresses connected to issuance records. As an organization that values privacy, removing this requirement is important to us.
  • Providing expiration notifications costs Let’s Encrypt tens of thousands of dollars per year, money that we believe can be better spent on other aspects of our infrastructure.
  • Providing expiration notifications adds complexity to our infrastructure, which takes time and attention to manage and increases the likelihood of mistakes being made. Over the long term, particularly as we add support for new service components, we need to manage overall complexity by phasing out system components that can no longer be justified.
  • mox@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    26
    ·
    edit-2
    17 hours ago

    My “client” is Lemmy’s native UI, and is rendering it correctly according to markdown and html specs. If your client is wrapping it or using a variable-width font, then that’s convenient for you in this case, but it’s violating the spec. (This is somewhat common in mobile apps, so I guess you’re reading on a phone.)

    • can@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      1
      ·
      15 hours ago

      Sync markup/rendering is presently a semi-completed conversion from reddit’s and it’s functional enough.