By all means describe such tweaks but make it clear that those using them need to know what they are doing - which in this case @Wyldanimal did and I have no problem with that post. I do have problems with those that say to everyone "just go ahead and change this undocumented registry entry, it's safe, honest," especially as they may not even work with some future release which many users will not be in a position to realise
I don't think I can totally agree with such a post - since I find to hardly have ever really have been any of the possible issues - or of the irresponsible users - which the post reports. I will explain:
@Wyldanimal 's postings and explanations are
always (not only in this case) so clear that, even for novices, the risk doing something unsafe for own system - as even (at least on such a software as iStripper) the risk to make registry modifications not anymore supported in a totally hypotetical future (so creating a total mess) is
so low to be comparable to the risk a chasm to open under our feet while we walk on the street: no one could say such a risk doesn't exist at all, but it's anyway so low a risk that no one needs to worry about it.
So, I find all the useful - and much appreciated by (almost) all of us - workarounds by
@Wyldanimal to be both
approved (since the company never stopped Wyld doing them) and
safe too: since, scrupulously following his clear advices, it's almost impossible to make mistakes and/or do harms.
I thank again
@Wyldanimal for his work, and i also encourage him to please go on.
Moreover, the large majority of people advicing others here on Forum for registry changes and so always explicitly quotes and invites to follow
@Wyldanimal 's posts on the subject - so, I can tell I am unable to see the huge problems some others see in the whole practice.