Secondly, I wish to clarify that even if that was the case (which it wasn't), I think it is acceptable to edit an existing PA entry, detail the native method of portability, and leave the link to the PA version for those who can't be bothered. That's preferred over having two entries for the same app, one PA and one non-PA.
I agree with what Hydral is saying here. If there is a relatively straightfoward way to make an app portable natively that doesn't involve hex editors and disassembly tools, I think that should be the first priority for TPFC. Otherwise, TPFC might as well be an alternative directory listing for PA apps!Hydral wrote:I'm with webfork here, some of us prefer to use the natively portable version (even if it's not 100% stealth), I only resort to PA.com versions if I really cannot be bothered figuring out if an app can be portableised. That's not to say your contribution is not valued, I use lots of PA.com apps, I just wish that every single one of them was natively portable, as soon as they are I will stop using the PA.com version.