geez people are already having AI psychosis, are we also going to have anti-AI psychosis now?

To me it’s just this is too perfect. Like did everything really come together by pure chance to make this happen? Obviously it’s possible, but it definitely rings alarm bells and it couldn’t hurt to check.

how about you fucking stop then???

Fun fact, the current pronunciation of “lose” likely comes from people in the past confusing it with “loose”! Quoting the OED:

The regular modern English pronunciation representing Old English losian would be /ləʊz/; the standard English pronunciation /luːz/ seems to be due to association with LOOSE v., which in some contexts (e.g. to loose hold) closely approaches this verb in meaning.

Otherwise it would probably be pronounced as /ləʊz/ (similar to nose, pose, close, etc.).

So people in the past doing the conflation - totally fine, accepted, and normal. Because that’s what you learned from the start. But people now doing the same kind of conflation - unacceptable, illiterate, stupid. Because that’s new and different.

People are afraid of change, who knew…

words merging is a thing that happened countless times in English’s history. why make a fuss about this one?

you are right. languages change whether you like it or not.

if you lived in china long term you wouldn’t have these problems because you would have already given up all your personal data and privacy to the state. but hey, you’d get some convenience out of it, so not so bad, right?

That orange face book is scaring me. Why is he looking at me like that.

Ok what are we going to call them now? Gitslop? Sloplab?

Such a nice concept though. Wish some real human artist will remake it…

Hmm interesting name

On Linux you can mask out bad memory ranges. Don’t know about Windows.

oh my god

our org forbids plain http

is redirecting http to https also out of the question? because let’s encrypt HTTP-01 accepts http -> https redirects:

Our implementation of the HTTP-01 challenge follows redirects, up to 10 redirects deep. It only accepts redirects to “http:” or “https:”, and only to ports 80 or 443. It does not accept redirects to IP addresses. When redirected to an HTTPS URL, it does not validate certificates.

Half a dozen sounds like a lot, kinda curious what you are running? If they all are web services maybe use a reverse proxy or something?

Depends on which DNS service you are using, a plugin might already exist that would do it for you. e.g. I use cloudflare for DNS and certbot is able to automatically set the txt record.

Well it should be as short as possible while still being practical. LE doesn’t have infinite server compute, renewal also takes some amount of time, plus if they make the validity too short people might stop using them (pretty evident judging from sentiment here) and move to other CAs and make what they do pointless.

45 days are still plenty of time yet people are already complaining. Does make me worry.

You can already get 6-day certificates if you want to https://letsencrypt.org/2025/01/16/6-day-and-ip-certs

I’m sorry but if you aren’t using automated renewals then you are not using let’s encrypt the way it’s intended to be used. You should take this as an opportunity to get that set up.

Wait, how’s this worse? This makes the Internet safer by reducing the window a leaked key can do harm.