Connect for Lemmy App

When clicking the Explore icon on the bottom navigation bar, the menu that pulls up only covers about 1/3 of the screen. It's enough to type a search string, but it leaves little space for the results.

I think a better use of space would be to bring the whole menu up to the full height of the screen once a query has been entered, or at least allow the user to pull it up manually by dragging it upwards

I go to view a comment with two dozen replies.

My comment is #16, a direct reply to the parent comment.

I want to view the original parent comment. I click parent.

Screen scrolls up half an inch to comment #15. Cool. I wanted to see comment #0 though....

Can we have the parent button do parent button stuff?

If I want to quote a specific part of a comment to reply to it, that's not possible with Connect right now unless manually copy pasting the segment.

Ideally, the existing "quote" option in the editor should take into account selected text

When viewing the front page, if I "pull down" the screen to refresh, the contents are different than the "refresh" menu option in the "top-right" menu.

I like having the image posts be full width, and the thumbnails with links to be in the "list" format.

Just something small I noticed while scrolling through [email protected], where the empty thumbnails took up a lot of the screen

This is a fairly persistent issue that appears to be exclusive to Connect, and extremely annoying.

Any time a post accumulates very large numbers of comments (say, 300 or more), Connect will eventually just... stop loading additional comments. At first, scrolling down will load a few more top-level comments, but eventually it'll just give up and act like there's no more comments to load, even though there Connect has loaded less than 50 comments out of a 1,000+ comment megathread. Worse yet, if a user direct links to a comment on one of those megathreads, Connect will load a completely empty comment thread. This issue doesn't occur on Voyager or Jerboa, nor on the web UI.

I was trying to edit a second comment (grrr autocorrect) in a thread I have previously edited a comment, but the app always loads the first comment I edited.

It works fine of I use the web interface (on feddit.de)

I currently have " hide read posts"and "scrolling marks as read" both turned in on my settings. Whenever I switch between my different logins, and returntl to the previous login, all of my read post history is reset and I have to start from the beginning again.

It happened to me a couple of times. May there be a warning dialog before that? Because if you unlog, you'd need to log in again with empty login and password forms. And it's just one tap from other accounts in account switching menu.

Or maybe put it onto the bottom of a sidebar? Idk.

It would be nice to have an option that hides NSFW posts in the front page and all collections, so I can browse on the work wifi without causing issues. Then be able to browse through those specific channels at home with all the preloading on.

Could either work as an extra setting in the main settings window, or perhaps a "hide this subscription from the main feed" on a per channel basis?

Or does anyone have a way of doing this already?

this thing

With lemmy.world going down a lot, I know that instances such as lemm.ee mirror quite a few communities. Is there an easy way to migrate subscriptions I have on lemmy.world to the corresponding communities on another instance?

Loving Connect, BTW. Wonderful app.

I normally switch between Hot, TopHour, and TopSixHour views but now every time I log back in or change communities, it defaults back to TopSixHour. how do I get it to stay on the one I just selected and only change if I change it?

*Edit: Reinstalled Connect and it's working!

I was browsing my Frontpage yesterday and was being inundated with posts from a single community. To remedy this, I navigated to that community and hit the unsubscribe button in the menu. Heading back to my Frontpage brings me to the title error.

Some troubleshooting steps I've taken:

Killed & reopened Connect, signed out and signed back into Connect, signed into an alt account on Connect (worked just fine), and I even resubscribed to the community that caused the problem in the first place to undo the issue. I've subscribed to new communities to see if that would generate posts on my Frontpage but no luck there either.

Visiting my instance's subscribed page (Frontpage) in a browser populates just fine.

I'm asking anyone here for help as I don't want to bother Kuro directly for a personal issue.

Other than that, the app is perfect

Hi dev thank you for your cool app, Btw I hope you'll consider this for a lefty, thanks again!

When voting on a video/gif that is playing reloads the video which restarts it playing from the beginning. Happens when both using the voting arrows or the swipe action. I expect it to continue playing.

The post swipe controls have hiding the post as an option. Giving the comments the same options would allow for a consistent user experience.

I'd like to turn on notifications in Connect, but I really don't want it polling for them every minute. Can we get some granularity for this feature?

My AMOLED theme kept reverting to the normal dark theme on app restart. Had to manually set the background colors to #000 to fix it.

Add an option to enable a Discord-style sliding left nav (i.e. swipe from anywhere and the main view gets "pushed" off to the right by the left nav).

See Discord for more details on how this looks and works.

The following regex, if inserted into the Filters section, causes Connect to fail to load any content from any instance and report "INSTANCE is not responding"

/(\[|\()[Mm](\]|\)))/

It is missing one left paren, and instead of a useful error message, it breaks Connect in a surprising way

As the title says: When I tap the "View full post" button, it loads all posts as expected but instead of disappearing after loading all posts, it stays on screen, still displaying the message: Viewing a single comment thread "View full post". And it won't go away even after tapping it repeatedly.