Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)AN
Posts
0
Comments
168
Joined
2 yr. ago

  • Beyond the initial setup, Arch has become quite easy to maintain if you have some Linux erperience, mostly because the community has grown a lot in the past few years. Still wouldn't recommend it to a complete beginner in most cases.

    Now, which fucking tank doesn't require regular maintenance or come with instructions you're expected to remember?

  • Almost none of the alternate modes or advanced features are required for USB-C devices. Most smartphones don't support high data rates over their single USB-C port. There are are probably more USB-C ports using the USB 2.0 specs, for example peripheral devices like mice or keyboards. Beyond stuff like DisplayPort alternate mode, there still isn't a big demand for more than one or two USB-C ports with high data rates or the full feature set.

  • 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.

  • It's because you forgot how communication between humans works. The primary reaction to your post and comments is confusion. In other words: if you obfuscate the content then you can't complain when people don't discuss it.

  • Don't think most plastic straws would melt, but they would probably soften and might infuse more chemicals into your beverage than it would if it were cold. At this point I'd just go for the obvious solution of repurposing an old heat exchanger from an AC unit or something. The strange taste will go away after a few times (probably).

  • 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.

  • 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.