I actually spend most of my time around democrats, being somewhere to the left of party mainstream (though my gun-related activities also put me in contact with many right-wing folk, there's little else on which I and they have common points). A clear majority support magazine size restrictions. A lot would prefer to see all semi-autos and handguns banned, reasoning that bolt-actions are good enough for hunting, and pump shotguns are good enough for self-defense at home (and considering handguns to be dangerous enough to override their utility as a portable self-defense tool). And "just ban them all" is not limited to one or two weird guys, either.

I'll grant you that there's also a minority with a somewhat libertarian outlook on policies other than economics, but it's just that - a minority.

Moderate democrats these day are usually not in favor of 2A as an individual right.

GP is a libertarian, clear and simple.

I suspect she would choose to print statues of Mary.

Your Google account is a G+ account, it just has a bit flag "don't tell me about G+" set in it, courtesy of Google.

When you're writing native desktop apps, the code that's actually running is also not the same as what you're writing and debugging - the former is assembly, the latter is C or C++.

I find it very dubious that the tech in question is actually viable today. I am not aware of any actual "smart gun" offerings on the market today, and surely there would be some if it could be pulled off in a reasonable way - there would be demand for them, if only among the casual gun owners who want an extra safety measure for the sake of peace of mind, even at the cost of reliability.

Well, we need some generic standard for push notifications first, and we need that standard to not require a centralized server - which kills it right away, since e.g. both Apple and Microsoft insist on people using its servers for all notifications on iOS, Win8 and WP8. Unfortunately, this whole battery optimization business resulted in a kind of lock-in for the new generation of high-level networking protocols.

Why not just sell them into slavery while you're at it?

Lead is trivially cast into bullets.

Black gunpowder is not hard to make, and, for all its disadvantages, can be used quite successfully in single-shot or manual-cycling designs (bolt/pump/lever-action), and even some repeaters (e.g. DAO revolvers).

Cases can be made out of plastic - see shotgun shells.

This leaves the primers. I don't know if these can conceivably be home-made, but I suspect it's not all that hard.

Anybody can create a gun out of a bunch of metal pipes and a couple of springs, all readily available in the local Home Depot, with as little as an electric drill. This has been true for decades now, too. It's just as untraceable, and you can actually make semi-auto (or even full-auto) weapons firing a decent-sized round that way. So, nothing new here, other than all the sudden attention.

The "future" has been here for a long time now. It's just that the media shit storm has caused more people to suddenly notice.

It's all about the rifling or lack thereof, not about the caliber. A rifled 12 ga slug gun is legally a rifle (and would be a destructive device if 12 ga wasn't specifically exempt as "suitable for sporting purposes", or some such).

They do say that Win8 Metro apps will be trivially portable. I can't help but wonder if that'll include games. For a lot of indie stuff, this would be quite sufficient.

There's no need to replace XMPP with anything, it's good enough. It's getting the big players to support it that's a challenge. A different standard would face the same exact problem.

The problem, as I understand it, is that iOS background model for apps is not conductive to pre-existing protocols like XMPP. For networking, if you want to react while in background, you have to use Apple's push notification service. On the other hand, for a compliant XMPP client, you have to keep a network socket to the server open at all times. All iOS XMPP clients that I've seen connect to app developer's server instead, which serves as a gateway; but, of course, this means that you are handing your credentials to the middle man, and they can spy on your communication if they want to.

Apple does allow apps to keep a background socket open indefinitely if they declare themselves as "VoIP", but they do actually check whether the app uses this capability for its intended purpose. I believe an XMPP client would only qualify if it's using the socket in question for voice traffic; it still can't use it for text.