My dude, look into tailscale. Same concept, just as easy to set up, and likely more features. And it’s human made, human tested, and used by a large number of different type of end users.

Haha yeah, it sounds like a joke doesn’t it. I was thinking of the shark that’s known for eating license plates and nails. Or the one that eats car tires.

How many trips is 2 tons of pea gravel one at a time?

To be fair, sharks bite a lot of things.

Yes, it’s also how I run all my services. I checked just this moment, and locally my certs verified by field is Let’s Encrypt, while remotely that field is Google Trust Services

I have never personally provisioned a cert from Google. I have only ever utilized Let’s Encrypt. That leaves just one involved party that could have requested, received and presented this cert: Cloudflare.

As you wish, wasn’t meant as a gendered ident so apologies.

I’m actually not familiar with how much environmental damage is done by training vs using. My initial assumption was that training would be less, by many many factors, because it “happens once” while the usage is constant and scales with the number of users. But that is admittedly an assumption made out of ignorance.

And to be clear, I’m not really trying to tell you you’re wrong, just trying to make my position clear since Lemmy is very anti AI in general.

Hey guy/gal/genderfluid pal, the cat is out of the bag. Either we embrace it for what it can do in a much more sustainable way, or we let corpos redefine sustainable.

Is this a good use case? No. But most use cases, I’d rather have a local agent running on my own hardware being offset by solar, than using a corpo offering.

To be fair, there are local agentic models.

Sanitation has stated multiple times on at least one account that they are using a firefox extension to crosspost a queue of things from reddit with touch of a button.

Pushes them very firmly into the “repost spam bot” territory.

Have you actually confirmed that is the case? My understanding is that cloudflare pretty much always re-signs with their own SSL cert. and I’m fairly certain that would be absolutely required when using their DNS proxies.

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

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.