Live data from Hacker News

MIT And Dropbox Alums Launch Inbox, a Next-Generation Email Platform

techcrunch.com

241–250 of 280 posts

Re: MIT And Dropbox Alums Launch Inbox, a Next-Generation Email Platform

#241
Unless it's dramatically more secure than current email platforms, it's not the "next generation" of email.

Anything hosted in big shared data centres in the USA cannot be more secure. That's last year's thinking, not "next generation".

Re: MIT And Dropbox Alums Launch Inbox, a Next-Generation Email Platform

#242
post #226

Earlier quoted context omitted.

But _why_? Email does not seem RESTful to me. Not the slighest. Read an email and then flag it as unread? Save and delete instead of move? Batch operations that are not atomic? What happens when the connection breaks then? Synchronous command requests, really? IMAP solved that 20 years ago. Do we really want a glorified POP to replace it? What is the purpose?

What do you mean by "does not seem RESTful"? It's a set of data. Writing a webmail app should be more like any other CRUD app. I don't see why that damages atomicity. Nor do I see why synchronous command requests are a problem, this works fine for AJAX. Especially if you can issue more than one at once. Store the mail in MongoDB or similar (possibly detatching the bodies of large mail for storage convenience). Stop u…

The question is why you think a RESTful data model fits the problem. It is a model that fits when resources are published globally, when the CRUD methods are enough, whose purpose is to enable global caching and make hyperlinks possible.

Pretty much none of this is true for email. You don't even want global caching here. You want responsivity, and a rich and extensible data model.

How would you move an email? How would you control whitelisting? Spam scoring? Folder ACLs? How would you sleep until a mailbox changes? Even if you _could_ represent these things as resources, it's going to be much more hairy than IMAP with the performance of POP.

The evolution of email has been completely opposite of dumbing it down. Users expect calendaring and global contact lists, and here you have the impedance mismatch _again_. Look at the mess that is CalDAV, and that's DAV which is much richer then REST.

Regarding asynchronous commands, I don't know what you think it has to do with AJAX. It is the Javascript that is asynchronous in AJAX, not the HTTP requests. Web browsers typically implement it using multiple connections. This is a problem. Do you really want connection pooling (so a server can serve _fewer_ clients)? No, you want an evented protocol. Such as IMAP.

And again, you probably could do it given enough work and come close to the performance of IMAP for most end users, but why would you? It doesn't really map to the REST architecture.

It you would rewrite your comment but s/REST/RPC/ I would not object to it. I would just think you were from the past :).

Re: MIT And Dropbox Alums Launch Inbox, a Next-Generation Email Platform

#243
post #93

Earlier quoted context omitted.

FWIW, inboxapp is self-hosted and under AGPL, so it's forkable.

AGPL with Contributor License Agreement, just to be crystal clear.

Is this viral like the gpl? Does the use of the inbox backend, hosted by me, require release of the full source to the entire app that uses the inbox backend? My brief reading of the agpl seems to say yes. Which makes this an interesting toy but nothing more...

Re: MIT And Dropbox Alums Launch Inbox, a Next-Generation Email Platform

#244
post #231

Earlier quoted context omitted.

Well, I think everyone kind of breaks down with their "morals" or idealistic visions when presented with the word "billion". E.g. see Occulus Rift founder Palmer Lucey's posts on Reddit from years ago claiming he will never sell the company under any condition. But a quick offer with a billion was made and just like that Oculus was Facebook's.

You know what's cooler than a billion dollars? Tens of millions and being in charge of a company that improves lives for millions of people around the world in a way you'd love to keep heading up.

With puppies and kittens, and everyone has rainbow coloured cotton candy whenever they want.

Wake up. You don't get to do any of that when your board is stacked with VCs.

Re: MIT And Dropbox Alums Launch Inbox, a Next-Generation Email Platform

#246
post #243

Earlier quoted context omitted.

AGPL with Contributor License Agreement, just to be crystal clear.

Is this viral like the gpl? Does the use of the inbox backend, hosted by me, require release of the full source to the entire app that uses the inbox backend? My brief reading of the agpl seems to say yes. Which makes this an interesting toy but nothing more...

Yes, the AGPL does require the release of the source of any code built on components licensed under it. Chances are they'll have a commercial license, though my salary disputes your assertion that an AGPL base can only be used as a toy - we have contracts with some of the largest companies in my country.

Re: MIT And Dropbox Alums Launch Inbox, a Next-Generation Email Platform

#247

Earlier quoted context omitted.

While I can't think of a legal way to guarantee "not going away", you can legally guarantee a very strict privacy policy, good for 10 years counting from when the account was created. Future changes in privacy policy would not be able to cancel the 10 years promise, so any acquirer would be prevented from pushing ads. The acquirer could still kill the produce though.

You simply set aside money in an endowment fund (or other funding apparatus) and create a legal entity charged with the task of using the money in the fund to continue operations in the event the main company shuts down. Just add a clause in the legal framework of the organization which provides for the startup and handover operations, put individuals on a "board" of some sort who will begin drawing a salary when the…

I am confused. The fund is set up by the company itself right? So if things get so bad that the company has to shut down, BUT they have a fund big enough to keep running the company, why must they shut themselves down to tap into it? Why can't the original company simply use that money to keep operations running?

Re: MIT And Dropbox Alums Launch Inbox, a Next-Generation Email Platform

#248
post #181

Earlier quoted context omitted.

The name is Inbox App, not Inbox. Nothing special there. I'm willing to bet that they'll have significant problems with the name if they try to call it just "Inbox". First, they didn't even get the inbox.com domain, theirs is inboxapp.com. Second, they don't seem to have a trademark on the product name as "Inbox" and I doubt that they'd get one. Third, their company name is Inbox App, Inc., so it doesn't seem like th…

Interestingly inbox.com seems stuck in 2003.

Email is, too, so that makes sense.

Re: MIT And Dropbox Alums Launch Inbox, a Next-Generation Email Platform

#249
post #83
post #50

Earlier quoted context omitted.

(Michael from Inbox here.) 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 AP…

But if you believe in the claim, why not sign a contract that brings some validity to the claim?

They've release the code. That's contract enough for me.

Re: MIT And Dropbox Alums Launch Inbox, a Next-Generation Email Platform

#250
post #235

Earlier quoted context omitted.

Sorry, but I have to disagree. The sentence only has no information in it I'd you choose to blindly look at the words in a vacuum. But if you think about what he said, what he meant, the tone has a ton of information, the most obvious is a drop frustration of the empty promises and frequent shut downs that is all too common in recent startups. I think the comment created worthwhile conversation. And I'm not sure it w…

> I think the comment created worthwhile conversation. 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…

> That conversation didn't require abusiveness to be created.

How can you say that with any certainty? The only real example you have of this kind of conversation happened right here; which is to say, you have pretty strong evidence that the conversation did require abusiveness to be created.

You as a moderator are making value judgments on what should be discussed; you're not clearly specifying rules of engagement in general, and in this topic you've proven you couldn't enforce them even if you had them written down.

You know what referring to the conversation about who's the fuckwad does? It validates me, because I was one that made a point of being part of that conversation. It tells me that that conversation was, in fact, worthwhile: because it got your attention.

And now I'm posting with (what's essentially) my HN main, a shadowbanned account, because I'm pretty sure that you'll still see it. With the topic dying, with your post only a few hours old, I'm basically given a free private message to you. (You can also definitely track down who I really am now, but that doesn't really frighten me.)

So I can say: we're not really on a different page on the "already precarious balance" here. Despite my hatred for this community, I still care about it. (That's practically what hatred means!)

What I'm sure we disagree about is perhaps what's encapsulated by this topic. The two conversations you see are actually intimately connected, though perhaps it would be more accurate to say that they inform each other.

I think the Valley has a serious problem with positivity. You can't be negative in the networking world, and what that leads to is a culture where legitimate negative criticism is shut down. And that's where I fought today, and where you fought; the balance is that the negative criticism won the day. Which is why I say that your moderation is ultimately powerless.

I'm still here, writing to you. Even if for some programmatic reason you never read this, even if you've made an effort to not hear specific voices, I still exist.

And even outside my participation, the point was abusively made, because those forces make their point regardless of this chatter, and it might just be true that damage is the only real way of understanding and coming to terms with change.

If talking about who is a fuckwad isn't worthwhile, why does so much of your moderation involve finding fuckwads and terminating their participation?

This is a good conversation, solely because it happened. Because I can drag you into it no matter how elitist you're acting. (And I don't really think you're nearly as elitist as pg was; you've gone good clarifying work on title renaming, but you inherited a stupidly tough position.)

In fact, I suspect I'm writing this just to tell you how screwed you are.

Post reply on HN