331
submitted 2 months ago* (last edited 2 months ago) by jeena@piefed.jeena.net to c/technology@lemmy.world

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.
all 35 comments
sorted by: hot top controversial new old
[-] mox@lemmy.sdf.org 94 points 2 months ago* (last edited 2 months ago)

OP, can you please remove the four spaces preceding each paragraph in your post? That syntax is for code formatting. It triggers a monospace font and 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.

[-] jeena@piefed.jeena.net 36 points 2 months ago

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

[-] mox@lemmy.sdf.org 11 points 2 months ago
[-] MrQuallzin@lemmy.world 12 points 2 months ago

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

[-] mox@lemmy.sdf.org 32 points 2 months ago* (last edited 2 months 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 1 points 2 months ago

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

[-] Faresh@lemmy.ml 10 points 2 months ago

It doesn't wrap in the default web interface.

[-] sugar_in_your_tea@sh.itjust.works 6 points 2 months ago

And the default web interface should absolutely be our standard.

[-] can@sh.itjust.works 5 points 2 months ago

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

[-] 299792458ms@lemmy.zip 10 points 2 months ago

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.

[-] can@sh.itjust.works 3 points 2 months ago* (last edited 2 months ago)

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

[-] 299792458ms@lemmy.zip 1 points 2 months ago

I know, clients not wrapping lines in codeblocks are also "rendering properly". Wrapping it's up to the client's parser, reason why I noted to use the aproppriate syntax regardless.

[-] atmur@lemmy.world 9 points 2 months ago* (last edited 2 months ago)

Readable on Voyager as well.

EDIT: Not to say it looks good, but it's readable.

[-] MrScottyTay@sh.itjust.works 10 points 2 months ago

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

[-] echodot@feddit.uk 3 points 2 months ago* (last edited 2 months ago)

If it was actually code that isn't the correct behavior. Code doesn't line wrap, because line breaks mean something in most languages, so introducing virtual line breaks causes confusion.

[-] vk6flab@lemmy.radio 26 points 2 months ago

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.

[-] MrScottyTay@sh.itjust.works 8 points 2 months ago

Much easier to read

[-] jeena@piefed.jeena.net 3 points 2 months ago

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

[-] inclementimmigrant@lemmy.world 11 points 2 months ago

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.

[-] catloaf@lemm.ee 5 points 2 months ago

What manual hooks? All the systems I've used LE certs in have supported fully automatic DNS challenges.

[-] rumba@lemmy.zip 2 points 2 months ago

Can't speak for OP but they can't seem automate my network solutions DNS through plugins.

I don't know why in the hell they are such sticklers about wild card domains. Just let me off it on any working domain, hell, force me to author on this is my wildcard.Mydomain.com. the DNS authorization is an unnecessary

[-] catloaf@lemm.ee 1 points 2 months ago

I mean that's just another item in the long list of reasons you should not be using Network Solutions.

[-] rumba@lemmy.zip 1 points 2 months ago

You're not wrong, but they don't support quite a lot.

[-] diamond 2 points 2 months ago

If you use Caddy with ACME DNS, all of this can be automated.

If you also use Cloudflare, you can do that + traffic routing with cloudflared without any need for port forwarding .

[-] inclementimmigrant@lemmy.world 1 points 2 months ago

Using nginx with certbot and duck DNS and I ended up using the manual option with a authentication, clean up, and post bash scripts and then final script that I called from chron job that called the scripts every three months.

Just from a beginning user of let's encrypt, and while a software developer I'm not versed in backend development, and I found the documentation to be a bit hit or miss, understandable with a plethora of open source projects. Using certbot, because that's the rabbit hole let's encrypt first send you down, the documentation while available isn't easy to navigate in my opinion and it took me a while to track down the variables used to pass down the text and the bulk examples found were all using http-01.

I just think that if your not someone with a background in tech, just wanting to get a server to and running with ssl following a bunch of other tutorials and guides, it could be a bit better to get adoption.

[-] Fuck_u_spez_@sh.itjust.works 1 points 2 months ago* (last edited 2 months ago)

Is that mostly for ISPs running CGNAT?

this post was submitted on 03 Feb 2025
331 points (100.0% liked)

Technology

69247 readers
3295 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years ago
MODERATORS