eaigner

Markdown is a client feature. We send markdown as text and converted as html. If you look at the API there are just text and html fields http://developer.nvlope.com/v1/mail/send/

Yes, we run the mail and api servers ourselves.

Yes, but we run our own servers.

I guess I didnt phrase this very well, with IMAP i mean cloud imap services.

the problem is that it is very complex, and features are not implemented consistently accross clients. Especially the newer, or not standardized ones you listed. You know that there is something wrong when an entire slew of RFCs can be replaced with a few simple api calls.

Well, could you add instant messaging functionality to IMAP? Can you manage multiple inboxes with one IMAP account? Can you do server side threading with IMAP? Can you manage attachments and messages separately with IMAP? Can you upload attachments NOT using base64 using SMTP/IMAP? Can you use labels with IMAP? Can you manage multiple domains under IMAP? etc.

As for iOS client's there are exactly 3 that come to mind. Gmail, Apple Mail and Sparrow (discontinued).

We realize that this product is not for everyone - but for those who want a zero config, hassle free product.

Mailpile is for an entirely different audience.

Not sure if I completely understood your requirements, but you can add several custom domains (number depends on the plan) to your account, create mailboxes and aliases for them and can send and receive from those addresses as well.

Those are added to your account and can be accessed as individual mailboxes or via the unified inbox. They are not separate accounts with separate logins. Enterprise grade account management would be a feature to add at some point in the future.

Thanks for the tip

2-factor auth won't be available at beta launch (it's a MVP, we still have to see if there's enough interest), but we'll probably add 2-factor auth using https://www.authy.com at some point.

Yes, we should definitely change that. Thanks.

cli script anyone? you obviously dont have to love excel...

Bootstrap is just a bad excuse for no design/js skills. Its JS codebase is an abomination, as well as it's overly verbose CSS. It's only good for quick-and-dirty projects and has nothing to do with a well crafted site.

If I were Google, I'd charge them processing fees...

Quick fix: https://github.com/eaigner/hood/commit/85948f72646e6703af09e...

As for now, you have to specify the complete where clause

    hd.Where("name = ? AND category = ?", name, category)

fixed: https://github.com/eaigner/hood/commit/7e7742dfd1aff966c6745...

Matching the json-tag style will probably be the best bet (using commas, e.g. `sql:"size(128),default('abc')"`)

That's a valid issue, definitely want to conform with Go standards and don't break anything. Like the "sql:" proposal very much, will change it to that!

schema creation is completely optional, you don't have to use it.

What's the difference to the "clientKey" of Parse's SDK? The requests should be served over SSL anyway, so if your point is you don't want to distribute a key you got the same problem with Parse. You can obfuscate the key though.

You don't need to implement APIs anymore. You can use the DataKit classes to interact with the web/db backend.

I originally planned it as a commercial project, but then decided to open source it. Let's see if that was a good idea and people actually need it.