Re: New Iron-Version: 9.0.600.0 Stable for Windows
Posted: Mon Feb 14, 2011 6:45 pm
I have moaned on about the topic of losing the 'ask me' option a few times in the recent versions of Iron, respect and concur with a lot of mele20's opinions/experience.
Third party solutions which you can trust, 100% compatible with your setup and do not have their own hidden agenda are a rare thing (even trusted ones sometimes are later found to have a clever encrypted wrapper for some ad/spy/malware), and for these same reasons I have not jumped on the extensions bandwagon (where can you find any guarantee they conform to not breaking chromes internal privilege elevation levels?, do not have additional unwanted functions you would have to read through reams of privacy policy to find the obfuscated wording which might give you a hint as to what else may be lurking in the installation?, google seem to be reluctant to put a stamp of approval on them (they certainly will not be checking out Iron compatability too - I dont think SRWare has enough time in a lifetime to keep on top of this aspect too), and the more desired ones do not have the necessary api to function as well as firefox equivalents.
However I also concur with IronUser; badgering SRWare (is this a one man show or does he have a few coders helping?) to produce the potentially millions of lines of code to re-instate a feature originally coded by googles cream of the crop army of coders is asking a bit much really, at one time I hoped it may be just a case of un-commenting the relevant parts so that they function again; how long a job or how complicated (would un-commenting such code break newer lines of code in the rest of the content manager and be no-longer compatible/break chrome?, I dont know for one)
I am pretty sure if SRWare could manage it with the stated intentions of producing the most private version of chromium ... he would.
Therefore, in the time being, the best compromise option I can think of is to revert to the old trick of putting Iron in full incognito mode where nothing is saved (add a space followed by --incognito to the end of the target line in Irons icon properties)
And ... Bug the hell out of google to re-instate it so the resulting chromium code comes down the line to us via SRWare stripping out the undesireable elements .... http://www.google.com/support/forum/p/C ... 21b7&hl=en
Third party solutions which you can trust, 100% compatible with your setup and do not have their own hidden agenda are a rare thing (even trusted ones sometimes are later found to have a clever encrypted wrapper for some ad/spy/malware), and for these same reasons I have not jumped on the extensions bandwagon (where can you find any guarantee they conform to not breaking chromes internal privilege elevation levels?, do not have additional unwanted functions you would have to read through reams of privacy policy to find the obfuscated wording which might give you a hint as to what else may be lurking in the installation?, google seem to be reluctant to put a stamp of approval on them (they certainly will not be checking out Iron compatability too - I dont think SRWare has enough time in a lifetime to keep on top of this aspect too), and the more desired ones do not have the necessary api to function as well as firefox equivalents.
However I also concur with IronUser; badgering SRWare (is this a one man show or does he have a few coders helping?) to produce the potentially millions of lines of code to re-instate a feature originally coded by googles cream of the crop army of coders is asking a bit much really, at one time I hoped it may be just a case of un-commenting the relevant parts so that they function again; how long a job or how complicated (would un-commenting such code break newer lines of code in the rest of the content manager and be no-longer compatible/break chrome?, I dont know for one)
I am pretty sure if SRWare could manage it with the stated intentions of producing the most private version of chromium ... he would.
Therefore, in the time being, the best compromise option I can think of is to revert to the old trick of putting Iron in full incognito mode where nothing is saved (add a space followed by --incognito to the end of the target line in Irons icon properties)
And ... Bug the hell out of google to re-instate it so the resulting chromium code comes down the line to us via SRWare stripping out the undesireable elements .... http://www.google.com/support/forum/p/C ... 21b7&hl=en