You may need to log out and log back in if you are experiencing issues with upvoting, making posts as read, commenting, etc. In most cases, it seems upgrading to 0.19 invalidates the access tokens.

Right now, I can’t give you an exact timeline. The current state of the master branch (the nightly builds) is less than ideal. It will require some time to make it less buggy and sluggish.

I could, however, put together a minor release from the patches we already have there but building on the 0.1.2 release. This would include the new sorting types and instance blocking introduced in Lemmy 0.19.

The latest version of Eternity is compatible with Lemmy 0.19. You might need to log out and log back in, though.

However, the new functions aren’t implemented yet (e.g. the new sorting methods)

Yes, It’s on my radar. Basically, that’s the next “big feature” I want to work on after multicommunities. Hopefully, I can get some free time soon to actually work on these

It seems like some authentication issue. Perhaps you need to log out and log back in?

Don’t worry; the latest version of Eternity is compatible with the upcoming 0.19 Lemmy release.

As for the lack of updates lately, I am very busy at the moment with work/uni stuff. I might be able to spend some time on it during the winter break, but I can’t guarantee anything.

Yes, I am not sure how I missed this. It was not intentional.

This was an issue with kbin magazines. It is fixed in the nightly builds

Yes, I’m working on preparing multicommunities, which includes the anonymous homepage feature.

This reminds me of one of my older projects. I wanted to learn more about network communications, so I started working on a simple P2P chat app. It wasn’t anything fancy, but I really enjoyed working on it. One challenge I faced was that, at the time, I didn’t know how to listen for user input while handling network communication simultaneously. So, after I had managed to get multiple TCP sockets working on one thread, I thought, why not open another socket for HTTP communication? That way, I could incorporate a fancy web UI instead of just a CLI interface.

So, I wrote a simple HTTP server, which, in hindsight, might not have been necessary.

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?

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.

Great news! It looks like the MR to add the app has already been merged here.

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.