This assumption might require substantially reworking the hyperlink model of the internet, so that external references to content delivered by third-parties is sharply distinguished from internal references to other pages within the same work.
This "offline archive format" has numerous benefits: (A) Cognitive benefits of a limited/standard UI for information (e.g. "read on a black-and-white ereader device"), (B) Accessibility: standardizing on text would make life easier for people using screen readers, (C) Performance (since accessing everything on localhost), (D) async access (reaching the "edge" of the subgraph of the internet you have pre-downloaded on your localnet could be recorded and queued up for async retrieval by "opportunistic means", e.g., next time you connect to free wifi somewhere you retrieve the content and resolve those queued "HTTP promises", (E) cognitive benefits of staying on task when doing research (read the actual paper you wanted to read, instead of getting lost reading the references, and the references's references).
I'm not sure what "standard" for offline media (A) would should target... Do we allow video or not? On the one hand video has great usefulness as communication medium on the other it's very passive medium, often associated with entertainment rather than information. Hard choice if you ask me.
I'm sure such "pre-fetched HTTP" exists already of some sort, no? Or is it just not that useful if you only have "one hop" in the graph? How hard would it be to crawl/scrape 2 hops? 3 hops? I think we could have pretty good offline internet experience with a few hops. For me personally, I think async interactions with the internet limited to 3 hops would improve my focus—I'm thinking of hckrnews crawled + 3 hops of web content linked, a clone of any github repo encountered (if <10MB), and maybe doi links resolved to actual paper from sci-hub. Having access to this would be 80%+ of the daily "internet value" delivered for me, and more importantly allow me to cutoff from the useless information like news and youtube entertainment.
update: found WARC https://en.wikipedia.org/wiki/Web_ARChive http://archive-access.sourceforge.net/warc/warc_file_format-...
How many links from any given page are ever taken? And is it worth network capacity and storage to cache any given one?
https://old.reddit.com/r/dredmorbius/comments/6bgowu/what_if...
Plan 9 OS and the 9P protocol
I'm carving out a subsection for this, as the concept appears to contain a number of the elements (though not all of them) mentioned above. See Wikpedia's 9P (protocol) entry for more:
In particular, 9P supports Plan 9 applications through file servers:
acme: a text editor/development environment
rio: the Plan 9 windowing system
plumber: interprocess communication
ftpfs: an FTP client which presents the files and directories on a remote FTP server in the local namespace
wikifs: a wiki editing tool which presents a remote wiki as files in the local namespace
webfs: a file server that retrieves data from URLs and presents the contents and details of responses as files in the local namespace
https://old.reddit.com/r/dredmorbius/comments/6bgowu/what_if...
I wish it was possible to use a html meta tag to declare to the user-agent that it should show the content in reader view.
Then sites that only want to provide text and images and no ads etc could be implemented without any CSS at all and minimal amounts of markup and still be nice and readable on all devices thanks to user-agent reader view taking care of the presentation.
And I don’t see any real benefit in changing the defaults either. Most sites want to provide custom CSS. The point of reader view is to make simple articles consisting of text and images comfortable to read on your specific device. Device/resolution specific defaults would be at least as painful, and probably more painful, to override for every site that wants to use custom CSS.
Whereas an explicit meta tag telling the user-agent to use reader view is entirely feasible. Such a meta tag does not interfere with existing pages, requires nothing extra from sites that don’t want it, and would still fall back to something that works for all end-users whose user-agents don’t implement it (because browsers ignore meta tags they don’t understand so those browsers would render the page in the exact same way they would any unstyled page). And on top of that this theoretical meta tag would be really easy for browser vendors to implement — they parse the HTML, see the meta tag and trigger the reader view mode that they have already implemented.
Couldn't an HTTP proxy work here? Something you run on localhost that fetches web pages, stripping them of trackers, adverts, and other undesirable stuff? Perhaps with enough development, it could even selectively strip CSS and JavaScript -- eg. it would be really nice if websites stopped shipping scrollbar hijacking / custom scrollbar code.
What would that constraint look like? Is animation and interaction prohibited there, for example?
The lesson from the modern web being, if you give web developers a toolbox, they'll figure out how to build a surveillance system.
And for decades we've been creating more powerful tools (Flash/ActionScript, ActiveX, JavaScript, Wasm, etc).
The answer would seem to be that we should be far more careful what tools we allow to be used.
(Note: Not saying restrict all the web this way, but if one wanted to build parent article's wikipedia-esque info web)
If we allow all those, it's just the modern web again.
I think it's generally useful to look at email here, where only a small subset of html—primarily photos + text—are reliably supported across clients.
No third party connections allowed. As for the originating server, they already know you requested the page, no?
Alternatively/in addition, the user agent can treat embedded assets like textbooks do, and present them all as numbered, boxed, and captioned figures.
I never understood why people have a problem with normal contrast. Low contrast is hard to read.
The vast teeming hordes of Kardashian fans and youtube addicts would not. They like where we are now.
A lightweight HTTP/TLS subset that severely limits client-side execution expectations would seem to accomplish the same goals.
While repurposing all the amazing tech we've built since the 1990s.
Essentially, "just pass me the bare minimum of response to make Firefox Reader View work."
... but then we wouldn't be able to serve high-value targeted ads, would we?