akesi_seli

Hi there, I decided the app is ready to see a first stable release after the project "relocation".

Here is the changelog of this version compared to the latest beta:

• fix: ripple effects (e.g. top bar titles, drawer drop-down button);
• fix: video rendering in timelines and attachment detail;
• feat: button to reveal sensitive images in timelines;
• enhancement: update "Saved" label for bookmarks;
• enhancement: update font scale factors;
• enhancement: change default name of settings JSON when exporting;
• chore: dependency updates (most notably, Compose Multiplatform 1.7.1);
• chore: update CODE_OF_CONDUCT.md, SECURITY.md and PRIVACY.md.

Hope you like it, have a nice rest of the weekend and remember to #livefasteattrash 🦝

In the Friendica/Mastodon application I am working on, while it was in alpha and beta stage, I have adopted the Sentry SDK for crash reporting, which works very well on Kotlin Multiplatform and is easier to setup than other (closed source, capitalistic and ugly) alternatives.

In doing so, I made an interesting , while I was submitting the app to open source stores (IzzyOnDroid and F-Droid), that if crash reporting is opt-in (i.e. disabled by default but it can be enabled in the app settings) the app is acceptable for their policies because users have to give their consent to enable reports (which are a form of tracking).

Considering there are users complaining about Raccoon for Lemmy crashing (e.g. while creating posts/comments) and that being a "deal breaker" (understandably!), my question is: would you accept it if I included Sentry, making it opt-in? In this way you could enable it just if there is some reproducible issue and turn it off whenever you like (restarting the app is needed to make any change to initialization effective).

Opinions are welcome, I will not do anything unless we decide together, especially because adding this service implies extra work for maintainer(s) 🤣

Hi raccoons of Lemmy! A new version of the app has been released and is available to all testers!

Here is the changelog:

• fix: text style used for links in Markdown (which appeared larger than the rest of the paragraph);
• fix: restore UI state after closing default sort bottom sheet in community detail;
• chore: improve readability of vote actions with arrow icons;
• refactor: migrate image loading to Coil3 (and remove obsolete Kamel library on iOS);
• enhancement: add new instances to default list;
• refactor/feat: migrate video player to Compose Multiplatform Media Player and make it possible to open videos full screen;
• refactor: migrate web views to Calf;
• enhancement: add Atkinson Hyperlegible font instead of Charis SIL;
• chore: review inter-item spacings in setting lists, modlog and side menus;
• chore: update user manual (new screenshots, new sections, table of contents and internal links);
• chore: update several dependencies.

Remember to have fun and #livefasteattrash

I would like to introduce a new font in the next version, with a particular focus on readability, in order to make the app easier to use.

My choice would be the Atkinson hyperreadable font by the Braille institute, which I personally use in other apps too because it gives my eyes some relief.

However, the APK size of the app increases with every new resource, so instead of just adding a new font I would like to replace the least used of the current ones.

Answer in comments to tell me what you would like to be removed. Thanks as always and #livefasteattrash

Hi everyone, first Wednesday of month so it's "Ask Me Anything" time. As usual, post your questions in reply to this post and I'll do my best to answer.

Forever L.F.E.T. 🦝🦝🦝

Thanks to all those who reached out to me to report bugs, here is the new version containing the following changes:

• fix for block action from timeline;
• restored user manual URL;
• fix for multi-paragraph quote rendering;
• font size and typeface are visibile again in their selection bottom sheets;
• migration towards Material 3 modal bottom sheets is finally over (this was quite a hard and time consuming task which drained resources from other activities);
• several dependency updates.

Hope you enjoy it and #livefasteattrash 🦝🦝🦝

Hi folks, a new beta has been released today! It contains some updates to the "App information" dialog (e.g. the link to the new Matrix room) and a fix for the selection of the feed type in the home screen, which incorrectly opened the instance selection.

I'm continuing the migration of all bottom sheets to Material 3 modal bottom sheets, there are just 9 left for the refactoring to be complete.

Thanks to everyone for continuing using the app, have a nice weekend and remember #livefasteattrash 🦝🦝🦝

A new beta has been released this week, here is the changelog:

• fix bug which prevented navigation after a long press on a bottom sheet item;
• add cancel action to the text toolbar to make it easier to close it;
• continue the revision of bottom sheets in the settings and advanced settings screens;
• several dependency updates, most notably Compose Multiplatform, so now all pull-to-refresh indicators have a matching material 3 style as well as MaterialKolor palette generator with a more playful theme if you use a custom theme color;
• restored the project website and manuals.

Let us know your feedback, feature suggestions, comments or anything you want to share. Given the app has no tracking whatsoever it's very difficult to understand whether there are actually people using it or not, and how much effort it is worth to continue the project.

Trashy yours, L. F. E. T. 🦝🦝🦝

Raccoons of the Lemmyverse, we're back! A new beta version of the app has been released, as promised in the last AMA (it was the next internal milestone).

Let us know what you think about it, you'll notice that there have been several layout improvements since the last version, e.g. bottom sheets have a new style, clickable areas now show the ripple effect, etc.

Hope you all enjoy it and, as always, L.F.E.T. 🦝🦝🦝

Welcome to the third session! For the rest of my day, I’ll be looking for replies to this thread and will answer your questions. If something remains unanswered, replies can be posted even during the following days.

There are no rules - “anything” is anything! Feel free to ask development questions, future plans, or things completely unrelated to Raccoon.

Ad, as always: Live Fast, Eat Trash 🦝🦝🦝

Welcome to this session! For the whole day I'll be looking at the replies to this thread and answer your questions. If something remains unanswered, replies can be posted even during the following days.

There are no rules, "anything" is anything! Use a grain of salt and a little bit of irony, though. Also, I would really like to hear something in your native language on your first comment: it can be a greeting, the question itself, a joke, an insult or anything crosses your mind in that moment. Have fun!

The last message before closing the old community stated that, after a break, it would be decided whether to restart from an existing fork or to recreate a repository in an anonymous account. We have decided to do both things, taking the most active fork (which was updated to the latest commit), transferring it to a neutral organization and using that as a starting point.

The biggest limit of the previous approach, as emerged on August 1st, was that even if the app was presented as a “community project”, its ownership and all the decision making process (as well as the majority of the development heavy-lifting) was concentrated in the hands of a single person, which could take questionable decisions due to personal contingencies. Being a human and having a single point of view, errors can be made and reactions can be disproportionate with respect to their causes.

In order to prevent this from happening again, the new organization will have a more open, transparent and community-driven approach, and everyone will have to participate more in the decision making process, so that ownership is shared as well as responsibility.

The new repository will be available here and we are working to restore everything so that a new development release will be available soon and can be installed from GitHub (in order to have a new Google Play account more time will be needed).

Moreover, in order to make sure everyone’s voice is listened to, there will be periodic AMA sessions once a month in this very community, using the [AMA] prefix in the post title. The session will be held the first Wednesday of each month, so the day after tomorrow will be the first one.

We hope you are convinced that mistakes like last week’s one will not happen again and you’ll participate in this new stage of the journey.