There's a great presentation by Tony Chen on the Xbox One's security features:
> https://www.platformsecuritysummit.com/2019/speaker/chen/
Examples of the kinda software you can put on the Xbox One in developer mode:
Hence why PS3 Other OS no longer did hardware acceleration.
Ya basic was only one front in that war.
I own one such kit.
Each of these schemes had different sets of regulatory checkboxes they were trying to tick, and so had very different end products.
Yaroze and PS2 Linux never had anything to do with tariffs.
https://www.pinsentmasons.com/out-law/news/playstation-2-is-...
It was the last time that a Japanese company made a fundamentally Japanese move.
And Toshiba and IBM, it was a three-way collab. There was even a second-generation Cell (PowerXCell 8i) released in IBM Q Series blade-servers.
What do you mean by this?
https://phys.org/news/2010-12-air-playstation-3s-supercomput...
And in my mind the whole story was a publicity stunt, considering the political wind at the time and the place that broke the story; which was then quoted at me in college.
buuuuut https://en.wikipedia.org/wiki/PlayStation_3_cluster the US government went ahead and did make a supercomputer out of PS3s.
anyhow thanks for helping me confirm my memory is functioning perfectly.
ETA: https://web.archive.org/web/20041120084657/http://arrakis.nc... probably where this "wacky" idea came from...
The PS3 was coincidentally locked down after it was jail broken (broken in Jan, otheros patched out in Mar.
Part of me also thinks that Microsoft were so forward with offering what was basically a test kit because they were confident in their security.
The proof in the pudding of this will be when the Nintendo Switch 2 reaches 2035 with no cracks. That's my prophecy; that this time around the cat actually will catch the mouse. Between NVIDIA's heavily revised glitch-resistant RISC-V security architecture and Nintendo's impeccable microkernel, there's nowhere left to hide. DRM may turn out to have been a very slow long battle to "victory," not a "this will always be defeated."
So even if Switch 2 doesn't make it all the way to 2035 with zero cracks, there's a strong likelihood that any exploits found will be short-lived.
Anyway, situations like the one you describe are one to be solved by legislation requiring certain devices be sold as open devices that put power in the hands of the owner.
My PS3 and PS4 were both jailbroken/rooted. I don't remember the ps3 routine, but the PS4 was loading the "system -> help" page while connected to a ESP32 wifi AP running a simple web server that replied to requests with the jailbreak for PS4.
I give it about a year, especially if nintendo has to change the specs or otherwise tampers with customer expectations. there's bound to be some way to reload firmware on a "dead" device without pulling chips, and that's all it takes.
The two pins were installed by design from Nintendo to activate the Tegra RCM mode. RCM mode meanwhile has a USB buffer overflow which is the real bug.
In modern NVIDIA chips, this RCM mode no longer exists. The new recovery modes meanwhile are running across multiple physically separate CPUs verifying each other (glitch one, the other notices), all running formally verified firmware written in SPARK (the thing you use for nuclear reactors and avionics).
As for the OS itself, according to a maintainer who rewrote the kernel twice for open source, it has zero bugs. None. The microkernel is tiny, has no drivers, and almost no attack surface. This is born out by WebKit exploits being a dime a dozen on Switch, but all of them are useless.
I guess that, when you absolutely want zero surprises, Ada is the language of choice.
This is hyperbole. We have 1 switch that routinely "won't power on" without a ritual of button holding & timing. My original switch used to hard lock, but i stopped trying to play the sorts of games that were causing the OS to crash.
Both of these disprove the zero bugs claim, unless we move the goalposts.
That's like saying "I plugged in my phone's charging cable, and unplugged it, 20,000 times, and now it's sometimes showing the charging symbol inconsistently, obviously a software bug proving the charging circuit driver has a security flaw."
Even if it were possible to find a vulnerability in the hardware, doing so without attracting the attention of law enforcement will be profoundly difficult, as Windows sends telemetry back to Microsoft about every instruction that runs on your hardware. Apple will claim to be more privacy-focused, at least for a year or two, but the M9 chip's NPU will just perform local inference on your activity and report you to Apple and the FBI if it detects attempts to break security.
Maybe we should think about this like the concept of public domain. Locked down for X years in order to protect the artist, then opened up for everyone to benefit society.
A lot of the early hacking focused on trying to breach the hypervisor from otheros. The hypervisor turned out to be quite secure, people smashed their heads against it for years until it finally fell to a memory glitching attack.
But turns out it was so much easier to just attack gameos with a USB exploit. The hypervisor did nothing to prevent it, and would then just decrypt games for you (because gameos was trusted)
We need to catch up on this because the people who know how to use language for propagandizing don't have the best intentions in mind.
But using the original term is not enough. We need to combat their word-twisting by upping them. We need a way to convey "their way of installing stuff by default is inferior and an attack on liberty".
Something like:
- direct install: installing as we always did
- caged install: installing through a locked store.
Maybe somebody better at marketing can find a good way to do this. In fact, we should have a whole site and community to organize together and shift the narrative on all nerdy things: formats, open web, DRM, patents, etc.
We have been weak on these points for so long because we care much more about solving tech problems than selling them. But openness is being eaten away under our noses. Has been for years.
That said, I do think words matter and I always point out that the reason these systems are locked down is because of Digital Restrictions Management. I also refuse to buy anything from Sony because they changed their mind about letting me install linux on the PS3.
I just think side loading is good way to describe installing custom software on a non-general purpose computer, and that not every computer needs to be general purpose. It's significantly better than the previous terms of hacking, cheating, stealing, and voiding your warranty.
When I think of "install" I think of general purpose OSes which can install software from almost any source no questions asked, or use the native out of the box support for software installations.
The similar distinction exists with android and iOS, and is probably why the term is popular in those communities too.
If nothing else, the term sideload makes very clear on platforms with native appstores or locked down distribution channels (consoles, phones...) that the install did not come from the native channels. Installs from game discs or the xbox store are inherently different from developer mode software and using the same term "install" for both disguises this fact.
Instead, they keep stripping stuff off the console. I'm still so annoyed that PS5 doesn't even have an integrated web browser anymore (especially trying to troubleshoot network issues from the console itself).
But hey, Sony can leave bullshit exploit vectors open like PPPoE clients on the console itself (why? just use a router?)...
There's a terrific incentive: Being able to play games without Steam or DRM in a portable format (possibly one file per game). Emulation is beautiful[1] and this time it may come at native speeds considering the Xbox One uses x86 architecture.
I get what this essentially means, but for those of us with a certain amount of love of language (or pedantry), it's fascinating to try and parse this literally because I don't quite think it works as intended.
Clearly the intended meaning is something like eclipsed in quality. And it may be overlapped in the sense that the same games are separately available on PC. But overlap isn't a relation of quality; quality is generally better or worse when it's comparative. So it's like a smushed together way simultaneously saying the selection of games on Xbone overlaps with what's available on PC and is also better quality on PC.
examples:
The 2013 system’s game library is largely overlapped, in better quality, on the PC platform.
The 2013 system’s game library is largely overlapped (in better quality) on the PC platform.
Minecraft: Xbox One Edition (the Legacy version) was of keen interest to our community as it would be playing LCE natively on a PC if you used a compatibility layer which never happened before.
So a few of my LCE cult friends contributed to WinDurango which was pretty much dead before they joined, and got Minecraft: Xbox One Edition to work.
Of course, you'd ask "why don't you just play Minecraft on PC normally?" Legacy Console Edition has so many minute differences and details that it's impossible to discuss all of them--things as big as the Minigames and as small as the mipmaps.
And then LCE source code from 2014 got leaked and that had a native PC port. Oh well.
The parenthetical is not needed. It is OK to call Wine an emulator. The "Wine Is Not an Emulator" thing came about later and was essentially a marketing change. How it came about is interesting.
The first suggestion to change the meaning of the word from a shortening of "windows emulator to the not an emulator backronym was in 1993 over concern that "windows emulator" might run into problems with Microsoft trademarks, but no action was taken.
Over time the not an emulator usage became an accepted alternative. The Wine FAQ in late 1997 for example said:
The word Wine stands for one of two things: WINdows
Emulator, or Wine Is Not an Emulator. Both are right.
Use whichever one you like best.
The release notes stopped calling it an emulator at the end of 1998. The 981108 release notes said: This is release 981108 of Wine, the MS Windows emulator.
The 981211 release notes said: This is release 981211 of Wine, a free implementation of
Windows on Unix.
As far as I have been able to tell from my recollections of that time and what I was able to find when I looked into it later is that this happened for two reasons.1. Wine was useful for more than just running Windows binaries on Unix. It could also be used as a library you could link with code compiled on Unix as an aide to porting Windows programs to Unix.
2. Hardware emulators that emulator old systems like GameBoy or Apple II had become popular. Many people were only familiar with that kind of emulator, and those (the emulators, not the people!) tended to be slow.
That was fine when your emulator is running on a machine with a clock speed 300x that of the machine you are emulating and that has a much more efficient CPU, but when you tried to use a hardware emulator for something comparable to your machine it was usually unbearably slow.
People only familiar with such hardware emulators might see Wine described as a Windows emulator and think it was doing hardware emulation and not even give it a try. By dropping calling it an emulator Wine sidestepped that problem.
Not the same as emulating its titles, but a lot of interest in the Xbone/series line (outside of actual console users) is the dev accounts. So I imagine a lot more effort went there first.
Then I'll finally hook up the XBOne I have again and put it to some use on the downstairs TV. I already have a 'retired' PS4 filling similar role on the upstairs TV (although it must stay offline to remain 'liberated').
My series x, combined with gamepass, is by a very large margin the most at-home-entertainment bang I have gotten for my buck.
Before then I had what could be regarded as a "vintage" gaming PC: 1st gen i7 (nehalem?), a gts 450 and some amount of ram. An upgrade (read: full replacement) was desperately needed. This was in the middle of the crypto gpu boom, so a decent GPU alone would've wiped my budget. I settled for an xbox as it was cheaper than a ps5.
I've always seen myself as part of the pc master race, and thought consoles to be very limited. But man, it just worked, the games just worked, and gamepass made it all a total steal.
Even now, when our 3 month old baby is settled for the night, me and my wife's preferred entertainment is a session of bg3 over watching tv.
Seemed a credible comment till that point! (/s)
Congrats :-)
Doing the math i can't find this to be true. As some one that has honed my taste in games, and have a large steam library, I don't spend as much money on games as game pass cost.
I think if I were forced to relocate my subscription and pay the full real price (€30/mo), I will probably cancel and buy a €90 game evey quarter or something.
Indie games are cheap and most AAA titles go on sale within six months, which is fine because I usually don't play them day of launch.
Then there's the issue with gamepass games not working on my system. It's the only platform where I've had consistent issues getting games to run. Even free games like fortnite, were bundled with the wrong anticheat.
Maybe that's what they're trying to achieve with Windows as well.
One of the reasons the Wii U was slow to be hacked was because Android TV boxes had come along plus things like Ouya/Nvidia shield, and it basically took away a lot of demand for a console turned into TV unit to use hacked software.
It still happened but not so quiclkly. Not like the original Wii which didnt really have much similar to it at the time.
The people that MS hired to make and break this were top notch, and there is definitely incentive to maintain control over a content platform. This dude has been at this for /years/. I’ve been a fly on the wall on all sides to observe this.
There has been a lot of interest in underground / pirate communities to hack this, but that’s not the only reason why people hack things.
And this explains why it's stayed unhacked so long. There was very little incentive to hack the system when the games are all playable on a PC. Pirates, cheaters, archivists, and hackers could just go there. Microsoft's best security measure was making something nobody cared enough about to hack in the first place