It's great to see such cool FOSS options. Thanks for sharing this – super helpful!
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.
Based on the error message, perhaps this problem is related to this issue? The issue now closed, but it's not in the releases yet.