Myself, and many others are currently using sig patches ripped from an older build of ReiNX, and putting them into atmosphere manually. I pretty much did this as a temporary solution to the lack of sig patches on the cfw, and shared it to others online. Any idea on when the sig patches will get implemented themselves? Thanks.
I may be wrong, but I'm pretty sure they wouldn't be implemnting this as it's piracy related. I'd personally like it as homebrew could be installed as a title.
I don't think it'll be implemented, and not even for homebrew, since SciresM want a framework for launching hb menu. (like luma3ds)
My 2 cents: As it stands right now, unsigned NCA installation = Piracy. "Homebrew" NCAs can technically happen but I see zero benefit in them vs homebrew NROs loaded through HBL, and I only see a plethora of problems regarding custom titles (especially with Nintendo banning users who have installed custom titles with or without invalid title IDs). I think we would be better off if people would stick to NRO. There's really nothing we can't change in HBL, and you should already have full FS permissions through it, as well as full service permissions (without even needing smhax, which was reimplemented anyway). Homebrew NCA per se aren't evil, but they involve too many potential issues and inconveniences to be a good way to run or support homebrew.
I think you should make your own fork of atmosphere with the things that 90 percent of the people want.
thanks Lunalik.
@Comput3rUs3r np. I don't know if I'll be able to release this on github though. I has parts of the ES, so it is kinda in the grey area. It even got removed from ReiNX because of this. @SapphireExile well if you are interested in using them for development, or personal use, search for Lunalik Person on Facebook, and check my first and only post.
I think without sigs being patched its not a cfw just a mfw but im old school i guess .
@drofdoom Other consoles had it in general because of it being bether (PlayStation particularly). The 3ds mostly had it for homebrew, cause a good framework was implemented very late. The wiiu: well idk. No one cares apparently :/.
As fincs explained, too many drawbacks, and mostly for piracy, so for now, 0 benefits.
@mariogamer2 I used it to install Hulu for devMenu. I also used it to install backups of games I OWN (so I don't have to bring the carts everywhere). There are uses other than piracy, and there will be more once hb apps are developed.
Yeah I know that installing backup of games is legit. But still.
(off topic: Hulu is on the switch?)
You can install backups of games and updates you dumped from that console without any "sigpatches".
Anyone asking for these is strictly for piracy (as they arent asking for unsigned NCA loading either, they are asking for patched ES to install fake tickets, which is stupid, because there are better modules to patch for that if you want it, except you dont want it because theres no reason to use fake tickets, even for piracy.)
@rajkosto But I don't think this is cartridge related, right?
You can install anything you own without forged tickets, which is what OP means by "sigpatches".
Ok.
I thought it wasn't related cause of the cartridge specific stuff.
@fincs Will we ever be able to suspend homebrew? Since we load it through an applet this isn't currently possible.
Some people just want to play their title key encrypted homebrew games. ( 汀掳 蜏蕱 汀掳)
@AnalogMan151 Keep in mind that supplanting the album applet isn't the only option. Any other legitimate title (i.e. non-applet too) should be possible as the HBL host title.
@Reisyukaku None exist currently and as I explained previously, there are no plans to support homebrew NCAs at the moment, due to no real benefit and on the contrary, several potential issues. As it stands right now, titles with forged signatures equate to piracy.
I was being facetious @fincs :p
title key crypto is gross anyways.
@Rei you get it ,its not a true cfw without it I dont care what anyone says its just moded sys modules .
i could see it being legit as consoles that have been banned from the CDN cannot redownload their own content leaving downlaoding it being the only option for playing legitimate content
By legitimate i mean stuff you paid for. For example i dont see downloading an iso for a game that is damaged to the point it is unplayable as legitimate
@fennectech they used cdn first -> let's not be blind, most people exlcluding devs use it for piracy. Even tho it wouldn't seem fair, I think it is.
(off topic: I do see that case as legitimate. It hapenned to me with mario kart 8 (disc), the game was for no reasons unlayable. I was stupid enough to buy it again.)
Well i didnt use cdn layered fs or none of that till i was banned from eshop for clearing my logs trying to hide homebrew so now im all in for the piracy acts .
My thoughts :
Of course, I can also understand your pros and cons, and I have followed this discussion with interest. Here was just my personal thoughts.
You can have hblauncher as menu icon without any patches, just exefs redirect of flog or similar system application.
Not neat enough thats just a work around plus wouldn't it have to be a pure exefs title ?
hblauncher is a pure exefs title.
I meant the donor
what romfs the donor has is irrelevant when the redirected exefs does not mount it.
Fair enough then why suggest flog and system titles with pure exefs ?
Closing this for now.
Most helpful comment
My 2 cents: As it stands right now, unsigned NCA installation = Piracy. "Homebrew" NCAs can technically happen but I see zero benefit in them vs homebrew NROs loaded through HBL, and I only see a plethora of problems regarding custom titles (especially with Nintendo banning users who have installed custom titles with or without invalid title IDs). I think we would be better off if people would stick to NRO. There's really nothing we can't change in HBL, and you should already have full FS permissions through it, as well as full service permissions (without even needing smhax, which was reimplemented anyway). Homebrew NCA per se aren't evil, but they involve too many potential issues and inconveniences to be a good way to run or support homebrew.