Wikiless - It was recommended here but I currently don’t see the point. As far as I can tell, you can browser Wikipedia perfectly fine without JS (I tried with Tor Browser on safest setting). Browsing through the site also does not require an account. No ads aren’t really a privacy enhancement, and Wikipedia isn’t a exactly full of ads, so this is not a concern. Finally, and I should mention this now that I’m still looking at the first option, “proxying” to another service isn’t necessarily a privacy enhancement, or even desired by default. People can use other tools (Tor or a VPN) if they want to hide their IP. With a frontend, Wikipedia might not get your IP, but the Wikiless instance is. Why do you trust the instance operator more?
Quetre - This can be considered, because Quora is notorious for blocking content behind a login screen. It would be interesting to look further into it.
Libremd - I don’t think this deserves a place on Privacy Guides at this point. The frontend doesn’t allow you to browse, and when you do replace imdb for the libremd instance for, say, a specific movie, you’re not able to click on something like an actor’s photo and browse further. It’s a static page with some info that someone could also get by using a search engine to search for a movie’s name. Perhaps in the future there will be a valid usecase for this, but I don’t see it right now.
Libreddit/Teddit - These are both being considered. The issue with Libreddit is that the developer is currently not working on the project. There’s a fork of it that’s relatively new and is an effort to keep the project alive. I have to evaluate these options and see which of the Reddit frontends it makes sense to recommend.
SimplyTranslate - Research needed.
Scribe - See above.
Neuters - I consider this too niche of a usecase. You can use Tor Browser, or you can use Startpage’s proxy mode to browse the site instead.
Beatbump - From their GitHub: “Beatbump is going through a major rewrite, so errors, bugs, and other problems may happen at random.” This may eventually be worth looking at, but we value stability and tend to not list alpha/beta software when we can avoid it.
ViMusic - This is an app that I’ve been using and testing out for a couple of days, and I like a lot of what it offers. I’ve also been looking at their tracker and like that the developer is opinionated and doesn’t accept all feature requests. Projects with a clear focus are more likely to succeed. While it does cache songs as you play them so that they can then be played offline, it doesn’t have a “make available offline” feature at this time, and the developer isn’t sure if they want to add that. I hope they do. Nonetheless, it can be considered once I’ve tested it a bit more.
Cloudstream - I’m not sure if this is a good fit for the site.