Stay cute.
>>41340873I agree. The issues with the claims made yesterday were that they were founded on speculation and stated with such vehement confidence despite none of their proposed information being verified outside of anonymous posts here.
People playing the game are experiencing issues - check.
The game does have unique interactions with the switch that makes it more likely to crash and set the shitty exfat driver on fuckup mode - check.
Orange screen is indicative of a hardware error, has occured to Switches prior to SwSh's debut - check.
SwSh doesn't have the permissions necessary to modify NAND - check, but you could make an argument that SciresM simply didn't realize something important due to him missing that shiny lock code doesn't cover static Pokemon.
These have been confirmed. Then all of the sudden two random tweets pop up claiming blue screen. Curious, but this is the point where a logical person should wait for a larger sample size and wait for confirmed specialists in this subject to speak up. That's where it should end. Instead, it spun into this whole story about SwSh utilizing NAND for VM, which ANYONE who understands the implications of that claim would know it's be absolutely ridiculous for Nintendo to approve that. It would legitimately give a potential backdoor for exploiting newer models of the switch on top of just being flat out dangerous to the hardware. Said claim had no citation, and was very aggressively pushed as a narrative to string together the (two) instances of blue screens with the SwSh crash issue.
