Connect for Lemmy App

After unmuting the video here and then closing it, the audio continues to play. This is occuring on v224.

EDIT: Occuring with other videos so it's not specific to that one. The only way to stop the audio at the moment is to go back to the video that was playing and mute it.

Just wondering if there is a way to show all replies by default rather than always having to tap "view more"?

Hey, just wanted to say i love the app and all the customization options. I was wondering though if theres a setting to change the background colour used for the top and bottom bars for images that dont fit the full aspect ratio of the screen. As of now it seems to be using an 'average' of the most dominant colour in the image which is usually very nice, but im using a dark theme and it can be quite jarring, especially at night, when the image is say a twitter screenshot, which gives very light grey top and bottom bars. Ideally I'd like to keep the average colour background for most posts but be able to set a 'minimum' brightness that is used for bright images, but it would also be nice to be able to just set a default background color. Sorry if this is already in the settings somewhere and ive missed it. Thanks

It's kinda useless for productivity or usability but I like it a ton. ;)

Hi, can you add alt text support for images? It was added in Lemmy 0.19.something, but Connect has no way of (a) setting it, or (b) viewing it.

If the user has more than one community they're moderating, the ModView is the feed of only those communities. It's really useful in the desktop version of Lemmy. Wish I could use it in the app. Not sure how difficult to implement. Maybe only show it if you're mod of more than one community or something, so as not to clutter the list of feeds for everyone else.

Awesome work btw. Anything I can do to help?

Weird "all" feed blanking bug. This is more likely to happen if the 20-30 thumbnails have not completed load.

This seems to be related to thumbnails that aren't fully loaded, but not always?

1. When scrolling fast and preventing thumbnails from fully loading, I can get the feed to temporarily hang until it finishes loading loading some thumbnails.

2. I will eventually hit a "feed limit" when scrolling through the feed to ~100 posts.

3. Sometimes, slowly scrolling back up the feed to allow unloaded thumbnails to finish may "unblock" the feed for a bit, but not always. It may load one or two additional posts, and hang again.

There seem to be multiple conditions causing the feed to pause vs completely hang, and I can't nail those conditions down.

This issue has gotten much better since 219, but is still a bit quirky.

Is it possible to get a few colour options (red, yellow, green preferably in my mind) for when we add a note to a user in the comment section? It seems like it would help be an even quicker way to use the notes, if I see a green name I'll stop and read, red just keep scrolling, yellow proceed with caution.

I know there's always the block feature but maybe that feels too absolute, as if there's some days that maybe I'd be willing to see, or debate a red note. Just an idea.

Any idea why post video thumbnails are showing in three distorted diagonal bars?

Once you open the video full screen it plays normally.

First. Thank you a lot for developing Connect. I like it the most from the first day. After the second update (month ago) I have issues 1, a month ago issue 2, and since a few weeks issue 3:

1.) With one of the the first Updates the letters of the maintext are a bit small and narrow, you can make the text bigger in the settings, but then the bottom and/or menu text is too big. Would be great to have more different fontsizes to choose in the settings.

2.) And only 3 instances are working for me. With 4 instances it has a log in problem (2x Guest, 2x with Account). With 4 instances he switches to this user - see screenshot.

3.) After one of the last updates media is often not loading - see second screenshot.

Sorry for the long post and my bad English - it's not my first language. Here's a potatoe. 🥔

I was curious:

Have you ever considered potentially incorporating some of the highly-praised UX elements, theming capabilities, and overall user experience from Sync for Lemmy into Connect?

Many users, including myself, have found Sync's interface and customization options to be exceptional, as well as leagues ahead of the competition (no offence).

However, there are concerns in the Sync community about Sync's closed-source nature, as well as the developer's loonngg periods of inactivity.

Given Connect's open-source ethos and active development, do you see an opportunity to potentially fill this gap by bringing some of Sync's most loved features to Connect, while maintaining your commitment to transparency and regular updates?

If done right, Connect could potentially become the new Sync, but open-source, and with active updates.

I'm curious about your thoughts on this, and whether or not it aligns with your vision for Connect's future development.

This is an odd problem to describe.

I can scroll through about 20 posts and then the feed will "hang". Once those 20 or so posts finish loading thumbnails, additional older posts will be loaded.

This is not as noticeable on fast connections, but causes significant lag on slow connects. There is no immediate indicator that Connect is still loading newer post data when you hit the end of the feed cache/buffer. (It feels like feeds have been split into "pages" and after 20 or so posts, there is a delay when hitting another "page".)

Thanks for attempting to read this shitty description of a problem. I tried.

Edit: The feed will actually get "stuck" sometimes. It's common for me on "all". I had 800mb in cache and just cleared it. It's got a little better for some reason. I can get close to 50-60 posts before the feed pauses or hangs.

FullWidth mode doesn't have this issue.

I have heard of this great app mostly through Lemmy.ca.

Is there no way to delete or report a private message? Is this specific to Connect or Lemmy in general?

I got a weird message and it's just sitting in my inbox.

They are leaning into it pretty heavy so I assume it looks fine somewhere, but on Connect most of the markdown in this post is not getting interpreted. https://lemmy.world/post/13129663

I keep running into a situation where the top menu bar disappears. I can scroll up down and enter/exit posts but I can't e.g. change filter settings because the interface elements for them aren't there. Most recently this happened when I blocked a community- my feed was reset and my menu bar disappeared.

Update April 19 2025 seems to be fixed in current beta Version 1.0.251

Not a huge deal, but a recent one. I scroll and scroll and scroll, see some community I don't want to see, so I block it. Now, the feed resets to the top and I am unwilling to regain my hard fought progress, so I inevitably exit the app for several hours until I am brave or bored enough to return.

I am going to edit this post and get some screenshots. (Done)

Note: Backing out of this post, after navigating to this post, via my profile, triggered the "blank feed" issue again. (See blank screenshot in comments.)

(Sorry for the issue replication testing in this post.)

Has anyone else experienced issues with screen tearing and garbled text? It seems to have gotten more pronounced since my most recent android updates.

Currently running stock android 14 on a Galaxy S21+ 5G.

I'm consistently getting this bug on 1.0.216. If I go to this post, tap on IninewCrow's comment, that starts with "Like Drump ...", to minimize that thread, then tap on it again to restore the thread, everything below their comment becomes an endless gray screen. Backing out and then opening the post again will fix the problem. When first entering the post, if I tap on a comment in one of the other thread chains, then I'm able to minimize comments in that particular chain without triggering the bug.

EDIT: This looks related so I'll add it here. If I go to this post, tap on AlolanVulpix's link, back out to the post, then tap on the overflow menu for the post, the whole screen becomes gray.

Also, AlolanVulpix's link isn't being resolved correctly by Connect and produces a "GoException: no routes for location: /post/39971490/14887796?hint=39971490/14887796&hintInstance=lemmy.ca" error but viewing the post in the browser, it works fine. It seems like Connect is using the home instance of the poster rather, like how I grabbed the Lemmy link from the overflow menu for the original bug of my post and it gave me the slrpnk.net instance for it rather than the lemmy.ca instance link, where the post was posted.

• Open an image
• Tap the three dots menu
• Select "share"
• Nothing happens

The "share URL" option does work, just share doesn't.

Using v1.0.216

This is just general experience feedback. Hoping this helps the dev, since it's marked "experimental"

I just switched that feature on to check out what it is. Today I had a lot of comments in my inbox on a single post I made and went to check them out. This feature makes it so that when I clicked on the first comment, it remembered that. So every other comment I clicked in my inbox, just redirected to that first comment.

I switched the experimental feature off and the problem was solved.

I switched it back on and again, the first comment I clicked was remembered and every other comment I clicked led there.

I'm experiencing an issue with the Default sort for Posts setting. Here's a scenario of how the issue plays out:

1. I adjust my Default sort for Posts setting to be Active through the Settings menu.
2. I close the and reopen the app, and it opens to Active.
3. I change the current sorting method to something else, e.g. TopSixHour, using the drop-down menu in the top-right of the app.
4. I close and reopen the app, and it opens to TopSixHour. Additionally, the option for Default sort for Posts has been changed to TopSixHour in the Settings menu.

I've only noticed this since recently getting a new phone, going from a Pixel 7 to a Pixel 9. I have tried uninstalling/reinstalling the app and that did not fix the issue.