Thanks for this amazing app!

Ciao guys, as usual for thr first week of the month, a new production release has been published!

This version contains some stability issues (especially when navigating through comments or posts, opening and closing a post detail, etc.), some performance improvements when opening contents or refreshing (for cases that were, at least to me, very annoying) and several layout enhancements (duplicated paddings, progress bars where they shouldn't be, system nav bar color, etc).

There are a couple of brand new features too, such as admin tools and the default editor language on a per-instance basis, plus the downvote option is not shown any more if it is not allowed by your instance.

There are lot (trust me, a lot) of under the hood improvements: new unit tests being added, several dependency updates and the whole project was migrated to Kotlin 2.0.0, Compose Multiplatform 1.6.11 and Gradle 8.8. As you may have noticed, this made it also possible to launch iOS builds apart from Android ones, and I dont exclude that in the future I may be working on a desktop port.

Have a nice month! 🦝🏳️‍🌈🦝 And enjoy the release!

So, guys, this is the last development release of this month be prepared for a stable release next time! Even though there are not so many shiny big new features, the only notable one if the ability to mark/remove posts as featured on an instance level for administrators, there are many fixes and under-the-hood improvements, mainly the project has been migrated to Kotlin 2.0.0 and Compose Multiplatform 1.6.10, new tests have been added and there are several fixes for the bugs you have reported in the past week. Additionally, the fact that I've managed to build the iOS counterpart of the app, which had been abandoned forever, gives me hope that one day we'll be able to ship something for other platforms too to increase the adoption of the project.

Next week I'll be working on a couple of reports I've received recently which I choose not to include in this build because I did not want to delay this release: the ability to set a preferred language community-wise and the navigation bar appearance. And then we'll be ready for 1.11.0!

Would it be possible to make the navigation bar transparent? I have the option turned on in settings but there's still a white/black bar at the bottom when scrolling through posts.

I comment text in both English and German. The (now semi-defunct) feddit.de instance has some/many/most communities that only allow German as language, while on other instances or in communities only English is allowed (or at least that's the only way my comments get posted).

This creates the problem that I cannot really set a default language tag, because that would regularly delete my comments when the comment doesn't get posted with no or the wrong language tag (because I forgot to add or change the tag.

I don't know about programming, but I'm not sure how taxing this would be memory- or caching-wise.

As you may (or may not) know this is a multiplatform project, but I've always given precedence to the Android version because Compose was still in its early stages on iOS.

But attending to KotlinConf'24 last week was really inspiring for me and gave me the bravery (and a little bit of recklessness) needed to spend a couple of nights staring at build errors and Xcode configuration files to make everything work together again.

And I did it! I am not going to distribute an iOS version of the app any time soon, but I wanted to just share with you guys that theoretically it could be done, and that's great news!

🎉🎉🎉

As anticipated, this development release contains mainly user experience improvements and fixes. The option to downvote a content is not visible any more if the current instance does not allow it, inbox items are marked as read after being opened or voted, the action items are bigger as you requested and an unwanted margin at the start of comments has been removed. Additionally, more unit tests have been added and several navigation, pagination and caching issues have been solved. I'll be away for some days from tomorrow, so until next week! Report any issues on GitHub please, sorry if I don't answer immediately but will take care of everything when I'm back.

Hi everyone! We are halfway through between version 1.10.x and 1.11... next week I am not going to have much time because I'll be attending KotlinConf '24 (btw, if anyone happens to be there, let me know!). So, what to expect for this project?

I am continuing on various user experience and layout improvements (especially the inbox section), I've fixed crashes I received reports for and, if I manage, I'll work on a small enhancement which I've been postponing for too long: hide the ability to downvote if your instance does not allow you to do so.

That's it, enjoy the weekend! I'll publish the next pre-release build on Tuesday May, 21st if you don't mind.

Hi guys, new week new development release! This week I have been working to fix some annoying bugs, e. g. a loader incorrectly positioned before video playback, the pull to refresh indicator was a incorrectly positioned in some screens, and a visual bug while replying to a comment.

Additionally I added a couple of new features, such as administration tools and configurable indent amount for comments which you requested.

Finally I have made several improvements under the hood, adding new unit tests, refactoring code, reimplementing the bookmarks screen to unify the pagination logic and created a CI workflow in order to enforce state checks, so that non-compliant pull requests cannot be accidentally merged.

I hope you enjoy it, have a nice weekend, be responsible and, as always, L. F. E. T. 🦝🦝🦝

I am considering a change in the upvote and downvote buttons, which version do you prefer? Or, alternatively, do you have any other proposals? Let me know in the comments.

Please don't ask me to put a setting for it and have both versions. 😂

Ok, so seemingly even version 1.10.1 wasn't perfect, there was a bug in how the post body max lines setting was enforced, plus a series of small issues (account switching, message loading at the beginning of conversations, the status bar style not being applied correctly with light theme) and several layout that still needed improvements.

I wanted to address as many issues as possible but not force everyone to update, so here is a development build for those who want to install the latest release.

In the Content Appearance settings, the "Post body max lines" doesn't seem to be a "max" value. Instead, it seems to display exactly that many lines. I set my "Post body max lines" to 10, and if the post body has more than 10 lines, Raccoon correctly hides the rest of the body. However, if the post body has fewer than 10 lines, Raccoon still allocates 10 lines of space. This means posts with only one line in the body appear like this:

Are you able to shrink that space to match the post body length when it is less than the "max" value? It looks like that setting is also being used as the "min" size.

Did I say "if anything goes wrong I can always release a patch"? Yes I did... and here's the patch.

This is mainly to solve a bug with the keyboard in coment creation, a bug in account switching and improve the image detail screen.

Thanks to those who took the time to report these issue and explain them to me.

Ok, I've decided this month's release is ready, so hopefully soon you should be able to get your updates through the stores.

This version has so many changes that I really struggled to make everything fit into the character limit, but if you play around you'll notice that there are quite a few new things.

It is now possible to fade out read posts, import/export app settings in JSON, navigate to previous or next comment in post detail and even navigate to previous/next post if you opened the detail from a list. Other new features are title autocompletion, bot account highlighting, an option to have full width (besides full height) images, custom tabs support, a monochrome alternate app icon, the ability to receive contents from the system "Share" menu and a brand new "sidebar" used to display community and user info.

Plus, of course, a lot of UI improvements and bug fixes based on your most valuable feedback. Thanks to everyone who dedicated some time to give suggestions, report or fix bugs, and helped in any way.

You are awesome! And, for those who know me a little bit, maintaining this project makes my life better.

Ok, this week's development release is receiving a lot of feedback (a huge thank you to all contributors!) so I'm splitting its lifecycle in half. I've worked through most of the requests and reports yesterday and I'm releasing a new intermediate release today so that from here until Wednesday I have time to collect further feedback and make further fixes.

I hope I'll be able to release 1.10.0 soon in order to deliver all updates to users that stick with the stable version, so unless there are blocking bugs or serious things, the next release will be pushed to the stable channel.

Have a nice weekend, raccoons of Lemmy 🦝 L. F. E. T. 🦝

Tried using different Keyboard(Simple Keyboard and Heliboard) but it didn't fixed the issue.

Using Android 10 Stock ROM.

Here's Screen Recording

I use a Tablet BTW.

Also It take me 2 or more click to open something. Maybe My Hardware problem but old versions don't have this problem.

As agreed, this is the new pre-release version of 1.0.0. There are some new features such as: opening links in custom tabs, navigation between comments in post detail and to previous/next post in feeds. Some of your requests about link opening and link banner display have been addressed too, plus the profile and login screen have been slightly improved. I had the opportunity to change some things under the hood, like the pagination mechanism, in order to make it possible to navigate to previous/next from the post screen, which was much needed and resulted in cleaner code, even if it took some time to refactor.

Hi everyone, I need your opinion about the next release. As you know, each Wednesday I release a new beta version and the first week of each month a stable version.

Tomorrow would be time for a new prod release but recently I've been working on a lot of new "huge" features such as opening links in custom tabs, comment and post navigation, etc. which nobody except me have tried in real world scenarios. And not everything is opt-out by default, e.g. the pagination logic had to be reviewed in the whole app in order to be able to navigate between posts from each feed.

Would you like to have stable 1.10.0 tomorrow or a pre-release and skipping the new stable to next week? Personally I would release anyway because if anything goes wrong I can patch it... but if one or two users help me with tests it is worth waiting a week before going into the wild.

Leave me your thoughts in the comments below and thanks as always!

If you tap on an image post's image, Raccoon goes into what I'll call an "image viewer" mode where you can zoom in, download, share, etc. However, if someone embeds an image in the post body (like I did here), then tapping on it in Raccoon does nothing. I was expecting that tapping on an image in the post body would also move into the "image viewer" mode so I could zoom in. Similarly, if someone embeds an image in a comment, tapping on that image will just collapse the comment (as if I'd tapped on the comment body). I was expecting to be able to zoom that image as well. Would either of those enhancements be possible?

Also, I have an unrelated question (not necessarily a request). On URL posts, Raccoon fetches the image thumbnail from the link. If I click on that image, it also goes into the "image viewer" mode as if it were an image post. Was that intentional? On most other apps I use, tapping the image thumbnail will launch the URL. So I believe in Raccoon, the only way to actually launch the external URL is to click on the URL itself (which isn't visible in Compact mode unless you view the post/comments). If you did this intentionally to allow URL thumbnail zooming then I won't argue with it, I'm just curious if this was an oversight and you're accidentally treating the URL thumbnail as an image post.

When using 'Card' or 'Full' Post Layouts, you display the URL at the bottom of the post. That's fantastic and I love it. However, for image posts (for example, memes) the URL is just the address to that lemmy instance's pictrs/image/ path and I don't think it's very helpful.

Is there a reason why you display the URL when it's just an image? I can understand including that image's direct URL when you long-press and choose the 'Share' option but I don't think it's helpful to always display it on every image. Actually, I think the 'Share' option would be a great place to put this URL since that feature already handles multiple URLs...

Note that I'm not suggesting adding a settings option to show/hide image URLs. I'm mostly asking if there's a reason to display the image's URL at all, because it feels like you're just treating image posts the same as URL posts rather than making a deliberate decision to show an image's URL.

In Jerboa, you can enable parent comment navigation buttons, which look like this (up/down arrows at the bottom):

I personally really like this feature because if there's a long comment thread I don't care to read, I like hitting the down arrow to jump to the next comment thread in that post. I know I could just collapse the parent comment but I'm usually half-way down a comment thread before realizing "oh... this just keeps going" and that's when I want to jump past it.

On the main page in Raccoon, you have that navigation bar at the bottom which disappears as you scroll down and slides in when you start scrolling back up (the bar, not the FAB). I'd love to have that exact same type of bar slide in with up/down buttons when reading through a post's comments.

New week, new release! In this one there a couple of interesting features like title autofill, the possibility to receive text (post URL or body) from other apps via the system's share menu and the ability to import and export settings to a JSON file.

On the layout side, I restored the profile screen like it was on version 1.9.0 (stable), introduced a side menu for community info and user info, reviewed some paddings and fixed the edge-to-edge display which was not working well on some devices.

Thanks to all those who reached out to me for feedback, suggestions, hints on how to get things done and everything. You are awesome! 🦝🦝🦝

Since I received some negative criticism (but also some positive remarks) about the profile actions which were moved in the floating action button in this week's release, I am planning to iterate over in for next week's release and I need your opinion.

Instead of using the FAB or having it all always visible, I propose to you to use a side menu from the right side, as implemented in the following pull request. Would you mind having a look at the video on GitHub and give me your opinion? I'll leave two comments below here and will decide what to do based on the number of upvotes of the individual comments.

Thanks to everyone who participates!

Hi everyone! We're releasing on Wednesday again because "what a week, huh?" but I hope it's equally fine for everyone. This development release has a couple of features you requested (marking read posts and showing the number of unread comments, both of which must be manually enabled from the advanced settings screen because I wanted to keep the experience consistent for most users). Plus a series of fixes and improvements.

In this release I have welcomed an external contribution too,which fixed a bug with credential autocompletion. The project is slowly but steadily finding its place in the lemmy-verse it seems. Thanks to everyone who is helping in this journey and, as usual, L. F. E. T. 🦝🦝🦝