Dear community!
As I want new build be as user friendly as possible I want it could address most frequent issues from newcomers.
For this purpose I'm planning to include (or have done it already) number of possible goodies - some of them you can see in the first CommMeleon build, and some would be newly included ones.
So I need your help in compiling 2 important lists:
1) first one - the list of most wanted extensions to be included into build a priori.
Some of them are there already (inserted by dugbug or by myself). Some of them I plan to include now.
It would help me if you tell me here 5 most needed extensions you use or want to use in KM.
2) The second point is the UA-spoofing issue (look for most popular threads in Bugs and Improvement request subforums).
I want to integrate
Auto Agentswitch extension and fill in the list of most popular sites what need spoofing.
Help me make this list more complete, universal by adding more sites like:
gmail.com
facebook.com
msn.com
hotmail.com
yandex.ru
etc. ...
Why I'm not going to make some fresh FF default UserAgent string?
Well, first reason is that sometime very new FF strings are not working fine with KM (and my general recommendation is to use 3.6.28 string - for example,
the one I use now
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.2.28) Gecko/20120306 Firefox/3.6.28
The second - and the main reason is security. When you surf as Firefox you are at heightened risk of malware intrusion in comparison with K-Meleon default UA. Why? It's simple - much of new malware is browser-specific: when you visit infected page or run malicious script, malware checks you browser (usually by user-agent string - the most easy way) and loads that variation of code that is prepared for this specific browser.
As KM is Gecko based, ff-ready malware has more chances to infect you PC through KM too.
With this in mind, its more secure way to browse in KM with Opera, Chrome, IE strings (than modern malware would be spoofed) or with default KM string which is almost unknown, exotic so malware could be stopped on the first stage.
But when you really need to spoof good sites the best way is to emulate FireFox. So I decide to use
Auto Agentswitch.
3) The third... I've said "two lists"?! Oh, sorry! There is a subject for the third one but this needs some more work than usual.
It's about overscripting prevention on some js-heavy sites with
Policies Manager extension.
Sometime such a site won't work in KM but some restrictions made by policies could get it back to life. (the example of problem and solution can be found
in this thread)
So what I need (not necessarily in the near future) is to help in finding such sites and trying to 'cure' them in KM by Policies Manager.
I see it that way: every user can report the 'bad' site and then every power user who understands using PM and other techniques can try to find solution for this particular site.
Than we can create policies that cover most frequent troubles and integrate it in next builds by default.
Edited 2 time(s). Last edit at 07/02/2012 02:58PM by rodocop.