This update introduces the new feature multi-communities. A multi-community is a user defined community made up of other communities. This allows users to group similar communities together (eg. group [email protected] with [email protected]).

This update also polishes the app even further.

Changes so far:

• Added support for multi-communities
• Added setting to disable auto-linking phone numbers
• Changed the behavior of tapping an image in the card and large list layout. Tapping an image of a link post will no longer expand the image, instead it will open the link.
• Changed the UI for card/large list layout. Indicate when an image will open in the browser.
• Handle more network/server errors.
• Fixed a UI bug with the comment editor when the keyboard is expanded.

Update

Update is almost ready. Probably doing a beta release tonight and doing a release tomorrow morning if everything looks good.

Multi-communities has a lot of edge cases so testing them all has been annoying. I’m getting close to working them out though. Funny enough the UI was more time consuming here than the actual logic for client sided communities. There’s a lot of UI involved like having UI to search communities, adding and removing communities and UI to select the icon for the multi-community.

Update 2

Everything looks good. I’m fine tuning some configurations for multi-community to improve performance and releasing it as v1.4.2. It should be live to everyone in a couple of hours. Since multi-community is purely client sided, performance isn’t super great when it comes to fetching posts from the server and it will degrade further based on the number of communities within the multi-community.

I had an idea mid writing this update to improve performance and it actually works great. New version will be v1.4.3 instead. Just don’t add like over 20 communities to a multi-community as a rule of thumb. Try to keap it between 5 - 10 guys. Thanks! (I will add a limit to the number of communities now that I think about it).

Update 3

Found another bug. v1.4.4 here we come.