KubeRoot

I think they decided not to, with some (IMO fairly) snarky comment on how that was just a proposal and people were getting needlesely outraged.

Calling somebody a racist or sexist hurts their feelings, should that be allowed?

Calling somebody out publicly can hurt their livelihood and thus ability to get things like medical care, should that be allowed?

All information on the manufacturer’s servers has been destroyed, including 10 terabytes of backup materials.

The numbers might not add up, but it’s possible the hackers had access to the (insufficient, and badly secured) backups to delete them too.

I would assume they sent them after the number was drawn, to before the number was drawn, which means the future self doesn’t need their own message to learn the numbers.

They sure do, unless you missed a parenthesis and somebody wants to point that out ;)

It’s not being made “as painful as possible”, it’s just manual. Arch isn’t a distro that’ll preconfigure things for you so everything’s plug’n’play, it’s a distro that’ll give you access to everything and the power to use it however you like, but with that comes the expectation and responsibility to manage those things.

Installing arch manually is simply a good lesson in how your system is set up, what parts it’s made up of, in part because you’re free to remove and switch out those parts.

And sure, there’s no magic bullet to make sure a new user understands everything they did, but I think in the end, if you’re not willing to read, learn and troubleshoot, you might just want a different distro.

I don’t think either has ntsync support enabled by default, but it’s supposed to have better accuracy or performance, thanks to putting the needed APIs directly in the kernel, right?

Isn’t installing extensions in it also a pain, since the Google webstore doesn’t let you install from it?

I guess to answer my own question, I looked it up - there’s an extension to let you do that alongside some flag changes, so I guess not too bad… But it’s another step on the list of things you’d want to do as a user

Not when taken to such an extreme so as to obfuscate the meaning and behavior of code, and make it difficult to understand how you would arrive at that code.

Sane defaults serve to reduce verbosity without obfuscating meaning, simpler syntax with different ordering and fewer tokens reduce verbosity to make the code easier to read by reducing the amount of text you have to pay attention to to understand what the result is.

I imagine there’s also a distinction to be made between verbosity and redundancy - sometimes extra text might fail to carry information, or carry information that’s already carried elsewhere. I’m not sure where the line should be drawn, because sometimes duplicate information can be helpful, and spacing out information with technically meaningless text has value for readability, but I feel like it’s there.

This is anecdotal, but a sibling of mine had a friend in school who had allergy(?) issues and couldn’t eat most ketchup brands, but heintz was apparently reliably fine due to the simple recipe, including lack of synthetic dyes. I never did my own digging, but if their goal is having that niche of quality natural products, it might not cost them much (if at all) but help maintain a reputation.

Not the same person and cba to get a timestamp right now, but it’s the 80% rule - the electrical stuff isn’t designed to deliver the rated amperage continuously for hours on end, so for car charging, you’re apparently supposed to limit it to 80%. Now, 80% of 50 isn’t 42 but 40, so not sure if it’s a case of 80% not being a precise number or a mistake here, but it roughly checks out.

Our public TV has no midroll ads, only between programs, and I’m so happy I can use a guide and usually find something to watch when eating and get no ads. But I’m also watching the endless reruns of a series I like, so that’s also not difficult to get.

This feels like surreal memes before they turned into almost entirely misspellings and other repeat jokes.

Overproduce to cover everybody’s needs, and if you want to use that overproduction to cover somebody else’s problems, make that the new target and produce over it to keep a safety margin. Otherwise you’re just going to hide the problem and run into trouble when production dips.

Not saying this is the right approach, but this is the idea I’m getting from the thread. I feel like it might not work with the economics of supply and demand combined with capitalistic greed, but if a margin exists as safety, allocating it removes that safety.

I think the point is that if you do that, then you’re just increasing the amount of people in the equation, and if they become dependent on you and the production drops, somebody will be lacking food again.

I had the impression cloud was about the opposite - detaching your server software from physical machines you manage, instead paying a company to provide more abstracted services, with the ideal being high scalability by having images that can be deployed en masse independent of the specifics of where they’re hosted and on what hardware. Pay for “storage”, instead of renting a machine with specific hardware and software, for example.

Yes, apple should allow that, and Sony should allow that. Your “gotcha” seems pretty stupid, because “allow” doesn’t mean “facilitate” - it’s not Apple’s responsibility to make those things work on their devices, but Apple is going out of their way to prevent individuals from making those things happen on their own.

If you license your project under GPL, and somebody submits some code (like through a pull request) that ends up in the library you use, you are now also bound by the GPL license, meaning you also have to publish the source of any derivatives.

The way to avoid it is to use something like a CLA, requiring every contributor to sign an agreement giving you special rights to their code, so you can ignore the GPL license in relation to the code they wrote. This works, but is obviously exploitative, taking rights to contributions while giving out less.

It also means if somebody forks the project, you can’t pull in their changes (if you can’t meet GPL terms, of course), unlike with MIT, where by default everybody can make their own versions, public or private, for any purpose.

Though it’s worth noting, if you license your code under MIT, a fork can still add the GPL license on top, which means if you wanted to pull in their changes you’d be bound to both licenses and thus GPL terms. I believe this is also by design in the GPL license, to give open-source an edge, though that can be a bit of a dick move when done to a good project, since it lets the GPL fork pull in changes from MIT versions without giving back to them.

Thinking about it… Since I’m not planning on switching to windows, and (non-VAC?) bans on steam are game specific, would I even care if I got banned from a game for using it on Linux?

Though I probably also won’t be playing this game, since I have no prior interest, so I’m biased.

Obligatory xkcd.

I don’t know enough to say how accurate the numbers are, but the sentiment stands - if it’s a password you’re memorizing, longer password will probably be better.