Thunder App Nightly @lemmy.world darklightxi @lemmy.world 7mo ago

[Pre-release] v0.5.0-1

github.com Release v0.5.0-1 · thunder-app/thunder

This is the first pre-release for Thunder v0.5.0! As always, this pre-release version contains many additions, changes, and fixes. Be fully prepared to know that these pre-release versions may cont...

This is the first pre-release for Thunder v0.5.0! As always, this pre-release version contains many additions, changes, and fixes.

Be fully prepared to know that these pre-release versions may contain major bugs which could cause Thunder to crash or behave unexpectedly.

Important: Your feed settings (default feed type and sort) will now be based on your Lemmy account settings. The previous feed settings will now ONLY apply to guest accounts. As such, you may have to re-configure your default feed type and default sort type.

Some notable changes to test out:

The Account Settings has been updated to include even more settings that are synced to your Lemmy account. You can change your display name, profile bio, email, default feed type and sort, and more! Additionally, the user/community/instance blocks have been moved to their own dedicated page for easier management.
Experimental: You now have the ability to view a post as a different user. You can access this option by tapping on the three-dot menu within a post, and choosing "View post as a different user". When this happens, you temporarily switch accounts and can perform actions and even comment on the post as if you were that account.
You can now set custom labels for users which allows you to append a note to a given user. To access this feature, long press on a comment and select User -> Add User Label.
Groundwork is being laid out to improve the performance and reliability of the post page. This new experimental post page is locked under the new experimental features toggle. While this is not yet complete, you can test out the new post page by enabling experimental features in the Debug settings page.

The full list of changes since v0.4.0 are mentioned below. As always, if there are any bugs or issues, please submit a new GitHub issue.

Additions

Added new experimental post page by hjiangsu
Added ability to create links to settings. by micahmo
Added account birthdays to user chip by micahmo
Added ability to view entire post as a different account by micahmo
Added ability to import/export database by micahmo
Added support for custom user labels by micahmo
Added post/comment language metadata by micahmo
Added additional account settings by hjiangsu

Changes

Disabled account switching when editing post or comment by micahmo
Deferred loading image dimensions when viewing image preview by micahmo
Decreased layout jank from images within comments, and improved image error states by micahmo
Removed page scroll animation when switching between bottom navigation items by hjiangsu
Moved experimental push notifications under experimental flag by micahmo
Improved parsing of video speed setting by micahmo
Improved link sharing for images/video URLs by micahmo
Show placeholder icon for posts without thumbnails by micahmo
Allow snackbars to be closed on action by micahmo
Added more push notifications debugging by micahmo
Removed images from push notifications, improved UnifiedPush logic by micahmo
Extended keyword filters to URLs by hjiangsu

Fixes

Fixed superscript/subscript parsing edge cases by micahmo
Fixed image overflow when rendering inside a spoiler tag by micahmo
Fixed issue where optimistic voting would not reflect upvotes/downvotes properly by micahmo
Fixed post text preview showing raw markdown by hjiangsu
Fixed dialog button alignment, disable autocomplete suggestions for user labels by micahmo
Fixed snackbar positioning when opening/dismissing keyboard by micahmo
Fixed mark post as read when previewing media on 0.19.4 by hjiangsu

Misc

Fixed macOS build errors by hjiangsu
Removed javaToolchain binaries by hjiangsu
Removed push package Android dependency by hjiangsu
Adjusted modBan localization string by micahmo
Misc: update PR template by hjiangsu

3 comments

Important: Your feed settings (default feed type and sort) will now be based on your Lemmy account settings. The previous feed settings will now ONLY apply to guest accounts. As such, you may have to re-configure your default feed type and default sort type.

IMHO this feels like a downgrade, I always enjoy the flexibility of having whatever sort fits better for me, for example I go with my subscribed lists in a top 6 hour sorting as default, if that was my global default, each community I enter will display no posts at all (depending of his active the community is), that is why I always put that sorting in scaled or hot, to show me something, I hope we can still get different sorting types per communities.
- Hey! I think there might’ve been some misunderstandings I would like to clarify.
  
  In the previous versions (v0.4.0 and below), the in-app setting for default feed type/sort was also applied globally for all feeds (e.g, subscribed, local, all, and individual community feeds used the same sort type). In this update, the same thing applies, except that it’ll use your Lemmy account’s default feed type/sort instead of the one configured within Thunder. The main reasoning is to allow your Lemmy settings to sync across apps!
  
  I hope we can still get different sorting types per communities.
  
  Definitely! There are plans to allow for custom sort types per feed/community mentioned in this GitHub issue. When this feature eventually gets implemented, that setting will take precedence over all other settings if (that makes sense). Once this is implemented, the order of precedence would be:
  
  Sort type of individual feed/community (if enabled)
  
  Lemmy account default feed sort type (when logged in)
  
  Thunder’s default feed sort type (for guest accounts)
  
  Hi, thanks for the reply, yeah I forgot to mention that in the current version there is no way to sort out per community, I am glad there is a ticket for that!
  
  What I wanted to mean was that I prefer to handle that per app basis (and then per community), but if we get to sort out per community as mentioned before then it should be all good for most users :)