KairuByte

Oh… boy, that’s an angle I hadn’t considered.

Doesnt any dns challenge currently just look at domain.com to see if it can create the lower cert?

Cloudflare doesn’t pass the cert you have through, it generates its own cert (or uses one you provide).

Cloudflare will only handle certs to the first subdomain, after that you either have to provide them. Or they may charge for it, I’m not sure anymore, but I’m going full free tier so I still need to provide them.

Oh this looks very promising, thank you!!

I’m not currently using kubernetes but its something I’ve thought of looking into before. I’ll definitely give that a look for better terminology though!

I’m looking for a way to both get a sub wildcard (I don’t know the exact wording but *.sub.domain.com would be an example) and push it into cloudflare. So a direct certbot install with manual distribution, while technically possible, sounds absolutely abysmal. I’d rather forget the entire idea than deal with that.

Centralized SSL certificate management?

I’m not even sure this title makes sense. I’m looking to handle LE certificates in cloudflare automatically. Specifically multi level subdomains.

You can hand off subdomain certs to them for single level, but the moment you want multi level you need to manage the certs yourself.

What I’m hoping for is an open source/self hosted tool that is meant to handle certificate requests and distribution. I just don’t know if such a tool even exists, and searching around hasn’t yielded results.

Does anyone have any thoughts?

You do realize that in C# at least, these compile to strongly typed variables? Barring a major change, such as migrating from 16 to 32 bit, you know what those value types are, you’re just not having to write them out. It saves you from having to type “LongDescriptiveTypeDescriptionBecauseSomeoneWasOverlyVerboseInTheirNaming” which is a small but nice thing to have. We arent talking about dynamics here.

Er… okay, yes. That would be quite the annoyance, but thats a bit of an edge case in this instance. I’d also wager that current implementations of IDEs would allow you to intelligently replace int with Int16/Int32/Int64 depending on the context before migration. I believe Visual Studio proper has that as an option in its code analysis and cleanup tool. You can also do the same for var => string typing if I remember correctly.

Not… really. I can kinda see where you’re coming from, but if you are assigning a .ToString() to a variable, the only type it could be is a string.

It’s not guessing, it’s inference. You’ve provided enough information to know what the type is, so it is now that type. The moment you introduce ambiguity, such as var test = 1 there are many things that variable could be, so you can no longer infer its type.

Inference is not guessing. Can it go wrong? Certainly! But its quite rare. And the solution in those rare cases is explicit typing.

Have fun banning hammers dude.

Jesus dude you’re just comin at me with the insults, kinda ironic you’re calling me an asshole. 🤣

Your article explicitly states they are banning the assholes. Which is good. It’s a very weird choice of article to back up your “meta knows the hardware is a problem” claim.

Bottom line is, humans are assholes. This is known. They are assholes with all kinds of tech, according to you that includes Lemmy. They can also be creeps here. That doesn’t mean the tech itself is the problem.

I’ll spell it out this time, a hammer can be used to break a window, does that mean we should ban hammers?

Jesus dude you’re just comin at me with the insults, kinda ironic you’re calling me an asshole. 🤣

Your article explicitly states they are banning the assholes. Which is good. It’s a very weird choice of article to back up your “meta knows the hardware is a problem” claim.

Bottom line is, humans are assholes. This is known. They are assholes with all kinds of tech, according to you that includes Lemmy. They can also be creeps here. That doesn’t mean the tech itself is the problem.

I’ll spell it out this time, a hammer can be used to break a window, does that mean we should ban hammers?

The article which does nothing to suggest meta glasses were actually an integral part to this? Again, cell phone in shirt pocket. Accomplishes the same thing. Or hell, a pen cam which is a thing that’s been around for decades and is a fraction of the cost.

The problem is that an asshole decided to ignore the “no recording” request. There are dozens if not hundreds of discreet ways the asshole could have done this, in the same way there are dozens of tools you can use to break a window.

I mean, they absolutely do. You can usually get away with the generics but I’ve run across my fair share of monitors that support minimum resolutions until the appropriate driver is installed.

Clarification, healthcare usually lasts till the end of the month, because that’s what already been paid for.

Ha, honestly as someone living in the US that sounds like a lot more than I’ve ever got.

Fuck man, you’re right. Let’s ban cameras in general, they can be used for creepy things. Ban phones too, those can be used for creepy things.

The tech is useful, and has potential to become much more useful in the future. Being a Luddite about the tech doesn’t solve the problem, it just ignores the assholes.

“Yeah, so we punished our end users because of something a manufacturer did.”

Like, I get the sentiment. But “no pushing drivers” ain’t the solution.

I also have to wonder if M$ can do that? If the drivers are being loaded by the monitor and not something like windows update, M$ has virtually no control over it.

To connect to those, you’re going through a Datacenter, or your not online.