this post was submitted on 03 Feb 2025
339 points (98.8% liked)

Technology

63134 readers
3461 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 content.
  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, to ask if your bot can be added please contact us.
  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
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
339
Let's Encrypt Ending Support for Expiration Notification Emails (letsencrypt.org)
submitted 2 weeks ago* (last edited 2 weeks ago) by jeena@piefed.jeena.net to c/technology@lemmy.world
48 comments fedilink hide all child comments
 

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.
you are viewing a single comment's thread
view the rest of the comments
[–] mox@lemmy.sdf.org 100 points 2 weeks ago* (last edited 2 weeks ago) (14 children)

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.

[–] MrQuallzin@lemmy.world 4 points 2 weeks ago (5 children)

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 31 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

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 weeks ago

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

[–] Faresh@lemmy.ml 10 points 2 weeks ago (1 children)

It doesn't wrap in the default web interface.

[–] sugar_in_your_tea@sh.itjust.works 6 points 2 weeks ago (1 children)

And the default web interface should absolutely be our standard.

[–] can@sh.itjust.works 5 points 2 weeks 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 weeks ago (1 children)

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 weeks ago* (last edited 2 weeks ago) (1 children)

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 weeks 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 6 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

Readable on Voyager as well.

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

[–] MrScottyTay@sh.itjust.works 10 points 2 weeks 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 weeks ago* (last edited 2 weeks 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.

load more comments (8 replies)