KubeRoot

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.

Sounds like something out of a dream, could she never have said it?

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.

I think the trick might be that nothing is stopping you from using more than one 32-bit integer to represent addresses and the kernel maps memory for processes in the first place, so as long as each process individually can work within the 32-bit address space, it’s possible for the kernel to allocate that extra memory to processes.

I do suppose on some level the architecture, as in the CPU and/or motherboard need to support retrieving memory using more than 32 bits of address space, which would also be what somebody else replied, and seems to be available since 1999 on both AMD and Intel.

I don’t think it’d be more work for them, since they presumably have to go back to the facility anyway.

Not necessarily, if they have “magic tech”, they could be uploading a virus that rapidly spreads across the entire internet, making every machine broadcast its data through electromagnetic waves or something like that, picking up all those transmitions with said magic tech.

It would still take longer just to read the data off off all the storage, but theoretically not DSL

We’re all the yellow guy sometimes

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.

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.

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.

Linux users are, as a group, less likely to share accurate telemetry and to masquerade as other OSes

I’m going to assume you meant “more likely” on masquerading, but I do want to point out, Linux users also tend to be more proud of their choice and to want to contribute to the statistics, want to be represented. Maybe those numbers effectively cancel out, but I doubt they significantly lean towards underrepresentation for the reason you mentioned.

I can tell you that that’s also what I got. The way confessions work, the priest gives you… “penance” is what it might be called? What you need to do to repent for your sins and be absolved of them. Usually that’s some prayer, but they can tell you that you have to turn yourself in and admit to your crimes to the police.

I have no idea if priests actually do that, and I imagine with the secrecy it’d be hard to get any information.

I got the impression that the PolyMC situation was quite different, with that developer masking it and doing a minority of the work, but after one change made by the rest of the developers they snapped, used their control over the repository to remove the rest of the maintainers and take sole control over the repository.

I was aware of some shenanigans and hostility from PolyMC and never used it, but I got the impression there were no major outward signs before that happened?

Do you have confirmation if you put in your card number? If yes, that’s good, but I also don’t think that’s a EU-wide thing.

My phone keyboard can’t comprehend what I’m about to write, looks like I’m on my own…

Aren’t rizz and gyatt separate though? Isn’t it that you want to have one of them, either rizzin or using that bussin’ gyatt, as you put it? Or is it that “skibidi rizz” is the gyatt, because skibidi=toilet? Am I reading into it too much?

Somewhat stale pizza can also be quickly improved by throwing a slice into an air fryer for a couple minutes, even crisping up the crust a bit

Probably people eating crappy or stale pizza, a good fresh pizza has delicious crust, but let it sit and it turns tough, dry and chewy

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.