If it's a takedown of some kind, your client erred by being subject to a government that ordered you unable to see the resource that you requested. The 4xx code fits, in this case, as 5xx implies the server made a mistake (it didn't).
2,034 karma · joined April 15, 2011
If it's a takedown of some kind, your client erred by being subject to a government that ordered you unable to see the resource that you requested. The 4xx code fits, in this case, as 5xx implies the server made a mistake (it didn't).
Unfortunate that a legal battle puts you in that position, but if this app is as important to her life as she says, she should be perfectly fine freezing that iPad where it is and not treating it like an iPad any more. It is now a dedicated appliance, not a general-purpose iPad. Buy another one for everything else.
Sucks, but, best solution given the circumstances, I think. Obviously, it'd be great if the circumstances changed.
(Edited to add backup.)
To that end, I can understand some of the complaints.
Q1 2013 (tentative) iOS 6.1
Q2 2013 (tentative) Mac Pro update
Q3 2013 (tentative) iOS 6.2
Does that give competitors a leg up on them, genuinely? What does Apple gain from being secretive? Is it just status quo thought at this point that is keeping companies thinking secretively? I understand new products being a surprise, that's kind of cool, but does it hurt Apple to be a bit more open? Is there some competitive advantage I'm missing?Say you're Dell. You see Apple is working on a Mac Pro update. Does that change your priorities at all, strategically? Does it matter to you? Now Apple working on a game-changer, that I understand, but a simple update? Why keep that secret? What do competitors gain from knowing every little detail of what Apple is up to?
I'm trying to figure out Steve's reasoning, since I'm not terribly versed in business, and this generally seems to be a business decision. It's especially epidemic in IT, where all of us are writing cool software, but nondisclosure prevents us from sharing with competitors except in special circumstances. So instead of advancing the state of the art, we're all reinventing the wheel because our prior wheel inventions are nondisclosured to the prior company.
I just don't get secrecy.
It's not just Apple I've noticed this with. Maybe it's time we rethink secrecy from a product development standpoint? Does it really give your competitors an advantage to know what you're working on in the days of the Internet? Is this something that business types have put thought into, since secrecy seems to be the status quo?
I can understand new products entirely, but a simple update to their Mac Pro is something they could just say, publicly, with little recourse, to reassure its small (and dedicated) fan base.
The firm fixed bid for the 96-mile (154 km) Evacuated Tube Transport (ETT) system was $253M, this was less than one tenth of the cost of the bid by Global Rail Consortium to build electrified double track High Speed Rail for $2.6B. The bid by et3 contained letters of support by three entities in China to supply IP and key materials for the project. The engineering consultants hired by the authority did not dispute the validity of the et3 bid price or ETT technology, but recommended to eliminate the et3 bid from consideration for other reasons.[1]
This comment doesn't pass judgment on whether Daryl Oster is a patent troll or not, but that's also a discussion worth having.
I have a hard time resolving litigation like this with the fact that the truth can change in minutes, as Web sites are fairly easy to edit. It's just scary.
Now step back and read this comment, as well as your PowerShell response below, then rethink why I'd say that.
When someone uses the word "fiat" in casual conversation with me (without meaning the make of vehicle) I reply, "oh, a Bitcoin fan, eh?"
This community is overcorrecting in a bad way and starting to identify sexism where it isn't. Usually, women don't correct this assumption. Please keep doing so. I hate that the definition of the word "sexist" is starting to evolve to mean "offensive".
Also, I like to think of myself as intellectually inclined, and I simply hate discussing and arguing minutia like this. It just doesn't matter, and my time is limited. I don't want to argue with you on what Dickens meant by a certain character's dialogue in David Copperfield, I'd just like to enjoy it as a great novel. (That is fairly specific, and there are instances where it's fun to think about, but in general it isn't.)
> Clearly you don't care about that topic, so that acknowledgement shouldn't cost you too much ego.
Not about my ego, oddly (most everything else is, but this isn't). It undermines the opinion or discussion at hand from everybody else's perspective, however subtly. It's an annoying opportunity to show off, as you say, like those people that get up at conferences and ask a question that shows off at the expense of everyone listening. Both are distractions from the topic and are a detriment to the conversation, regardless of their original purpose.
This pedantry really frustrates me, and it extends beyond Hacker News. It's pervasive in conversations I've been having recently as well, as if we're all looking for the slightest thing wrong with what someone has said so that we can achieve some kind of acclaim by pointing it out. I made a point recently about how people need to work together and cited a Star Trek film as a joke, and some jackass in the group decided to go to the mat with me on the fact that I had cited the wrong Star Trek film (my quote was in III, not II).
There is nothing more frustrating than a pedant. It seems like it's tech people that do it most, too, which makes sense, but still.
That isn't to say this doesn't happen now, just that it's only going to get better.
Thank you for the kind words.
I genuinely and honestly cannot log into your Gandi account and fix your nameserver delegation, so that means I'm just here to shit on things? That's a logical leap for you? You are delegating xip.io to a nameserver that is refusing queries for your zone; that's seriously broken and can result in resolution failures, making your clever hack worthless.
I don't know why I bother providing feedback, since people from your school of thought (I'm looking at the 37signals community as a whole, here, which you're being a shining steward of) just get defensive and take your software being broken personally. You wrote a poor DNS server. Read the spec, study BIND's or NSD's source to understand the years of work that went into this before you, and understand the problems I've pointed out. I just get annoyed when people flagrantly misimplement DNS, because that starts trends, like Heroku suggesting for a long time that you use a CNAME for @ (don't do that).
I'm not making this up: http://i.imgur.com/zFNkV.png