nikclayton

16 seconds is excessive, and suggests a latency problem with your server.

I just timed a cold start with this mastodon.social account and it was less than 5 seconds.

Pachli has to make a number of requests to your server before it can start showing your timeline. Some of these can run in parallel, some it has to wait for before proceeding.

Looking at a cold start with an account on mastodon.social Pachli makes the following requests (I've added the time it took for the most recent one too):

• /api/v1/accounts/verify_credentials, 1,405ms

nikclayton

It is, but it's a bit confusing. There's a couple of different things at play here:

First, mastodon.rxbrad.com reports it is running mastodon+glitch. So I expect you're using its feature that lets you write Markdown when you post.

Your server then converts that Markdown to HTML and sends the HTML on to the rest of the network. So Pachli doesn't see the backtick characters you used, it sees <pre> and <code> elements.

I.e., you're writing something like this:

This is some `code`.

nikclayton

Mention display bug

Problem/tl;dr:

• In the post https://btfree.social/pub/objects/01KQBGCXB2CTRM1T145PWTDQ4X Pachli is not displaying some of the @-mentions in the post as clickable.

Cause:

• The mentions.url references for those accounts (when surfaced through the Mastodon API on mastodon.social) don't match the a.href attribute in the HTML content for the post
• This causes clients to disregard the @-mention

nikclayton

I have a list of items, each item has a "Delete" button. Pressing the button should show a dialog asking the user to confirm the deletion, and include the name of the item being deleted.

Currently, I have this, which works:

In the viewmodel

// The dialog's state. Either hidden or visible. If visible it needs to display
// text specific to the item associated with the button the user pressed.
sealed interface ConfirmDeleteItemDialogState {

nikclayton

Synopsis

Some Android devices don't respect Android's rules when apps want to perform work in the background.

In Pachli this can result in delayed notifications, slow timelines, or crashes.

After reading this document you will know:

• How to tell if your device has this problem.
• How to configure your device to prevent this problem.

nikclayton

Most important

Survey what other servers have done and don't reinvent the wheel.

Support posting a thread

See mastodon/mastodon#32171. In that I suggest v1/thread, but this could just as easily be v2/statuses.

Different API routes for posting a scheduled vs. a non-scheduled status

nikclayton

Getting a Pachli Current log with adb

Synopsis

If Pachli Current crashes it normally allows you to e-mail a crash report to team@pachli.app which can help troubleshoot the problem. Sometimes that might not work. In this case you can retrieve and e-mail the log yourself. This document explains how.

Before reading this document you should:

• Be comfortable installing and running command line tools.
• Have a computer running Linux, Windows, or OS X.

nikclayton

Snapshot (accurate as of 2025-10-01 I think) of features/functionality Pachli has relative to Tusky, since people keep asking me what the differences are. This is not exhaustive, it's just the ones I think most people are likely to be interested in.

Entirely possible there are also features Tusky has that Pachli doesn't. I can't speak to those.

• Monthly release cycle, so you get new features faster
• Pachli shows your whole timeline. Tusky can miss posts. See these bug reports for examples.
  • https://codeberg.org/tusky/Tusky/issues/2831
  • https://codeberg.org/tusky/Tusky/issues/3505
  • https://codeberg.org/tusky/Tusky/issues/5176
• More features:

nikclayton

The problem is triggered by any account on your home timeline that has a Role associated with it.

That's probably your server owner @doktorzjivago.

Options I can think of are:

Mute or unfollow

Temporarily mute or unfollow @doktorzjivago (use the web UI to do this) until I can release Pachli 2.15.1 with a fix for this.

nikclayton

If you're not sure about any of this you can contact the GoToSocial devs at https://codeberg.org/superseriousbusiness/gotosocial#contact -- there should be enough information here for them to determine if this is a misconfiguration of your server, a GoToSocial bug, or a Mastodon bug.

Your account name isn't displaying properly on Mastodon. It looks like this:

Note the :purplerabbit: in there.

This is because you have several emoji references in your account's display_name, but your account info doesn't include all the emoji details, so other servers can't show it.