Your link is a good resource, since not all forms should go to Fresno, but that office is more than just California. For instance, in Kansas and Missouri, 83(b) elections are sent to the Fresno office. The receiving offices are organized by regions.
Maybe in some areas. Here in Austin AT&T, Time Warner and the local ISP Grande are all now offering cheap plans from 300Mbps to full gigabit because Google is coming to town and they need to compete. I pay something around $50 for 300Mbps (no cap) from Time Warner and it works great.
This is exactly what Google needs - in order for their vision of the future to happen people need to have far better connections on average than they do now. When Google Fiber enters a market, everyone wins - even if you don't switch to Google as your ISP.
1) There are regimes that would lock you up (or worse) for looking at some "purely informational" sites.
2) Defaults matter and developers make mistakes. Without required TLS many sites that should be encrypted won't be (they forgot, the site grew into something it didn't used to be, they had no idea what TLS was, etc)
Ruining the web in order to prevent any possibility of bad things happening is something I'm firmly against. I have several small blogs and websites that I absolutely would not bother with if I had to pay for and set up https on each.
Here's a tiny twist on WordCount that many, many companies use MR for (often their first foot in the water): you have many gigabytes or terabytes of web access logs and need to bill customers via some API scheme like /api/3001?x=1&y=2 where "3001" there is the customer ID. You add some regex and now you're doing "WordCount" on the customer ID (per day, month, etc).
That depends, the article mentions Amazon Prime which implies these episodes are free to watch after you have a subscription. If that's true it just means the author is confusing streaming and "cheap subscription services." iTunes is just like buying a DVD except on your computer, so that's not exactly "special."
apt-get build-dep beanstalkd
apt-get source beanstalkd # or in your case, download the newer source-package
dpkg-buildpackage -rfakeroot -us -uc
This should do the trick. There are a lot of variations regarding the last line. Just google for Debian packaging or Ubuntu packaging tutorials. It really works well for minor changes. If you need to deploy it to several machines it's also possible to add a custom flag to the package version...
It did, but it's only relevant for packages which actually updated their build scripts. A huge proportion of packages from 12.04 will still build fine on 10.04 (which I've been doing in order to backport certain packages to install).