It appears API rate limiting has effectively killed these alternatives. You essentially get nothing but “Too many requests” 429 errors.
Lemmy sadly does not have the active niche news and discussions I want. But now nothing can be read without going to Reddit. I hate Spez
Im not sure I agree here, I host my own libreddit instance and I have no issues with rate limits. I would highly recommend going your own instance if you can
I have checked multiple instances, and everyone has the same trouble. And I have no idea how to host my own instance.
It’s probably an issue with the instances having too many users instead of libreddit being broken. It might be worth trying to find a smaller instance or trying to host your own. Hosting libreddit was my first step into hosting services using docker and it was surprisingly easy
Nope, it’s the API changes: https://github.com/libreddit/libreddit/issues/840
I can’t test mine right now as it’s only accessible on the internal network and I’m not home. But it was working when I last used it a few days ago, I think it might be a combination of the the api changes and public instance being overloaded with too many requests and hitting the new api limits. When I can I will test my instance and let you know if it still works, If it does I would recommend that you do look into hosting your own as it will provide even more privacy than a public instance and will lesson the load on the public instances. Feel free to ask me any questions about hosting libreddit (or teddit) if you do decide to host it yourself!