Here to corroborate what @Lacius
has said. Blawar knows his program better than us (obv), so he tries to engage in discussion about the complexities of things we can't know (it being closed source, and us having stopped using it after the initial breaking changes in 4.0.0). Additionally, he always refers to it as it currently is (or seems to be doing so; he could also just be lying, but based on previous discussions, I think he's got some "technically
I'm not lying" minutiae on his side) -- but I know this: when I first used the thing, it changed my launcher (forced me to use Mercury, I think), changed my button combos, broke other apps, bundled Incognito unnecessarily, and then justified changes to his Atmosphere fork to support Incognito, a software he's clearly bundling so he can justify this vendetta against Kosmos/Atmosphere. This is his bid to say "well, if you're going to disagree with me, then as a developer of a large app (made larger by the name he stole), I'm going to modify your CFW to my liking so I can control it and take credit for it".
But none of this is driven by good product design, UX design, nor even actual development -- and those are things I do for a living, mind you. There do seem to be some legitimate complaints about Atmosphere going against a spec they helped outline/agreed to, and some violations of entering code into codespace belonging to Atmosphere that specifically supports HBL (which makes it non-agnostic), but they could easily use the same "trying to develop a full suite for the Switch experience" excuse he does. But in any case, he can't file a complaint with them because they refuse to speak with him or support his stuff. And speaking with him myself, I can easily
see why. I let him go through the whole spiel in that other thread, and none of what he said was actual justification. When I provided other solutions that don't
require modifying a user's firmware without their express and informed consent (he'll tell you it's implied and he disclaims enough, but it's garbage), he either ignored the good ones, or would nitpick some thing he didn't have control over.
The largest and scariest thing to me is that he exposes the user's prodinfo (ostensibly so Incognito can back it up and wipe it, but who knows if that is the true motive), but doesn't inform the user that he's doing this, that this is composed of the unique bits that make up the identities bans are tied to, and/or could be uploaded elsewhere (the tinfoilmod author says he RE'd Tinfoil and found nothing untoward), and used by others to spoof themselves as innocent users so they can download stuff under their product info and get them banned instead of themselves. That is also besides
it hijacking my button combos and purposefully configured launcher.
And mind you, this all takes more work and code from him. Any developer that doesn't want to support something is basically like "look, it's a headache for me to consider all that, I don't even use that in my own setups, you're essentially sailing uncharted territory, anything can happen, I'm not responsible." But instead, he's trying to say it's "unsupported" while specifically going out of his way to support it in a way that lets him modify/control the user's experience, and in ways that make it less secure. And when we point this out, he's like "fine, I can just prevent Atmosphere users from launching Tinfoil at all". And it's not like he's got old versions linked on his site -- he specifically wants to control what you run.
- Seconding what Lacius said
- blawar changed a bunch of stuff, some of it unsafe
- he's not properly informing/getting consent to do this
- His motives are mostly personal, and to do with a developer feud, not anything necessary, or useful for users
- exposes your prodinfo (the stuff that can get you banned)
- works extra to do all this, says this is what "unsupported" looks like
Anyhow, I highly recommend tinfoilmod, keep anything blawar has written away from your Switch for now.