#Tusky v22 beta 2 should be showing up in Google Play and FDroid soon.

1. The number of notifications that load at once has been reduced back to the Tusky v21 amount. Turns out loading many more than that can be quite slow for a lot of servers.

2. The new "Show post statistics in timeline" option hid the old "0/1/1+" indicators for replies if it was turned off. So they've been put back.

3. If a post matches a filter and is set to "warn" Tusky now warns you with the title of the filter, *not* the keywords that are used in the filter.

4. Tapping a post could open a link from a completely different post. Not any more.

5. Reporting a post would cause a crash.

6. Some other edge-case crashes have been fixed.

In the course of testing beta 1 we've also discovered that Pixelfed does not follow the Mastodon API for notifications. If you use Pixelfed with Tusky you may see duplicate notifications, and scrolling through them will probably not work. If you are interested in the technical details see https://github.com/tuskyapp/Tusky/issues/3580#issuecomment-1527198806.
22 beta: Notification error in pixelfed · Issue #3580 · tuskyapp/Tusky

When connecting current 22 beta release (or nightly) to pixelfed.social, notifications timeline will display notifications for a moment and then switch to an error screen. Reloading will again make...

GitHub
@Tusky do you know why it was closed, without a fix or answer provided though?

@NafiTheBear Any fix would need to be in Pixelfed. Daniel (Pixelfed's lead dev.) is aware of the issue.

It's their choice as to whether they want to fix this, and any issue tracking that would be in the Pixelfed repository, not the Tusky repository.

@Tusky thank you for the update. Daniel is sadly quite intransparent on changes, but I'm glad that he knows about it. I'll just wait then.