@raccoonforfriendicaapp version 0.4.1 has been finally released! I was waiting to fix a couple of old issues but I realized I was keeping people waiting too much since almost 2 months had passed since the previous stable version.

If you were on the latest beta, the only new feature is the possibility to see in every timeline the "source platform" each post is coming from (Friendica, Mastodon, Lemmy, Misskey/Sharkey, Pleroma/Akkoma, Kbin/Mbin, WordPress, GNU Social, Pixelfed, Peertube, GoToSocial, Diaspora, generic ActivityPub and more are coming).

If you were using 0.4.0 there are a ton of improvements, the most important of which are:

  • feat: add per-user rate limits;
  • feat: suggest hashtags while typing;
  • feat: swipe navigation between posts;
  • feat: exclude stop words from timelines;
  • feat: add shortcuts to other instances ("guest mode");
  • feat: open post detail as thread;
  • feat: post translation;
  • feat: followed hashtag indication;
  • feat: show source protocol for posts;
  • enhancement: support for embedded images.

This version is also available in the production track on Google Play, so you don't have to participate in the beta program any more to get it.

Let me know what you think about it, enjoy your weekend and as always #livefasteattrash

#friendica #friendicadev #androidapp #androiddev #fediverseapp #raccoonforfriendica #kotlin #multiplatform #kmp #compose #cmp #opensource #foss #procyonproject

@dieguitux8623 @raccoonforfriendicaapp Yeah, filters! 
Btw, is it intended that Raccoon is not restorable with Neo Backup?
After restore it crashes after launch. Not sure why, didn't have time to have a look at logcat.
@johnassel no, not intended... I think you discovered a "feature" πŸ™ˆπŸ™ˆπŸ™ˆ if you manage to read the logcat it would be helpful. Since it crashes at startup I don't think enabling bug reports with Sentry will produce anything beneficial, because it may happen before SDK initialization.
@dieguitux8623 Alright, I'll have a look at the logs when I find time.
@johnassel Ok seen it. It is due to encrypted shared preferences (used to store on device your auth token). It fails to open after you restore the app, probably due to failure to decrypt them because the key changes when you reinstall it. I'll investigate more to see if there are workarounds.
@dieguitux8623 Maybe something like a check if the token is decryptable before using them. If not, one has to login again.