Once I'm enrolled I can enable Javascript when the product makes use of it. :)
The main problem I see is that you can embed trackers in the link URLs.
(You probably want the proxy to be a stateless cache shared by many users, which prevents tracker stuff from persisting in whatever rendering engine it uses for the conversion)
We haven't really thought much about running this kind of thing as a proxy service, or what it would be like to implement it. Our tools are really intended for web articles, so they will fail on lots of other kinds of content you'll encounter in day-to-day browsing. If the intention is to avoid trackers, the proxy will have to handle everything, and not everything will be web articles. Browser extensions might be best here.
Thanks for the response!
The idea is to strip out all of the JavaScript before it even hits the client. People could then use it exclusively for news reading. I suspect it would reduce bandwidth and client side energy as well as block essentially all web trackers.
I ask because it looks like you’ve done most of the heavy lifting between this and your full-text RSS feed service.
Thanks!