- cross-posted to:
- [email protected]
- webdev
- cross-posted to:
- [email protected]
- webdev
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.
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.
Fixed it now, I didn’t realize that the copy and paste had those spaces in front.
Thanks!
Could be your client. With Sync it properly word wraps, and for myself I actually find this font easier to read
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.)
Sync markup/rendering is presently a semi-completed conversion from reddit’s and it’s functional enough.
It doesn’t wrap in the default web interface.
And the default web interface should absolutely be our standard.
Yeah, I love Sync, but currently it’s the last thing I would pick to set a standard
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.
They’re talking specifically about the word wrapping. Note in their screenshot it is properly rendered in monospace code block font.
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.
Readable on Voyager as well.
EDIT: Not to say it looks good, but it’s readable.
The syntax colouring, really doesn’t help though. Standard font looks better for text blocks than a code block.