We need an iBrowse replacement for 68k!!!

[bbond007]

I
This upset a few classic users that couldn't use the site after the update. So, I wrote a small degrader proxy in PHP that parses the markup and degrades it into (far obsoleted) HTML that iBrowse (and AWeb) can cope with.

Compare this site in iBrowse versus this one: http://aoproxy.extropia.co.uk/

What you could do is set up a sub domain on a1k and we could look at installing a suitably modified version of the code on it to cope with whatever forum engine you ultimately go for.

Karlos, I use this on my A1200 all the time. Can the parser replace the bad grammer as well? J/K

I always wondered if you had a similar proxy for EAB?

Thanks!

[bbond007]

What would really be useful in a 68k browser is a Javascript whitelist feature such as NoScript provides for Firefox. An improved JS engine would be nice, but ultimately there's just too much JS bloat on modern websites; even modern systems get dragged down by it. A whitelist would at least help to contain the insanity; as is, I spend more time in iBrowse waiting for scripts to time out than I do actually looking at webpages.

Even if you get some sort of browser(for the classic amiga) that supports the latest CSS and whatnot, its still going to be kind of discouraging to watch it lock-up the machine for minutes on end while it does some inefficient javascript routine. This is the situation on the Raspberry Pi which I'm sure is faster than an 060.

HTML started as a good idea, but it evolved into this mess that only somewhat runs correctly on high-end x86 hardware.

The best browser on amiga is rdesktop

[bbond007]

I don't, but as it's already using vbulletin, I don't expect it to be a big task to adapt it. It's just text processing at the end of the day.

Yeah, so I can log in to EAB on my 1200 and see the lack of progress on the Indivision AGA MK2...