It’s a lot better if you’re scrolling for short to medium bursts of your feed. The problem mostly remains with longer scrolling of the feed, but there does seem to be a performance improvement.

A new issue is scrolling active and top 6h, on All, will now shortly result in a no more posts message after hitting the new content break 2-3 times. I had to use active to hit the 6 or more content break twice to reproduce the problem originally reported. Also the content breaks require you to scroll up a bit to load new content; prior, you could scroll down and up.

On that topic, can you increase the password length field to 128? I was trying to login to my Piefed account and couldn’t. Had to lower the password length to 60. Services like Bitwarden have 128 as the upper end for passwords and I think that’s a healthy size to have.

I tried tapping on a bunch of images in active and top 6h but was not able to reproduce the image data error. You do need to close and reopen Connect after toggling for the preloading to take effect; and the errors to stop coming up.

If you’ve reopened the app and that error is still coming up, can you post a bug report? To do that, go into Settings and tap on the three dots in the top right. Then on Report bug. You can copy it and just reply here if you want. Mainly, I’m curious which settings you’re using that seems to produce this problem.

Both of those issues have been fixed in a previous beta build. If you’re not getting the update in the app store you may want to try leaving and rejoining the beta. If you’re not on the beta and want to join, you can do so on Connect’s app store page.

FYI, I’m not the dev. But it seems a lot of people have this issue so I’m sure the dev will try to fix it as soon as they can.

When you go into Settings, it’s displayed at the top.

If you’re getting this on v314, it’s due to the preload images setting being disabled. Tap on that link to go to the Settings page to turn that on. It’s on by default and having it enabled is generally better.

The post API errors were fixed a while back so I’m wondering if maybe you’re on an earlier version. I’m on v1.0.314 and I haven’t seen this particular issue. If you are on 314, can you post a bug report? To do that, go into Settings and tap on the three dots in the top right, then on Report bug. You can submit that for a new post or copy it and post it here as a reply.

You can turn that off by disabling the display Community banners setting.

I’m also seeing this on 314. Even after clearing the app cache. Scrolling the feeds is fairly smooth in card view but you’ll see it in list view. The feed will stop scrolling at certain points and there’s a performance chug as images and/or videos are loaded(preloaded?). Toggling things like image preloading and webp conversion had no effect.

Originally, I was going to report a different issue so I’ll describe it here. I noticed this problem in maybe this or a recent update; I don’t recall this issue previously.

Embedded pictures in comments are always pixelated and blurry. I have to tap on them to see the full resolution. Toggling the preload images setting on/off had no effect.

I don’t think I’ve seen that but I’ll know what to do now if there’s a problem with receiving a Play Store update.

It seems to be working fine for me in v1.0.307. This problem was fixed in 1.0.303 so if you’re on an earlier version, you should update the app.

If you’re on a later version than that but still having this problem, can you post a bug report? To do that, go into Settings and tap on the three dots in the top right. Then on Report Bug. You can submit that or just reply to your post and add the info here. Mainly, the settings info after the steps to reproduce part will be helpful.

Ahh, so that’s a list view issue. People on card view are fine; with the gallery combine setting off. For now anyways, I’ll sure the dev will fix it in the near future.

That’s what I see when I view the post you mentioned in your report. That’s with the gallery combine option off.

Another issue I noticed was when I was composing the bug report, I tapped on the uploaded image to check something and when I tapped again to go back to the draft, it wasn’t saved and reverted back to a n older draft. When I went to test, the title will save fine if you view your image while composing but the body portion isn’t saved.

Just to add, the problem remains in v307. The issue is due to the combine to gallery setting. It’s somewhat better disabled but then each image gets two placeholders. The top of which shows an unresolved link but will lead to the image to a subscribe link for the thread’s associated community. While the bottom spot will show the appropriate image.

I think the addition of a condition that doesn’t combine images of certain posts like the one listed in the report may be ideal. Like if thread images are posted in between links to threads then it’s not combined.

Just to piggyback, timestamps from comments are gone? They were there recently. Now when I view any post, I just see points next to the username , of comments, and nothing following that.

Unfortunately there’s an issue with turning it on. I was viewing this post and noticed that viewing it the first time is fine. When you reopen the post and try to scroll up from the bottom of the post, the app let’s you for a split second before seemingly preventing the scroll action. Turning off the setting lets you scroll fine on revisits with the caveat that you need to refresh to view comments.

I had that off and turning it on does fix it. Guess I’ll turn it on.