UPDATE: Fixed this issue here.
Yes, it loads the full size of the image instead of scaling it down. It's an old issue that I need to fix. It has been reported here.
I agree. This would be a cool addition
The app should make use of Lemmy's cross-posting API instead. I should create an issue on Codeberg for this functionality as well.
Ohh no. It seems I've broken it somehow. Could you please open an issue on Codeberg for it?
I haven't removed those options. I'm hoping I can get that feature ready for the next release. I have a somewhat working proof of concept implementation ready and I have a few ideas to improve it.
If you want to follow the progress you can check out this PR: #209
Sure thing! I worked on merging changes from Infinity to Eternity, and one of these changes was actually this very thing. Implementing this by itself isn't too hard either, and it would help improve the usability of the app.
I've just realized that the reason why I couldn't reproduce this issue is that I've used Lemmy redirect as the link handler. If I set it to Eternity, it works as described in your post.
I haven't experienced this myself. Does your system show an "Application not responding" message?
I think it's most likely because your instance is trying to fetch the post for you. Perhaps it would be a good idea to add a loading screen of some sort to indicate that something is happening.
I discovered a channel called 'Just Alex' awhile ago, and I've binge-watched most of his videos. He makes videos about a variety of activities he engages in. For example, two years ago, he started beekeeping as a hobby. In these videos, he shows the progress he has made since then, taking care of his bees and harvesting their honey.
He also has videos on collecting mushrooms, growing crops, and traveling around Europe.
What I like about him is how calming his videos are and the amount of effort he puts into making them interesting, without resorting to clickbait content.
In the Codeberg issue, someone mentioned that disabling the "Respect community recommended comment sort type" option fixes the issue. Is it enabled on your end?