agent_js03
Well-known member
Hi everyone,
the reason I am posting this is because I have seen multiple people express interest in using email/web with older macs, i.e. system 7.
I have been working on a project called LegacyWeb that is intended to turn a raspberry pi into a wireless bridge combined with a kind of middle-man that allows you to use email, file sharing and various web services from an older computer. So it assumes you have your old computer plugged into the ethernet side of the rpi, and the wireless connection is the WAN.
The web side of this is still a work in progress. As of yet I have only implemented a stripped down version of google maps and started on one for wikipedia, which is currently really ugly and only does text, no pictures (I intend to change that soon, like in the next couple of weeks or so).
I guess the reason I am posting now instead of when it is more "mature" is because:
1. A lot of people are interested in using their old web clients with modern email. LegacyWeb includes an stunnel setup that wraps the pop3 and smtp connection in SSL, as well as a postfix setup that will do your SMTP authentication for you in case your client does not support it. So yes, you can use your really ancient version of outlook/eudora that does not support SMTP auth.
2. I would like perhaps some suggestions for different kinds of sites to add as web services for legacyweb. I intend to add weather, news and youtube (basically this will be a web interface for starting the video, and send it to vlc, and the video out of the raspberry pi would have to connect to an apple video system in order to view the youtube video).
3. I would like to see if anyone else might want to contribute.
The basic secret behind doing web dev for vintage clients is:
1. For alignment, tables are your friend. Don't use divs.
2. No SSL. If you need SSL, tunnel it.
3. No Javascript. Or very little. Make sure it actually works with your old browser first.
4. Do everything you on the server side (in php). For user input, form submission is your best friend.
5. No new media. Old browsers will choke on pretty much any images other than jpg and gif, for example. What I am doing is either downloading the image from the site, converting it if necessary and then storing it in a ram disk in /var/www/html/images-tmp (I don't want to do it on actual storage, since I don't want to wear out the disk).
I have done my testing in Netscape Navigator 4.04.
Project site:
https://github.com/justinschw/legacyweb
the reason I am posting this is because I have seen multiple people express interest in using email/web with older macs, i.e. system 7.
I have been working on a project called LegacyWeb that is intended to turn a raspberry pi into a wireless bridge combined with a kind of middle-man that allows you to use email, file sharing and various web services from an older computer. So it assumes you have your old computer plugged into the ethernet side of the rpi, and the wireless connection is the WAN.
The web side of this is still a work in progress. As of yet I have only implemented a stripped down version of google maps and started on one for wikipedia, which is currently really ugly and only does text, no pictures (I intend to change that soon, like in the next couple of weeks or so).
I guess the reason I am posting now instead of when it is more "mature" is because:
1. A lot of people are interested in using their old web clients with modern email. LegacyWeb includes an stunnel setup that wraps the pop3 and smtp connection in SSL, as well as a postfix setup that will do your SMTP authentication for you in case your client does not support it. So yes, you can use your really ancient version of outlook/eudora that does not support SMTP auth.
2. I would like perhaps some suggestions for different kinds of sites to add as web services for legacyweb. I intend to add weather, news and youtube (basically this will be a web interface for starting the video, and send it to vlc, and the video out of the raspberry pi would have to connect to an apple video system in order to view the youtube video).
3. I would like to see if anyone else might want to contribute.
The basic secret behind doing web dev for vintage clients is:
1. For alignment, tables are your friend. Don't use divs.
2. No SSL. If you need SSL, tunnel it.
3. No Javascript. Or very little. Make sure it actually works with your old browser first.
4. Do everything you on the server side (in php). For user input, form submission is your best friend.
5. No new media. Old browsers will choke on pretty much any images other than jpg and gif, for example. What I am doing is either downloading the image from the site, converting it if necessary and then storing it in a ram disk in /var/www/html/images-tmp (I don't want to do it on actual storage, since I don't want to wear out the disk).
I have done my testing in Netscape Navigator 4.04.
Project site:
https://github.com/justinschw/legacyweb