sxan

The past three houses I've lived in have had convection ovens; I thought convection mode was fairly common by now.

Or, as the quote I know better know: France is a lovely place; if only it weren't full of the French.

I was at a place outside Paris, not too far, but in the Normandy countryside, in a tour group for French people because that's what was running when we arrived and we didn't want to wait an hour for the English version.

Me, with my three years of college-level French, was reasonably able to translate for my wife and ask simple questions. I held most of our questions until the end when everyone else had wandered off, so as to not bother anyone, and when we got the chance I started in with the more involved questions. This biscuit of a young woman listens to me stutter my question out with an utterly deadpan look on her face, and paused, then answered in English.

I was like, I'm trying here. At least acknowledge I'm trying to respect your culture.

Docker of one version of software that uses Linux containers to encapsulate software and that software's dependencies, while limiting that software's access to the underlying OS. It's chroot, but for more of the system. It can make running software that has a lot of moving parts and dependencies easier. It can also improve your security running that software.

For how-tos, watch one of the 875,936 YouTube tutorials, or read one of the 3 million text tutorials. Or ask ChatGPT, if you really need hand-holding.

Related, but just hanging this on here. As the default (as installed) security of distributions has improved, so have the amount of headaches when trying to use tools like this increased. For decades, when I've had issues like this is not been because of a LAN firewall issue, and so now my first thought is never been, "I should check the firewall," when it should.

Sadly, firewall info is almost always locked down so that apps can't even check by themselves and provide helpful hints to users.

Anyway, it's been a hard lesson for me to learn, for some reason. I need to practice my mantra: it's always the firewall.

Creative Commons is exactly the tool you need for licensing; they even have a "build-your-own" customized license tool. The tool will generate an icon, text, and a link to easily understandable legalese for your license.

CC is like GPL (but more flexible) for art, and it's an awesome service.

Flatpack puts all app data in ~/.var?? Ewww! No thanks.

I've only used my GL.iNet router with Mullvad, and I assume you're going through the manual configuration for WireGuard part of the UI? Have you found the scan qr/upload config/manual input config part? From as far as I've tried it, it's like setting up any WireGuard endpoint - you have to give it the same sort of config file you'd give wg-quick, including subnet, hosts, etc - the same place you'd put your pk.

Generate the config file on a different computer and upload it through the UI.

I'm cheering her on if only because any of her wins has to burn another ulcer in Trump's stomach.

Plus, Biden might be able to beat Trump again; I'm not so sure how he'd do against Haley, especially after she'd pivot post-primary to more moderate center messaging.

I'm still glad she's hanging in there being a distraction for Trump. She's definitely going to lead the party ticket in 2028, though. This is just a pre-game practice for her, and the Democrat party better be paying attention. I mean, assuming Trump fails to turn his presidency into a perpetual dictatorship a-la Putin, which is still on the bingo board.

Your point is a very important one. The numbers have to come up so that manufacturers notice. It might make the difference in a laptop designer choosing a well-Linux-supported wifi chip, instead of a shitty, closed chipset like Broadcom. When the price-per-unit difference is pennies, knowing that you're potentially losing some thousands of customers in exchange for saving a few cents per unit can make the difference in how you choose.

It also matters in user choice in the workplace. The more normalized Linux is, the more likely there will be skills in IT support, more mass-management tools, and more willingness to allow employees to choose their OS.

But where it really matters is in standards. Diversity puts pressure on software developers to use standardized and open data exchange standards. I can't emphasize enough how important diversity in OSes is to driving creation of, and conformance to, standards, and how much of an anathema to standards monocultures are.

Even within OSS this is true: github and git have become monocultures; they aren't standards, they're tools developers are forced to use if they want to interact with the wider development world in any meaningful way. They're not bad; git became dominant largely because github used to be so fantastically better than anything else available at the time; but now, their very dominance stiffles diversity and innovation. Want to try the rather exciting pijul, the patch-based spiritual successor to darcs? Fuck you, because you won't be able to collaborate with anyone, and you repos won't work with any proglang module systems like cargo or Go modules, because it isn't git[1]. Monocultures are bad, whether they're evil corporation software, or FOSS.

Higher Linux use increases diversity, encourages data format standards, and creates a healthier ecosystem. That's why these numbers are important.

[1] Go and Rust's cargo support more VCSes than git, but they could easily not, and I'm sure the maintainer's of the vcs code wish they could drop support for some of the long tails - and everything that isn't git is on the long tail at this point. There are attempts at creating some standards around this; ActivityPub has tossed around ideas, forgefriends has been trying for a breakthrough for years - none of them address the root issue of how tools can access sourcecode efficiently in a way abstracted from the underlying vcs. Any such tool currently must have some bespoke code to speak the network language of the vcs, for every vcs. And since git is the most popular, when faced with the daunting task of supporting N vcses, when N-1 of them are in toto used by a small percent of users, it's just easier to support only git.

I think at 25 in a row it's a silver jubilee.

Sure. My point is that it's trivial to make and test packages for many distributions; it is harder to do so for Nix. It tends to get your software out there and used faster if you bootstrap the packaging - immediately, if you have an AUR account.

IMHO, Nix is unreasonably harder. There are frequently small projects that don't get packaged for most distros. When I encounter these, I have a couple of options:

• Submit a packaging request. Hope someone is willing to accept it. Wait until it is packaged.
• Install it from source and let it pollute the core system. Hope this causes no issues. Manually track and maintain the installation. If lucky, the software lets itself be installed somewhere non-standard, in which case I can use stow and keep things a bit cleaner.
• Throw together a package for it and let my distro manage the installation.

The third option is preferrable to the others, for a variety of reasons, and it's easy on most distros. On Arch, I might submit the package to AUR, but I'll often just make a -git package and install it locally.