akesi_seli

I am going to (finally) move again the localization of the app to Weblate, just like before the project changed ownership this summer.

Considering:

1. there is a number of messages for the free tier which is shared with the other app;
2. in order to be compatible with Weblate, resource files have to be converted (manually 😅);

I am planning to remove some of the least used languages: Arabic, Bulgarian, Czech, Danish, Greek, Esperanto, Estonian, Hungarian, Croatian, Latvian, Lithuanian, Maltese, Norwegian (both variants), Dutch, Romanian, Russian, Slovakian, Slovenian, Albanian, Serbian, Swedish, Toki Pona, Turkish… based on the fact that nobody ever reported translation errors (which are there).

Does anyone have any objection? I can add one or two more if you are using some of them (but you've been very silent indeed if you do). All the other languages which have not been mentioned in this list will be preserved.

Raccoons of Lemmy, as promised in December's AMA session, version 1.13.3 has been published. Here is the changelog:

• feat(app): support for opening posts and comments;
• fix(postlist): image height;
• fix(zoomableimage): high resolution image, loading state and action buttons;
• fix(createpost): autofill empty message;
• refactor(di): improve dependency injection;
• refactor(build): define and apply Gradle convention plugins;
• chore(deps): update dependencies;
• chore(qa): add more unit tests.

Enjoy the rest of the week and – as always – #livefasteattrash 🦝

Hi everyone! Sorry, I forgot about last week's "Ask me anything" session, so let's use this post as usual: you reply with questions and I'll answer them.

Moreover, I would like to give you some news about the project roadmap. I did not forgot to release a stable version, actually 1.13.3 is expected by the end of the year. In the meantime I've been focusing mostly on technical improvements, refactoring and code cleanup. For example I made dependency injection and gradle scripts much more maintainable, and I've been fixing a couple of issues that you reported.

Once I'm done with some more bugs (e.g. the ones concerning images) I'll be releasing, so don't worry. If some of you are willing to test the beta releases, you are more than welcome, thanks.

As always #livefasteattrash 🦝🦝🦝

Today a new synchronization job has run and the app has been imported! 🎉🎊🎉 I know it may not mean much to you, but for me (after more than a year for the first build attempt) this is a great achievement! I had lost hopes but, since I was starting the submission again for the "twin" project Raccoon for Friendica, I thought it would cost little to try again. And the idea proved successful!

If you are wondering what the root cause of the issues was last year, builds were not reproducible due to a l10ns plugin. F-Droid maintainers told me so I proceeded to remove it and find another way to read localization files.

Another "infrastructure" news is that I've set up a cool code coverage (Kover) plugin to measure how much the code is covered by unit tests and upload the reports to Codecov to see charts about how the metric evolves.

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