Hi, Connect 1.0.63 is our two week birthday (from this post). Hard to imagine it's only been two weeks. This version brings a lot of new things but the big features would be instance level blocking, 'show more comments' buttons to make comment views more compact, new theme options, and the ability to mark a post as read while scrolling.
What's new
- Added community icons next to names in the main feeds
- Added an option to show @instance labels on all usernames and communities
- Added instance level blocking
- Added dividers between cards
- Create post community suggestions are improved, will now autofill with your subscriptions and suggest a community you've subscribed to first
- Added show more comments buttons
- Added option to mark posts as read on scroll
- Added more theme options
Fixes
- Fixed an issue with the profile tab not refreshing in some scenarios
- Changed community icons to be smaller and they should load faster
- Added some new sort options for posts
- Fixed notification icon hopefully (no more blank square)
- Fixed swipe to reply not working from the inbox
- Viewing a comment from your inbox will now remove the comment when you go back
- Improved the tap target when interacting with a short comment
- Fixed an issue with uploading an image in comment view
- comment title text now wraps instead of getting cut off
- Improved memory usage when scrolling through a lot of images (still some more improvements coming on this one, we're not freeing up images in memory as often as we could be)
- Fixed an issue with NSFW communities not being searchable (and subsequently some link handling being broken if the community is marked nsfw)
- Fixed an issue with the search back button
- Fixed an issue with incorrect passwords if the length is more than 60 (it's now capped to 60 which is what Lemmy does).
In case you're wondering what was in versions .60-.62, they were all minor hotfixes that have been combined into this list. Also for those wondering when it's going to be open sourced it's coming, I hear you! my focus right now is on adding features and improvements.
Links:
-kuroneko
Loving the updates so far!
Small request though: Toggleable setting that adds a hide/show button to each comment so that we can immediately hide a post instead of waiting for the long press to trigger. I know screen real estate is at a premium for most phones, which is why this would be a Toggleable setting.
There's a setting for reversing comment actions so they can be hidden with a tap, is that what you're looking for?
Thanks for being so responsive! I tried out that setting just now and it's not quite what I mean in terms of UX. To preface: I'm not trying to make your app a clone of RIF which I heavily used, and your app does feel the most similar to that for me so do what you will with my feedback.
My main issue with the way Connect currently behaves is if I wanted to collapse the first few comments after returning to a post, I'd have to either toggle the setting to tap each comment to hide them all, before toggling it again so that I can interact with the comments normally, such as voting, bookmarking, sharing, etc. Whereas, if the options were available all at once when tapping on a comment, I can do everything in two taps, versus one or the other, with two taps, or waiting for a long tap to process.
As stated previously, I know screen real estate is at a premium for some devices, so cramming more buttons below each comment is not necessarily ideal. But what RIF did well, was including these features all at once to the user when the comment was tapped, by displaying extra action buttons above the selected post, in addition to the normal interaction buttons below the post. See the screenshot attached below:
Edit: To add to this, after rereading that post, I'd like to make the distinction that I mean collapse a comment, everywhere I say the word hide. As there are many times I'd like to reread comments if new replies are posted below them, and I've yet to figure out how to unhide comments after testing the hide feature out.
Edit 2: Also just noticed a bug. Viewing the community info displays Subscribe for all instances, regardless of actual subscription state.