Comment 47 for bug 974480

Mark,
I fully understand the desire to move forward with Unity. I don't see how this change does that. Let me explain (and please, correct me where I am wrong):

* This is not a bug/security fix, no exploit is being fixed by removing the whitelist
* This is not a performance enhancement. There will be no speed increase with this change
* The whitelist is not blocking desired functionality - there is no new features that can be added once the whitelist is disabled.
* Keeping the whitelist would not negatively impact any other applications, or end user experience. I say this because the whitelist is off by default and there is no UI in Ubuntu to change it - if you make a change, it is HIGHLY likely you know what you are doing.
* Many of the programs this change breaks are in Ubuntu's own package repos. Things like guake, pidgin, _ALL_ kde apps (that use systray), etc will be broken by this change, but still offered in the defaul software list. Moreover, pidgin is Ubuntu approved! So, now 13.04 will presumably include pidgin, have the little ubuntu logo indicating it's tested and working, but will actually not work as expected. **You are breaking software you claim to support**

Also consider, you are not disabling the whitelist at all, all the functionality to implement a systray in the app indicator will be there for the foreseeable future to support Java and Wine.

So, my question is, why do Java and Wine get a pass ? Size of project ? Importance to end users ? Who makes the ultimate decision to say the Java and Wine teams can ignore Unity's App Indicator, but other teams can not ? What is gained ?

You keep mentioning "moving forward", but I have yet to see an explaination of what *specifically* turning this off accomplishes other than disappointing anyone who still needs systray.