• Steps To Reproduce:

1. Open the inbox tab.
2. Click on the profile icon on the top left corner and select the current account.
3. Click on the inbox tab.

• Expected Behavior: it opens the inbox tab with unread notifications.
• Current Behavior: Nothing happens.

So Summit for Lemmy already supports "advanced screenshots" letting you take screenshots of posts and comments with ease, allowing you to include any and as many comments as you want. However this doesn't work as well if the post or comments have animated GIFs in them. I'm working on a feature that will allow you to take an "advanced screenshot" but as a GIF so you can capture any video or GIF as well.

Changes so far

• Added a feature to "record" a screenshot as a video or GIF.
• Fixed a bug where links are invisible in conversations.
• Changed long tap on the header, expand button or the side to expand actions as well.
• Added option to mark a post as read/unread in the post option's menu.

The focus of this release is DMs. Direct messages have been difficult to manage and respond to in the past especially for message chains. This release cleans up the DM experience to make them much easier to use.

Full changelog

• Redesigned the DM experience.
• Changed messages in the inbox. Messages sent by you will no longer show up in inbox.
• Make it more obvious when loading in the inbox screen(s)
• Changed the "Mark as read" gesture to toggle the read state of the post. Eg. if a post is read and the gesture "Mark as read" is performed, the post will be marked as unread.
• Added a fade effect to the bottom screen when screens are stacked together. Eg. when viewing a post from the community feed.
• When viewing a reply message in the inbox, added a button in the context section to make it easier to see the post of the reply.
• Fixed a bug where the navigation bar does not highlight the correct item in certain cases.
• Fixed a bug where the open link button is visible when no image is shown in the post list.
• Fixed some bugs that occur when viewing a link to a Lemmy post of another instance.
• Fixed some minor bugs with people search.

v1.40.1

There were some dependency issues so I had to do a version bump. There shouldn't be any changes from the base release though.

v1.40.2

• Fixed a bug where images are not shown/loaded within direct messages.
• Added a full text editor to the send message input field. When sending a direct message, you will be able to tap on the full editor button to open the "advanced text editor" to make it easier to compose more complex messages.
• Fixed a bug where the post in the "context" section of an inbox message would have a random amount of whitespace at the bottom.

If I am reading the messages of my inbox, I get prompted with the post in collapsed state (A). If I want to visit the referred Reference I have to expand your Notification (ViewGroup B). At the bottom I am able to go to the comment posted.

Please add this Button (from bottom of (B)) to the left to the expand-Arrow on said view (state (A)) to avoid scrolling.

---

You should even be able to restrict the context of a scroll of such notification so that one can get the opened post scrolled to the clicked action (since you elected to context perfectly already). Though that may be inconsistent to clicking the name, instance or (not implemented) comment of the post.

It depends on the Context (when comparing A or B). If we are all PowerUsers, Implementation elected is obvious... Hard to document. Still requestiong a duplicate button bound in collapsed RecyclerView.ViewHolder :- )

---

I would be able to elect a suggestion more carefully if I could test it locally on my devices. I feel like you have engineered the most capable app. So thanks for this..

Hopefully you are not tracking my direct messages. Can't judge due to licensing ;).

For the Views of comments and posts you explicitly bound the former@latter.part to its own onClickListener. You didn't implemented that within anything in our inbox. Therefore I ask you to bind the nested RecyclerView when opening a inbox message - as well as its message itself - to the same interactions.

Sincerly, a happy user.

Making this post to track progress on the next release. Will decide on a title later.

Changes so far:

• Fixed a bug where the navigation bar does not highlight the correct item in certain cases.
• Fixed a bug where the open link button is visible when no image is shown in the post list.
• Changed messages in the inbox. Messages sent by you will no longer show up in inbox.
• Fixed some bugs that occur when viewing a link to a Lemmy post of another instance.
• Make it more obvious when loading in the inbox screen(s)
• Changed the "Mark as read" gesture to toggle the read state of the post. Eg. if a post is read and the gesture "Mark as read" is performed, the post will be marked as unread.
• Added a fade effect to the bottom screen when screens are stacked together. Eg. when viewing a post from the community feed.
• Fixed some minor bugs with people search.
• When viewing a reply message in the inbox, added a button in the context section to make it easier to see the post of the reply.
• Redesigned the DM system in the app completely.

Update

With how the release is going it's seeming very likely this release will focus on cleaning up the DM experience.

The current DM experience is pretty bad. Messages are littered everywhere and it's very difficult to follow a message chain. This wasn't high priority since it was assumed most users are not using DMs. However as other parts of the app becomes polished, DMs are suddenly the weakest part of the app.

The current minimum plan is to group DMs with individuals together into chains at the very least. Other improvements are still up in the air.

Unfortunately, designs of the DMs will probably be limited to what the Lemmy API can provide. For instance, I was exploring an email like approach where one item is shown per message thread however there is currently no API that returns only top level message threads. Instead you can only get individual messages. Of course we can still implement this on the client however it can lead to an excessive amount of network calls.

As an example, imagine a scenario where user A and B exchange a lot of message. Let's say they exchanged 1000 messages. Let's say the client is configured to fetch 50 messages at a time. Given this, if the user navigates to the messages screen the client will fetch 50 messages. The client will then group all 50 messages as a conversation between A and B. However since this is just one conversation, the client will need to fetch more messages to make sure there aren't any other conversations. This will repeat until all 1000 messages have been fetched. At this point the client is finally sure there are no other conversations and it will stop. This means that the client will need to make 20 network calls in order to load the messages screen which is pretty costly.

There are some solutions but they all vary in effort or usability. The easiest solution is to not collapse conversations in the messages screen. The downside here is usability as it would be difficult to look for specific conversations. The highest effort solution would be to group all messages on the messages screen and build a database on the client side that tracks all messages. By doing so, the first time messages are loaded might still be costly but subsequent refreshes should be relatively fast.

I'm still mulling over what to do here.

Update 2

I love you guys so I'm going to implement the best possible DM experience with no cut corners. It's going to take some time though.

Update 3

I think I can wrap this update up sometime this weekend. I think a release is possible by Monday (Aug, 19) if not earlier.

This update focuses on general app improvements and bug fixes.

Full changelog

• Added new image loading animation.
• Improved styling on collapsed comments. Voting on a collapsed comment will update the score and cause the score color to change.
• Fixed many bugs with the layout "list with cards". Specifically it was missing the voting buttons and the comments counter. This has been added. Several other fixes has also been applied for this layout.
• Fixed a bug where the header text of a post would be cut off when using certain layouts.
• Fixed a bug where the link icon would appear on a post even if the post does not contain a link.
• Fixed a bug where paragraphs within a spoiler block may not be correctly formatted.
• Support subscripts in markdown (forexample)
• Fixed a bug where opening. closing and opening the same post will cause the post to not be highlighted when the post is closed.
• Fixed a bug where sometimes you can drag a blank window from the right side of the screen.
• Fixed a bug where the progress bar when loading videos does not conform to the app theme.