You don’t have to make an image though. Just start with a Debian or alpine base image and install the software within

Docker? Meh. If you need it it’s like 5 lines of docker files to write.

Yeah the p2p sync is a paid feature. The master mode sync is not however.

That’s the one

go-suki

Finally a reasonable person around here.

Is this the return of BonziBuddy?

You need to set the fsid fort your export entry in the NFS server since they are all on the same actual mountpoint.

Then SOCKS is what you want. It can be used on a Chromebook as well.

These proxying websites are running full browser instances in the background. It’s the only way to guarantee all the traffic is routed through it.

I just had a look at croxy you’re right, it doesn’t run a full browser… and there’s a TON of data that doesn’t get proxied.

Yeah what you want is a SOCKS5 proxy then just launch another browser with the proxy config.

You can run a browser inside a docker or VM, and then use webvnc or something. I just don’t see the point.

What exactly do you mean by web proxy? Something site specific like Invidious? Or an HTTP or SOCKS5 proxy like danted?

Yeah that do, I remember that the demo was pretty impressive ten fifteen years ago!

And you better inspect and execute a downloaded copy, because a malicious actor can serve a different file for curl/wget than to your browser

Also https://github.com/acon96/home-llm/blob/90c0edc0907e4567eeca89a6f89b43c0b0b807eb/docs/Setup.md

Home Assistant can absolutely do that. If you are ok with simple intent based phrasing it’ll do it out of the box. If you want complex understanding and reasoning you’ll have to run a local LLM, like Llama, on top of it

Absolutely. Simply use ACME with the DNS validation method. Using bind you’ll want to create keys and allow TXT access for those keys to the validation domains. Fear not, this isn’t exclusive to bind, ACME tools supports dozens of other backends. That’s all you need the actual domain doesn’t need to be resolvable with an A/CNAME record. Internally you can run an entirely different DNS server to resolve your hosts, use hosts files, or use bind zones.

Except it isn’t. Saying it is trivial is just gross generalization. It’s trivial to configure bind to have internal zones that aren’t resolvable publically. It all depends on configuration, such as reverse ns entries, zone accessibility, etc.

You can have (sub)domains that are listed in the certificate lists and yet aren’t resolvable externally as well.

It’d be better and more accurate say the list of certificates then.

Sub domains aren’t public unless your DNS server has XFER on.

Worth noting about this approach is that the global list of subdomains is publicly searchable.

Can you expand on this? What is it that you call the “global list of subdomains”?

It’s not rocket surgery

Easy to say for a rocket appliantist.

Anything that supports bind’s built-in nsupdate.