The (wildcard) certs are the same, as it’s what caddy is pulling via API. You can either build the cloudflare module into caddy via docker build, or use a prebuilt version. It doesn’t create two separate certs for local and remote.

It works really well for me, and is actually the most straight forward way to get valid certs for internal services I’ve found. Since they’re wildcard, my internal domains don’t get exposed through certificate authorities.

Efficiency still matters very much when self hosting. You need to consider power usage (do you have enough amps in your service to power a single GPU? probably. what about 10? probably not) and heat (it’s going to make you need to run more A/C in the summer, do you have enough in your service to power an A/C and your massive amount of GPUs? not likely).

Homes are not designed for huge amounts of hardware. I think a lot of self hosters (including my past self) can forget that in their excitement of their hobby. Personally, I’m just fine not running huge models at home. I can get by with models that can run on a single GPU, and even if I had more GPUs in my server, I don’t think the results (which would still contain many hallucinations) would be worth the power cost, strain on my A/C, and possible electrical overload.

You can use caddy to get internal https via cloudflare API, and no traffic needs to go through a cloudflare tunnel for that.

Awesome! Keep signing though, some signatures will fail to validate so there should be as many as possible.

They also aren’t ashamed or scared to show their faces.

So much for keeping the US out of war…

I can’t speak to beef, but there is more to Android security than what Google provides. That’s what Graphene is for, to make Android even more secure through hardening various attack surfaces and introducing other completely new security features. If that weren’t the case, Graphene wouldn’t be necessary on Pixels because Google does monthly security patching for them.

It’s also at the firmware level, which Google does not provide except for on their own hardware, and on top of that Google phones are some of the only ones capable of providing some security feature at the hardware level. This seems to be the main thing the Graphene team is trying to point out.

Graphene is centered around security. I’ve heard bad things about Fairphone in that regard - the Graphene team even talks about them in the replies on that thread.

Sure, I was trying to correct the statement that it’s not possible at all though.

You can still torrent with Mullvad, it’s just gonna be slower because you have less peers. But it’s still 100% doable. They don’t block torrenting entirely…

This article isn’t about that, so clearly you did not read the article.

Sounds like a system crash of some sort. I’ve had similar things happen with really bad crashes. Android recovers with a reboot in these cases.

I think that was pretty obvious, no?

Oh my god, not you again. Give the slop a rest. Your last (now-deleted) post said you had “no marketing”, but here you are again.

It’s a structured low tech kit solution that uses Legos and hammers to hit them when the data tells it to with no guidance or tutorials which makes you money when you (a solo builder) are going broke.

What’s so hard to understand about that?

It’s clear that we don’t get guidance - you don’t even seem to know what your “platform” does.

“no marketing”, meanwhile you’ve created an account with your platform’s name? what would you call what you’re doing right now then? “Sharing” doesn’t count unless it’s open source and free, btw. So, it’s not that.

Try again, not using the word “kits”. Why would a “solo builder” need this (which you haven’t been able to coherently explain yet) when they could use real software to do so?

It’s my favorite feature of Kagi. I’ve blocked so many AI sites.

KPUD in Kitsap County, WA does something similar: https://www.kpud.org/fiber-internet/free-public-wi-fi/

They also have very affordable public fiber.