I'm seeing a crash reported A LOT in the Google Play console for Tusky 32.1. I have no idea how to reproduce it, but from the stacktrace it is somewhere in a timeline. Most crashes are on foldable or tablet sized devices and Android 16.
If you have seen random(?) crashes please let me know, this needs to be fixed.
Edit: The issue is identified, it happens sometimes after using "load more", I'm working on a fix
I asked this before out of curiosity but now I'm seeing crash reports that indicate it should be possible somehow: How (with which client or fedi server) can I edit a post to add a quote?
Edit: Oh it is when a quote goes from pending to actual quote π€¦ββοΈ
These certificates are from 2021 and not trusted on Android versions that are older. We already do the same with two ISRG/Let's Encrypt certificates for the same reason. Closes https://codeberg.org/tusky/Tusky/issues/5423
Not sure I understand what you're saying.
If, when I click on "Load more", and there are too many new posts to load in one go (so the banner stays), I would expect them to be loaded ABOVE the banner.
That way, the last post I read is still the one BELOW the banner and I am still at the correct point in my timeline.
If the new posts are loaded below the banner, then the last post I read is pushed down the feed and I have been skipped forward in my timeline by however many messages were just pasted in. So I've effectively missed all of those pasted-in messages unless I manually scroll back down to try to find the last message I read.
I can reproduce this consistently. When I reach a "Load more", and click on it, one of two things happens:
1. The "Load more" disappears and the new messages are pasted above where it was (and above the last message I read, which is expected behaviour).
Or:
2. The "Load more" remains and new messages are pasted below it. If I click on it again, it disappears and the next lot of messages are posted above where it was (as per 1).
So the problem only manifests when there are too many messages to paste in one "hit".
You're welcome π
Ironically, I mainly use Trunks (with this account) and only dip in to Tusky occasionally with my mastodon.ie and c.im accounts.
But certain people always seem to hit bugs immediately, without even trying. I've akways been one of those people.
TL;DR: "Load more" behaviour is inconsistent in the latest builds.
I have my feed set to "Oldest first". So when I fire up Tusky, I'm taken to where I left off. I scroll upwards through the feed, reading newer messages. Eventually I come to a "Load more" bar. I click on it.
Previously, new messages were loaded ABOVE the bar, so the last message I had read (below the bar) was still on screen with the newly-loaded ones above. I could continue as normal.
Now, the new messages are sometimes loaded BELOW the bar. So, in effect, I've been skipped forward. The last message I read is now some way down my feed and I have to scroll back down to (try to) find it so I can continue where I left off.
This doesn't happen every time and I've been trying to find a pattern. I think, though I'm not completely sure, that if "Load more" doesn't load all of the missing messages (so the bar stays there ready to load another batch) the messages get loaded below. But if it is able to load all missing messages, it loads them above.
Hope that all makes sense.
The code to display attachements in a grid is one of the most complex parts in Tusky. There are different aspect ratios, blurhashes, focuspoints, ...
I'm currently rewriting it in Compose and it is SHOCKINGLY EASY π³
The old code to respect the focuspoint alone has 144 lines including comments (it does some Matrix calculation stuff). The new code is 6 lines (it just works natively in Compose, lol)
Conny Duck
Nick