Contoversial will be added in 0.19

It's just hasn't been added yet. For that feature it would have to continuously poll in some interval in the a background for each account. Since the websocket API is removed.

That's a lemmy bug, nothing to do with Jerboa.

See https://github.com/LemmyNet/lemmy/issues/3588

Deletes are not being federated

Not a Jerboa specific issue

Some quick unrefined feedback (my remarks, no bad ill intended):

UX:

• It takes up a lot screen real estate without giving much info back:
  • Each posts displays: Title, username, communityname (twice), communityinstance, embed preview or post body, What Jerboa now displays as info in card layout: Community(icon/name/instance), User (name, icon, bot, mod), Total score, (up/down)votes, post title, post body/ post preview, time posted/edited, read/unread, pinned, deleted, featured, saved, already (upvoted/downvoted), total comments and new comments
• Community name and username are bit too small, hard to read, makes touch targets very small thus hard to hit
• Title fontsize too big, long titles will reap havoc (And believe me they can get long, especially the mastodons federated posts as it includes a link each time)
• No user actions buttons,
• to reiterate, takes up lots of precious screen real estate. (It's why current doesn't have padding between posts, only when needed). It's tough to balance: giving loads of information in easy to digest format. Its why currently it uses lots of assumptions, lack of some information can give you more, (ex: doesn't show upvotes/downvotes if it are all upvotes, community instance not included if its your home instance )

UI:

• Don't like the upvote downvote , too big

Interesting filter prototype at the top there? This scrolls with the feed I assume, so once you scrolled a bit and you want to change the filter you have to scroll all the way up again? And if it popups like the topbar, then it would take up more than 10% of your screen each time

UI/UX Design is hard, definitely what I struggle the most with while contributing to Jerboa. UI wise you can't please everyone ,ppl have preferences. (The real reason why full search + filters isn't implemented yet, haven't had the time yet to prototype it, which is the biggest time sink, the actually functionality is rather simple)

Jerboa now uses a different library for the imageviewer which by default zooms until a certain size e.g. you can zoom a lot more in bigger images. I ll take a look if I can remove this limit. Previously it was actually limited to 2x.

It already adds the instance to community names in the feeds. For communities local to your account they are not displayed.

Its bug in listingpostmode. We ll be fixed in the next release. The card post modes show it properly

Solved this, should be fixed in the next the release

https://reddthat.com/nodeinfo/2.0.json

Reddthat instance doesn't have the correct version set in their nodeinfo. It is empty, this is important for federation (and for Jerboa to know which API implementation that it needs to use). Now I don't know if this is a Lemmy problem or just a problem with just that instance. But Jerboa behaves as expected

How it should be

This option has been reworked in Lemmy 0.19.4 because of that Jerboa no longer supported the old option.

I have added a PR that restores this functionality. https://github.com/LemmyNet/jerboa/pull/1544

Alright, looked into it. There was indeed a bug where it did the initial posts request by page and the subsequent by page_cursor. But this has been there for a while. Pre 67 we used to deduplicate every post returned by Lemmy. So it was masking that bug. I didn't think the deduplication was still necessary with page_cursor, so it was removed. If it still frequently happens after this fix. I'll add it back.

Paging reddthat admin @ticoombs@reddthat.com

This is definitely a bug, can you make an issue on github for it.

We are aware, it has not made it into this release yet.

In 61 a migration is borked, this caused some appsettings to be switched around. So previsously if you had custom tabs enabled, this would enable the prevent screenshots setting.

Now I fixed this, so this means those who changed them will see them swap again. And those who haven't upgrade yet won't notice anything. There should be release tomorrow which address all the bugs introduced in this update. Sorry for the inconvenience!

Could you make an issue for the crash with the logs?

It is an option that you can disable in the settings.

Are you on 61 or 62 ?

There is a button to mark as read, aswell a mark all as read button.

It's option in app settings, it was reset.

It's called post action bar mode

There is a mark read on scroll option, that marks every post read that you scroll past

It should still be there, can you go in the settings disable the show navigation bar setting, and check if it now appears? If so then it hidden behind the navigation bar. Which should be fixed in the next release

Pre 0.0.60, the rules for showing the votes in arrows were -> show scores setting enabled + and if there are downvotes

Now with 0.0.60 Dessalines reworked how the votes are displayed.

Modes (all in header):

• Display full -> show score and downvotes
• Display score + upvote ratio
• Display score
• Hidden

They will be configurable once the setting is persisted.

I have proposed to add a Display votes in arrow setting (Old behaviour)

We will see what comes from it.

Go to user settings and disable show read posts, note that this will also hide read posts in the community, saved and profile where the latter two are fixed but they are not included yet in lemmy 0.18.4

Can you not use google talkback with Jerboa?

Jerboa uses Jetpack Compose as toolkit instead traditional Views system that most apps use. The problem lays at core of a textfield component. It affects every app that uses this toolkit. And we can't fix because it would need to be fixed at very low level, we don't have access to nor domain knowledge about.

Where do you suggest we should place it?

Jerboa will support it once there is support for it in the API, This support will most likely come with 0.19 see https://github.com/LemmyNet/lemmy/pull/3869

Make GitHub issue with full logs

Jerboa uses Jetpack Compose toolkit, instead of traditional Views approach. It is not mature yet and the source of many of these problems you are experiencing. It works well with Gboard but not so much with other keyboards.

• Weird behaviour on text removal on OASP keyboards or derivatives https://issuetracker.google.com/issues/294102838 https://issuetracker.google.com/issues/221636606
• Or this one where when you are typing your text starts getting behind your keyboard https://issuetracker.google.com/issues/266094055
• Or this which causes stuttering behaviour in some scrollable contents https://issuetracker.google.com/issues/250632404

The biggest performance changes should be from 0.0.56

Due to a compound of factors:

• Upgrade of Jetpack Compose, the toolkit we use for the app, they have done some optimizations

• Stability config change (Basically we tell Compose these elements are stable)

• More memozation of function calls

Those factors lead to that we do a lot less recompositions now. Which means that that each frame we do less calculations, "keep the same UI element as before", it is smarter at about detecting elements that stayed the same and should not be recalculated. So each frame is cheaper and it can do thus more per second

In 0.0.60 I have updated the baseline profiles (It ships the app with AOT bindings, instead of which you would get after a week from release on the playstore)

Google does some amazing work, it just takes them a long time. Once this patch lands we should see more optimizations https://issuetracker.google.com/issues/241154852

I also recommend list/small card view, if you prefer the feed to not jump due to images loading in. At some point i'll refactor some infra so that I can Image and post preload feature out. So that it should be able to instantly load those images. But that is quite deep in the backlog.

Can you check if autoPlayGifs setting is enabled?

There is currently a bug with our image viewer that it seems to use imageloader that is set on the application level (which is controlled by that setting) instead of the one that is passed into it(which has it always enabled).

You can selectively hide any of the scores in the account settings .

We cannot solve that issue on our end. It is a problem with the toolkit that we use, see https://issuetracker.google.com/issues/294102838

This is already fixed, it ships with 0.0.48

Make sure you have 'show scores' enabled in the settings.

There is a loadingbar below the search that loads when it is searching

Preferably you report this on the issue tracker. But here is fine too.

Which version of Jerboa do you use? settings > about

And on which screen (Home , community, inbox, ...) do you have this? And do you have it as soon as you press the sort by icon? or when you select a sort? And if so which sort?

What Android version?

I have not been able to reproduce this problem.

In Lemmy 0.19.4, scores were reworked. So that you could individually pick which score you like to see (upvote, downvote, total, ratio)

Before this this option its behaviour was to disable every score type. Now it just hides the "total". With Lemmy 0.19.4 they did a poll to see which scores are the most popular and should be the default. Upvotes + Downvotes won. So show_scores is now by default false.

Currently our setting division ('Account settings' vs 'look and feel') doesn't make much sense. But 'look and feel' is all the settings that are stored on the device. Thus apply to all accounts. Account settings are settings we retrieve from Lemmy and are different per account.

So that brings us to the listingviewmode. That shows the total_scores but since its disabled, it is hidden. I'll probably rework it so that it shows the upvotes if 'shows_scores' is disabled.

There is a PR in works for that and that one allows you to disable it too.