>>41335680>>41335725>>41336282Hey lads, I'm the one who wrote the explanation that's been screencapped in the OP (not the TLDRs, whoever copy-pasted my post into their discord or w/e added those)
Was not and am not baiting, bear with me as I attempt to explain.
When I made that post it was in the context of the thread OP saying
>USING NAND AS VMand an anon asking what that was supposed to mean
I figured I was just behind the times and assumed the OP was correct given all the talk about corrupted SD cards, messed up Rokus, and bricked switches, and so I explained what that would mean and why it's a dumb thing to do.
I'm posting as an anon, but in another post in the same thread I do in fact call into question the plausibility of the switch's eMMC module (what everyone calls the NAND, which is just the kind of flash memory eMMC modules use) even allowing itself to be written to in such a manner. Impossible? No, but I'd call it very unlikely without knowing more about how the game interacts with the system's memory.
I should've gone out and verified before making the second paragraph as definitive as I did, or added some sort of sidenote that I was trusting what the OP said, so I apologize for the misleading nature of my post, especially if it's taken out of context. Had I known it was going to receive the attention it has, I would have been more thorough.
Anyway, just want to make it clear that I wasn't trying to say that is absolutely what it happening, only that I was under the presumption that the OP of that thread was correct with the second half of my post.
Also, a correction that I'm surprised I haven't been called out on: I said NAND has a limited number of read/write operations, but that's not really true. NAND-based flash storage has a limited number of "program/erase cycles", which are for most intents and purposes write operations (you must erase before writing). Read operations don't really affect the lifespan of NAND-based storage.
