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.

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

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

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

Paging reddthat admin @ticoombs@reddthat.com

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

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!

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.