1) Steal credit card
2) Use stolen credit card to buy new phone
3) Take/sell phone and credit card to Russia
4) ???
5) Profit!

Usually the credit card companies compares your address to the shipping address of the order, not the seller's address. This is why you'll often have problems buying something online as a gift and trying to have it shipped to them directly.

Cool, so now people with multiple credit cards (personal & business, etc) need to either carry multiple phones or fumble around swapping sim cards in the grocery store line-up.

Policy? The government put in a law REQUIRING them to do it. They had no choice. You'll notice they are still charging you $50 to *undo* a restriction *they* put on your phone.

I know a family that lives next to the US-Canada border (their driveway is less than 500 meters from 0 ave.) they had to call their cell-phone provider so often to reverse the charges that the provider started just automatically waiving any roaming charges on their phone because they were sick of getting the phone calls! (Note: They live on the Canadian side).

Right, because everyone loves having to maintain *multiple* phone contracts, phone numbers and voicemails, not to mention how freaking tiny and easy-to-drop sim cards have become. We should not have to put up with this crap when we all know they're routing the data between each other using the same technology as a free voip call.

Though not particularly unusual, I once received a bug report by email and proceeded to debug, fix, deploy (to test server), test and deploy (to production server) a fix for a non-profit group on the train on my way to work.

Are you talking about pipelight (which runs silverlight in wine and pipes it to your native browser) or running the entire browser in wine?

Pipelight uses the silverlight plugin which Netflix currently only keeps working for the Mac users (at least, until now apparently...), so if Mac users switch to HTML5 who knows how long that will keep working.

Running the entire browser under wine has always been even more difficult, usually resorting to using the silverlight plugin inside wine as well (see paragraph 2). So unless someone actually gets HTML5 Netflix running under wine, we are basically boned.

When I fought my ticket (officer thought I had no seat-belt when I did), there were no fees except for forfeiting the "early payment" discount and my personal costs of time and transportation to get there. This was in western Canada, so YMMV elsewhere.

Another thing to keep in mind is you can get the early discount on part of a ticket if you only plan to contest another part. For instance, my ticket was for speeding (which I was and they had a radar gun) and the seat-belt (which I was wearing). I got a discount on the speeding portion and still fought the seat-belt part (I won because the officer didn't appear in court).

I'm not sure the line is as distinct as you present it to be. What about companies that only link to the libraries? What about companies that distribute their product as source code (shopping carts written in PHP for instance have no binaries)? And what about companies running (but not developing or distributing) this vulnerable code but handling sensitive data (hospital using OpenSSL for the HTTPS on their website)?

So they were recommending a Windows-based devices to avoid the viruses on the Linux-based devices? That's almost funny!

That's right, set a legal precedent that would prevent any company from ever contributing to open source projects in fear of legal action. That aught to ensure that bugs never get missed in the future!

Or maybe they intentionally did a bad job so others wouldn't even try?

Same thing in Surrey, BC (south-east of Vancouver).

Maybe not, but the flicker (not present in LCD technology) gives many people a headache. In our old high school, there was this 1 monitor that had to be kept at 60Hz because of a high-voltage line going up the wall behind it (the other side of the wall was the metal shop with a CNC) and any other resolution would cause the monitor to go squirly (wavy lines, etc). People *hated* sitting at that computer, even those who had no idea we'd changed the refresh rate from the 72 (which the rest of the monitors used) to 60, it was literally painful to look at close up.