wafrn VS alternative-frontends

take a look to wafrn. it has some bad practices: I put most of it in the same module No auth guards I use async instead of rxjs have fun repo the web app

wafrn, a small social network

Oh boy youre gonna like my shitty project

use alternative privacy-focused frontends: https://github.com/digitalblossom/alternative-frontends

I use nitter and proxigram to query RSS feeds.

I use something similar to this, the only differences are because my use case is privacy protection and avoiding algorithmic feeds. I use the Redirector extension for Firefox so that it redirects e.g. Youtube, Twitter, and StackOverflow links to the corresponding alternative frontends Piped, Nitter, and AnonymousOverflow. You can find maintained lists [1] [2] of such projects and their instances. Mostly they are FOSS and privacy-respecting, and they have distraction-free frontends because it's a helpful coincidence of being ethical software.

[1] https://github.com/digitalblossom/alternative-frontends

for a full list, refer this: https://github.com/digitalblossom/alternative-frontends.

There are front end alternatives for major sites if you really need that btw. I use from time time to time Invidious when I want t o see a YT video for example. As for sites that require tracking cookies to work I simply stopped using them. If a given site requires the use of intrusive "necessary" cookies I just stop using it. I'm convinced is about priorities. If you quit a browser that is safe because is slow, well, you need to re-estate your priorities imho (not you, op, anyone ;) ).