I'd rather not see AI being used to generate new games for any platform. I'm not gonna read something nobody bothered to write, and I'm not gonna play something nobody bothered to write. AI has no taste and it's not a matter of post training because the Taste is the human component and actual effort put into something.
I'm less interested in the factors that obscured it's detection and more in a logical root cause. Very grateful for the medical advancements that slowed the spread of the pandemic though. As the Technology becomes more advanced so will hopefully the Risk Assesments and eventually explain Risks and Limitations of mRNA Technology.
Leaving aside any and all COVID and vaccine issues, the expected "random sudden death rate" is given early on:
For clinical trials enrolling tens of thousands of participants, a baseline incidence of SUD is expected based on population epidemiology. In a trial of approximately 44,000 adults with diverse age and comorbidity profiles followed for six months, one would anticipate approximately 40-50 sudden cardiac deaths as background incidence alone
Later, it turns out the 44,000 example happens to be more or less the size of the Pfizer trial that saw 38 deaths (and a lesser number of SUDs as some of the 38 had cause I assume).
That's from a skim read, it would take a careful and close reading of much of the source material to get an independent feel of whether there was any additional increased (or decreased) SUD risk during the trial.
Bearing in mind that the COVID era saw some drastic changes to "the normal way of life" - less travel and exposure to others for some, varying amounts of more and less stress in life, etc.
There is. Simply do not install sudo and do not allow access to root at runtime. I am serious. There is absolutely nothing you cannot run unprivileged these days. Can even run sshd from a systemd user unit in your home folder, and even assign port 22 to it if needed with Linux Capabilities.
On a modern Linux system you do not need sudo to compile software, install it, or even run it as an unprivileged system service in a User Namespace bound to port 22 (if you give your user the correct Linux Capabilities).
The only thing you cannot do as an unprivileged user is update kernels, but that requires a reboot anyway and the risk of letting an unprivileged user do that is mitigated with hardware enforced secure boot.
Most distros are holding onto 90s designs that are very hard to change once established.
Did you actually try or are you provocatively speculating?
I do have non sudoers groups devices and I also have shared devices with non sudoers users. It works. It's not necessarily for everyone, e.g. not for powerusers who want to go fast very often, but it's definitely usable for most users still.
Linux root/regular-user model comes from an ancient time with multi-user architecture where you defended against one user taking over a big machine they didn't own.
But today on personal computers all the good stuff is inside regular users accounts, and there is nothing valuable to be gained by becoming root.
So the whole security model is broken, it protects the OS system files that nobody cares about, while allowing any piece of software complete access to valuable user files.
Well you of course want to sub-divide every application in user space either with gvisor or a hypervisor, like QubesOS.
If someone pwns your personal browser they should pop out into an environment where nothing exists but that browser, with no idea the work browser is in a sibling vm.
You do need some root process to be able to write the updated kernel image to a root owned directory. On macos that is presumably their update daemon, while on something like ParticleOS[0] IIRC it is the systemd-sysupdated daemon, though I don't know if you can initiate the update as an unprivileged user or if its done on a timer or only root initiated (sysupdate has had a lot of changes not too long ago that reworked it extensively. It use to be something only root invoked transiently with a possible timer to "update all", but now it has a full on daemon).
Basically the reason we "need sudo access" (or anything to elevate privs to root) is because how the system is architected and changing that is mostly only possible on new distros which can decide to change the architecture.
on Windows the UAC (GUI sudo equivalent) requires actual user input (keyboard, mouse) on a dialog presented in a secure way (can't be faked by malware)
UAC is only a sudo equivalent when running under a non-admin user account, at which point it's nearly as convenient to simply run admin commands from a command prompt running as a separate user, or a separate desktop session entirely.
Hypothetical but serious question on your stance: if someone takes "your" code, claims authorship, sells access, and becomes a billionaire from it while you get accused of plagiarizing "their" code and can't get a job coding, are you still cool with it?
Being accused of plagiarism seems orthogonal. Even if I assert IP ownership of my code, someone else can falsely claim it as theirs. They are wrong in both cases and in both cases it'd have to be settled in court.
If nobody owns the code and everyone has the same rights to it (per the parent) the person copying the code would have the same right to claim they wrote it. And there are definitely people who will do this when there is money and reputation to be gained. It happens all the time even with the IP protections we have.
My point is that the blast radius of losing those protections goes beyond open source.
Why should I care that someone else became a billionaire other than that amassing that amount of wealth in a world rife with poverty is already immoral?
Music in the Field of Music should always come first. Sorry for the bluntness but I listen to the demo for 10 seconds and it sounds... shit. Really shit. Then I look at who made it and it looks like someone shoving a data structure into a field they know little about for the sake of the data structure itself?
Fine. Wishing I burned in a Fire isn't technically a Death Threat. Congratulations.
I have no incentive to be nice either, but I am because I want to. And If you are nice while constructively formulating your anger you don't get banned. easy.
sounds like you are just being an asshole because you hate the general consensus on this site, and can't be bothered to be polite in favor of creating new accounts all the time. That makes you the asshole from my perspective.
I come here with the expectation that this isn't 4chan and I leave my opinions exactly as they are while still being polite. This isn't inevitable. Else nobody would use this site. You can be upset about many things like AI and people will share that sentiment or not. You can read the Guidelines, it's not hard to see they aren't unreasonable. And it's easy to see if you violate them.
reply