Hacking Rumor SX OS is not over

[urherenow]

I'm a fan of TX and can see the double standards too but it was never the only option. Atmosphere was available before Fusee-Gelee was released for anyone with access to a software based exploit to use. TX also 100% steals code, that is obvious to anyone who has messed with homebrew development on SXOS. In fact TX has never outright denied stealing code, they refused to respond to the accusations.

nope. I ordered SX pro May 28 2018. Aug 4, there was a Reddit post saying that Atmosphere was PLANNED to be released in August. I was using SXOS more than 2 months before an Atmosphere release. There was no github page for Atmosphere, so AT THAT TIME, how, exactly, did they steal code from Atmosphere?

I'm not denying that they do use other's code. I'm just saying they didn't simply start out with a stolen product, and they were FIRST to get a fully functional product to the public. Period.

 

[CompSciOrBust]

nope. I ordered SX pro May 28 2017. Aug 4, there was a Reddit post saying that Atmosphere was PLANNED to be released in August. I was using SXOS more than 2 months before an Atmosphere release. There was no github page for Atmosphere, so AT THAT TIME, how, exactly, did they steal code from Atmosphere?

I'm not denying that they do use other's code. I'm just saying they didn't simply start out with a stolen product, and they were FIRST to get a fully functional product to the public. Period.

Given that the Switch released in March of 2017 and the first year was spent with software exploits I think your timeline is off.
The first git commit to Atmosphere was on January 18th 2018
https://github.com/Atmosphere-NX/At...ab2540b0c0576c52cdb8da0126+3535&branch=master
The announcement of Team-Xecuter's at the time new exploit was on January 2nd 2018. However, crucially, they do not show it running a custom firmware. You can tell their initial showcase is a proof of concept because they just patch the boot logo like failoverflow did.

Between the announcement of their exploit in January and the release of their exploit (I can't remember the exact date but it must have been after April due to when F-G was leaked on paste bin) they were likely planning to make their own cfw but realized it would be much easier to reband and modify Atmosphere.
The first official release of Atmosphere was in October of 2018 but anyone with the ability to compile homebrew was able to unofficially use it long before then.
https://github.com/Atmosphere-NX/Atmosphere/tree/0.7.0

 

[urherenow]

Given that the Switch released in March of 2017 and the first year was spent with software exploits I think your timeline is off.
The first git commit to Atmosphere was on January 18th 2018
https://github.com/Atmosphere-NX/At...ab2540b0c0576c52cdb8da0126+3535&branch=master
The announcement of Team-Xecuter's at the time new exploit was on January 2nd 2018. However, crucially, they do not show it running a custom firmware. You can tell their initial showcase is a proof of concept because they just patch the boot logo like failoverflow did.

Between the announcement of their exploit in January and the release of their exploit (I can't remember the exact date but it must have been after April due to when F-G was leaked on paste bin) they were likely planning to make their own cfw but realized it would be much easier to reband and modify Atmosphere.
The first official release of Atmosphere was in October of 2018 but anyone with the ability to compile homebrew was able to unofficially use it long before then.
https://github.com/Atmosphere-NX/Atmosphere/tree/0.7.0

Yes, I'm off by a year (will correct that in a second). 2018. Months were correct, however, and I've been compiling the homebrew myself from the beginning (later in August for Atmosphere. The Github page was not originally Atmosphere-NX, and the first few releases are not in there). I Was definitely using SXOS, before a usable commit was public on Github for Atmosphere. Same goes with emunand functionality.

The only homebrew I use right now that's not easy for me to compile is TomVita's port of Edizon-SE, because my libraries must stay up to date for Atmosphere to build, and the Edizon-SE code is old.

 

[CompSciOrBust]

Yes, I'm off by a year (will correct that in a second). 2018. Months were correct, however, and I've been compiling the homebrew myself from the beginning (later in August for Atmosphere. The Github page was not originally Atmosphere-NX, and the first few releases are not in there). I Was definitely using SXOS, before a usable commit was public on Github for Atmosphere. Same goes with emunand functionality.

The only homebrew I use right now that's not easy for me to compile is TomVita's port of Edizon-SE, because my libraries must stay up to date for Atmosphere to build, and the Edizon-SE code is old.

That doesn't change the fact that people were able to, and did use Atmosphere before the first official release. As for emunand, yes TX were the first to do that on the Switch, I never denied that.

 

[hippy dave]

If I spam this thread with enough furry porn or something will it get locked, and finally leave us in peace?

 

[urherenow]

That doesn't change the fact that people were able to, and did use Atmosphere before the first official release. As for emunand, yes TX were the first to do that on the Switch, I never denied that.

NOT before SX was released. Deal with it.

 

[linuxares]

Lets close this thread now. It's run it's course.
If SX comes back, we will post about it most likely.

 

[Joe88]

nope. I ordered SX pro May 28 2018. Aug 4, there was a Reddit post saying that Atmosphere was PLANNED to be released in August. I was using SXOS more than 2 months before an Atmosphere release. There was no github page for Atmosphere, so AT THAT TIME, how, exactly, did they steal code from Atmosphere?

I'm not denying that they do use other's code. I'm just saying they didn't simply start out with a stolen product, and they were FIRST to get a fully functional product to the public. Period.

Well I think at the time when tx announced their hack, it was going to be vastly different than the sx pro that was released, think of a soldered mod chip akin to the current sx core.

Then fusee gelee was released, a far more user friendly entry point hack. This would drastically increase their sales since pretty much anyone could do it. So they simply retooled everything for the new hack or the sx pro was born. Now as to where atmosphere plays a role in all this. I think atmos was probably better and or more reliable and stable then whatever software/os they were working on. Also open source, so they mainly only had to worry about their specific/exclusive features working and updating those. As they never showed their software before it's hard to tell.
Tx did update their own os a couple of times for new switch firnware support even before atmos put out a pre-release for new fw support so they did have someone there who know what they were doing and not just copy pasting code. The same person who was creating and maintaing all the exclusive features too.

This entire thing is just personal conjecture, but just my thoughts on the it.