testAccount

By default the theme is set to dynamic. Older Android versions don't support this, for this we default to a set theme. Previously that was pink theme now it is blue theme. (I preferred it)

But you can always select which theme you want.

Illustrates the possibilities https://github.com/MV-GH/LemmyBackwardsCompatibleAPI/assets/67873169/62d7f6d4-be1e-4f71-94dd-6954e090379d

There is actually a title (requirement from lemmy) but its just whitespace so that wasn't very visible. Not sure what to do about this scenario. Seems rare to be actionable

There are multiple bugs though:

• the whitespace in the footer actually works as a collapse children comments instead of opening the post
• All the background should be tapable (header is missing this)

Thanks for the feedback

Yeah the admin should be made aware of this

Paging reddthat admin @[email protected]

np

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

I see what you mean, originally this was intended as such but I understand that this isn't the wanted behaviour, it is also inconsistent with the other modes where tapping the empty space is opening the comment. I'll open up a issue for this. Thx for your feedback

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

It's called post action bar mode

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

Are you on 61 or 62 ?

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

In 61 a migration is borked, this caused some appsettings to be switched around. So it enabled the setting Show content for collapsed comments and disabled another one.

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!

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!