I absolutely love it, that the website is available over plaintext HTTP. (The maintainer(s) should consider honouring the Upgrade-Insecure-Requests header[1], so that modern browsers still get the HTTPS version.)
I've recently got my hands on a PowerBook G4 (2002), a quite interesting and still somewhat capable machine; however the OSX version it's stuck on (10.5.8) is having more and more problems reaching the TLS-secured web: TenFourFox is no longer maintained; Safari, curl, etc are all built against an ancient release of OpenSSL; etc. Even downloading TenFourFox is no longer possible, as system Safari can no longer load SourceForge, since SF requires a more modern TLS version than what the OS can understand.
Treating both plaintext HTTP and modern HTTPS as first-class citizens is the way to go for such projects & efforts, so hats off.
I've recently got my hands on a PowerBook G4 (2002), a quite interesting and still somewhat capable machine; however the OSX version it's stuck on (10.5.8) is having more and more problems reaching the TLS-secured web: TenFourFox is no longer maintained; Safari, curl, etc are all built against an ancient release of OpenSSL; etc. Even downloading TenFourFox is no longer possible, as system Safari can no longer load SourceForge, since SF requires a more modern TLS version than what the OS can understand.
Treating both plaintext HTTP and modern HTTPS as first-class citizens is the way to go for such projects & efforts, so hats off.
[1]: https://developer.mozilla.org/en-US/docs/web/http/headers/up...