![]() ![]() That means we at Nylas won’t continue contributing to or maintaining the open source code on which the program is built. What this announcement means is that the current version of Nylas Mail is the last one we will sponsor as a company. If you’re interested in Nylas Mail as a user, you will still be able to download Nylas Mail and create a new account. This means that if you download and run Nylas Mail from GitHub, you no longer need to login to a Nylas ID and your mail credentials are not sent to the cloud. We’re also re-licensing Nylas Mail under the MIT License, allowing people to use and remix the source code without worrying about complex license terms, and we’re unlinking the project from our private infrastructure. The full Nylas Mail repository is on Github at. With that in mind, beginning today we’re open-sourcing the remaining components of Nylas Mail and sunsetting further Nylas-sponsored development of the email client. The entire team has done a fantastic job, growth has continued, and it’s become clear that Nylas must focus all its energy on a single opportunity. This spring, as the API business grew, we had to tap the Nylas Mail engineering team to work on API developer experience and infrastructure. In the last few years, the Nylas API has exploded-we now sync terabytes of messages every day across hundreds of thousands of mailboxes for our API customers. Since then, it’s been energizing to see the community rally around the project, file issues, submit pull requests, and build dozens of plugins and themes. It began as an experiment to see what the mail client of the future might look like given the work we’d done on our APIs to make email easier for developers to work with. When we announced Nylas Mail (then Nylas N1) back in May 2015, we had no idea what the response would be. Will see what’s going on there as well.The year 2017 has been an exciting one at Nylas and we’d like to update you on the future of Nylas Mail. I think the fancy unread count on the dock icon is still a work-in-progress, though we should support the Unity dock badge. I think it must be doing some sort of on-the-fly unpacking or setup? I’ll look into that tray icon issue-we definitely need that resolved. (Would actually be curious to know what the plan is for that…) I’ve also noticed that the app is suuuper slow to launch, especially the first time it’s run. We’ll probably need to add a post-installation note about any libraries you need to have installed for them to / - I think the system theme is something they’re working on in snapd. The app.asar file essentially “links” out to them in the unpacked - I’ll look into the desktop notifications. asar file because they need to be accessible to the external filesystem. The directory contains files we can’t include in the. Hey folks! Thanks for the feedback - this is really - yep, both of those are required. ![]() It just syncs snooze dates and other metadata using the Mailspring ID, since those features can’t be built on IMAP alone. Note that in order to use Mailspring you’ll need to create a “Mailspring ID”, but the app doesn’t send your email passwords or credentials to the cloud-all email sync is done locally on your computer. I’m really excited to be moving to snapcraft because it means Linux folks are finally getting autoupdate alongside our Mac and Windows users. We’ll be directing folks to the snap release instead of the dep / rpm packages in the next update cycle providing everything goes well. If anyone has some spare cycles and is interested in trying a new mail client (or already using Mailspring!) grab the snap and give it a spin via snap install mailspring! If you run into any issues, please post them here. Over the last few weeks we’ve been putting together a snap release and working through a few configuration and sandboxing issues (couldn’t make ourselves the default client anymore, etc.) Now that snapd 2.29.3 is out, the last known issue has been fixed! ![]() Hey folks! I’m the lead maintainer of the Mailspring email client (formerly Nylas Mail). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |