KubeRoot

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

It sounds simple and not at all mental gymnastics - they encountered this issue with a minor thing, started reading up on it online, and when digging into that kind of stuff ended up reading on what the legal situation is with discriminating based on it in general, finding out that companies can discriminate when hiring.

If anything, I’d say half of the post is maybe irrelevant, since you don’t need the backstory of how OP ended up looking into it, but it seems to be a reasonable recounting of events.

Maybe I’m confused, but I feel like you missed the part when they went from the backstory (investigating google family features) to their revelations from looking into it (companies can refuse to hire you based on this information)

They’re fast and efficient, by putting the heating element right up against the water, and also safe thanks to shutting off automatically. Great shit!

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.

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.

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.

Is it? Or did they choose Arch because of the ease of setting it up with all the latest software the community was already packaging?

NFTs try to introduce artificial scarcity

Just want to add to that, NFTs aren’t inherently about artificial scarcity, they could also be used to track ownership of rights or real life items without a central authority that everybody needs to trust.

Of course, cryptobros immediately went to pushing them as an investment scheme, and the actual implementations are slow, inefficient, and downright expensive to use. I don’t think anybody has managed to make NFTs actually useful, but I imagine the original creators weren’t looking to create… Whatever this is.

Doesn’t change the voting situation. Since your votes need to be seen by other instances, Lemmy needs a mechanism for federating votes. Since instances are untrusted, there needs to be some way of preventing manipulation. Thus, AFAIK, Lemmy simply shares your votes across instances, letting each one tally them up. As a side effect, any server admin of an instance you can interact with can also get a list of all your votes.

Having two different configurations of assets requires making a system that can switch between them, separate deployments for them, some way to actually fetch the asset pack by the users, testing to make sure both configurations work correctly, actually deploying the separate asset pack during an update, and then spending time fixing bugs that inevitably come up with any added complexity.

Could they do it? Absolutely. Should they do it? Probably.

Would there be no downside, no tradeoff? Claiming so is plainly ridiculous.

Dual booting is problematic, as mentioned you’re messing with your partitions and could mess up your windows partition, but also windows can, unprompted, mess up your Linux bootloader. As long as you’re careful with partitions and know how to fix your bootloader from a live image, there’s no real issue, but it’s worth keeping in mind.

By the way, I recommend rEFInd for the bootloader when dual booting, it doesn’t require configuration and will detect bootable systems automatically.

A VM sounds like a good idea to try a few things out, but do keep in mind performance can suffer, and you might especially run into issues with things like GPU virtualization. If you want to properly verify if things work and work well enough, you’ll want to test them from a live system.

As a final note, you can give your VM access to your SSD/HDD - if you set that up properly, you can install and boot your Linux install inside a VM, and later switch to booting it natively. You still have the risk of messing up your partitions in that case, but it can be nice so you can look things up on your host system while setting up Linux in a VM.

I think the main pain would be manually aligning the frames on every line with every change, occasionally having to extend the width and updating every line of code to match it

Yes, but the issue is that the lemmy.ml maintainers are the Lemmy developers. The people who created the software, and continue maintaining it, are the same people who created the instance.

It’s the well-known question of if you can, or should, separate the art from the artist. By funding, in its current state, the development of Lemmy, you’re supporting the people running an instance you disagree with. Unless you’re willing to take up the work to fork and continue development yourself, you can’t detach them, you either support both or none.

If you want media where you might actually use past tense, consider lost media (like old episodes of Doctor Who), live streams (especially where the person stopped streaming), long-term ongoing series that keep up to date with current events (vlogs, blogs, maybe reality TV?)

Git exposes a lot of internals through odd commands, so I suspect you could manage synchronization by sending changes over email or something.

Bonus fun fact: there’s a git bundle command that “dumps” the repository into a single file, that can be interacted with as a remote. So if you’re ever working with a local repository and want to put it on a server over ssh or something like that, you can just create a bundle, scp it over, and clone from that on the server.

Fundamentally, the repository you have on GitHub is the same thing as the repository you have on your computer when you clone it. Pulling and pushing are shorthands for synchronizing commits between the two repositories, but you could also synchronize them directly with somebody else who cloned the repository. As somebody mentioned, you can also just host the same repository on two servers, and push to both of them.

The issue is that git doesn’t include convenient features like issues, pull requests, CI, wikis, etc., and by extensions, those aren’t included in your local repository, so if GitHub takes them down, you don’t have a copy.

An extra fun fact is that git can be considered a blockchain. It’s a distributed ledger of immutable commits, each one representing a change in state relative to the previous one. Everybody who clones a repository gets a copy of its entire history and fast forwards through the changes to calculate the current state.