It’s always been a “whole ass computer”, not some kind of simple storage device.

Pretty sure that the registry path for official images is “library” (at least it used to be). So it should be “docker.io/library/debian”, though I can’t double check at the moment.

You mean hiding their public IP? I guess that’s a feature.

That’s what a firewall and a DNS service is for respectively, imho. As long as you get an IPv6 prefix from your ISP, you can expose as many devices or services to the public as you want, by just allowing incoming traffic to a listening port. That was sort of the whole point of having a large enough address space when moving away from v4. Maybe it’s just me but reading stuff about “private AI” on a website where the relation to the product is not immediately obvious, makes me question their legitimacy.

The more I look at their site, the more it reads like a sales pitch for IPv6, which sounds kind of expensive at $6-10 a month.

What problem does this solve? Do ISPs not provide IPv6 prefixes anymore?

That script is a wrapper around a single call to qrencode. I’ve been making qr codes from wireguard config files in the terminal at least since PiVPN existed. There are plenty of guides on how to do this as well.

I get what you’re saying, but this feels like a weird question to ask in a community for selfhosting enthusiasts.

https://en.m.wikipedia.org/wiki/Showreel

I’ve heard of it before and I don’t work in advertising or video production. Why is everyone focusing on this term like these guys invented it?

No idea. Do you unplug your TV from the mains when it’s not in use?

It’s possible to auto-renew dev mode via SSH with a shell script running on an interval on another device in the network. I would give more detailed advice, but unfortunately it seems LG has changed that part of their API a while ago. The webOS manager linked above used to be able to generate a script for this purpose. I’m not sure if it still works, but it’s worth checking out.

Install the AdFree YouTube homebrew app for WebOS using developer mode.

Doubt.

Cool attitude. In my experience, most docker/docker-compose setups will work transparently with podman/podman-compose. If you want to tighten security, lock down ressource access, run rootless (daemon and inside the container), integrate with SELinux, then you might need to put in extra-work, just like you would if you used docker.

Why re-invent the wheel?

They aren’t. Podman is mostly just a docker-compatible CLI wrapper around an existing OCI runtime (runc by default). It also lets you manage pods and export k8s yaml, which is arguably the more important industry standard at this point. Podman was also completely usable in rootless mode way before Docker support for that was on the table, which was the main reason I switched years ago. Podman development effort also yielded buildah, which is a godsend if you want to build container images in a containerized environment, without granting docker socket access (which is a security nightmare) or using some docker in docker scenario (which is just a nightmare in general).

YAML is way too bloated of a standard and has a ton of inconsistencies between implementations, despite the widespread reputation of simplicity. It is easy to read as long as you limit yourself to a fraction of its capabilities and err on the side of caution when it comes to escaping characters (especially when number literals are involved, or booleans for that matter). As far as alternatives go, I prefer TOML for simple key=value configs, but it has its own issued and is nowhere near as featureful, for better or worse.

I don’t have a horse in this race, but this is a really unhelpful non-answer.

You can set up an intrusion detection/prevention system, that logs/blocks certain traffic. If you do have public services running, you could block access based on location, lists of known bad actors etc. I guess you could argue that this is beyond the scope of a traditional firewall.

The certbot authors tried really hard at one point to make snap the only available distribution mechanism for their application and for some time the version that Fedora packaged would display some weird deprecation warning and urge you to use the snap version.