meteokr

That jumped out to me too. Seems incredible that the reason the system exists at all, has become a "weird" way to use it. You can git clone the kernel just like any other repo on github, so no big deal.

Just citing a source in case anyone wants a little history: su.

I've gone swimming in specifically man eating shark infested waters for years and nothing bad has happened. So surely nothing bad will ever happen, and my actions have no risk tied to them. Think about why so many people have discouraged the actions you propose, safety rules are written in blood after all. You can, in fact do whatever you want, just keep it in mind when you are doing something risky.

aren't a lot of games aarch64 only? do they even support x86? I've attempted in the past to use waydroid for a game, but no way to install it on an x86 machine. Does waydroid support some kind of box64 layer?

I am very patient, so I'm in no rush for this community. Time only gives us more content,

I don't think that can exist within the current understanding of LLMs. They are probabilistic, so nothing is 0% or 100%, and slight changes to input dramatically change the output.

Would the red team use a prompt to instruct the second LLM to comply? I believe the HordeAI system uses this type of mitigation to avoid generating images that are harmful, by flagging them with a first pass LLM. Layers of LLMs would only delay an attack vector like this, if there's no human verification of flagged content.

To me, there is no greater high than seeing big negative numbers on a commit. Deleting stuff is the most satisfying experience in programming. A commit with +10, -142 is mint.

The best solution to that situation is just a more vigorous application of XGH.

You missed the point of my example entirely. How can those commits exist, and those people exist in that instance if they don't have accounts? I was refuting your statement that a frontend needs an account. By mirroring an existing repo, as an example, you could verify that my claim is correct. Git as platform is already decentralized and doesn't require accounts. You could email someone your git diff's and it will function the same.

You need a frontend

Yes, but the requirement of said frontend are very small.

and a frontend needs an account.

Not required at all actually. For example, mirror a github repo in gitea. You'll see all the commits, their messages, and who made them. Yet that gitea instance isn't accessible publicly. None of those people have an account, and none of them can login even if they could access the instance. A commit is just attached to a name, that is user configurable, and a lot less data minable than a "real" account.

If you don't mind me asking, then how do you know the kernel they use is bloated compared to any other kernel? A vast majority of the device-list stuff is loaded only when that device is detected with kernel modules. You aren't actually running everything from the entire kernel, it just has support for the devices if it does detect them. which is basically the functionality you are asking for, ad-hoc device modules.

Monolithic kernels aren't "bad". That's subjective. Monolithic kernels have measurable and significant performance benefits, over micro kernels. You also gain a massive complexity reduction. Micro kernels, historically, have not been very successful, e.g. Hurd, because that complexity management is extremely difficult. Not impossible, but so far kernel development has favored monolithic kernels not without reason.

If what you say is actually that easy, why wouldn't all distro's just do that during the install, and during updates with their package managers? I believe you could do this in Gentoo, but I don't know if it has measurable benefits beyond what performance tuning for your specific CPU arch would give you. Since none of those devices you aren't running are consuming any resources beyond the storage space of the kernel.