I haven’t used TypeScript in a classically OOP way and it never felt like I was being urged to do so either.
I haven’t used TypeScript in a classically OOP way and it never felt like I was being urged to do so either.
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?
I would fucking hope not. TERM is explicitly passed along as the only exception, which is the only sensible default for temporary privilege elevation in a shell.
It’s a phoronix article, there’s never more than two paragraphs and a quote in there anyway.
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.
Almost nothing uses ethernet over HDMI to my knowledge.
People who spread fud about x11
Who does that? X11 is ancient. It’s a known variable in every possible way. How would you spread FUD about it?
In reality the ones who advocate for Wayland the most are the people who used to thanklessly maintain X…
It already has improved. You’re just very ignorant in your idealism. I’ve used it at home and for work for at least 6 years now and the problems have honestly been way less than expected for an X replacement. Screensharing was probably the biggest hurdle initially, but even that has worked for quite some time now. The last remaining issues are pretty much down to individual applications.
You could not write an operating system even remotely comparable to Linux in that time with the ressources the Wayland devs had available.
I used a zyxel mini wifi router once. It would soft-brick when changing the subnet range. There was another cool feature that would effectively prevent a new admin password from taking effect until you entered a second one (basically creating a queue of passwords). That was fun to figure out.
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.
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.