However, I do feel that these issues need to be resolved at the earliest because right now is the time many users are leaving reddit or looking for an alternative. If the situation arises that the issues that the community faces while using lemmy are not fixed in timely manner, then new users might simply decide to not stay here very long.
Yeah, I think that this is a big reason why the developers have been quite busy pushing for version 0.18.0, which has a significant number of fixes. But the reality is that Lemmy is still in a very early development phase, and I expect that bugs will continue to show up for a long time....
To address your points:
I’m unable to subscribe to some communities. With some of them I was successful after I k interacted with them, but others like technology or android communities are still pending.
This is a known issue that affects Lemmy: https://github.com/LemmyNet/lemmy-ui/issues/1315 I think that the message appears but that the subscription does go through. But correct me if I am wrong, I am interested.
after viewing a post, when I click back it often takes me back to the top. Facing the issue on both the web page and jerboa app
I have not experienced it myself, so I can't help you write this issue myself. But if you know how to reproduce this effect, it would be good to open an issue, as I have looked through the issues and I do not see this one being reported. (Lemmy-ui issues, Jerboa issues)
sometimes, mander.xyz is unaccessible. The webpage gives an error that such a page doesn’t exist while other communities still show up. Not sure why this is
This one can have a few different explanations. Here I posted about an example of a case in which I may have managed to track the source: https://mander.xyz/post/771616
In cases like this one, this is a function of Lemmy's performance and the hardware in which it is hosted. There is still a lot of room for optimization in both fronts. At the moment, the hardware in which the instance is run is well above what is needed for regular use. It is sudden spikes in RAM usage that can cause the instance to blip, but I need to understand these spikes better before I can fight them. I see that other instances suffer of these too, so I suspect that optimizing the performance of Lemmy is the more significant way to progress towards stability. But I will also work on hardware and see if that helps.
Other explanations can be that I will sometimes reboot the instance - for example, if a user asks me to make a small change to the code, adding a theme, or for upgrading the version. But these are rare and short-lived interruptions, and I try to do it during times when I see low activity in the site, so it is not so likely that this is the reason. An exception may have been a few minutes ago when I updated to version 0.18.0-rc.6, and there was an unexpected delay due to a change in a configuration file.
the main feed is still a mess. I have to visit the subscribed communities to get any real content from them, but the subscribed feed either shows old content or just spams from a few of them.
The sudden spam of posts is quite an issue. I have updated to the newer version, and I hope that this problem is fixed now. Unfortunately, I can already see that updating to the new version brought with it some new problems too...