51 Matching Annotations
  1. Feb 2023
    1. But a good short story is always basically a memento mori.

      An interesting theory...

      An Occurrence at Owl Creek Bridge by Ambrose Bierce comes to mind as an excellent example.

    1. The pirate flag, which existed in many variations, is revealingin itself. It was normally taken to be an image of the devil, but often itcontained not only a skull or skeleton, but also an hourglass,signifying not a threat (“you are going to die”) so much as a sheerstatement of defiance (“we are going to die, it’s only a matter oftime”)—which crews making out such a flag on the horizon would

      likely have found, if anything, even more terrifying. Flying the Jolly Roger was a crew’s way of announcing they accepted they were on their way to hell.

      What was the origin of the idea of memento mori? Did this concept within piracy influence early masons who practiced memento mori?



  2. Dec 2022
  3. Aug 2022
    1. Annotator Requirements Annotation client should be able to: handle targets for both canonical document URLs and versioned document URLs associate annotation with their specific versioned document URL establish whether the document server supports the Memento protocol, or whether there is an appropriate third-party Memento server (such as the Wayback Machine) which does store previous versions of the document negotiate datetimes with the Memento server for retrieving the correct version of the document in the case of a third-party Memento server, request that the service make a snapshot of the document at the time of annotation
  4. Mar 2022
  5. Jan 2022
    1. 4. Robustifying a link when linking to a specific version

      If the main intent is to link to a specific state of an original resource, for example a snapshot of the original resource in a web archive or one of its version in a version control system, then Robust Link information is conveyed as follows:

      • href for the URI that provides the specific state i.e., the snapshot or resource version;
      • data-originalurl for the URI of the original resource;
      • data-versiondate for the datetime of the snapshot or resource version.


      <a href="http://en.wikipedia.org/w/index.php?title=Web_archiving&oldid=485347845"
         data-versiondate="2012-03-20">Robust Link to this specific version of the Wikipedia page</a>
    2. 3. Robustifying a link when linking to the original resource

      If the main intent is to link to an original resource but also allow future users of that link to see the state of the original resource around the time the link was put in place, then Robust Link information is conveyed as follows:

      • href for the URI of the original resource for which the snapshot was taken;
      • data-versionurl for the URI of the snapshot;
      • data-versiondate for the datetime of linking, of taking the snapshot.


      <a href="http://www.w3.org/"
         data-versiondate="2015-01-21">Robust Link to the W3C home page</a>
    3. The approach proposed here is to convey this information on a link by leveraging HTML5's attribute extensibility mechanism. It introduces the following data- attributes for the anchor (<a>) element:

      • data-originalurl for the URI of the original resource;
      • data-versionurl for the URI of the snapshot;
      • data-versiondate for the datetime of linking, of taking the snapshot.
    1. Any interaction with the card index is differently informative not simply because the query is different but also because the variety is recursively reproduced and dependent on the past.

      Somehow this sparked the realization:

      The tattoos on Leonard Shelby's body in the film Memento act in some way as a physical zettelkasten of information stored on skin rather than index cards. The information can be traversed in a number of ways for a short period of time by Leonard. He uses the information over time to solve a murder.

      Guy Pierce as Leonard Shelby featuring a number of text-based tattoos on his torso and arms



    1. Making a Memento

      To create an archived version of the page that could be played back properly, I used the Internet Archive’s “Save” feature by going to this URL in my web browser:


      …which created this snapshot:


      From here, we can use wget to look at what gets played back:

      $ wget --server-response http://web.archive.org/web/20150709104019/http://iipc.github.io/warc-specifications/primers/web-archive-formats/hello-world.txt


        HTTP/1.0 200 OK
        Server: Tengine/2.1.0
        Date: Thu, 09 Jul 2015 10:41:38 GMT
        Content-Type: text/plain;charset=utf-8
        Content-Length: 13
        Set-Cookie: wayback_server=19; Domain=archive.org; Path=/; Expires=Sat, 08-Aug-15 10:41:38 GMT;
        Memento-Datetime: Thu, 09 Jul 2015 10:40:19 GMT
        Link: <http://iipc.github.io/warc-specifications/primers/web-archive-formats/hello-world.txt>; rel="original", <http://web.archive.org/web/timemap/link/http://iipc.github.io/warc-specifications/primers/web-archive-formats/hello-world.txt>; rel="timemap"; type="application/link-format", <http://web.archive.org/web/http://iipc.github.io/warc-specifications/primers/web-archive-formats/hello-world.txt>; rel="timegate", <http://web.archive.org/web/20150709104019/http://iipc.github.io/warc-specifications/primers/web-archive-formats/hello-world.txt>; rel="first last memento"; datetime="Thu, 09 Jul 2015 10:40:19 GMT"
        X-Archive-Orig-x-cache-hits: 0
        X-Archive-Orig-x-served-by: cache-sjc3122-SJC
        X-Archive-Orig-cache-control: max-age=600
        X-Archive-Orig-content-type: text/plain; charset=utf-8
        X-Archive-Orig-server: GitHub.com
        X-Archive-Orig-age: 0
        X-Archive-Orig-x-timer: S1436438419.302921,VS0,VE141
        X-Archive-Orig-access-control-allow-origin: *
        X-Archive-Orig-last-modified: Wed, 08 Jul 2015 22:33:03 GMT
        X-Archive-Orig-expires: Thu, 09 Jul 2015 10:50:19 GMT
        X-Archive-Orig-accept-ranges: bytes
        X-Archive-Orig-vary: Accept-Encoding
        X-Archive-Orig-connection: close
        X-Archive-Orig-date: Thu, 09 Jul 2015 10:40:19 GMT
        X-Archive-Orig-via: 1.1 varnish
        X-Archive-Orig-content-length: 13
        X-Archive-Orig-x-cache: MISS
        X-Archive-Wayback-Perf: {"IndexLoad":359,"IndexQueryTotal":359,"RobotsFetchTotal":1,"RobotsRedis":1,"RobotsTotal":1,"Total":371,"WArcResource":10}
        X-Archive-Playback: 1
        X-Page-Cache: MISS
  6. Dec 2021
    1. Abstract: [...] [The HTTP Memento protocol] lacks support for the management of data updated at high frequencies or the interactions during resource modification and only provides inefficient means for managing resources with many revisions. To address these shortcomings, we propose three extensions to the HTTP Memento protocol: arbitrary resolution timestamps, resource creation support and range requests for TimeMaps. We provide a reference implementation of our proposals as open source software and quantitatively evaluate the extensions’ performance, showcasing superior results in terms of resource capacity, insertion correctness, latency and amount of transferred data.

    1. JCDL 2010 presentation about using Memento to reconstruct the state for web resources involved in annotation.
    1. Getting data from web archives using Memento

      Systems supporting the Memento protocol provide machine-readable information about web archive captures, even if other APIs are not available. In this notebook we'll look at the way the Memento protocol is supported across four web archive repositories – the UK Web Archive, the National Library of Australia, the National Library of New Zealand, and the Internet Archive. In particular we'll examine:

      • Timegates – request web page captures from (around) a particular date
      • Timemaps – request a list of web archive captures from a particular url
      • Mementos – use url modifiers to change the way an archived web page is presented
  7. Nov 2021
  8. Oct 2018
    1. The W3C Wiki and the W3C specifications are now accessible using the Memento “Time Travel for the Web” protocol.
    1. InterPlanetary Wayback (ipwb) facilitates permanence and collaboration in web archives by disseminating the contents of WARC files into the IPFS network. IPFS is a peer-to-peer content-addressable file system that inherently allows deduplication and facilitates opt-in replication. ipwb splits the header and payload of WARC response records before disseminating into IPFS to leverage the deduplication, builds a CDXJ index with references to the IPFS hashes returned, and combines the header and payload from IPFS at the time of replay.
    1. The HTTP-based Memento framework bridges the present and past Web. It facilitates obtaining representations of prior states of a given resource by introducing datetime negotiation and TimeMaps. Datetime negotiation is a variation on content negotiation that leverages the given resource's URI and a user agent's preferred datetime. TimeMaps are lists that enumerate URIs of resources that encapsulate prior states of the given resource. The framework also facilitates recognizing a resource that encapsulates a frozen prior state of another resource.