Even with this they fall back on the god forsaken Digital Millenium Copyright Act (at least in the states). Since they encrypt the system, if you have a key from your own system then it’s assumed that you acquired it by violating the DMCA.
Seriously. They will get to it eventually, they probably just got distracted with suing the Tump administration for their tariff refunds.
The Switch is ARM (nvidia tegra x1) while the Deck is x86 (amd zen2?). There’s translation involved. Not saying that will guarantee a slowdown, but as @FireWire400 said, if the emulator is shit power won’t help much. My oc’ed ryzen 5600x could barely run switch BOTW at 15fps when it first released (though that was arguably still better than the experience I had on my Wii U… shudder)
PMed
edit: hint - try ‘firmware’ instead of BIOS in a search
It’s hard to explain without dumping some massive spoilers. Lets just say it didn’t give them the endings they deserved.
Oh my bad I thought we were talking about the entire Ars team, not the individual author.
“malpractice” would have been not puling the story/issuing a retraction.
Journalistic integrity? On my internet? Well I never.
Gonna turn an old vacuum tube into an extruder nozzle to keep that nice, warm analog sound.
Can’t wait til 3d printers get good enough to make records so i can stock up on audiophile filament!
I would also put a good bit of the blame on executives and marketing people being way out of touch with the average person.
to get something as flexible as my android tv i’d need an nvidia shield and those are going on ten years old at this point. maybe if/when they do a hardware refresh, assuming sideloading isn’t completely impossible by then.
Yeah. To be honest on the DNS side it would probably be far easier to just do a whitelist instead, block everything except your specific service. and yeah, its a stupid amount of work. i hate smart tvs but i’ll be damned if im gonna pay extra for a streaming box =|
just saying its possible
Not sure if you mean hardcoded DNS IPs or hardcoded “phone home” IPs. Hardcoded DNS addresses in devices are annoying, the only way i’ve found to get around that is using destination nat rules (DNAT) which requires more than a consumer router typically. hardcoded phone home IPs would get blocked by your firewall. you’re right that most firewalls are set up by default to implicitly allow outbound traffic. you set up a rule that explicitly denies all outbound traffic from the TV, then only allow port 443 (or whatever port your streaming service uses) on the specific IP/IPs that your service uses. Here’s Netflix’s published IP info for example.
edit also i’m fully aware it’s fucking ridiculous that we as consumers have to go through this much rigamarole. you shouldnt have to be a literal network engineer to do something as simple as have an internet-connected tv that doesnt spy on you.
no it helps to block everything that isnt just netflix or whatever streaming service you use. you combine a DNS adblock along with blocking all the unused ports and it severely limits the communications. you could also add a vpn to add another layer of security. idk about jellyfin but most streaming services i know use https/443 to stream to your tv. so youre only allowing the specific service you want and only on a specific port. buncha great dns blocklists here https://github.com/hagezi/dns-blocklists, and a smart tv specific one for pihole here https://github.com/Perflyst/PiHoleBlocklist/blob/master/SmartTV.txt
It’s relatively easy to restrict a smart tv to TLS/HTTPS traffic only using your router and a dns adblocker.
Right? They should be making them watch the entire Lord of the Rings extended trilogy instead.
hah, computers have had the same drive rail layout for so long that i didn’t even notice! ._.
not unless you figured out how to adblock on youtube tv. this isn’t for desktop clients.