Both are common, but compile to different code.
Do you code to 'a procedure should live on a page'? How about 'a procedure should have a purpose'? Return errors or throw exceptions? Return values or modified arguments? Kitchen sink constructors? Getters & setters or fluent builders?
There's seven variables without stopping to think, dividing coders 128 ways, and I'm sure you could find another dozen or so, taking it to one-in-a-million level. There's no need to obfuscate...

Get another email account externally, and configure your email server to send all your outgoing email via that account (using POP3/SMTP authentication). Comcast might already provide an email account/server you can use like that...

Yes, Facebook is the hosting platform, just as email once existed within computers and didn't travel between them. We don't yet have a Social Media Transport Protocol that allows peering between providers, but one day we will, and Facebook will follow AOL & CompuServe to the big walled garden in the sky. But, IMHO, that day is not in the near future.

If you're a bank or finance company, borrowing and lending on your own account, then yes, customer funds are liabilities. But stockbrokers, lawyers, accountants, et al. keep their customers' funds in a segregated trust account, and Mt.Gox and all the other exchanges should be following this model.