Hacking Sharing Error Information

  • Thread starter Thread starter CecilioX3
  • Start date Start date
  • Views Views 4,771
  • Replies Replies 9

CecilioX3

Well-Known Member
Newcomer
Joined
Jun 16, 2018
Messages
54
Reaction score
5
Trophies
0
Age
30
XP
431
Country
United States
I've had "Sharing error information" off in the switch system settings ever since I first got my hands on mine. Just curious if my console would still send information despite the setting being turned off? Been hearing a lot about bans.
 
Read what it says and you will find out.
"share error information from this console with third-party developers whose software has crashed for analysis and improvement purposes"
 
Last edited by Kubas_inko,
  • Like
Reactions: CecilioX3
Probably there will still be sent information to Nintendo, even if you disabled that option. We don't know yet where the error logs get stored on the console. They could only be stored in the NAND, but maybe there's an internal storage to which the NAND talks to. People reported being banned although they turned that option off.
 
Read what it says and you will find out.
"share error information from this console with third-party developers whose software has crashed for analysis and improvement purposes"
Completely missed that, thank you.

--------------------- MERGED ---------------------------

Probably there will still be sent information to Nintendo, even if you disabled that option. We don't know yet where the error logs get stored on the console. They could only be stored in the NAND, but maybe there's an internal storage to which the NAND talks to. People reported being banned although they turned that option off.
Hm I see. I should probably hold off on layeredfs then
 
Probably there will still be sent information to Nintendo, even if you disabled that option. We don't know yet where the error logs get stored on the console. They could only be stored in the NAND, but maybe there's an internal storage to which the NAND talks to. People reported being banned although they turned that option off.

a lot of people are dishonest about their bans though and experimented with everything and therefor cause of bans are completely unknown
 
a lot of people are dishonest about their bans though and experimented with everything and therefor cause of bans are completely unknown
We are forced to learn from the mistakes of others to determine what caused the bans. If we don't trust anyone, we will be sitting here for a long time without actually making progress.
 
We are forced to learn from the mistakes of others to determine what caused the bans. If we don't trust anyone, we will be sitting here for a long time without actually making progress.

there arent any ''pure ts os only'' focus groups trying to get banned. while they might have checked NO to "Sharing error information", nobody knows if theyve administered cheats or or things that weren't error-based that got them banned. A lot people arent honest to their doings in hopes of getting their bans reversed (an idiotic self-perpetrated way of tying to make themselves feel like they've done no wrong)
 
there arent any ''pure ts os only'' focus groups trying to get banned. while they might have checked NO to "Sharing error information", nobody knows if theyve administered cheats or or things that weren't error-based that got them banned. A lot people arent honest to their doings in hopes of getting their bans reversed (an idiotic self-perpetrated way of tying to make themselves feel like they've done no wrong)
People used LayeredFS, disabled that option and still got banned. Of course, not only error logs are the trigger for the recent bans. We need to find the intersections between the bans.
 
People used LayeredFS, disabled that option and still got banned. Of course, not only error logs are the trigger for the recent bans. We need to find the intersections between the bans.

so far not many have been banned
 

Site & Scene News

Popular threads in this forum