Out of curiosity, what have you adopted for your platform (inside the Heroku "dyno" container)?

It's using node.js. The server code is really quite small. TBH I haven't delved much into it. I was new to the platform when I started and my roommate set me up with it, using some code he'd written previously... all it does is blindly serve requested files via HTTP. The only modification I had to make to it was a few lines to get it to serve arbitrary requested files.

If I had my druthers, the thing would be running off of a real DOS computer using MTCP or something. That way I could also have an FTP server. But that is a big project that will have to wait for another day; I don't even have a static IP right now.

This website has good retro browser compatibility. A collection of random readme files both tech related and otherwise. Not sure if its what you are looking for but it might be worthy of being included in your list of links:

http://www.textfiles.com

gca wrote:

This website has good retro browser compatibility. A collection of random readme files both tech related and otherwise. Not sure if its what you are looking for but it might be worthy of being included in your list of links:

http://www.textfiles.com

I like it. I'll add it to the list; thanks!

Some more content has been added.

There is also now an FTP server for the website: ftp://casablanca25.mynetgear.com
We will see where that goes.

Just tried accessing your FTP server on my Fedora 7 box using Konqueror 3.5.9 and it works just fine. Thought you would like to know.

gca wrote:

Just tried accessing your FTP server on my Fedora 7 box using Konqueror 3.5.9 and it works just fine. Thought you would like to know.

Thank you for testing!

Update: added a hit counter. Because why not?

keenmaster486 wrote:

It's using node.js. The server code is really quite small. TBH I haven't delved much into it. I was new to the platform when I started and my roommate set me up with it, using some code he'd written previously... all it does is blindly serve requested files via HTTP. The only modification I had to make to it was a few lines to get it to serve arbitrary requested files.

I appreciate the irony of using such a bleeding-edge trendy hipster platform (node.js) to serve vintage hardware pages. Good job! 😁

Although you shouldn't put the "W3C HTML 3.2 Validated" badge on a page that is not valid HTML 3.2 😜

That said, HTML 3.2 is a good compromise between backwards compatibility and functionality, I think. HTML 2.0 is missing a lot, and HTML 4.01 support doesn't appear until *shudder* IE6.

I wrote the low-fi version of VogonsDrivers to HTML 2.0, it's spartan to say the least hahaha

SquallStrife wrote:

I appreciate the irony of using such a bleeding-edge trendy hipster platform (node.js) to serve vintage hardware pages. Good job!

Thanks! Yeah, it's pretty ironic. Honestly, we will see whether I stick with node.js.

SquallStrife wrote:

Although you shouldn't put the "W3C HTML 3.2 Validated" badge on a page that is not valid HTML 3.2

Yes, you are correct, of course - I put that badge on there back when it WAS valid HTML 3.2, but not any more and I don't know whether I am actually interested in making it that way. Maybe practical browser support is more important. I may remove the badge.

keenmaster486 wrote:

Yes, you are correct, of course - I put that badge on there back when it WAS valid HTML 3.2, but not any more and I don't know whether I am actually interested in making it that way. Maybe practical browser support is more important. I may remove the badge.

Maybe instead get some of those "Looks best in Netscape / IE" badges! 😜

E.g.

Maybe I should make my own badge, which says "A computer is required in order to view this website properly" or "downgrade your browser for best performance".