Let's Encrypt Ending Support for Expiration Notification Emails

[jeena@piefed.jeena.net]

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.

[vk6flab@lemmy.radio]

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]

OP, can you please remove the four spaces preceding each paragraph in your post? That syntax is for code formatting. It puts each paragraph into a single line, forcing readers into painstaking horizontal scrolling to be able to read each one. It's like trying to read a book through a keyhole.

[mrquallzin@lemmy.world]

Could be your client. With Sync it properly word wraps, and for myself I actually find this font easier to read

[atmur@lemmy.world]

Readable on Voyager as well.

[mox@lemmy.sdf.org]

My client is rendering it correctly according to markdown and html specs. If your client is wrapping it, then that's convenient for you in this case, but it's violating the spec.

[mrscottytay@sh.itjust.works]

The syntax colouring, really doesn't help though. Standard font looks better for text blocks than a code block.

[faresh@lemmy.ml]

It doesn't wrap in the default web interface.

[mrscottytay@sh.itjust.works]

Much easier to read

[299792458ms@lemmy.zip]

It is not the client, that it is actually how markdown works. Every markdown guide specifically tells to avoid this indentation because its meant for code blocks which by default do not wrap text lines.

[jeena@piefed.jeena.net]

Ah thanks for pointing it out, I fixed the formatting.

[jeena@piefed.jeena.net]

Fixed it now, I didn't realize that the copy and paste had those spaces in front.

[sugar_in_your_tea@sh.itjust.works]

And the default web interface should absolutely be our standard.

[inclementimmigrant@lemmy.world]

Well that kind of sucks. I wish they had more tutorials about how to automate then because if you're not using http-01 via certbot due to port 80 being blocked, which if you're on a residential line it's pretty common, so then you have to use dns-01 and manual hooks which isn't exactly clear for and documented well.

[idkwhatusernametoputherelolol@lemmy.dbzer0.com]

Calandar Apps have joined the chat

(Seriously, do people just not use them to set reminders?

[jeena@piefed.jeena.net]

I think yeah, most people don't use calendars.My wife doesn't even use one at work.

My dad though started using it after I implemented audible announcements of them in Home Assistant. He normally doesn't use his phone or computer much, but this way anywhere he is in his house he is reminded 90min before the event and then at the event again. With this he never misses appointments at doctors and so on anymore. That was what pushed him to use a digital calendar, every missed appointment costs quite some money.

[can@sh.itjust.works]

Yeah, I love Sync, but currently it's the last thing I would pick to set a standard

[can@sh.itjust.works]

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

[can@sh.itjust.works]

They're talking specifically about the word wrapping. Note in their screenshot it is properly rendered in monospace code block font.

[lodemike@lemmy.today]

????????

Literally this is how I know if something is wrong