The 3G bands used by T-Mobile and AT&T are different and generally not supported on the same device. For example there was a T-Mobile version of the N1 and an AT&T version of the N1. They both work on the others 2G network, but not on the 3G network.
Also, a minor point, the heading for the last graph talks about the increase in credit from '99, but the legend shows '02, so I'd be hesitant comparing those numbers to the rest.
I am not a lawyer, or an accountant, or anything like that.
My understanding is that for federal Canadian corporations a certain percentage (I think 25%) must be Canadian residents.Before doing anything like registering a company in another country it would be advisable to consult an accountant.
Recurly claims to be PCI compliant on there web page [ http://recurly.com/features/ ]. Its possible they are on the list under another name, I'd give there support people a shout. I'm not sure if recurly,spreedly,etc. are actually storing the data, it seems like they might be having the gateway (i.e. authorize.net) store the data, but that is pure speculation on my part.
I am interested in doing some re-occuring billing stuff my self so do post back with your experiences with which ever provider you go with. Best of luck :)
Given that he is asking about recurly, chargify, etc. I'm assuming its because he wants to do reoccurring billing, for which PayPal/Google Checkout are less than awesome solutions for.
It would be strange if it was true.
Unless things have changed in the past ~1 year, Microsoft does not encourage employees to get their non-employee friends to use the employee discount. There is some fairly specific stuff about being able to use your employee discount on gifts, but not in exchange for $s or products.
The so called anti-sec movement confuses me a lot. They seem to hate script kiddies, but these people are no better, if anything they are more dangerous because they have a false set of ideals they believe they are promoting. I wish I could slap them with a trout.
In my personal experience, public discloser has legitimate uses in strong arming companies into dealing with security issues that they would rather ignore.
I could really go for a sane caching load balancer. My experience with stuff like pound,squid and nginx so far leaves much to be desired (and chaining them isn't exactly desirable either).
Why do they have default maximum url lengths less than IE that can only be fixed with a recompile, its madness I tell you :p
But if it becomes normal for a mailman to do this, there is now an expected man-in-the-middle. Sure the mailman might be benign, but what about if there is another man-in-the-middle (less benign), now that I expect my communication to be tampered with I won't notice anything suspicious.
[Note: Zed's proposed solution is to forward on the original mail as well so it can be verified]
I think the solution is to not allow the domainbyproxy services anymore [like some cctlds have done]. Having valid whois contact information (especially abuse) is can be very useful. e-mail often isn't always sufficient.
This is a total fluff piece. They talk about a phone which has been rejected as too dull, but dell has not even commented on making a phone, nor have any of the carriers commented on it being too dull. Either this is link bait pure and simple or I failed at reading it.
The existence of a low end instance in addition to some higher end instance availablity options is pretty awesome, this makes it cheap enough for something which you might only really need VPS level availability to make sense to build on top of their platform and then if you need a bunch of instances all at once ok to fire up.
They have quotes on the site like "I couldn't even find Amazon's phone number" which seem a bit miss-leading (Amazon simply charges for phone support), but yay for competition :)