31–40 of 65 posts
I saw "generate clutter..." in the title and thought "why would I want to generate clutter?" I know it's a minor point but I'd go "Remove clutter, ads and trackers from any article" for a stronger initial proposition.
> Generate pages free of ads, trackers and other clutter.
Put the major purpose in the first two words.
[edit - otoh it doesn't generate pages really but generates versions of existing pages]
I saw "generate clutter..." in the title and thought "why would I want to generate clutter?" I know it's a minor point but I'd go "Remove clutter, ads and trackers from any article" for a stronger initial proposition.
How'd you build it? I built something vaguely similar (but generating epub) using Mercury Parser.
What's the short of why manual refresh is needed?
Given that it now has queueing, server-side processing, and forever-links, clearly there's computing power and storage behind it. What will this cost to run? Would I not risk ads being shown when we start to use this frequently?
Why isn't this achieved client side?
CORS makes this difficult. For non-CORS enabled sites you would need to use a server-side proxy. But at that point why not do the filtering on the server to avoid transferring unnecessary data?
Which is essentially every website, as CORS underpins how the web works. Only if there is a public API for a given site, would it be possible to do otherwise. And then you'd usually still need URL to API mapping, plus any further API sign up stuff that may or may not be required for simple GETs.
Earlier quoted context omitted.
CORS makes this difficult. For non-CORS enabled sites you would need to use a server-side proxy. But at that point why not do the filtering on the server to avoid transferring unnecessary data?
> For non-CORS enabled sites Which is essentially every website, as CORS underpins how the web works. Only if there is a public API for a given site, would it be possible to do otherwise. And then you'd usually still need URL to API mapping, plus any further API sign up stuff that may or may not be required for simple GETs.
But backwards compatibility is nice I guess.
There are 2 caveats:
* There are broken HTML files that somehow still work with a browser.
* There are web pages that rely on javascript even for the main text.