It's better because it's where the people are.

When you're trying to build a new platform, it's not enough to be better. You have to be so much better that staying with the existing platform doesn't make sense. Otherwise the momentum of the existing community already being where it is, of people knowing to look there for it, all of that mass is just not worth moving.

Unless the platform you're competing with screws up so handily people feel like they don't have a choice. Take a look at freenode a couple years ago removing effectively all the value of the platform in a matter of days when a new owner took control. People moved, and moved quickly, because the thing they had been using disintegrated, just like reddit is in the process of doing now.

Ah, and

chsh # change to zsh

This is my mantra:

vi /etc/apt/sources.list # switch to testing/unstable and add contrib & non-free
apt-get update
apt-get dist-upgrade
apt-get install vcsh mr vim zsh screen openssh-server # the most important bits & pieces
vcsh clone /mr.vcsh # clone the repo containing location info of my configuration repos
cd .config/mr/config.d
ln -s ../available.d/{what,i,need} . # enable whatever repos for code & config which I need on that machine
cd
mr -j 5 up # automagically clone, checkout, whatever ALL the things
reboot

Sorry, but it's crap:

* Uses plywood instead of wood that's naturally resistant to water and insects, line white pine (pinus strobus)
* That build wastes a huge sheet of wood instead of starting with small pieces. That's a waste
* Need for CNC
* Insanely complex build
* Angled roof, resulting in bad support for the hive
* No room to extend the hive to harvest honey
* No immediately obvious way to access the hive from below
** No way to check on bees to see if they are all right
** No way to deploy stuff that kills varroa destructor

There's a German non-profit called Bienenkiste.de (literally "bee box"). It's a simply, sturdy design that went through over a decade of improvements and incorporates feedback from professionals. Honey yield is 1/2-1/3 of that what the same hive would get with traditional hives, but they are a lot less work and the bees are in a more natural state. This means that the bees are so relaxed, I can do all my work on the hive without smoke or protective equipment.

http://www.bienenkiste.de/doku/bauanleitung/ for instructions. Translate into English, the pictures and videos should be largely self-explanatory.

Came here to say this. It's not uncommon to see family-type cars go faster than this.

I probably go over that speed at least twice a day: during my daily commute.

You can do this without killing the ISPs even. The municipality can own the cable in the streets and on the poles, and bring it back to a POP where different ISPs can connect in. You want to switch from comcast to verizon? Someone moves a cable in the POP, and it's done.

I think this is the logical next step, as it'll be a bit easier to do this without the ISPs lobbying it away. (but still nearly impossible)

If every site uses the same set of questions that fulfill the four requirements laid out be OP, the system is still broken.

Yah, cause iOS does not. Especially since most people write it as IOS.

> 2-300 pictures a day is a lot

That's not even close to a lot.

Even disregarding series of night sky pics for stacking and other continuous shots, there are a lot of reasons to reach 1000 per day. "Birds in flight", for example.

If you are using Linux or *BSD (including OS X), git-annex is the way to go. Seriously.

http://git-annex.branchable.com/
http://www.kickstarter.com/projects/joeyh/git-annex-assistant-like-dropbox-but-with-your-own

Not if you are in an area where locals don't speak English. And, for example, neither spoken nor written Latin gets you anywhere in a Chinese pharmacy.

Still, keeping it low tech is the right thing to do.

They also last a good 6 years... (assuming they ever stop working.)

1) git-annex (if on Unix)
2) badblocks -swo foo.bb /dev/foo #this will erase all data on disk. If it reports even one single bad block, toss the disk out.

No.

* LightSquared gets an assignment of free spectrum
* LightSquared invests tons of money
* The GPS industry has been violating FCC rules by not filtering out non-GPS spectrum _as they are required to_ on all devices. Independent tests say 75% are not FCC-compliant
* The FCC performs tests with models chosen from said 75%
* The FCC states that the risk is too large and destroys LightSquared's business model, assets and tells them they are not allowed to use their spectrum.

Now, I do get the safety aspect. This is valid.

In my opinion, the willful neglect by the GPS manufacturers requires them to fix it at own cost. It does _not_ make if OK for the FCC to destroy LightSquared. As much as I disagree with the sue-happy stance in the USA, this is a valid way to recoup their losses.