4 ms·
> just block anything that is not actual content At this point the reverse approach (whitelist) becomes easier. Just pluck out the content, ignore the rest, an
by megous 8y ago
> just block anything that is not actual content
At this point the reverse approach (whitelist) becomes easier. Just pluck out the content, ignore the rest, and write your own simple UI. Most websites can be modeled quite easily as category->article(->comment) with some additional data.
Writing UI for that is quite trivial.
It can be done in browser via extensions/userscripts (without a database), or you can fetch the data into a database and view it via an electron app, or cli tools, or whatever.
- dao- 8y ago> At this point the reverse approach (whitelist) becomes easier. Just pluck out the content, ignore the rest, and write your own simple UI. This basically exists already. It's called Reader View in Firefox.
- gcb0 8y agowhich doesn't even work with github readme.md
- est31 8y agoAnd outline.com
- toomuchtodo 8y agoOr Pocket.
- andrepd 8y agoIf I understand correctly, ublock origin in dynamic filtering mode does this.
- darkpuma 8y agoMore aggressive whitelisting is warranted in my opinion. I recommend using uMatrix to block all javascript by default, including first party. Built your whitelist over time by enabling only that which is necessary to read the content you're after, which more often than not is nothing. Contrary to popular expectation including my own expectation, javascript is totally unnecessary for the majority of sites I visit. Of course this is only feasible for technically competent users. Regular users are forced to rely on lesser blockers with simplified UX. Such is the unfortunate nature of techno-inequality. Rectifying this would be a worthwhile pursuit.