browservice VS retro-proxy

Browservice - proxy but goes one step further and renders the page and actually only sends back a clickable image to the browser on the old machine. Almost like screensharing.

I have a [Browservice](https://github.com/ttalvitie/browservice) server set up for the faster machines, which basically streams images, and a [retroproxy](https://github.com/humbertocsjr/retroproxy) service for the slower machines :)

Original iMac G3 (the very first) running Mac OS X 10.1 and Netscape 7.01. The magic comes from this program : https://github.com/ttalvitie/browservice

Browservice may be suitable if you have to use IE6 and you're OK using a proxy system.

"browservice" will render web pages server-side and then deliver them to your browser as an image with simple javascript.

It works in virtually all "old" browsers and can be very useful for older computers.

https://github.com/ttalvitie/browservice

TL;DR: Read the entirety of Readme.md (it's at the bottom of https://github.com/ttalvitie/browservice). If you still have specific questions, i'll try to help.

Check out browservice; either run it on your host, or in another VM.

A 4th gen i7, the VM gets 2.3 GB, but I've done similarly stupid stuff on an AMD Athlon 64 (sluggish but usable, 720p YT dropping frames but watchable). Browservice running in a VM to serve XP's IE8 is another fun Goldbergian trick.

https://theoldnet.com/ https://github.com/tenox7/wrp https://github.com/DrKylstein/retro-proxy

Retro-proxy is the biggest contributor. It handles https to http, strips out javascript and css, resizes images a bit, and minifies html. It helps a lot.

Net traffic is being proxied through retro-proxy to handle SSL and minifying some of the content. Details of the in-house 'ISP' I'm using can be found here.

I have Linux computers and a Windows 10 mothership and have looked at https://github.com/DrKylstein/retro-proxy but there's very little documentation and I can't even tell if Retro Proxy provides a proxy address, let alone makes it available to the DOS machine.

Also thanks to DrKylestein for [Retro Proxy](https://github.com/DrKylstein/retro-proxy)

Also thanks to DrKylestein for Retro Proxy

On the server mgetty is configured for normal tty access, but also to support /AutoPPP/, which kicks off a pppd session and allows machines to connect via PPP like any dial-up internet provider. net.ipv4.forward is set to 1, and ipfwadm is set up to forward traffic. The server acts as a router, doing NAT for the dial-up client. Works great, though I do have browservice and retro-proxy servers running on a VM to handle https -> http and/or rendering for websites too modern for older browsers.