Coupled with a little local content storage server, this could be as simple as a five-line userscript: AJAX the whole HTML document and any "relevant" embedded content (video, audio, images...) to the server with the current URI as storage key.

Retrieval and serving by local server (rewriting embeds on the fly), and offering as part of a distributed content store, is a later exercise, but a quick Streisand hack should be easy enough.

...that's all assuming you don't just POST current URI to a little app that just wget-spiders the whole thing. :)

On 28 June 2015 03:36:35 GMT+01:00, coderman <coderman@gmail.com> wrote:
On 6/27/15, Zenaan Harkness <zen@freedbms.net> wrote:
 ...
 So if I've read something I personally considered worthy of the price
 of my human attention, it exists somewhere on my local storage.

this is good practice; although it would be better to have two way
flow of collaboration - open design, etc. while pragmatism fills your
local cache, open content fills workflows, production.



 I call this pre-emptive since I always consistently download the
 content before ever reading, listening or viewing (/"consuming" -
 sounds like a base description, belittling we humans).

i remember Zooko musing about this years ago, needing
a browser
extension that kept a complete archive of all pages / content viewed
during a session. i don't recall him finding it, and i can't seem to
locate the blog post. i will try again later...


best regards,

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.