Nathan goes back to the PPC days - he is absolutely right about IE.. sadly, in OS 9, we had to use IE and just to test out things, i used IE 5.1.7, sadly, I wish Netscape was revised so it can be a browser like Classila.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
- Status
Re web standards..why not go with W3C standards. The world wide web consortium. They set standards in the early 1990s.. based on the idea the web is for everyone...including the blind. A good web site should be accessible with minimum hardware and browser and readable by readers for the blind..ie read out loud the content. But the world wanted lots of bells and whistles ..so cluttered up web pages that must be a nightmare for blind people to listen to.
When I was learning to code in html5 you could test your page design on their web site.. this was coding without using a web making program...that add 'extras' with a click.
Their whole philosophy is ' Making the Web Accessible'.
Home
Accessibility resources free online from the international standards organization: W3C Web Accessibility Initiative (WAI).www.w3.org
..and just checked.. yep..still can test web pages for accessibility:
Evaluating Web Accessibility Overview
Accessibility resources free online from the international standards organization: W3C Web Accessibility Initiative (WAI).www.w3.org
+1 on this. Should be added to the 1st post as well.
[ Wiki Organization ]
Added a fifth category for specialty websites lacking message boards.
[ Website Additions ]
Added Based Cooking.
[ Wiki Formatting ]
Added addendums for sites that require SSL / HTTPS to access. (No SSL should be the default here as requiring it cuts out most 90's and millennium browsers that certain environments are restricted to.)
Added a fifth category for specialty websites lacking message boards.
[ Website Additions ]
Added Based Cooking.
[ Wiki Formatting ]
Added addendums for sites that require SSL / HTTPS to access. (No SSL should be the default here as requiring it cuts out most 90's and millennium browsers that certain environments are restricted to.)
Last edited:
So, here is a good question - is there a way to access macrumors through any browser under OS 9 ? Didn’t they gave a site back in 2000s ?
Dude, you missed nothing, except that I am toying with idea of making a web browser for OS 9.
The only way to access MR on OS9 is through proxies like WebRenderingProxy and Browservice. There are no TLS 1.2 browsers for OS 9 right now. I'd recommend Browservice.
Forget it, the idea of doing a web browser for OS 9 is not an easy task. If Cameron threw the towel because he can't keep up with the pace of web evolution, no one can do it. I'd recommend you to give up on it, it's a dead end.
Actually, I wanted to find a way to run Power MachTen + Crypto Ancienne to run a local proxy for OS 9 browsers. I have no clue on how to do it. Cameron explains on his blog, but it's not for the faint hearted. One needs a more simple explanation/walkthrough for how to do it.
Forget it, the idea of doing a web browser for OS 9 is not an easy task. If Cameron threw the towel because he can't keep up with the pace of web evolution, no one can do it. I'd recommend you to give up on it, it's a dead end.
Actually, I wanted to find a way to run Power MachTen + Crypto Ancienne to run a local proxy for OS 9 browsers. I have no clue on how to do it. Cameron explains on his blog, but it's not for the faint hearted. One needs a more simple explanation/walkthrough for how to do it.
This maybe stupid question, but how hard is it to add TLS 1.2 ? Is it a line of code or is it a complete overhaul of the browser ? Also, can my iPhone 7 be used as a proxy so, if I was outside with my PB G4 using OS 9, I could access the web that way ?
1. Extremely hard and requires a complete overhaul, yes. Also needs ancient software to compile for the intended target (ancient OS9/OSX operating systems). Not possible anymore.
2. Nope, your iPhone 7 cannot be used as a proxy even if it were jailbroken. If you expect to improve web rendering, there are no proxies using the Safari webkit rendering engine, all I know are using Chromium engine (Browservice and WRP). If you only want to bump it to TLS 1.2, you need to find a way to run a squid proxy or stunnel on it as a background service. And even if you do it, on public places like a Starbucks cofee, your phone would be vulnerable and be open to anyone on the same local network to access it.
I could try iSH for iOS and see if it can run a stunnel or squid service on background, but I doubt it. The iSH developer is not a great person to deal with either. I asked him one day if he could improve it to run a mysql server so I could run a small webserver for development there, but no way. a light web server can run on iSH, but without a database this is useless for me.
2. Nope, your iPhone 7 cannot be used as a proxy even if it were jailbroken. If you expect to improve web rendering, there are no proxies using the Safari webkit rendering engine, all I know are using Chromium engine (Browservice and WRP). If you only want to bump it to TLS 1.2, you need to find a way to run a squid proxy or stunnel on it as a background service. And even if you do it, on public places like a Starbucks cofee, your phone would be vulnerable and be open to anyone on the same local network to access it.
I could try iSH for iOS and see if it can run a stunnel or squid service on background, but I doubt it. The iSH developer is not a great person to deal with either. I asked him one day if he could improve it to run a mysql server so I could run a small webserver for development there, but no way. a light web server can run on iSH, but without a database this is useless for me.
Also needs ancient software to compile for the intended target (ancient OS9/OSX operating systems). Not possible anymore - are you referring to Xcode for OS X, and CodeWarrior for OS 9 ? I have these already.. the only real OS X versions worthwhile to do this with would be Tiger and Leopard. Well, no I wouldn’t access the public internet at Starbucks - I would use my own WiFi service to access the web through OS 9.
Well, I had just written a large and well thought out message, only for it to be lost due to some failure within the rich text editor draft-saving feature.
Note to self; never reload until at least copying post contents to clipboard...
It is a bad day...
Note to self; never reload until at least copying post contents to clipboard...
It is a bad day...
I did my best to make my own website compatible with older browsers, and it will in fact work back to Safari 6. But the one thing I absolutely wasn't willing to give up was Flexbox. It's really freaking useful for basically any semi-complex layout, and it's a crime that the web went on for so long without it.
Embedded media is good.
If you're a Mac enthusiast, it's presumably because you care about design on some level. The original Macintosh was created to improve upon the text-only UI of the Apple II. Early OS X was all about Aqua.
Perhaps more importantly, the early internet wasn't text-heavy due to limited processing power so much as limited bandwidth. It's difficult to load more than a few images on a dial-up connection, or even DSL. Today, even the slowest cable connections don't have that problem.
The thing slowing down old computers is Javascript, and to a lesser extent overly-complex CSS. (Did you know you can make Minesweeper purely out of CSS? It's kind of nuts.)
Disclaimer: I work at a web design studio. But I believe in the power of good website design!
If you're a Mac enthusiast, it's presumably because you care about design on some level. The original Macintosh was created to improve upon the text-only UI of the Apple II. Early OS X was all about Aqua.
Perhaps more importantly, the early internet wasn't text-heavy due to limited processing power so much as limited bandwidth. It's difficult to load more than a few images on a dial-up connection, or even DSL. Today, even the slowest cable connections don't have that problem.
The thing slowing down old computers is Javascript, and to a lesser extent overly-complex CSS. (Did you know you can make Minesweeper purely out of CSS? It's kind of nuts.)
Disclaimer: I work at a web design studio. But I believe in the power of good website design!
Last edited:
@Wowfunhappy I largely agree, but I have also seen relatively simple pages with either large images or many images (or even many large images) significantly slow down machines among the ranks of a 400 MHz G3, and even weaker G4s.
So in my opinion, they shouldn't be overdone (unless they're compressed, in which case have at it).
So in my opinion, they shouldn't be overdone (unless they're compressed, in which case have at it).
If I wrote a webpage under OS 9, using BBEDIT, would it work for all versions of Mac OS X ? I just got a book called OS 9 Bible which I want to learn everything about OS 9, as I still believe it’s a useful OS. The squid proxy is good for snow Leopard to allow LWK to access those websites which currently give an SSL error. But, because I now have PowerMacten for OS 9, and CodeWarrior. I am going to read when I have the time how to compile Classila using these, then attempt to inject (code maybe) ? Crypto Ancienne per Kaiser’s instructions for Classila - if successful, my compiled Classila code would be TSL 1.2 compliant. Whether the rendering of most of the web will be realized, that it yet to be seen.
so, also I plan to use my PB G4 titanium 1ghz(soon to be 1.2) for compiling a new Classila. I know it can be done..
Wowfunhappy,Embedded media is good.
If you're a Mac enthusiast, it's presumably because you care about design on some level. The original Macintosh was created to improve upon the text-only UI of the Apple II, and early OS X was all about Aqua.
Perhaps more importantly, the early internet wasn't text-heavy due to limited processing power so much as limited internet speeds. It's difficult to load more than a few images on a dial-up connection, or even on DSL. Even the slowest cable internet connections don't have that problem today.
The thing slowing down old computers is Javascript, and to a lesser extent overly-complex CSS. (Did you know you can make Minesweeper purely out of CSS? It's kind of nuts.)
Disclaimer: I work at a web design studio. But I do believe in the power of good website design.
for creating a webpage under OS 9, I would use BBEdit ?
Alright folks, it looks like option two (equal to or lesser than HTML4, CSS2, frugal JS, frugally embedded media - similar to early 2000's Web) has won out as the proposed standard for Web 1.1 sites, according to a majority 23 out of 32 people polled over almost a month's worth of time.
Personally, I have already started practicing advanced HTML and CSS for the last several weeks in the hopes of contributing to the already expanding selection of Web 1.1-compatible websites. For this purpose, I have found Khan Academy's course for writing HTML and CSS immensely helpful in gaining a better understanding of rudimentary website design (which is actually rather simple once you get the hang of it), which can be found here:
www.khanacademy.org
And with that knowledge, I have also found the following site useful as a sort of sandbox for designing and creating simple webpages in real time:
www.quackit.com
Using the above resources in tandem, once you have a collection of HTML files finished and linked together, they can then be made publicly available at no charge, courtesy of Macintosh Garden Hosting (albeit under the home.macintosh.garden/~<websitename> subdomain), which currently offers 100 MB of storage space by default:
If however you desire a custom domain, an independent domain name can be affordably procured from a registrar like Namecheap, which Macintosh Garden Hosting can then host the files of for a small one time fee (this is how sites like Cornica and System 7 Today operate, for example).
Otherwise, once your website has been published, post it here so we can add it to the directory (and in the process further our epic conquest of overthrowing the bloated and institutionalized modern Web with efficiently-designed Web 1.1-compliant websites!).
-
If you find yourself at a loss deciding what subject your site will revolve around, feel free to refer to the Website Wish List in the main Wiki for ideas (which anyone can add to).
And on that note, when we have a couple more websites added, we should probably come up with some type of footer badge to signify Web 1.1-compliance for easier identification ... as well as move this resource to somewhere else (like a Macintosh Garden page), so that old browsers / computers can actually access it.
In addition, I would also like to add that unless absolutely necessary, site security should probably be limited to TLS 1.0 and / or SSL 1.0 (if at all) to preserve a wide range of browser compatibility (this will be optional if purchasing a custom domain from a registrar, and not applicable when using the home.macintosh.garden parent domain), and in my opinion, use of simple JavaScript (meaning no AJAX) should probably be restricted as much as possible to maintain site performance on very old systems, unless some feature is to be implemented that requires its use to a very minimal extent.
Also, no ads, tracking, analytics, fingerprinting, or data mining servers allowed, because those aren't fun for anyone.
-
Now with that being said, let's take this opportunity to begin our epic conquest to overthrow the bloated and institutionalized modern Web with efficiently-designed Web 1.1-compliant websites!
Happy coding!
Personally, I have already started practicing advanced HTML and CSS for the last several weeks in the hopes of contributing to the already expanding selection of Web 1.1-compatible websites. For this purpose, I have found Khan Academy's course for writing HTML and CSS immensely helpful in gaining a better understanding of rudimentary website design (which is actually rather simple once you get the hang of it), which can be found here:
Intro to HTML/CSS: Making webpages | Computer programming | Khan Academy
Learn how to use HTML and CSS to make webpages. HTML is the markup language that you surround content with, to tell browsers about headings, lists, tables, etc. CSS is the stylesheet language that you style the page with, to tell browsers to change the color, font, layout, and more.
And with that knowledge, I have also found the following site useful as a sort of sandbox for designing and creating simple webpages in real time:
HTML Scratchpad Examples
Using the above resources in tandem, once you have a collection of HTML files finished and linked together, they can then be made publicly available at no charge, courtesy of Macintosh Garden Hosting (albeit under the home.macintosh.garden/~<websitename> subdomain), which currently offers 100 MB of storage space by default:
If however you desire a custom domain, an independent domain name can be affordably procured from a registrar like Namecheap, which Macintosh Garden Hosting can then host the files of for a small one time fee (this is how sites like Cornica and System 7 Today operate, for example).
Otherwise, once your website has been published, post it here so we can add it to the directory (and in the process further our epic conquest of overthrowing the bloated and institutionalized modern Web with efficiently-designed Web 1.1-compliant websites!).
-
If you find yourself at a loss deciding what subject your site will revolve around, feel free to refer to the Website Wish List in the main Wiki for ideas (which anyone can add to).
And on that note, when we have a couple more websites added, we should probably come up with some type of footer badge to signify Web 1.1-compliance for easier identification ... as well as move this resource to somewhere else (like a Macintosh Garden page), so that old browsers / computers can actually access it.
In addition, I would also like to add that unless absolutely necessary, site security should probably be limited to TLS 1.0 and / or SSL 1.0 (if at all) to preserve a wide range of browser compatibility (this will be optional if purchasing a custom domain from a registrar, and not applicable when using the home.macintosh.garden parent domain), and in my opinion, use of simple JavaScript (meaning no AJAX) should probably be restricted as much as possible to maintain site performance on very old systems, unless some feature is to be implemented that requires its use to a very minimal extent.
Also, no ads, tracking, analytics, fingerprinting, or data mining servers allowed, because those aren't fun for anyone.
-
Now with that being said, let's take this opportunity to begin our epic conquest to overthrow the bloated and institutionalized modern Web with efficiently-designed Web 1.1-compliant websites!
Happy coding!
Last edited:
I wanted to try and make a more well supported portfolio website. I'm not sure what to use to layout my page using CSS. I'm very use to using grids but that's not very well supported. Does anyone have any suggestions of what I can use to layout the page? I wanted to have some photos I have taken in two columns and then if the display screen is smaller I'd change that to one column using a media query (i'm not sure if media querys are supported by older browsers though).
I need to update my site. Its design is a little over a year old and, while good, I feel it could do for a refresh.Alright folks, it looks like option two (equal to or lesser than HTML4, CSS2, frugal JS, frugally embedded media - similar to early 2000's Web) has won out as the proposed standard for Web 1.1 sites, according to a majority 23 out of 32 people polled over almost a month's worth of time.
Personally, I have already started practicing advanced HTML and CSS for the last several weeks in the hopes of contributing to the already expanding selection of Web 1.1-compatible websites. For this purpose, I have found Khan Academy's course for writing HTML and CSS immensely helpful in gaining a better understanding of rudimentary website design (which is actually rather simple once you get the hang of it), which can be found here:
Intro to HTML/CSS: Making webpages | Computer programming | Khan Academy
Learn how to use HTML and CSS to make webpages. HTML is the markup language that you surround content with, to tell browsers about headings, lists, tables, etc. CSS is the stylesheet language that you style the page with, to tell browsers to change the color, font, layout, and more.
And with that knowledge, I have also found the following site useful as a sort of sandbox for designing and creating simple webpages in real time:
HTML Scratchpad Examples
Using the above resources in tandem, once you have a collection of HTML files finished and linked together, they can then be made publicly available at no charge, courtesy of Macintosh Garden Hosting (albeit under the home.macintosh.garden/~<websitename> subdomain), which currently offers 100 MB of storage space by default:
If however you desire a custom domain, an independent domain name can be affordably procured from a registrar like Namecheap, which Macintosh Garden Hosting can then host the files of for a small one time fee (this is how sites like Cornica and System 7 Today operate, for example).
Otherwise, once your website has been published, post it here so we can add it to the directory (and in the process further our epic conquest of overthrowing the bloated and institutionalized modern Web with efficiently-designed Web 1.1-compliant websites!).
-
If you find yourself at a loss deciding what subject your site will revolve around, feel free to refer to the Website Wish List in the main Wiki for ideas (which anyone can add to).
And on that note, when we have a couple more websites added, we should probably come up with some type of footer badge to signify Web 1.1-compliance for easier identification ... as well as move this resource to somewhere else (like a Macintosh Garden page), so that old browsers / computers can actually access it.
In addition, I would also like to add that unless absolutely necessary, site security should probably be limited to TLS 1.0 and / or SSL 1.0 (if at all) to preserve a wide range of browser compatibility (this will be optional if purchasing a custom domain from a registrar, and not applicable when using the home.macintosh.garden parent domain), and in my opinion, use of simple JavaScript (meaning no AJAX) should probably be restricted as much as possible to maintain site performance on very old systems, unless some feature is to be implemented that requires its use to a very minimal extent.
Also, no ads, tracking, analytics, fingerprinting, or data mining servers allowed, because those aren't fun for anyone.
-
Now with that being said, let's take this opportunity to begin our epic conquest to overthrow the bloated and institutionalized modern Web with efficiently-designed Web 1.1-compliant websites!
Happy coding!
- Added Personal Websites category.
- Added Life Without Megapixels to Personal Websites.
- Added chat room site to Website Wish List.
- Added Life Without Megapixels to Personal Websites.
- Added chat room site to Website Wish List.
Last edited:
How do we apply to get our sites added to the Personal Websites category?
Also, what sorta chat room site are you thinking of? IRC might be able to nicely fill that void depending on what you're looking for.
@RogerWilco6502 Anyone can edit the WikiPost, so as long as your website is compliant with the decided Web 1.1 specification (and contains nothing that your grandfather would strongly disapprove of), feel free to add it in.
I'm not sure; all I know is that I vaguely remember visiting a couple back in the day and remarking that they were interesting places to take part in. I also think that a dedicated website would be a much more accessible solution than an IRC client ... but that's also my opinion and hence, only a wish.
I'm not sure; all I know is that I vaguely remember visiting a couple back in the day and remarking that they were interesting places to take part in. I also think that a dedicated website would be a much more accessible solution than an IRC client ... but that's also my opinion and hence, only a wish.
Ok, thanks! I can definitely see a site being more accessible given IRC clients require a bit of config.@RogerWilco6502 Anyone can edit the WikiPost, so as long as your website is compliant with the decided Web 1.1 specification (and contains nothing that your grandfather would strongly disapprove of), feel free to add it in.
I'm not sure; all I know is that I vaguely remember visiting a couple back in the day and remarking that they were interesting places to take part in. I also think that a dedicated website would be a much more accessible solution than an IRC client ... but that's also my opinion and hence, only a wish.