Hacking Clarification of emuMMC safety?

[a5723797]

Nobody has ever been banned for a low fuse count before, and it's not something that is currently detectable outside of the boot process or sleep functions. The same goes for AutoRCM.

Pardon me for asking for clarification again:

Is it possible to detect low burnt fuse(both kind) count in future OFW(HOS) ??

Although not now, if it's still possible for future OFW, then I guess the safest(no guarantee for sure) way to go online without a ban is to use OFW in sysNAND with everything normal including correct burnt fuse count(both kind), and only to use CFW for any hacking activity in emuMMC? Maybe also remove sd card with emuMMC before booting into OFW?

Or is it impossible to check fuse count even in future OFW, for sure?

Thanks

 

[Lacius]

Pardon me for asking for clarification again:

Is it possible to detect low burnt fuse(both kind) count in future OFW(HOS) ??

Although not now, if it's still possible for future OFW, then I guess the safest(no guarantee for sure) way to go online without a ban is to use OFW in sysNAND with everything normal including correct burnt fuse count(both kind), and only to use CFW for any hacking activity in emuMMC? Maybe also remove sd card with emuMMC before booting into OFW?

Or is it impossible to check fuse count even in future OFW, for sure?

Thanks

I can't predict the future. I doubt fuse count mismatches will ever be detectable by Horizon.

 

[BaamAlex]

I know this is a bit old. But is an emuMMC safe atm? Or is something there detectable which nintendo can see? I have been thinking for a few days now whether i should really set up an emuMMC.

 

[annson24]

Ban Risk:

Instant ban:
• Piracy of any sort
• Homebrew nsps
• Changing user icon through homebrew
• Sketchy eShop behavior

Not so instant ban, but still a ban:
• Modding online games, except in very niche circumstances
• Cheating in online games
• Clearing error logs after they've been uploaded to Nintendo (this may extend to using both emummc and sysmmc online, due to mismatched logs)

Not a ban, so far:
• Atmosphere itself
• Homebrew
• Custom themes
• Custom sysmodules (sys-ftpd-light, etc.)
• Mods/cheating in offline games
• Overclocking with sys-clk (just don't do it competitively, for all of our sakes)
• emummc

We just don't know enough yet:
• Screwing with PRODINFO, but NOT committing bannable offenses
• Using the experimental PRODINFO dummying included in Atmosphere 0.11.2 and later.
(this assumes that you disable online syncing for games you intend to save edit of course)