Not developed by Apple, but vlc does that fine (at least on my Linux box, with VLC media player 1.0.6 Goldeneye).

I'm afraid you got wooosh-ed, my friend.

I installed Folding@home for precisely that reason. I used to do a "yes > /dev/null" but then thought I could donate those cycles for something useful.

System-wide programs are stored in directories not writable by normal users, but that doesn't prevent a user from downloading a trojan into his own directory and running it, which is what the parent was talking about.

Unix systems do offer the option to mount /home (and other mount points like /tmp where the user has write access) with -o noexec which would close that issue, but I've never seen a linux distribution that would do that by default, because users expect to be able to run programs they've downloaded without having to jump through hoops.

You're totally right on the missing bridge to email, but the invite system is good in that it permits controlling the load on the system, by only giving as many invites as the system can handle. If they had opened it to everybody right away, it would have been *really* unusable due to overload. (And also makes people with an invite feel special and therefore want to use the system)

I agree the current situation is far from perfect (Ideally, the people at freedesktop.org would build a unified centralised password access protocol like they did with dbus etc, so applications developers wouldn't have to implement all existing protocols every time) but having each application implement its own strategy is worse.

Three reasons:

First, the user either has to type as many master password as there are implementations (Now I have to type three passwords when logging in: the session password, the kwallet password, and the firefox password because firefox doesn't integrate with kwallet) or store them in cleartext (or in an easily decrypted format). If I had to type one master password for each program that needs passwords (IM, browser, email, irc, gpg, ssh, etc), that would mostly defeat the purpose of them.

Secondly, having a single storage space enables sharing passwords securely between applications. Now I need to save my passwords separately for firefox, konqueror, and chrome. You'll say "stick to a single browser then" but it shouldn't have to be like that.

Third, writing your own implementation increases the risk of having bugs that lead to security holes, compared to a single implementation that got polished over time.

I'm not sure your statement that most users don't use those is right but know too little a sample to support my opinion (I don't know that many linux users but all of them, and not only experts, do use gnome keyring, and I use kwallet).

CanvasBlock? :) They say it has stability problems but I'm sure those will get ironed out (possibly through an actual plugin rather than a greasemonkey script) when the need arises

A proof that video quality does have long term effects: http://www.xkcd.com/598/

I used to run a catchall, but nowadays my domain receives on average ten thousand spam mails a day, and 97% of it has a randomly generated user name part, like istinsunbonnetsamuel@mydomain, carrilloeddypedagogytruillo@mydomain, etc. So now I do like you do, but with a white list of user names. Anyone sending a mail to a nonexistent address gets his IP blacklisted for a few minutes. This IP blacklisting cuts down about 40% of mails sent to legitimate addresses. Mail forged to appear sent from my domain makes up 20%, and spamassassin removes the remaining 30% of spam (the rest, 0.1% of the total, is legitimate mail).

Sorry but you are wrong. In the first part of your comment, the three cases (boy boy, boy girl and girl boy) are equally likely.

If you don't make the "one of the children is a boy" hypothesis, then these three cases all have 25% probability, and girl-girl has 25% probability as well.

You're right that same sex (girl girl + boy boy = 25% + 25%) and different sex (girl boy + boy girl = 25% + 25%) both have probability 50%.

But the problem says *knowing that one of the children is a boy*, what's the probability the other also is, i.e. what's the probability of the boy boy case assuming we aren't in the girl girl case. That gives 25% divided by 75%. IOW, knowing that one of the children is a boy, we're in case boy boy with probability 33%, boy girl with probability 33% and girl boy with probability 33%.

In the second part of your comment you're counting twice the families that have two boys, both born on a Tuesday, which is why you get probability 14/28=50% instead of 13/27.

What you said about the Monty Hall problem is correct.

I don't think chat networks like Yahoo, MSN chat (or whatever it's called today), ICQ encrypt the passwords...

Sorry, replying to myself but I forgot this: All window managers I've tested (kde's, gnome's and ion) lets you set a keyboard shortcut to put a window full screen, i.e. hiding window decorations and task bars for when I want a window completely full screen, whether the application supports it or not.

I constantly need to see many windows at a time... When coding I often need a documentation window, when designing a webpage I need to see the webpage while I type the source, when making a document I need to see the rendered version, when following instructions from a webpage for doing something in a terminal I need to see those two simultaneously, etc. Also I like keeping that IRC window at the back and just showing the last line below other windows so I can see what people are talking about without interrupting my work.

I only ever maximise windows when browsing the web or doing something in the terminal that doesn't require looking at documentation...

Ah, this. :)

That video got deleted for not complying to site rules or something. What was it?