Ouch. We're just a few hackers trying to fix broken developer tools.
Any claim is just a claim, for sure. We know that it's a long road to earn trust of other developers. One of the (many) reasons we made the sync engine open source was so that developers could run it on their own metal without trusting us. Transparency is really important to us.
This is just the beta announcement of our API. I'd love to hear any comments you have on what guaranteed level of support+performance you would need for a hosted product. We're working on a hosted version now (so you don't have to run it yourself), and developer happiness is the #1 priority.
And we (gwillen and anyone who agrees with his comment, myself included) are just a few hackers who are tired of having the rug pulled under their feet when $CORP inevitably comes with the big bucks and all claims made by the founders in the early days of the company mysteriously disappear from the homepage.
Talk is cheap.
https://github.com/inboxapp/inbox
But yeah, I totally understand the lousy feeling of being burned when $STARTUP gets acquired or shut down.
Wish I could say more to quell your concerns. We're just going to keep working on this every day to earn respect from developers. We don't take it lightly.
/edit
Even if they were bought out the code would still be available and someone else could provide the service and continue development. Releasing the code seems like the best guarantee possible.
This may be part of your problem. The way I see it, IMAP and POP suckage is not a developer problem; it's a user problem. As in, users don't care that IMAP and POP suck; they only care that their email works. Most people's email works.
In other words, you can make developers as happy as clams and it won't matter, because "making developers happy" is not a sustainable business model. (Particularly if the way you are going to make them happy is to open source your toolkit and give it away for free. Not that that isn't a great thing to do: it's just not a sustainable business model.) I think a lot of the skepticism in this thread is because on some level everyone realizes this, even thought it's kind of an unpleasant truth for developers.
A sustainable business model would be: you're going to (a) convince users that, even if their email works now, it will work so much better with your new platform that they'll be amazed; and then (b) get the users to pay for that awesome service. I have seen nothing that indicates you have such a business model. Without it, I have to agree with the skeptics that, from a VC's perspective, you are far more likely to exit as an acquisition than as an IPO. Which means the VCs aren't really investing in your business, they're investing in your talent; that's what they're betting that some large company will be willing to pay for down the road, once you've demonstrated the ability to build something. But once you're acquired, you might end up building something completely different from "a better email".
Makes the existing user base much less valuable to possible buyers though :)
But if you do see it, please check my reply to dang's comment for a thought on why I'm so angry about this.
Your comment is needlessly mean-spirited. The top-voted comment on the recent Show HN thread would seem to apply here: https://news.ycombinator.com/item?id=7984826
Why is it so wrong to criticize a bad idea? To do so bluntly?
The "effect that it had" was an honest conversation. Ultimately I find HN's policies an embarrassment and a symptom of dishonesty. Way I see it, you were brought on to make moderation more transparent, and you're doing well, but you weren't actually given powers to attack HN's main problem, which I'd define as a discomfort with disagreement.
And maybe that's a human problem. But we live in a very negative time. Outright hatred is a part of life, and tools of hatred (downvoting, shadowbanning) are hypocritically applied to shut hatred down.
But it doesn't shut it down, and it shouldn't. To say "You shouldn't feel this way" is fair game when applied as an argument between people. What you say when you banish shit is "You shouldn't exist," and that's an unsustainable mindset.
You can see the logs. You can probably see that I'm a serial offender when it comes to pissing people off here. I've got yet another account on your bad list because you think you can control discomfort.
But you don't have a modicum of transparency or honesty in your line of work, dang: there's nothing you can point to that explains why my downvoted comments are both at -4 as some minimum, but the css makes them different shades of grey.
That's really trivial shit to care about, but that's my point: you're not taking care of trivial explanation of policy. You're an improvement, but that doesn't mean you're done.
But I'm so sick of startups just being R&D for corporations and screwing over their userbase once they get acquired. Or even worse is companies that only get off of the ground because of user support via kickstarter or similar fund raising platforms and then get acquired.
Of course it would be much harder for those companies to raise funds but there's always bootstrapping. It'd be a big win for the consumers of the product and if marketed correctly (something like "Non-Acquirable LLC"), it could become a good way for a startup to show that they put their users first.
Having clauses with each investor that let you purchase back your shares from them at predetermined times and rates (returns would need to be healthy for them) limits their upside, but lets you buy back control whenever. - assuming you can afford it
for public companies in the US, also see "Poison pill":
http://en.wikipedia.org/wiki/Shareholder_rights_plan
http://blogs.wsj.com/moneybeat/2014/06/30/dealpolitik-poison...
I was involved in setting one up at university (http://www.srcf.ucam.org/) and it's still running long past the time I had anything to do with it. I believe it's a good model for "community" internet services, by definition run in the interests of the users.
It's not impossible for one to sell out, but it requires the members (customers) to vote for it. In the case of the UK building societies, by bribing them with the capital reserves that were turned out to be essential to keeping the mortgage system running.
You'd hope there'd be a lesson in there somewhere - short term gain versus long term stability.
Take it down a few notches, you're solution will likely not work.
This is the company's only product. If the product gets discontinued, the company is likely broke. The "significant monetary penalties" is unenforceable because the company will not have any money to fulfill the SLA penalty.
Or has just been acquired, which I think is more what the parent was getting at.
>The "significant monetary penalties" is unenforceable because the company will not have any money to fulfill the SLA penalty.
The acquirer would, though!
Not like they can't shutdown their company irrespective of any promises.
They will gladly shut the service down once someone offers them enough money in aqui-hire.
It's a bummer this is the status quo with startups. To me, it's the most disappointing thing about the tech world. I actually interviewed at other companies first, and only cofounded Inbox when I couldn't find anywhere else to solve this problem.Probably the only convincing thing I can say is that if you wanted to build a company to flip quickly, an email infrastructure startup is certainly the most painful, masochistic way you could go about it. We spent the better part of last year reading RFCs and fixing tons of obscure bugs to get this far.
Really, I'm more uncomfortable with a link to a webcomic joke as an argument point...
The 'shut up' detracts from the comment. Being a jerk is bad.
But being confrontational is in this case a benefit. The first line is "Your claim that your product will not be discontinued is worthless." This is confrontational in a good way, and this line is not being a jerk. It's pointing out a serious flaw without attacking anyone.
Something like, "How will you back up your claim of the product not being discontinued?" or "What will prevent your product from being discontinued?" Gets the same point across without coming off rude (it may just be me but saying "your claim ... is worthless" seems rude.) The OP of the comment definitely has a good point but it's said in a way that isn't constructive.
Whatever it is, it's worthless.
You seriously don't think you called him a fuckwad?
You are just as rude as the activity you're calling out. That's all I'm trying to say.
Please don't be aggressive like this on Hacker News. It violates the guidelines and degrades the discourse.
That sentence has no information in it—it's just rude—so the comment would be better without it.
(Because of HN's lack of comment notification system, I had no idea it was so controversial until I happened upon it again just now.)
Its significantly positive score does suggest to me, though, that there is a lot of sympathy for my position, and the angry way I stated it. In fact, it's one of my most upvoted comments. (And assuming it's received a significant number of downvotes for being unnecessarily rude, I suspect it's my most-upvoted comment of all time, in gross numbers.)
The claim that I'm complaining about is basically outright fraud, as far as I'm concerned -- they're advertising their startup as being different from other services, on the basis of having a quality they have absolutely no ability to promise (that of being guaranteed not to terminate service out from under the users without warning.) The only mitigating factor is that they are almost certainly misleading themselves as much as their users. Whether this is noble, I leave as an exercise for the reader.
In some contexts, rough-and-tumble language is just fine and makes things more vigorous. Empirically, HN isn't one of those. Its system is too fragile. So if we want any high-quality discourse, we have to protect it. It's not an ethical injunction so much as a practical tradeoff.
I think the comment created worthwhile conversation. And I'm not sure it would be better off without it. Obviously you can disagree, and given your position perhaps my opinion doesn't really matter, but to say it has no information is just being dishonest, and I say that in the nicest way possible.
I see two conversations here. One is about users feeling betrayed by acquisitions and whether that could be mitigated contractually. That conversation didn't require abusiveness to be created. The other conversation is about who is being a fuckwad, and hardly counts as "worthwhile". Unfortunately, it is what such rudeness leads to, and it only gets worse.
Keep in mind that we're not talking about rudeness in general. We're talking about its effect on the already precarious balance of a particular optionally-anonymous internet forum. The argument here isn't ethical so much as empirical.
'unexpectedly' is the key. Giving people 3-6 months of runway to say "we're shutting down on day X" is still living up to that statement.
If you're so sure of that, put your money where your mouth is, and offer an SLA with a contractual minimum duration you promise to keep the service up, and significant monetary penalties if you fail to meet it.
Doesn't sound like a good idea? Then shut up.