raccoonforlemmy

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. 🦝🦝🦝

This is a minor complaint but I hope it's also a simple fix. In both the Google Play Store and in F-Droid, Jerboa is listed as "Jerboa for Lemmy". But when you install the app, it shows as just "Jerboa". Raccoon also appears as "Raccoon for Lemmy" in both the Google Play Store and F-Droid but its name after installing is still "Raccoon for Lemmy". This means when I add the app to my homescreen, it appears as "Raccoon f..." because the name is too long to fit on a single line. You definitely need the "for Lemmy" when trying to find the app in the app store, but once the app is installed can you change the display name to just "Raccoon"?

Again, I know this is a very minor complaint. But if Jerboa can do it, I'm hoping it's also a very simple fix.

EDIT: Here's how Jerboa did it: https://github.com/LemmyNet/jerboa/pull/904

I tried enabling "Mark posts as read while scrolling" and then scrolled for a bit. But if I scroll back up, all the posts look the same as unread posts. I even tried clicking on some posts and coming back to the list (to explicitly "read" them) and they still look the same.

I'm used to "read" posts being "dimmed" in some way (grayer font color, darker card color). Is there any way to tell whether raccoon actually marked a post as read? I can't tell if this is a defect, a feature request, or if I'm doing something wrong.

This week I'm releasing the development build earlier because I'll be a couple of days away for work. Hope you enjoy it and let me know your opinion about the enhancements and new features and have a great weekend! It sounds a little strange said on Wednesday but... what a week, huh?

This week will be a busy week so I don't have much time, anyway I'll be working on the following areas:

• a screen with the list of licenses of all third-party libraries and resources used, plus a monochrome icon variant
• experimental support for background checking of inbox unread items (i.e. local notifications)
• fixes for a couple of bugs you have reported (e.g. zoomable image screen, full height images in compact mode, etc.)

Many thanks to everyone for your feedback, suggestions and help in building the community around the project! 🙇🙇🙇

Great app so far! I use it to browse without an account and it is smooth, lightweight and fast! I have no idea how to vectorize the current icon so I was wondering if people had ideas for or were interested in a themed/material you icon?

Edit:saw it was being added! You're awesome, thanks!

Today, being the first Thursday of the month, I released the new stable version with all the improvements and new features that testers have already been able to see in the past weeks. The user base is kind of stable, no review on Google Play and I have lost some stars on GitHub, so the outlook is a little negative... I'll continue working on the project every now and then but that's it. Thanks as always to all who reached out to me... and in the meantime L.F.E.T.

The 5 options there should be put somewhere else, it is very cluttered.

Might be similar to #263.

You can test it out on this post here.

Hopefully there is a quick fix for that.

In case anyone missed it, today I released the last pre-production release of March. There are many improvements to the Explore section which has been polished and can now be used to explore a whole other instance in guest mode (by selecting the "Explore <instance name>" option in the top right menu from a community or user detail).

Other features are:

• possibility to share images as files (as opposed to URLs);
• for moderators, the possibility to edit community metadata;
• search in subscription management.

Enjoy the weekend (depending on where you are it may or not be Easter) and stay tuned for next week's roadmap. Since I am planning to release a new stable version for the new month, don't expect many new features, unless you have new crunchy requests (but I haven't received any so far).

L.F.E.T. 🦝️🦝️🦝️

Presently when we open an image we get 2 options at the top. Either download or share. Share produces a link to share the image.

Can we have options to (a) share the link (b) share the image itself (c) share both? I am not sure if the last one is even possible!

Last week of the month, I should consider releasing a new production build for the beginning of the next. For the release of next week, you'll probably find the following new features:

1. a simplification of the Explore screen with better usage of screen space (and the possibility to subscribe on-the-fly to communities listed);
2. from the user detail and community detail you'll be able to open an "Explore instance" screen which is basically the Explore screen but locked to a local search on the other instance;
3. moderators will be able to edit community metadata (image, banner, sidebar, etc.)

In the meantime I'll continue with my chores (like writing tests, updating documentation, upgrading dependencies, etc.)

Yes, I know I should be releasing on Thursday but ten minutes more, ten minutes less who cares... So, that's it for this week. This version includes:

• UI improvements, especially font sizes and spacing;
• a new screen where you can see all the contents you have liked or disliked;
• a revised interface for moderated contents (which now has both posts and comments from your moderated communities in the same screen);
• easier copy from post title/text as requested by you;
• filter in comments from post detail, which was issue #40 on GitHub but I never had time to implement it;
• the possibility to set a default language for newly created posts and comments;
• other minor fixes and enhancements.

Stay tuned for what I'll be working on next week, as always L.F. E. T. 🦝️🗑️🦝️

Thanks as always for testing yesterday's release. For next week I'll be focusing on these tasks:

• feat: search in comments (requested here)
• feat: easier copy (requested here)
• enhancement: default language for posts and comments
• feat: add the possibility to search within local post of another instance (in Explore?)
• fix some bugs you have reported (inline images sometimes bringing to app crash, manage subscription layout, font sizes)
• as usual some chores (dependency updates, tests, etc.)

The updates in this version have been revolving around 3 areas:

• community management: you'll be able to save images in community-specific directories, override sort type for specific communities and filter posts inside communities;
• explore screen: you can now search for Lemmy handles referring to communities, a bug has been solved while refreshing the explore screen (once every 2 times it gave no results);
• UI improvements: drop downs have now a material design style, the advanced settings screen has now section headers, bar colors have been improved, etc.

More detailed changelog on GitHub. Stay tuned, before next Monday I'll be sharing the planning for week 3.

Tomorrow's release (March week 2) approaches and besides the possibility to store images on a per-community basis or the ability to set community-specific sorting, which were already announced, I have a small surprise for you that I hope you like: the possibility to search within a community.

The option will be available in the drop down menu in the top right corner of the app bar when you are opening a community detail and are not in guest mode. A search field will replace the header and you'll be able to perform a community-specific search as if you were in the Explore screen.

This is not an uncommon feature (Voyager and Eternity have it) but I thought it was nice to have and quite easy to implement even if the night before the weekly release.

Source code here. Until tomorrow, people!

There are really few of use and even fewer like to talk. Yet, I did not give up entirely the idea of creating a community around this experiment. Last month I closed the Matrix space (and all the rooms) because nobody interacted, but still I am seeing very low participation.

I am open to ideas/suggestions or even to abandon the idea of using some external discussion platform to host the community.

How can I subscribe to new communities with raccoon? I tried the explore feature with the filter set to all, but no communities are found. I tried multiple times to give my server the chance to fetch the remote community. I searched using the full address with a leading !: \!raccoonforlemmy@lemmy.world

This week I will be focusing on some small improvements, such as:

• possibility to specify custom image download locations (as requested on GitHub in #572)
• save sort option for specific community/feed type

plus I'll be working on some other bugs I collected in the issue tracker and continue writing the tests. So don't expect any big change, but rather a stabilization.

Would it be feasible to increase the minimum movement to start sliding a post left or right? I keep accidentally initiating the slide when trying to scroll up or down.

I also find some menu navigation requires what feels like too much precision or touching the text bounding box and not a space/button with the text in it. I mostly find this when navigating the long press to block a community from a post. It has taken as many as 3 tries and a different thumb attempt to have the press registered.

🦝️ of the Internet, it is Thursday so: weekly release time! This testing release contains the "Moderator tools" in the user profile screen, the possibility to specify ban duration a better handling of the unsaved changes in the web preferences screen, improvements for profile loading and account switching and other enhancements.

A special thank you to all those people who interacted here to suggest improvements or just reached out to provide motivation and support. Hope this is the seedling of a small community which is starting to grow and develop. There are few of us but... I like it here.

Always remember L.F.E.T.!

...

Weekly touch point from 🦝 dev! For next week, I don't see any new issues, so I will consider some of the tasks from my backlog and I will be adding more tests as previously announced.

So, the next "big" thing will be the Moderator zone, i.e. a centralized dashboard to make life easier for moderators in order to access:

• global list of report from all moderated communities;
• global modlog;
• contents from moderated communities.

I will add references to the code in comments as long as I progress during the following days.