@apps Wouldn't that be using the standard cache, though? I thought the new home cache feature was meant to download the timeline in the background, so you didn't have to wait for it when you started the app. I have no doubt that the existing cache works, because I always see messages when I start the app, but they're *old* messages, and no newer ones are available until I wait for it to refresh.
@apps I must have misunderstood what background caching meant. I thought I could open the app and it would have already downloaded my timeline, but I'm still having to wait for it every time. I confirmed that the app is not restricted in battery usage.
@apps I voted yes, but only if the timeline jumping issues can be fixed - it would be horrible for it to be automatic and to change your position while you're reading.
@apps I'm worried that support for Mastodon will fall behind. There are a number of bugs that seriously impact the interface, and it seems that effort is going into new systems rather than fixing and polishing the existing ones.
@apps Definitely the jumping timeline. You say not to discuss current bugs, but this one has had many attempts at fixes but keeps recurring. It must be a hard problem with the way Fedilab does its timeline.
@apps I still get the odd panning behavior after zooming in. I zoom in, then drag a finger across the image, and the image will move a few pixels, but then get stuck. If I drag again, I get a few more pixels, and then it gets stuck again. It seems odd that I can't pan around smoothly when zoomed in.
@apps Yes, "fit preview images" and "display previews in all messages". Maybe it didn't have the height information yet, and shifted the timeline when it got it? I'm not sure. It seems like the true fix is to have images loading above the reading point shift upward, not shift anything below them downward?