@idunnololz
@lemmy.worldSo 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
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
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
Making this post to track progress on the next release. Will decide on a title later.
Changes so far:
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
Decided to post this here since this community isn't very active :(.
I had a blast with Swarm overall. It's an excellent game mode.
I cleared Aatrox in the order Riven > the rest in order that they appear in the selector. I attempted it with full upgrades + lv 10-20 anima power (don't remember the exact number) with the reroll behind "kill 40 elite monsters) still locked. I'm fairly certain you can attempt it as soon as you have full upgrades.
Changes so far:
Edit
I must have been really tired last night because I accidentally posted this as a release when it's a WIP release. Fixed.
Update
I'm moving the fixes here into 1.38.1 instead.
This release adds the option to offline a post feed, giving you the freedom to browse while offline. The use case here is if you know ahead of time you are going to be offline you can download a feed beforehand and read it later.
This release also implements several user requests.
Full changelog
v1.38.1
v1.38.2
v1.38.3
Hello everyone. I just wanted to announce that it's been over a year since I started working on Summit (I started on June 13th, 2023). This is going to be a quick post as I am still busy with real life stuff but I wanted to commemorate this event.
I wanted to thank the community for the support and also for all of the feature requests, bug reports and the translations. The app has grown tremendously in just a year and I'm excited for the projects planned this year.
Thanks everyone.