Sebastian Hengst archaeopteryx at
Fri Jul 11 17:50:25 UTC 2014

 From about Palemoon (these likely also apply to 
Thunderbird where applicable): Scroll down

"Requirements for the regular Pale Moon browser are, in short: a 7th or 
later generation CPU with SSE2 support."

"The following features have been disabled by design:

     Accessibility features. Most people don't have a need for 
accessibility features. This cuts down some on the input complexity, and 
increases speed, but will, obviously, not be suitable for people who 
need these features.
     Parental controls. Pale Moon aims to be a fast browser for general 
use, not a "secured family browser". The design impact of parental 
controls as introduced in Firefox 3.0 and later is significant, and has 
had serious implications for building the browser. As such, parental 
controls have been disabled.
     WebRTC. Apart from opening up a whole can of worms security-wise, 
"Web Real Time Chat" (comparable with Skype video calls and the likes) 
is not considered useful or desired functionality for Pale Moon. This is 
best left to dedicated programs or at most a browser plug-in.
     Maintenance service. Pale Moon does not use the Windows maintenance 
service and does not update silently in the background.
     Integrated PDF reader. The code for this is still included for 
emergencies (i.e. when you need to read a PDF but don't have access to a 
reader) but disabled by default - you are always recommended to use a 
separate, up-to-date document reader for PDF files (as an external 
program, not as a browser plugin) for your own security and to have 
documents displayed in their fully intended format instead of a 
stripped-down in-browser reader.
     Social API. The code for this is still included for people who 
choose to use it, but completely disabled by default.
     Tab Groups. The Tab Group (aka Panorama) feature has never properly 
matured and has not seen many people using it. In addition, the feature 
is generally slow to use, not intuitive, and puts a rather hefty load on 
the browser when included. For people who still prefer to use this 
feature even though it has been completely removed from the browser, an 
add-on is available to replace the removed code.
     A few miscellaneous things like the crashreporter and telemetry 
data gathering since they require server-side components that are not in 
place at, as well as the latter impacting user privacy.


-------- Original-Nachricht --------
Betreff: Re:
Von: Patrick Cloke <clokep at>
An: tb-planning at
Datum: 2014-07-11 18:20
> Looking over posts on the forum a bit it seems to be pretty much
> Thunderbird:
> "Fossamail comes with different defaults (both UI and under-the-hood)
> and has been rebuilt with a newer compiler and better optimizations than
> Thunderbird.
> Otherwise, there aren't many differences. At least not at this time."
> pretty much talks in
> circles that it's "optimized" but won't say how.
> --Patrick
> On Fri, Jul 11, 2014 at 12:07 PM, Kent James <kent at
> <mailto:kent at>> wrote:
>     On 7/11/2014 3:47 AM, Ludovic Hirlimann wrote:
>         Hey,
>         Shall we reach out to the guy so we can get whatever patches he
>         applies ?
>         Ludo
>     Reading his material on that email client as well as their
>     more-established browser alternative PaleMoon, it sounds like they
>     are focused on tweaking settings and reversing controversial UI
>     decisions (PaleMoon: "Familiar, efficient, fully customizable
>     interface (no Australis!)" But perhaps someone with more than my 5
>     minutes of experience with them could comment. Still, if someone
>     like Fossamail feels strongly enough about a UI or settings decision
>     that they are willing to ship an alternate product with a tweak,
>     perhaps we could revisit some of our decisions and make sure that we
>     are confident that our defaults are what we want.
>     What we should do is to reach out to them, make sure they know they
>     we are happy they are shipping a similar product, and try to embrace
>     them as part of the overall Mozilla comm-central community. Maybe
>     even get them to consider sending someone to the summit!
>     :rkent
>     _________________________________________________
>     tb-planning mailing list
>     tb-planning at <mailto:tb-planning at>
>     <>
> _______________________________________________
> tb-planning mailing list
> tb-planning at

More information about the tb-planning mailing list