7 ms·
Beware: from what I understood, this isn't a self-sufficient MUA in traditional sense, it's a thin client that offloads the interaction with the actual mail ser
by drdaeman 11y ago
Beware: from what I understood, this isn't a self-sufficient MUA in traditional sense, it's a thin client that offloads the interaction with the actual mail server to a remote system. That said, the credentials to access the mailbox are entrusted to a third party.
> See the README for full instructions on setting up the sync engine, API, and N1 on your local machine.
Sadly, there is no instructions in the linked document yet.
I wonder, can the sync engine and whatever else be bundled with a client, so it'd be a self-sufficient standalone piece of software?
- e0m 11y agoCheck out https://github.com/nylas/N1/blob/master/CONTRIBUTING.md https://github.com/nylas/N1/blob/master/CONTRIBUTING.md We've added (and are continuing to add) more documentation about how to get the open source sync engine setup.
- kstenerud 11y agoActually, I kind of like this. It means I can run a dockerized backend that will keep a copy of all my email from various servers and present it uniformly to any N1 client I happen to be using. Existing email protocols aren't nearly that flexible.
- grinich 11y agoHere's what you need to install to run the entire stack locally: https://github.com/nylas/sync-engine https://github.com/nylas/sync-engine Sorry-- launch day craziness :) More docs to follow soon!
- StavrosK 11y agoWhy do I need to run a whole stack for a mail client? It's a mail client! Why is everything JS web services :(
- webXL 11y agoYou don't have to do anything. Relax. Any open source project leverages other open source projects. How is this "stack" any different?
- StavrosK 11y agoBecause it's a mail client, and it needs a server that will talk to my SMTP server and the mail client. Which means that I either need to give all my most private and important data (my emails) to this service, or I need to set it up locally. For a mail client.
- chris_wot 11y agoNot sure I see the point you are making. Why the concern it's running a server if it is running locally? You already give your email data to another server, and even if you run your own mail server, then what's the issue with running another server yourself?
- StavrosK 11y agoI don't want to have to keep my computer on and connected to the internet 24/7 for something my mail client does anyway. I don't see why someone would architect a mail client like this.
- chris_wot 11y agoI can't see why you would need to run your computer all the time. Why do you think this is necessary? You just turn on your computer and the sync service restarts where it left off. Just like Thunderbird, or any other MUA. But I can see plenty of reasons the design was chosen. If you are bringing in lots of mail accounts, having it running as a daemon isn't necessarily a bad way to go. A sync program doesn't need to be associated with a tty, is better off run in the background in its own process, is arguably more extensible in design terms, doesn't necessarily take up any more memory than a regular executable, allows for multiple UIs (e.g. terminal program, Gtk+ GUI, WxWindows GUI), seperates processing from the UI, lots and lots of reasons. Maybe the developers can step in here with a response? You can make a UI to turn off the service or use the command prompt, if that's the concern. If you can give me a valid technical reason running the sync part of the program as a daemon is bad, I'm definitely all ears though.
- jordigh 11y agoYeah, if you want a free, modern, encrypted, web-based MUA, Mailpile looks like the right choice: https://www.mailpile.is/ https://www.mailpile.is/