Pachli
Pachli 2.0.0 released
Pachli 2.0.0 is now available, and can translate posts for you. This uses your server’s support for translation (if enabled by your server administrators).
Improving translation is the through-line for the Pachli 2.x release series. Future releases in the 2.x line will support translation whether or not it is enabled on your server by carrying out privacy-preserving translation on your device.
Read on for more details about this, and other changes in this release.
Governance model update
In the last governance update I mentioned starting the application process with the Nivenly Foundation.
As announced in their Updates for October and November blog post the Pachli application process is underway.
There are two Q&A discussions currently happening in their forums:
If you have questions please do come along and ask.
Supporting server translation
Edit: This feature is now also available in Pachli 2.0.0.
Pachli Current (on Google Play) now supports server-side translation of posts.
This means the translation does not happen on your device. Instead (and if your Mastodon provider is configured to support it) Pachli asks your Mastodon provider to translate the post, and they, in turn, typically contact a third-party translation service (often DeepL.com) to do the actual translation. Then a copy of the translation is sent back to Pachli.
This comes with a few caveats and additional details.
Pachli 1.4.0 released
Pachli 1.4.0 is now available.
Assuming things go to plan this will be the final release in the 1.x series. The 2.x series will be released soon, featuring support for translating posts.
The significant changes in this release are:
Pachli 1.3 released
Pachli 1.3 is now available.
This is the first release that includes changes from other contributors.
- Eryk Michalak updated the Polish translation
- sanao contributed two PRs (see below), and updated the Japanese translation
Thank you to both of them.
The significant changes in this release are:
Pachli Current
Pachli aims to put out a new major or minor release approximately once a month. But there’s a lot of code that can change in that time, and only so many problems that automated testing can catch.
The wide range of devices running Android, differences in supported hardware, and customisations made by different device vendors make this even more difficult. Code that runs with no problems on a developer’s device may fail or perform in unexpected ways on other devices.
Enter Pachli Current.
Pachli 1.2 released
Pachli 1.2 – and 1.2.1 and 1.2.2 – are now available.
This took a little longer to release than planned. 1.2 was submitted to the Google Play store last week, and was rejected because of an unspecified issue with the Pachli Privacy Policy.
This policy, and how it was displayed in the app, had not changed in the Pachli 1.0 or 1.1 releases, and the Google app review staff do not provide specifics about what needs to change.
Reading the tea leaves I made changes in 1.2.1 and 1.2.2, neither of which satisfied the reviewers.
What did work was changing the link to the privacy policy from https://github.com/pachli/pachli-android/blob/main/PRIVACY.md to https://pachli.app/privacy/.
As best as I can tell the reviewers think that using GitHub as the canonical location for the privacy policy makes it “editable”
The significant changes are:
Accessible fonts
To improve accessibility Pachli allows the user to change the font used in the UI.
The feature originated from work I was doing on the Tusky client. I had seen occasional user requests asking for different fonts, either to improve overall legibility, or specifically to assist people with dyslexia.
I put together a proof-of-concept using Atkinson Hyperlegible from the Braille Institute and OpenDyslexic as they are both freely available and claim to be helpful.
This allowed me to experiment with the UX and identify any issues that might make adopting this difficult.
This is not an accessibility issue I currently have to contend with, so I approached the user community for feedback and recommendations for additional fonts, asking:
Governance model update
When the project launched About Pachli described the goals for Pachli-the-association, and noted that:
At the time of writing it is undecided whether Pachli-the-association will exist as a separate entity, or whether those goals can be met under the wing of an organisation like the Software Freedom Conservancy, Software in the Public Interest, or the Nivenly Foundation.”
Read on for update on that process.
Pachli 1.1 released
Pachli 1.1 is now available.
This is a bug-fix release, with fixes including:
- Fix crash on entering MainActivity on tablets (#25)
- Ensure refreshing does not create a gap in the timeline (#43)
- Restore the user’s home timeline position (#44)
- Show the FAB according to the user’s preferences (#29)
- Fix toolbar flickering when scrolling lists (#26)
Download Pachli from Google Play or the GitHub release page (availability on F-Droid is dependant on the F-Droid volunteers approving merge request #13682).
Read on for more details about the changes in this release.
hello, #pachli
Pachli is an application (now) and an association (aspirational).
Pachli-the-application is a best-in-class open source Android application for Mastodon and Mastodon-like servers. If you’re familiar with Tusky then you’ll love Pachli.
Get Pachli on Google Play or F-Droid, carry on reading to learn more about the application, or head to the About page to see what we’re all about.