

That isn’t really saying that much. It could still be a creation engine that has a UE5 renderer on top. Like the Oblivion remaster.


That isn’t really saying that much. It could still be a creation engine that has a UE5 renderer on top. Like the Oblivion remaster.


But windoze 10 or 11 are different operating systems then windows 7 or 8.


Security through layers. The flaws found here are about compromised server, so hosting your own server is a good first step. Next step is making the server only accessible via your own VPN. And of course hardening the server.


This is what all the listed password manager claim.
What was done here was tricking the client through the server to do things. So the fixes went into the client application.
TBF, people have been programming with XML and JSON, YAML and so forth for a while. From XSLT to Ansible.
Well, it isn’t open hardware. It’s license isn’t OSH compliant.
No? This isn’t a open source printer, its license isn’t at least OSI compliant and also not FSF compatible.
And the everything else. Since it isn’t under a open source license.


Pleading guilty would have at least demonstrated some remorse.
I’d rather forgive someone that said “Sorry, I did something bad, and learn from it” then someone that just first say “I didn’t do it.” and then when informed that they aren’t going to be punished say “Whatever.” and walk away.
So, she not pleading guilty and still not getting punished, while at fault is more rediculus to me.


But she didn’t plead guilty, according to the article. She pleded ‘no-contest’ so she didn’t admit guilt, just stopped defending herself after she heard that she isn’t going to be punished anyway.
She just walked away after the judge said she can do that without consequences.
TBH, paying for every RGB combination would have been a bit funnier, as the ridiculous next step of paying for retextures.
Letting people pay for every change is just too lazy and uninspired…
In case of illegal numbers, intention matters. Because any number could be converted to different numbers, for instance through ‘xor encryption’ different ‘encoding’ or other mathematical operations, which would equally be illegal if used with the intention to copy copyright protected material.
This was the case previously. You cannot simply reencode a video, a big number on your disk, with a different codec into another number in order to circumvent copyright.
However, if big business now argues that copyright protected work encoded in neuronal network models is not violating copyright and generated work has no protection, then this previous rule isn’t true anymore. And we can strip copyright from everything using that ‘hack’.
I had a similar thought. If LLMs and image models do not violate copyright, they could be used to copyright-wash everything.
Just train a model on source code of the company you work for or the copyright protected material you have access to, release that model publicly and then let a friend use it to reproduce the secret, copyright protected work.
But isn’t that the wrong approach?
If you want to choose something better, shouldn’t be ‘enshittificationability’ be the main point you want to address? That is the reason discord is doing most of the bad stuff. Proprietary software is about enshittification.


If there are NPCs, there is AI.
You should be more specific. Ask about machine generated content or neuronal networks, etc.


The point I am making is about protecting teens from adults. So teen-per-default means that adults can freely talk to teens, which should be prevented. Either allow no teens on your platform, or teens have to proof that they are teens first.
Adults (and teens for that matter) are pretty good at obfuscating grooming.


So an adult could just create two accounts, one to access teen spaces, where they don’t verify their age l and one for accessing adult spaces, where the age gets verified?


Teamspeak isn’t open source… Use Mumble, MediaMTX or Matrix instead.
That would actually be the wrong thing to want. In an ideal system trust would always begin by the owner of the hardware, where possible, not the software or vendor they decide to trust.
First the person that bought the system should take the ownership by overwriting the previous owners keys, and from there start signing the vendors key, they decide to put their trust in. Because it is important that the system is trustworthy to the end user/owner first.
Any anti-cheat mechanism relies on not trusting the person that owns the hardware, and why would that be good?