read as: Good enough for those not doing any own software development and/or bugreporting.
With closed source parts of your system you can never be sure where the rare crash came from. You cannot recompile the driver with safety barriers (_FORTIFY_SOURCE, mudflap, valgrind...), hardware watchpoints trap in binary code you cannot easily verify...
This results in unstable software commonly found on closed source platforms as nobody can provide reliable software there.
what needs "public" IPs? What
SIP (its STUN support works only with a luck).
Besides any service providing = servers which I run some for local stuff even on my notebook.
So I have to square root the billion pixels first and guess the painting size or guess the parameters of "an average digital camera"... Why they just cannot say the DPI? slashdot is a technical magazine or - ok, it is no longer.
So what's left of GNU code now?
Choose any two GNU packages on your system. That is still more than that one Linux kernel.
what is wrong (philosophically, security-wise, or wishing leprosy on oneself, etc.) with installing Moonlight
That you may get sued (=Fedora forbidden item).
Checking it out across the world on various machines. If I find I miss something on some host, I do `cvs update' by hand. Not a rocket science.
I have only one host I consider secure enough so there is no point in distributed mails.
I was using my Gecko bookmarks in $HOME but I had to create a small script to "normalize" them. Otherwise they contain a lot of useless info (timestamps, whether expanded etc.) making both history diffs useless and conflict merges difficult/impossible.