RetroZilla | owlman.rf.gd
RetroZilla
To quote the GitHub page for this project; "RetroZilla is a fork of Gecko 1.8.1 for improved compatibility on the modern web", the term "improved compatibility" is a strong idea, as the browser itself seems to have trouble connecting to websites that use HTTPS, however, the GitBub page also says that it was made "with Windows 95 and Windows NT 4.0 in mind", but the thing is, HTTPS was created in 1994 (saying that, the protocol was only formally specified by RFC 2818 in May 2000), while Windows NT came out in 1993, and no points for guessing when Windows 95 came out.
Screenshots
Screenshot 1 (PNG, GIF)
Screenshot demonstrating that the browser test page can indeed work with RetroZilla.
Screenshot 2 (PNG, GIF)
One of the upsides of using the RetroZilla browser is that it knows how to handle the gopher protocol from the get-go. Here it is viewing the tilde.pink's gopherhole.
Screenshot 3 (PNG, GIF)
What's kind of annoying about using the RetroZilla browser is that, *for some reason*, it doesn't furry support the HTTPS protocol (as of version 2.1). *All* good web browser from, like, 2008 onwards would support this protocol fully, it's amazing how a browser released in 2017 did not support it, what's more is that the official website for RetroZilla, https://github.com/rn10950/RetroZilla, would *not* be supported, as it would get the same error.
Links
You can download RetroZilla from the following URL; https://github.com/rn10950/RetroZilla
You can download RetroZilla 2.1 from the following URLs;
owlman@protonmail.com
Last updated: 2019-11-11
Thank you to Bytemoth of cd5k.net for correctly pointing out that what I wrote, "*All* good web browser from, like, 1995 onwards would support this protocol fully", is indeed incorrect, Bytemoth writes "Old browsers support SSL2/3 encryption at either 40 or 128 bits. TLS 1.2, which is what most modern websites use, was released in 2008 and has 256-bit algorithms" - thank you for the correction.
