• Date: 2024-07-28
• Status: Possibly incomplete / inaccurate

The client's goal during the OAuth sequence is to obtain a long lived access_token that can be used to authenticate future requests.

• domain
• The domain the user wants to log in to, e.g., mastodon.social

This is a very rough list of things to do in Pachli. Some of these are already filed as issues that may have more information, others aren't because I'm trying not to overwhelm the issue list with work that might be several months away.

This list is likely incomplete. See Issues · pachli/pachli-android · GitHub for more.

What and why: Finish the work of splitting the code in to modules:

core:... modules with core functionality

There's some weird stuff in some server responses to /api/v1/instance and /api/v2/instance.

Here's some I've seen in the wild. Format is:

• Heading with server type (e.g., "akkoma") and whether this was v1 or v2
• Then the error when trying to parse the data
• Then a list of all the servers that triggered the same parse error, with their reported version number

Some of these have been fixed in newer versions of the servers but the fixes haven't fully rolled out.

This is a reply to https://social.polotek.net/@polotek/111973724539175076 which rapidly became too long for a single Mastodon post.

I'm a client developer. I'm largely[^1] building a client that meets my needs, and hopefully it meets others needs as well.

When I see someone having a bad experience (your problem statement was "I can't seem to find many interesting conversations"[^2]) I'm interested in understanding the problem because maybe the client can be changed to improve that. I'll benefit, and so will everyone else that uses the client.

For example, would your experience be better if it was easier to browse or follow the local timelines of servers that are for specific communities? This might show you more people that you would be interested in following because they share your interests.

At the time of writing the current release of Pachli is 2.1.1, forked from Tusky 23.0, and contains many quality of life improvements and bug fixes. Some of these have subsequently appeared in later versions of Tusky (I try and indicate them below with a "*").

[!NOTE] This is a bit rough-and-ready, but I think it's accurate. Obviously this will become out of date after a new Pachli or Tusky release. Corrections as comments to this gist are welcomed.

The most significant and impactful are probably:

• "Load more" is gone. Posts are loaded automatically as you scroll through your timeline
• No missing posts. Tusky (and many other Mastodon clients) have a bug that causes some posts to be missed if you leave the app and come back later. Pachli always shows you your full feed
• Never lose your reading position. Tusky (and many other Mastodon clients) can lose your reading position if you leave the app and come back later. Pachli always restores your reading position in whatever timeline you were rea

[!IMPORTANT] This is a draft, the translation feature hasn't launched yet.

Pachli Current, and any version of Pachli from 2.0 or later.

Tap the "..." menu at the bottom right of the post, and choose "Translate" or "Undo translate" as appropriate.

• Status: draft
• Author: nik@ngo.org.uk, @nikclayton@mastodon.social

One of the release tasks is putting together the release notes.

This involves going back through all the merged PRs, figuring out what they did, and boiling that down to a one or two sentence summary.

This is significantly easier if the PR is self-contained. This means: