This seems specious. Correctly assigning blame won't matter to readers; most people couldn't care less. Sticking a different brand name on the failure is side-stepping the issue: nothing stays up 100% of the time. Create a custom page that treats the situation with a little bit of levity.
If legitimate downtime happens often enough that someone would actually internalize the difference between your failures and Heroku's, you have bigger problems than your error page.
> Then they conspired (shown in leaked emails) to only follow DMCA requests coming from large US entities (while ignoring requests coming from Mexico, for example).
Color me ignorant, but this doesn't sit right with me. Does the DCMA have international scope? Does the FBI enforce Mexican law?
That's not being asked. The question is wether a Mexican entity has legal standing to take legal action using a US law against a US-based entity in a US court.
* Marital status is a protected class. You can't consider it when hiring.
* Age is a protected class. You can't consider it when hiring.
* Pregnancy is a proxy for sex, a protected class. You can't consider it when hiring [1].
* Parental status is a protected class, but apparently is not applicable to Employment cases [2]. So you could get away with avoiding parents in some places. But man, what a great way to violate the No Asshole rule. Frankly, I'd rather not work for a startup that would want to go down this path.
I'm 27, with a wife and three kids. I've been working full-time on my own startup for the past 9 months. Without salary.
See, there are plenty of us who can kick ass and raise a family at the same time. Not to mention plan and budget responsibly. In fact, you might really want to hire people who are good at that sort of thing, rather than the Red Bull-chugging, couch-sleeping, college codemonkey stereotype. But I suppose stereotyping is what got us here in the first place, and that's not fair to Red Bull aficionados.
I guess I'd just rather you let me and other prospective employees assess the risks for ourselves. That means frank discussion about clear, accurate information. But don't curtail things because of personal bias.
I understand what you are getting at and I agree but I'm not really sure it would be in your best advantage to divulge that kind of information in interviews for instance.
Good point - I seem to have forgotten that as well as I considered 3GS or greater to be my target. So it is a good point to consider for usability, depending on the app. But FYI, at least in my app's case, it wasn't a determining criteria or test in order to pass app store review.
Personally, I find myself disagreeing with both sides too much for this to be effective at all.
I'm not going to say one should or shouldn't vote Democrat. But, there are too many considerations on which I'm unwilling to compromise to just vote for the enemy of my enemy. Neither party is your friend.
Politicians will always do whatever is in the interests of the people or companies giving them votes or donations, so unfortunately without voting for the enemy of your enemy (and maybe convincing others to do so), you don't have any other tool to punish these politicians.
And they need to be punished, just like a good spanking at the right time does wonders for spoiled brats.
"unfortunately without voting for the enemy of your enemy (and maybe convincing others to do so), you don't have any other tool to punish these politicians."
From experience (see the NRA in particular), a largish single issue voting block that is willing to support either party can be enormously effective at advancing their issue.
