Non-cancer link: https://old.reddit.com/r/LocalLLaMA/ (though that won't work on VPNs now)
(I just got a little emotional because these are things we used to say on reddit and now we say them about reddit. How the mighty have fallen)
(I just got a little emotional because these are things we used to say on reddit and now we say them about reddit. How the mighty have fallen)
Did for me just now, although as of a week or two ago reddit has been blocking many of my attempts to access through a VPN old. or not. Usually need to reconnect about 3 or 4 times before a page will load.
I'm sure there are myriad browser extensions that will do it at the DOM level, but that's such a heavy-handed solution, and also lol I'm not putting an extension on the cartesian product of all my browsers on all my machines in the service of dis-enshittifying one once-beloved social network.
I can't imagine any type of Pi-hole setup which would be faster, seems like a "holding a hammer" kind of solution.
You could perhaps intercept the HTTP requests, but that would require decrypting SSL, so you'd have to MITM yourself if you wanted to do it at the network level.
You'd replace the DNS request for `reddit.com` to some device that intercepts the traffic. That device would redirect the HTTP request to `old.reddit.com` if applicable; static assets would be routed to `reddit.com`. I don't know how things like HSTS and certificate pinning fit into an idea like this.
Doing this at the device level is probably easiest. I've used Redirector [0] in the past and it works well.
Create a vhost for reddit.com, add reddit.com to your hosts file to point to the webserver (or setup a stub in the dns to the vhost webserver), and do a redirect to old.reddit.com on your webserver vhost.