Live data from Hacker News

Mailpile Alpha Release: Shipping Bits and Atoms

mailpile.is

41–47 of 47 posts

Re: Mailpile Alpha Release: Shipping Bits and Atoms

#41

I have been looking forward to this. Of course there are a lot of features missing, but the overall feel of the application is, so far, pretty nice. It's U.I is very nice. Man, I can't wait for the final release.

Glad ya like what we are doing, thanks :)

Re: Mailpile Alpha Release: Shipping Bits and Atoms

#42
post #25

Gratulations on shipping the alpha. Installing now and trying to get Offlineimap running with Yahoo/Outlook. Any pointers?

No exact pointers, as none of us are Yahoo / Out look users- we'll happily add any quirks you discover to our wiki https://github.com/pagekite/Mailpile/wiki/Getting-started

Re: Mailpile Alpha Release: Shipping Bits and Atoms

#43
post #8

Great news. Glad to see my donation being put to good use. I last installed this back when it first got some traction but interface wise there was almost nothing there. Even still it was showing good promise with what it could do. Seeing it now it's evident that a lot of work has been going on. Kudos to the team, their dedication really shows.

Really glad we seem to be delivering and making so many of our backers happy- thanks for your support :)

Re: Mailpile Alpha Release: Shipping Bits and Atoms

#44

thanks. i've been watching it for a while but, i always thought the main hell of personal email setups is that you have to deal with postfix or exim. which is why atmail was so great. milepile doesn't help me with that does it? http://atmail.com/products/

Mailpile does not help deal with postfix or exim. We have various plans to make the whole "email" pipeline easier + secure + cooler down the line!

Re: Mailpile Alpha Release: Shipping Bits and Atoms

#45
post #18

saw the talk at fosdem yesterday. would be happier if they would have tried to be just a mail user agent instead of their vision of being everything at once. Well but maybe hte unix philosophy of doing one thing really well really is dead

Please point me to a copy of this "Unix philosphy" you speak of.

You can't, because there isn't one.

If you were at the talk yesterday, like I was, and actually listened to what they said they explained why they chose to do things.

That was the actual point of the of the talk. Plus they want additional helps (fosdem being a developer conference).

They explained their use of own indexing system (was an experiment, is .onion address so you communicate with having to register with any service but still speak with people on gmail), why they are thinking of including an SMTP server (it means that you can directly get mail routed to you, via your .onion address; and your communications metadata is far harder to get to)

Re: Mailpile Alpha Release: Shipping Bits and Atoms

#46
post #33

I’m curious how the search engine is going to scale. Every time things like that are reinvented instead of using something that already exists, like, say, ElasticSearch, I will be skeptical. Then I looked at the implementation, and it begins with "take all the message-ids you know… then do a bunch of set intersects on it". Um, seriously? Do you have some stats on runtime behavior with, say, 250k messages?

Brennan here from the team. Yes, one can ask that question "Why not use [INSERT SEARCH / DATASTORE]" the answer is a quirky story about the birth of a neat software project, if you're curious check out our blog, site, videos, etc... Re: performance here is our current stats https://github.com/pagekite/Mailpile/wiki/Mailpile%27s-Perfo...

Re: Mailpile Alpha Release: Shipping Bits and Atoms

#47
post #24

Why no HSTS? Or Content-Security-Policy?

Smári here, from the Mailpile team. There's no HSTS because Mailpile is generally supposed to be run on localhost. We don't bundle SSL certs because it simply wouldn't make sense. That said, we will be improving things w.r.t. use of SSL and Internet-facing installations before 1.0, including authentication mechanisms and such. We will also be doing some Content Security Policy work before 1.0.

It should run on SSL even if it is localhost. Self-signed cert/adding a personal CA is a valid config.

If you are proposing to be secure, I would think that you want to cover security (encryption in this case) for both in-flight and at-rest data in both local and internet facing configurations.

Post reply on HN