4 ms·

Is the "open source" label still comically misleading? [0] I tried it out, didn't read the fine print, filed an issue, never looked at it again. Because "It k

by wink 10y ago

Is the "open source" label still comically misleading? [0] I tried it out, didn't read the fine print, filed an issue, never looked at it again. Because "It keeps user data local and private." is kind of one of the main benefits. [0]: https://github.com/nylas/nylas-mail/issues/860 https://github.com/nylas/nylas-mail/issues/860

bengotow 10y ago
Ahh thanks I need to update that! Originally Nylas Mail was OSS, but tied to the Nylas Cloud APIs (which did the actual mail processing.) The cloud strategy was too expensive, and in version 2.0 the entire mail-sync system was moved into the client and open sourced. (https://github.com/nylas/nylas-mail/tree/master/packages/client-sync https://github.com/nylas/nylas-mail/tree/master/packages/cli...). It's now much more like Thunderbird. There's a bit of cloud processing for snoozing / send later, etc., but it no longer syncs all your email through the cloud.
- Ao7bei3s 10y ago
  Is there a way to configure it so it makes zero requests to your servers? If not (yet), would it at least be technically feasible, and would supporting this be an option for you?
  - grinich 10y ago
    Definitely feasible but it's not our product focus right now. Most of the features that help differentiate Nylas Mail require some cloud component. (snoozing, send later, reminders, open tracking, etc.) We totally encourage folks to fork the project and take it in whatever direction they want. If you want to chat with other devs in the community, you should join our Slack room: http://slack-invite.nylas.com/ http://slack-invite.nylas.com/ (I work at Nylas)
    - problems 10y ago
      > (snoozing, send later, reminders, open tracking, etc.) None of that has any appeal to me, I'd much rather a mail system which doesn't require using someone else's server. Maybe this isn't a priority for other people, but just putting it out there. This is what's making me not use Nylas today.
      - atonse 10y ago
        He's already given you a good alternative – fork and collaborate with other devs on a version that doesn't touch their server. Seems sufficient.
        hutzlibu 10y ago
        I would consider forking a last option, instead of "a good alternative". A good alternative in my opinion would be just to make some parts optional. Does not sound too hard, to implement (if the codebase is well done)
        deleted 10y ago
        [deleted]
- fps 10y ago
  I remember the last time I looked at Nylas, it was a fancy gmail frontend. Now it appears to require a "Nylas ID" which is not something I need. I don't want my mail being synced to someone else's computer. Where's the "host your own sync system" package?

by wink 10y ago

bengotow 10y ago

Ahh thanks I need to update that! Originally Nylas Mail was OSS, but tied to the Nylas Cloud APIs (which did the actual mail processing.) The cloud strategy was too expensive, and in version 2.0 the entire mail-sync system was moved into the client and open sourced. (https://github.com/nylas/nylas-mail/tree/master/packages/client-sync https://github.com/nylas/nylas-mail/tree/master/packages/cli...). It's now much more like Thunderbird. There's a bit of cloud processing for snoozing / send later, etc., but it no longer syncs all your email through the cloud.

Ao7bei3s 10y ago
Is there a way to configure it so it makes zero requests to your servers? If not (yet), would it at least be technically feasible, and would supporting this be an option for you?
- grinich 10y ago
  Definitely feasible but it's not our product focus right now. Most of the features that help differentiate Nylas Mail require some cloud component. (snoozing, send later, reminders, open tracking, etc.) We totally encourage folks to fork the project and take it in whatever direction they want. If you want to chat with other devs in the community, you should join our Slack room: http://slack-invite.nylas.com/ http://slack-invite.nylas.com/ (I work at Nylas)
  - problems 10y ago
    > (snoozing, send later, reminders, open tracking, etc.) None of that has any appeal to me, I'd much rather a mail system which doesn't require using someone else's server. Maybe this isn't a priority for other people, but just putting it out there. This is what's making me not use Nylas today.
    - atonse 10y ago
      He's already given you a good alternative – fork and collaborate with other devs on a version that doesn't touch their server. Seems sufficient.
      - hutzlibu 10y ago
        I would consider forking a last option, instead of "a good alternative". A good alternative in my opinion would be just to make some parts optional. Does not sound too hard, to implement (if the codebase is well done)
        deleted 10y ago
        [deleted]
fps 10y ago
I remember the last time I looked at Nylas, it was a fancy gmail frontend. Now it appears to require a "Nylas ID" which is not something I need. I don't want my mail being synced to someone else's computer. Where's the "host your own sync system" package?