Thursday is shortened to Th or Thu, though. Otherwise it’s just the same as Tuesday.

With all due respect, go $fsck yourself

By installing Linux, right?

Right?

You better filesystem check yourself before you filesystem wreck yourself

I recently saw a self-hosted imgix/cloudinary alternative. I thought I starred it on gh, but apparently not and I can’t remember the name.

Edit
I think this was it:
https://github.com/imgproxy/imgproxy

But also, on a second read of your post, I now realize what you are looking for is right here:
https://squoosh.app/

It’s open source and it’s entirely client-side. It allows you to customize the settings to compress your image to the file size and format you need and maintain as much as the quality as possible. I can’t think of a simpler solution that works across all your devices.

That’s a good point, and it aligns with the idea of the large group migrating from reddit. Thanks for that perspective.

It’s always just been obvious to me. I’ve heard many people say this, too.

Ironically, bullets already have jackets. So using the clothing item is kinda redundant. (Yes, that’s probably the joke)

I believe the ring does have the ability to exert its magic on its surroundings. It can also change its size. So if you took this scenario seriously, I think it could break the zip tie.

So Kirk holding those Cheetos to his cheek before putting them in his mouth?

“I get you don’t think it’s important, but there’s plenty of sysadmins that do, with experience backing that up.” Is a passive aggressive remark designed to belittle me based on a notion that you have experience and qualifications over me that makes your point more valid, and also that other people with experience and qualifications would hypothetically agree. It very clearly implicitly claims that I am not a sysadmin and that lacking sysadmin experience is why I am wrong. This does not add to the point at all and provides, so it could not be seen as any other way than an expression of that. However, I still gave you the benefit of doubt and I felt I expressed pretty rationally that that remark does not add to the comment and is disrespectful and that it may have been unintentional to be disrespectful.

But now “I think this guy just likes to argue.” and “it sure escalated with the other commenter” is clear evidence that you were just trying to be rude. I certainly don’t like to “argue” but much more than that I don’t like to be disrespected. So I will stand up for myself and call out such poor behavior.

Drive errors would pile up on critical systems because they didn’t filesystem check themselves before they filesystem wrecked themselves

Jabba could’ve been NalHutta

To add to that, to effectively use docker and basically anything important for self-hosting is to learn the basics of Linux.

A good resource for that is https://learnlinux.tv/

At first I read the title as

How much pareidolia is too much?

And I was bracing for a fun thread, but then my brain caught up and now I’m disappointed.

Yeah, I’m not buying into your trolling. Go somewhere else.

Interesting how you feel the need to disingenuously misrepresent my point.

Opponents beware

What registrar was that? Were they as big as Cloudflare? How exactly did they “go tits up”? Isn’t the situation you describe a completely different scope from an individual’s usecase? It’s also an anecdotal point of data without including the full context of how common that situation is. “It happened to me once, and I have heard stories” does not necessarily mean it’s common enough for everyone to prepare for every time. I’ll remain skeptical of the

Mainly, though, I’m not saying it’s a bad idea in total. I just think that for someone who is inexperienced with DNS management and self-hosting, those types of concerns are already unlikely and just keeping the environment simple and cost less has far more value than being prepared for unlikely scenarios. It could even prevent self-inflicted issues by keeping it simple, which would be far more likely than Cloudflare’s infrastructure creating a problem that they have to remediate themselves.

If anything, the true argument for risk mitigation would be to have multiple DNS servers for redundancy.

I just don’t believe that, in this type of usecase, it’s worth pressing for and that there’s more of an argument to keep it simple.

Additionally, you can leave out trying to use your credentials and a hypothetical group of people to make your argument for you. It makes it seem like you’re trying to talk down.

I get that you’re likely exaggerating by saying “it’s no extra work”, but managing another account is markedly extra work. It will also cost extra because Cloudflare does not add any markup for registration, which is why they are the cheapest registrar.

I think the convenience and reduction of cost greatly outweighs the highly unlikely situation where “something goes fucky”. If it does, then what? You can’t make DNS updates for a little while?

The most likely reason to get locked out is billing issues, or maybe you lost your login information or something like that, which is going to be the same risk regardless of who your registrar is. Otherwise you’d have to be involved in some sort of legal issue associated with your domain and that is a much deeper issue than can be solved by simply changing nameservers.