Not quite. It is a real counter that synchronizes with the actual number every 60 seconds. In the interim, it increases by a constantly adjusting rate that's usually pretty close to correct. See http://www.infocraft.com/projects/ffcounter/
No, we fixed it, and then we made that information public to the world on our "Known Vulnerabilities" page (http://www.mozilla.org/projects/security/known-vu lnerabilities.html), linked to from our Security page (http://www.mozilla.org/security/), just as we've done for each release. Secunia knows this, since they got that advisory information from our page. Why don't you?
We did disclose the security bugs. Every time we release, we update our vulnerabilities page (http://www.mozilla.org/projects/security/known-vu lnerabilities.html) with the list of security bugs fixed in the new release. Secunia just cribbed their advisory information from that very page.
The world might be a better place if you actually paid some attention.
-Blake Ross
This is incorrect. Phoenix is NOT just a rewrite of the GUI portions, it already has plenty of its own backend (i.e. C++) code.
Changes were made in the chrome registry to support the new extensions manager *specifically for Phoenix*. The Phoenix team is not waiting on "Mozilla" to implement uninstall functionality, it just hasn't gotten the time to do it itself yet.
Slashdot Mirror
Not quite. It is a real counter that synchronizes with the actual number every 60 seconds. In the interim, it increases by a constantly adjusting rate that's usually pretty close to correct. See http://www.infocraft.com/projects/ffcounter/
No, we fixed it, and then we made that information public to the world on our "Known Vulnerabilities" page (http://www.mozilla.org/projects/security/known-vu lnerabilities.html), linked to from our Security page (http://www.mozilla.org/security/), just as we've done for each release. Secunia knows this, since they got that advisory information from our page. Why don't you?
Blake
We did disclose the security bugs. Every time we release, we update our vulnerabilities page (http://www.mozilla.org/projects/security/known-vu lnerabilities.html) with the list of security bugs fixed in the new release. Secunia just cribbed their advisory information from that very page.
The world might be a better place if you actually paid some attention.
-Blake Ross
This is incorrect. Phoenix is NOT just a rewrite of the GUI portions, it already has plenty of its own backend (i.e. C++) code. Changes were made in the chrome registry to support the new extensions manager *specifically for Phoenix*. The Phoenix team is not waiting on "Mozilla" to implement uninstall functionality, it just hasn't gotten the time to do it itself yet.
This is not YAGBB, it is a mozilla.org-backed foray into a future Mozilla.
You can do that now. Go to View > Customize Toolbar... in Phoenix.
mozilla.org backs Phoenix.