The idea behind it is maybe to have such a proxy server that recognizes your browser (by its UA), hence knowing W3 standards it accepts (e.g. HTML version). Then it forwards http request, introducing itself as an adequate known UA (possibly mobile, too, like WindowsMobile).
My idea is that there are two proxy components
- simple forward using predefined UA list
- forward and (XSL) transformation to the native html code
Since old Amiga browsers are simple, transforming should be pretty simple, too.
How I see it - by clicking "refresh" button, proxy would switch among all possibilities (user agents corresponding to one's browser, plus transformation mode). Then one could "switch" anytime between content been served, so that he/she picks up most fancy one, probably thoroughly better than original.
See my point?