The image viewer is supposed to let the image draw behind the system bars, covering the full display. The tap is supposed to hide/show the systembars, to imitate full screen behaviour.

On tap it just asks Android to hide/show systembars. So its quite strange that it behaves differently here for the status bar. Probably something to do with Android 14.

See https://github.com/user-attachments/assets/ba96831c-e515-4c92-b9f4-4c73f6277926

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

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

Solved this, should be fixed in the next the release

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)

Contoversial will be added in 0.19

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.

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.

Not a Jerboa specific issue

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

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

Deletes are not being federated

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