CC BY-SA 4.0 is one way compatible with GPLv3.
It does mean that anything released under older CC SA licenses aren’t, so they can’t be used in GPL projects. And MIT isn’t compatible at all.
CC BY-SA 4.0 is one way compatible with GPLv3.
It does mean that anything released under older CC SA licenses aren’t, so they can’t be used in GPL projects. And MIT isn’t compatible at all.
Emulation and emulators aren’t illegal. Yuzu for example got in trouble mostly for distributing tools for circumventing copy protection and dumping roms and not for the emulator itself.
But it doesn’t really matter as nobody has money to defend themselves against something like Nintendo. Here just even the threat of it was enough to get the Ryujinx devs to fold just in case.
If you set your pages and repositories to be viewed publicly, you grant each User of GitHub a nonexclusive, worldwide license to use, display, and perform Your Content through the GitHub Service and to reproduce Your Content solely on GitHub as permitted through GitHub’s functionality (for example, through forking). You may grant further rights if you adopt a license. If you are uploading Content you did not create or own, you are responsible for ensuring that the Content you upload is licensed under terms that grant these permissions to other GitHub Users. -https://docs.github.com/en/site-policy/github-terms/github-terms-of-service#5-license-grant-to-other-users
License can’t really revoke that.
Bigger problem is the No Derivatives clause of the CC licence, as compiling or forking the code creates a derivative, so it’s now a project nobody is allowed to use (or distribute) in any other form than their exact, precompiled releases.
In fact, as the GitHub terms of service specifically require you to allow forking - as recently demonstrated by the WinAmp project - I wonder if CC ND is even possible to be used in GitHub in the first place.
When you are a paramilitary organization, the line between what is military equipment and what isn’t gets quite blurry. Especially when they weren’t really “boobytrapped”, they were turned into remote explosives.m, they did nothing until explicitly triggered.
Thought sabotaging enemy equipment to explode isn’t.
Had this been a bunch of Russian or Wagner Group radio equipment exploding because they had been rigged by Ukraine, it wouldn’t be a war crime - combatants don’t stop being valid targets even if they are on leave and are at fault of endangering the civil population, possibly themselves causing a war crime by effectively using civilians as human shields.in the process.
The entire network is nuked in those situations, there are no accessible forks left.
Tesla CEO Elon Musk said his estranged transgender daughter was “killed” by the “woke mind virus” after he was tricked into agreeing to gender-affirming care procedures.
“I lost my son, essentially. They call it ‘deadnaming’ for a reason. The reason they call it ‘deadnaming’ is because your son is dead.” https://eu.usatoday.com/story/tech/2024/07/22/elon-musk-jordan-peterson-interview/74506785007/
It is still in early access and optimising the game is their current goal according to the road map, though as the whole concept of the game is about simulating every NPC properly at all times it’s always going to be really heavy game to run.
And you are right about accessibility making resource hungry games more common - they allow indies to make projects and use concepts that would have been scrapped as technically non-viable by a publisher before. Shadows of Doubt started development back in 2015, which would have meant reducing the scope of the game until it ran on a PS4. Being indie, they could just do whatever instead, and now it’s going to be enough if they can make it run acceptably on a PS5.
Nokia hasn’t actually made a mobile phone since 2014 after they sold their phone division to Microsoft, they just licence the name because it still sells.
Sure. But the IPv6 implementation is a bit like if we went “you know the y2038 problem of 32 bit numbers, and how goin under 1970 is sometimes hard? Lets solve it by making it start from the big bang and store time as a 256 bit integer so we don’t run out until year 3.1 x 10^69”.
IPv6 is big enough for 340,282,366,920,938,463,463,374,607,431,768,211,456 unique addresses. Are we expecting to create an universe consuming army of exponentially replicating paper clip converting robots that each need an IPv6 address or something?
IPv6 is big enough to give 10 billion unique addresses for every grain of sand on earth and still have some left over. Just in case we need to, I guess.
For ghost of tsushima, all of them, as it has fsr3 and dlss 3 support.
They went just a teeny tiny little bit overboard with the address space. Ipv4 is four groups between 0 and 255, ipv6 is eight groups of four digit hex, 0000 to ffff - e.g the Google DNS ipv4 address is 8.8.8.8. the ipv6 one is 2001:4860:4860:0:0:0:0:8888 (thankfully at least some devices allow using :: to skip all the zeroes, so it’s “just” 2001:4860:4860::8888)
But we now have enough ipv6 addresses to give more than 10 billion ipv6 addresses to every single grain of sand on earth, and still have some left over.
Live Paper is not E-Ink, so it shouldn’t have the same inherent issues with ghosting or refreshing.
E-ink is a very specific display technology with ink particles floating in oil controlled by magnetic fields. They don’t explicitly state what this Live Paper exactly is, but they do state it’s something that solves the downsides of typical reflective LCDs, so, probably one of those but better.
Actual e-inks have the benefit of looking like ink blobs on paper and not square pixels, and the image staying even when power is completely removed, and the massive downside that because they are being physically moved, it actually takes a bit of time so they have terrible refresh rates.
Assuming 1 second per swap, a 64 disk tower of hanoi would take 585 billion years to solve - it has 2^64 -1 swaps.
Because the internet has made it both easier to do, and to enforce.
But it’s not a new thing at all, patents and copyrights have been enforced from pirates for well over a hundred years. This is from 1906
They should. But you can’t exactly be surprised if you get in trouble because you broke the law, no matter how stupid you think that law is.
I think it’s stupid that you can’t always turn right on a red light. Plenty of people would agree. I’ll get a ticket if I do it anyway, and it’ll be my own fault.
It means a GPLv3 project can use something licensed as CC BY-SA 4.0 by converting it to GPLv3, as is required. E.g using a CC BY-SA photograph as a background or a splash image in a program.
And while you technically can’t take the original, yeah, practically everything except “here is the image file alone in a folder” counts as modifying and a derivative work. Resize it, crop it, change a .png to a .jpg etc - all modify the original work.