Charter - A Swift mailing list client for iPhone and iPad

• Localisation files for Portuguese and Spanish
• Localized possible xibs
• String localisation with constants through Localizable.swift % Corrected NoThreadsTableViewCell xib to support bigger strings: constraining labels to leading and trailing instead of centring X and giving it max width @matthewpalmer Issue #36

People often put [Idea] and [Review] and stuff in the subject line for their messages. It'd be cool to turn these into coloured labels (c/f github issue labels) on the message, and maybe eventually search for them

In case someone opened this repository not on mobile, Apple's download banner doesn't help much. Added QR code and moved CI build status to the top of the Readme.

Hi. swift-build-dev is quite useful to track especially when you're interested in Swift Package Manager development. This pull requests adds support for this mailing list both in client and backend code. Cheers.

Hi, I'm sorry to bother but I took the liberty to localize your app to Portuguese and Spanish. My problem is that I created a branch for it, directly from your repository instead of forking first. Only noticed it when was pushing the commit.

Are you interested in localizing it as you say in the Readme? If so, any advice on how to handle it now or should I just create the PR?

Often when reading you come across an awkward newline... I wonder if we can do something like if char == '\n' and column == 80 (I think they get wrapped at 80?) then strip the newline otherwise use the newline.

• [x] think about whether the data sources to the various view controllers should be turned into protocols and injected (at this stage, I'm thinking yes, but it's maybe a little tricky because of the view lifecycle)
• [x] unit tests for thread detail data source
• [x] add tests for formatContent on the EmailFormatter class
• [x] remove various retain cycles that I've introduced
• [x] go through TODOs littered throughout the codebase and open issues or fix

Add a backend for faster list refresh

• [x] add mail listener
• [x] parse emails
• [x] present emails as REST API
• [x] auth for REST API
• [x] ~~partition emails into threads if they have no references or in-reply-to. also handle the Dave Abrahams case where he doesn't set in-reply-to~~. Hmm... not sure what to do here yet, but definitely need to be better at handling this so that we get proper threading all the time. Also, provide a /threads endpoint for a list that just has the root emails for each thread

New feature

• [x] add archive URL so we can link to the posts on the swift lists website

Current thinking for the archive URL approach:

Compute a new message's archive URL from the previous message in the db. Every x minutes check that the most recent document's archive URL matches the page it points to. If it matches, we're ok, and continue. If it does not match, find the message that the page references, set the archive URL for that page, and then recompute all archive URLs for messages that come after that message (by date).

This won't ensure 100% accuracy, but bounds inaccuracy within hour-long periods and minimises the number of requests we have to make against the server

• [x] Add tests for backend
• [x] Clean up logging
• [x] ~~Clean up db instantiation~~
• [x] Open source the backend (open sourcing might take a little while to get all the config stuff set up... also, #7 ?)

One of the things I noticed when watching @orta’s tvOS app code review video was how helpful it was to have a storyboard to look at when first seeing the codebase. I want new contributors to this app to be able to get a quick overview of the app flow, and a storyboard is the best way to do that. While it might not be 100% the best technical choice, the value it'll add to the community is too much to ignore.

I use Charter quite often these days to stay informed about Swift's evolution (thanks for making the app, by the way!)

One thing I find tedious is navigating within a thread. I often want to get a feel for the general opinion on a specific subject instead of reading everyone's whole argument in detail.

This pull request adds previous/next arrows to the ThreadDetailViewController navigation bar to jump instantly between replies instead of having to scroll manually through long messages and threads.

• Load thread items automatically the first time a thread is loaded. I'd figure it be nice to not have to pull to refresh as soon as you open up a thread.
• On the mailing lists table view, don't show cell separators for empty cells.
• On threads table views, show cell separators when datasource is not empty.

Let me know what you think.

Cheers!

It seems the app doesn't display any message that was sent after June 8th.

I tried uninstalling the reinstalling the app but the issue didn't go away. Maybe there's something wrong with the app's backend?

This won't be ready for a while.

Need to figure out precisely what a star means:

• appears at the top of the threads list?
• receive push notifications?
• adds visual identifier next to message?
• more like a "read later" thing? can you view a list of all starred convos? do we need user accounts?
• do we have star counts for all convos? can people order threads by number of stars?