This is great, thanks for this. I’ll give this a try later!
This is great, thanks for this. I’ll give this a try later!
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!
It’s a very valid question in my opinion and as is often the case with security, it really depends on your individual threat model and threat tolerance. As you said it seems pretty unlikely that a maintainer would install malicious code as they have a reputation to protect. And as mentioned by another commenter, even if you compiled the code yourself, unless you can audit code yourself you still have to just trust the developers. Personally for my threat tolerance, I do not see the risk as big enough to warrant the extra effort.
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
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
Off topic but could you explain a little on how you use a VPS to access your internal services? There’s a few services I want to open up but I don’t trust cloudflare and I don’t want to port forward.