I guess Mailpile isn't trying to be commercial, so perhaps it will keep soldiering on the power of donations for as long as that keeps up.
I guess Mailpile isn't trying to be commercial, so perhaps it will keep soldiering on the power of donations for as long as that keeps up.
We've structured our business to... actually have a business. Our team spent the first year selling APIs to developers [1] which already power lots of paid apps. The N1 mail app we released two months ago[2] follows this and will have paid features next year.
Plus both are open source free software, and quite popular on GitHub. [3]
What is Nylas? The website doesn't seem to be written for me, but for PHBs. Apparently you have great business, design, and APIs, but what is it that those things do? Are you an email client? A server? A webmail service?
What makes you different from Gmail or from Mailpile?
1. APIs for developers that replace IMAP/SMTP/Exchange. Use this to build any app that integrates with a user's mailbox, calendar, or address book.
2. A new extensible email app, built on web technologies (Chromium+NodeJS). This is called N1 and was released about 2 months ago.
We sell the APIs as an infrastructure business (like AWS).
I think certain enterprise-y email solutions have this, but there's no way to have that happen in the distributed email ecosystem unless all your messages were just links to a website that could delete the content centrally, or similarly, jpg's of rendered text that were somehow forced to be remotely fetched each time.
I know I had a former boss that loved to try using the outlook "unsend the stupid thing i sent" feature.
Little did he know the cients could turn that bit of functionality off. He hated when we replied to the emails he had "purged".
other than that, i don't think receivers like the idea that others can control what's in their inbox.
I went to the "releases" tab on GitHub and it looks like the last one was in 2014. I see things in the GitHub repo that suggest there are Dockerfiles and Debian packages, but I don't see an actual Debian package repository or an entry on the Docker Hub. Is the recommended way to use it today just cloning the git repo? Or is there a stable release of the sync server that's tested/known to work with the binaries of the client?
We don't have "releases" because we are constantly releasing to production. Check out the `production` branch on GitHub for what we're running right now. Usually it's just a handful of hours behind master (at most).